From f82c042a5645770271958d9107605eddc02d00b5 Mon Sep 17 00:00:00 2001 From: avivsinai Date: Tue, 21 Jul 2026 21:26:26 +0300 Subject: [PATCH] docs(coop): correct amq-keepalive reboot vs sleep mechanism MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The #263 wording (inherited from #244) conflated two distinct mechanisms: it credited the user LaunchAgent with reattaching wake after reboot. Per the companion README's Boundaries, the tool does not resurrect terminal sessions — the LaunchAgent supervises registered wakes through sleep, while reboot survival comes from the SessionStart hooks reattaching the recreated session (which registers its current target). Split the claim accordingly. Co-Authored-By: Claude Fable 5 --- COOP.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/COOP.md b/COOP.md index 6a0b428d..c78075d0 100644 --- a/COOP.md +++ b/COOP.md @@ -357,10 +357,11 @@ local user who owns the mailbox. If you prefer a supervisor that follows explicitly registered terminal sessions instead of fixed plists, [amq-keepalive](https://github.com/ohade/amq-keepalive) is a standalone companion tool that implements this recipe for macOS: it keeps a -registry of attached terminal targets (Ghostty, cmux), reattaches `wake` after -reboot or sleep through a user LaunchAgent, and can install SessionStart -reattach hooks for Claude Code and Codex. It follows the same daemon-free -contract and talks to AMQ only through the public `amq` CLI. +registry of attached terminal targets (Ghostty, cmux), keeps registered wakes +supervised through sleep with a user LaunchAgent, and can install SessionStart +hooks for Claude Code and Codex to reattach recreated sessions after reboot. It +follows the same daemon-free contract and talks to AMQ only through the public +`amq` CLI. **Options:** - `--inject-mode auto|raw|paste|none` - Injection strategy; `none` enforces zero terminal input