afk

Posture for sessions where the user has handed work off and won't be available to course-correct in real time. Mutates session behavior until explicitly dropped. Common uses: overnight runs, discovery/optimization sweeps, audits, spec-driven implementation on low-risk repos, greenfield work.

Off-signal

Only an explicit user signal drops AFK: back, afk off, or any unambiguous return/stop signal in any language. Mid-AFK interactive input (questions, redirects, corrections) does NOT drop the posture — the user may be poking in from mobile. Answer briefly, stay in AFK. A new session starts fresh; nothing persists.

Preamble — first response after /afk

Open with [afk mode engaged] so activation is visible, then two steps, then wait. Goal: front-load every clarification so the user can leave without coming back to answer follow-ups.

Step 1 — Subagent / token budget (one question, three options). Ask the user to pick one:

• Single-agent — Claude alone. Simpler, context compounds. Most token-conservative.
• Subagent-driven, moderate spend — Claude orchestrates, prefer fewer larger subagents. Reduces context bloat without multiplying tokens hard.
• Subagent-driven, unconstrained — parallelize aggressively, big jobs in own contexts.

Bake token concern into this question — don't ask separately.