docs(coop): link amq-keepalive companion in supervisor recipes - #244
Closed
ohade wants to merge 1 commit into
Closed
docs(coop): link amq-keepalive companion in supervisor recipes#244ohade wants to merge 1 commit into
ohade wants to merge 1 commit into
Conversation
Contributor
Author
|
Closing this in favor of the in-tree contribution (#245). Consolidating on a single option rather than asking you to pick between two. |
avivsinai
added a commit
that referenced
this pull request
Jul 21, 2026
Recovers the docs link from Ohad's #244 (which he closed) and the outcome of the #245 review: keep `amq-keepalive` external, and link it from AMQ's supervisor-recipes section. Adds a short pointer in COOP.md to [ohade/amq-keepalive](https://github.com/ohade/amq-keepalive) — a standalone macOS companion that supervises target-aware `amq wake` for explicitly registered terminal sessions (Ghostty, cmux) via a user LaunchAgent, with SessionStart reattach hooks. It stays external, keeps AMQ daemon-free/transport-only, and talks to AMQ solely through the public CLI. Text is Ohad's own wording from #244; verified the target repo is public and non-empty. Co-authored with Ohad (credited in the commit). 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Ohad Edelstein <ohade@users.noreply.github.com> Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
avivsinai
added a commit
that referenced
this pull request
Jul 21, 2026
Follow-up accuracy fix to #263. Codex caught that the wording (inherited verbatim from Ohad's #244) conflated two distinct mechanisms — it credited the user LaunchAgent with reattaching wake after reboot. Verified against the companion README's Boundaries section: - "The tool does not launch or resurrect terminal sessions." - "Reboot survival comes from reattaching on session start, not from assuming a terminal id survives … restart. The recreated session registers its current target." So: the LaunchAgent supervises registered wakes through sleep; the SessionStart hooks handle reboot reattach. Split the claim accordingly. Caught by codex; verified live against ohade/amq-keepalive README. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Docs only. I added a short pointer in the Supervisor recipes section to amq-keepalive, a standalone companion I built for the macOS side of this recipe. It keeps
wakeattached to explicitly registered terminal targets (Ghostty and cmux adapters), reattaches after reboot or sleep via a user LaunchAgent, and can install SessionStart reattach hooks for Claude Code and Codex.It sticks to the daemon-free contract this section describes, meaning it never parses AMQ mailbox, lock, or presence state and only talks to AMQ through the public CLI (target-aware
amq wake,amq env --json).If you'd rather keep external tool links out of the docs, feel free to close, I'll keep it as a personal tool.