feat(monitoring): CrossSessionCoordinator — light advisory cross-session signal#500
Open
JKHeadley wants to merge 1 commit into
Open
feat(monitoring): CrossSessionCoordinator — light advisory cross-session signal#500JKHeadley wants to merge 1 commit into
JKHeadley wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…ion signal Concurrent Claude Code sessions on one agent home share `.instar/` state but are blind to each other. The damaging incident (2026-05-28): one session built a fix while another flipped a feature flag off + mass-withdrew 19 commitments — neither knew the other was acting. Justin approved a LIGHT fix (topic 15579): a visible "I'm about to do X" signal, no hard locks; "learn to collaborate slowly." CrossSessionCoordinator: a shared append-only scratchpad of recent high-impact structural actions + voluntary intents. Any structural action surfaces other recent entries by a different/unknown session as an advisory `coordinationWarning`. It never blocks and never mutates target state — purely advisory. - Routes: POST /coordination/intent, GET /coordination/recent - Backstop auto-record: sensitive PATCH /config flips + commitment withdrawals, attaching coordinationWarning to the action's own HTTP response - Default-ON housekeeping, near-silent (no Telegram); audit at logs/cross-session-events.jsonl - Wired in AgentServer (always alive → GET 200 not 503) + CapabilityIndex entry - Migration parity: ConfigDefaults default + migrateClaudeMd awareness section + generateClaudeMd template - Docs: CrossSessionCoordinator + /coordination routes in the docs site (docs-coverage) - Tests: unit (16) + integration (8) + e2e lifecycle (6) + migration parity (5) Spec: docs/specs/cross-session-coordination.md (converged + approved, topic 15579) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
JKHeadley
force-pushed
the
echo/cross-session-intent-beacon
branch
from
5a8b25f to
f65b77f
Compare
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.
What & why
Concurrent Claude Code sessions on one agent home share
.instar/state but are blind to each other. The damaging incident (2026-05-28, topic 15579): one session built a fix while another "hit the safety brake" — flipped a feature flag off and mass-withdrew 19 commitments. Both reached a correct local diagnosis; neither knew the other was acting. Net: bug fixed, engine left off, test bed wiped.Justin approved a LIGHT fix (chosen from a light/medium/heavy menu): a visible "I'm about to do X" signal, no hard locks — "learn to collaborate slowly and smoothly."
The fix
CrossSessionCoordinator— a shared, append-only scratchpad of recent high-impact structural actions + voluntary intents. Any structural action surfaces other recent entries by a different/unknown session as an advisorycoordinationWarning. It never blocks and never mutates target state — purely advisory.POST /coordination/intent,GET /coordination/recentPATCH /configflips +POST /commitments/:id/withdrawrecord themselves and attachcoordinationWarningto their own responseAgentServer(always alive → GET 200 not 503) +CapabilityIndexentrylogs/cross-session-events.jsonlX-Instar-Session), never the agent id (which all sessions share and would wrongly suppress the warning)Design decisions (see convergence report)
CommitmentTrackerevent) — avoids double-count; the route is the single agent-facing path and gives the inline warning for free.kind+target+valuecollapsed two distinct intents into one and suppressed the warning; caught during implementation review and fixed.Migration parity
Config default in
ConfigDefaults.SHARED_DEFAULTS(propagates viaapplyDefaults),migrateClaudeMdawareness section +generateClaudeMdtemplate. All unit-tested.Tests (all three tiers + parity)
Out of scope (deliberate)
active:trueliveness ghost — a separate staleness bug, candidate next step.Spec:
docs/specs/cross-session-coordination.md(converged + approved) · ELI16:docs/specs/cross-session-coordination.eli16.md· side-effects:upgrades/side-effects/cross-session-coordination.md🤖 Generated with Claude Code