@@ -6,6 +6,15 @@ CrewCoder is a first-class CrewCode chat and Crew provider implemented by
66` --mode ` , and translates newline-delimited JSON-RPC 2.0 onto the shared
77` AgentBridge ` event stream. CrewCoder remains the ACP agent.
88
9+ CrewCode consumes optional ` _meta["crewcoder/progress"] ` thought snapshots by
10+ turn, item id, and kind. Updates replace that item's Thinking log text, including
11+ completed corrections and empty results, instead of appending the portable fallback
12+ again. Commentary snapshots also identify the matching portable dialogue echo;
13+ CrewCode consumes that echo once in Thinking rather than opening a reply for each
14+ token. Snapshot updates do not close an active dialogue bubble, so interleaved
15+ progress cannot fragment replies. Older ACP thought chunks still stream as text deltas. This keeps the existing
16+ CrewCode Thinking log presentation without changing CrewCoder's own thinking UI.
17+
918CrewCoder-specific usage metadata, permission semantics, reasoning,
1019and tool-call ordering must not change Hermes behavior.
1120
@@ -98,6 +107,46 @@ plan is a normal composer message; CrewCoder treats that as a new
98107
99108## ACP lifecycle
100109
110+ The shared desktop/Brain Stop path requests cancellation but never waits for its
111+ acknowledgement before runtime teardown. Windows kills target the exact owned
112+ runtime PID and its descendants, including npm launcher children. Stop keeps the
113+ saved native session id so the next user message follows normal resume; it never
114+ replays the cancelled prompt automatically. Unix and SSH keep their existing
115+ process/channel termination paths.
116+
117+ Switching chats or unmounting the visible pane does not cancel a submitted prompt,
118+ including while its bridge is still starting. The send retains its original chat,
119+ provider, and checkout. Explicit Stop, same-session provider/checkout changes, and
120+ session removal/reset retain cancellation. If removal wins a startup race, the
121+ registry stops the exact late bridge and refuses prompt dispatch.
122+ The Stop button explicitly requests ` dropBridge(..., { stopRunning: true }) ` ;
123+ it must bypass the deferral used for launch-setting changes, affect only the
124+ selected session/provider, and retire a late startup before dispatch.
125+ Stop also clears the pane's local pending-send indicator immediately, without
126+ waiting for startup/resume RPC settlement. Late completion of a stopped send
127+ must not clear a newer send's indicator or make another chat look busy.
128+
129+ Launch-setting changes discovered during startup or an active turn must not
130+ terminate that chat. CrewCode defers model, effort, profile, approval, and other
131+ bridge invalidations until the next idle send, which restarts with the latest
132+ settings and the existing resume key. Sends under changed settings are refused
133+ until the current turn settles. Explicit Stop and session removal still stop
134+ their exact bridge.
135+
136+ Unexpected ACP exits report the observed exit code or termination signal and a
137+ bounded stderr tail, including an unterminated last line. Missing exit status is
138+ reported explicitly. CrewCode does not automatically replay an interrupted prompt.
139+ The preceding error carries the cause even if the generic exit row has no code.
140+
141+ Every CrewCoder stop request and exit also appends a diagnostic record to
142+ ` crewcode-crewcoder-lifecycle.jsonl ` in the agent host's OS temporary directory
143+ (` %TEMP% ` on Windows). This remains active for expected/internal stops, whose
144+ chat errors are intentionally suppressed. Records include bridge/process ids,
145+ the stop caller stack, exit code/signal, whether Stop was requested, and a bounded
146+ stderr tail; they exclude prompt and response bodies. A requested stop establishes
147+ that CrewCode initiated teardown, not that the user clicked Stop. Inspect this
148+ file for unexplained ` agent exited (unknown) ` rows instead of inferring an old build.
149+
101150The bridge performs this handshake before reporting ready:
102151
1031521 . ` initialize ` with protocol version 1 and text-file capabilities. The bridge
0 commit comments