1 files changed, 36 insertions, 5 deletions
diff --git a/claude-templates/.ai/workflows/suspend.org b/claude-templates/.ai/workflows/suspend.org
index 3691f60..166f9c9 100644
--- a/claude-templates/.ai/workflows/suspend.org
+++ b/claude-templates/.ai/workflows/suspend.org
@@ -23,8 +23,10 @@ straight:
   Refreshes the anchor in place, prompts Craig to type =/clear=, and a hook
   resumes the *same* logical session in a fresh context. Craig is still here.
 - *suspend* (this workflow) — *leave.* Captures richly into the anchor, leaves
-  the file in place, and Craig walks away. The next session is a cold startup
-  that detects the present anchor and resumes from it.
+  the file in place, detaches the tmux client so the session parks in the
+  re-attachable set, and Craig walks away. The next session is a cold startup
+  that detects the present anchor and resumes from it — or Craig re-attaches the
+  still-live session directly.
 - =wrap-it-up= ([[file:wrap-it-up.org][wrap-it-up.org]]) — *end.* Writes the
   Summary, archives the anchor into =.ai/sessions/=, commits + pushes, and runs
   the phrase-dependent teardown.
@@ -91,7 +93,32 @@ when the Summary body is from an earlier thread.
    that set — but the default shared behavior is to leave the tree alone.)
 4. *Leave =.ai/session-context.org= in place.* Do not archive it.
 5. *Brief handoff* — one or two lines: what was captured, where the resume
-   pointer is, the most-active thread. End and let Craig go.
+   pointer is, the most-active thread. This is the last thing Craig sees before
+   the view detaches (Step 6), so deliver it complete.
+6. *Detach the tmux client.* As the final action, detach the client viewing the
+   =aiv-<project>= session so it drops out of Craig's active view while staying
+   alive in the background. This is a DETACH, not a teardown: the session and the
+   agent process keep running, nothing is killed, no context is lost.
+
+   #+begin_src bash
+   sess=$(tmux display-message -p '#S' 2>/dev/null)
+   [ -n "$sess" ] && tmux detach-client -s "$sess"
+   #+end_src
+
+   Run it as the very last tool call, after the handoff text has rendered — tmux
+   preserves the pane, so Craig sees the full handoff when he re-attaches. Unlike
+   wrap-up's teardown (which must defer to a =Stop= hook because it kills the
+   session the agent runs in, which would cut off the valediction), detach runs
+   inline: it disconnects the view but leaves the agent's session alive, so
+   nothing is cut off. Degrade gracefully — if not inside tmux (=$TMUX= unset, no
+   session), skip silently and the session simply stays attached.
+
+   Why detach on every suspend: Craig cycles his live agent sessions in Emacs
+   with alt-space, and rotates through everything — including re-attaching
+   detached ai-term sessions — with shift+alt+space. A suspended session left
+   attached clutters the active rotation; detaching parks it in the
+   re-attachable set, which is what makes suspend-and-walk-away work. Re-attach
+   is one keystroke (shift+alt+space) or =tmux attach -t aiv-<project>=.
 
 * What suspend does NOT do
 
@@ -103,8 +130,12 @@ does beyond capture:
 - No KB / memory promotion sweep.
 - No Linear / board reconciliation.
 - No session-record archive (the file stays live).
-- No teardown (the ai-term buffer + tmux session stay up). It drops no
-  =Stop=-hook teardown sentinel, so the wrap-teardown hook stays dormant.
+- No teardown. Suspend DETACHES the tmux client (Step 6) but never kills the
+  session: the =aiv-<project>= session and the agent process stay alive in the
+  background, only the view disconnects. It drops no =Stop=-hook teardown
+  sentinel, so the wrap-teardown hook stays dormant. Teardown — killing the
+  session — is wrap-it-up's job, not suspend's; detach is the lighter move that
+  parks a still-live session.
 - No blind commit of working files (step 3).
 - No valediction. A suspend is a pause, not a goodbye.