mirror of
https://github.com/garrytan/gstack.git
synced 2026-09-09 22:48:57 +02:00
docs(codex): resume does not amortize the ~21K session prelude (#2387)
Measured (#2387): every codex exec call pays Codex's session prelude, and a resumed call came in slightly ABOVE a fresh one — resume buys continuity, never token savings. The skill now says so where the resume flow lives: prefer one codex call per skill, batch questions into it. Fixes #2387. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Fable 5
parent
423a963d22
commit
c856472034
@@ -629,6 +629,14 @@ elif [ "$_CODEX_EXIT" != "0" ]; then
|
||||
fi
|
||||
```
|
||||
|
||||
**Session-cost reality (#2387, measured):** every `codex exec` call — resumed
|
||||
or fresh — pays Codex's ~21K-token session prelude (its skill catalogue +
|
||||
instructions); `resume` does NOT amortize it (a measured resume came in
|
||||
slightly ABOVE a fresh call). Resume buys conversational continuity, never
|
||||
token savings. So: prefer ONE codex call per skill where the workflow allows,
|
||||
batch questions into that call, and reach for resume only when the follow-up
|
||||
genuinely needs the prior session's context.
|
||||
|
||||
For a **resumed session** (user chose "Continue"):
|
||||
```bash
|
||||
_REPO_ROOT=$(git rev-parse --show-toplevel) || { echo "ERROR: not in a git repo" >&2; exit 1; }
|
||||
|
||||
Reference in New Issue
Block a user