fix(codex): preserve side thread tools

This commit is contained in:
pashpashpash
2026-05-10 22:03:45 -07:00
committed by Peter Steinberger
parent e15f99e34e
commit ddc9581d00
4 changed files with 41 additions and 29 deletions

View File

@@ -40,8 +40,10 @@ The important mental model is:
For Codex harness sessions, BTW stays inside Codex by forking the active
app-server thread as an ephemeral side thread. That keeps Codex OAuth and native
thread behavior intact while still isolating the side answer from the parent
transcript. The side turn stays tool-free and read-only. Non-Codex runtimes keep
the older direct one-shot path.
transcript. Like Codex `/side`, the side thread keeps the current Codex
permissions and native tool surface, with guardrails that tell the model not to
treat inherited parent-thread work as active instructions. Non-Codex runtimes
keep the older direct one-shot path.
## What it does not do
@@ -49,7 +51,6 @@ the older direct one-shot path.
- create a new durable session,
- continue the unfinished main task,
- run tools,
- write BTW question/answer data to transcript history,
- appear in `chat.history`,
- survive a reload.