docs(coord): cap mail replies at one line, printed by the hook that forces the turn - #439
Merged
Merged
Conversation
…orces the turn The drain hook BLOCKS the Stop, so every delivery re-invokes the session and bills a turn with the entire conversation context re-sent -- the same charge whether the reply is one word or six paragraphs. Measured 2026-08-18: a paused session with nothing to do produced about a dozen consecutive turns of multi-paragraph peer-traffic digests, none requested, while the owner was watching pool burn. The rule is "<who mailed you>: <minimal reply>" on one line, and mail arriving is not a reason to produce output. Peers correcting each other is the channel working, not news; surface a message only when it needs the OWNER's decision. Printed in the hook footer rather than left to docs/SESSION-MAIL.md alone. A peer seat established the same day, on announce-before-fan-out, that a norm with no observable consequence for skipping it gets skipped -- and a doc nobody re-reads does not reach the moment the reply is composed. The doc carries the record and the reasoning; the footer carries the rule to where it applies. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
wshallwshall
enabled auto-merge (squash)
August 19, 2026 01:42
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.
The drain hook BLOCKS the Stop, so every delivery re-invokes the session and bills a turn with the entire conversation context re-sent -- the same charge whether the reply is one word or six paragraphs.
Measured 2026-08-18: a paused session with nothing to do produced about a dozen consecutive turns of multi-paragraph peer-traffic digests, none requested, while the owner was watching pool burn.
The rule
<who mailed you>: <minimal reply>, on one line. Mail arriving is not a reason to produce output. Peers correcting each other is the channel working, not news -- surface a message only when it needs the OWNER's decision, and then say only that.Why the footer and not just the doc
A peer seat established the same day, on announce-before-fan-out, that a norm with no observable consequence for skipping it gets skipped. A doc nobody re-reads does not reach the moment the reply is composed. The doc carries the record and the reasoning; the footer carries the rule to where it applies.
Note for other seats
Each worktree runs its OWN copy of
scripts/hooks/mail-drain.ps1and they already differ. Landing this on main does not change any running session until that worktree pulls.Authorised by the owner as a one-time push and merge.
🤖 Generated with Claude Code