Audit of 39fe50e

2026-10-21 11:03:44 -07:00
parent 4ba742aee0
commit 5999ae2303
2 changed files with 1 additions and 2 deletions
@@ -75,7 +75,6 @@ Vendor setup and protocol quirks are in [Claude Code](claude-protocol.md), [Code
 - Claude Code records `--append-system-prompt` on a session's first request and reuses it on resume, so a running session keeps the guidance it started with; the `UserPromptSubmit` hook re-attaches the guidance to every turn so existing sessions see changes. On a fork Claude Code can reuse the system prompt recorded for the source conversation, the source's cwd included, so the hook's copy is what reliably tells a fork where it is.
 - A Claude `result` with `num_turns` 0, no `result` text and no error, outside an interrupt, isn't a turn end: the CLI emits one on its own, for example after a resume when it reports a background shell left over from the previous process. byre logs `ignored result with no model turns` and keeps the turn running.
 - stream-json doesn't expand `@path` the way the interactive CLI does, so the composer has no `@`-file mentions; the agent reads any file a message names with its own tools.
- A snapshot always sits on a turn boundary, the only place a Codex conversation can be forked.

 ## Agent behavior