AFK changes how often GDP needs you, not who owns authority. GDP Desktop can continue eligible local work inside the permission envelope you selected, while target, policy, risk, and evidence checks remain active.
Choose the permission envelope before you leave
GDP separates a request from permission. Active keeps you directly involved; AFK can continue eligible work inside a previously selected envelope; Custom narrows repository or workflow rules; Run Everything can run eligible queued work and Suggested Checks under the enabled local profile and safety rules.
AFK is delegated authority, not unlimited access. The hosted gateway or model does not become an unrestricted shell.
Let local policy make bounded decisions
The exact repository and task target still matter.
Command validation, working-directory confinement, risk policy, and timeouts still apply.
Foreground or focus-stealing UI checks remain explicit local work instead of silent AFK Auto-Run.
Uncertain mutations must be reconciled rather than blindly replayed.
Return to evidence, not a success message
Inspect the latest repository and task state when you return.
Read the most recent relevant check runs and patch/apply evidence.
Separate old failures from newer successful evidence.
Continue only from the next step that is not already proven.
A model saying “done” is not proof. GDP-owned repository state, local command output, exit codes, and recorded check runs remain the basis for completion claims.
