🤖 implementation references: headless sessions and gremlins
This commit is contained in:
@@ -47,5 +47,14 @@ Full id not recorded here; spacecraft notes mention "Sonnet 5".
|
||||
- Both extremes failed. Many tiny fresh implementers relearn the code each time. One implementer carried across tasks reached about 960k tokens and drifted (spacecraft, 2026-09-29; model probably 5.5 through the alias).
|
||||
- Measured: dirigent blocks of 11–36 min of agent work used 186k–344k tokens each (Sonnet, 2026-10-01). None ran out.
|
||||
- Guesstimates (unmeasured): a trunk read at intake of about 100k–250k; leave room for fallout and the fix pass rather than running close to the comfortable limit.
|
||||
- With gremlins (2026-10-16), the trunk read is the base's training, not the Athanor's context. Measured: the Phase 0 large base was 182k tokens (P0.2) and the smoke base 23.7k; the Athanor reads plans and reports, not code (preflight report; Phase 3 contract A13).
|
||||
|
||||
**Future work:** orchestrator introspection of subagent token use, and signals into running work (dirigent is working on this). Until then, the Athanor records what usage it sees in completion results and judges by block count and size.
|
||||
|
||||
- Update 2026-10-16: gremlins (headless sessions) report per-call usage through `usage` (tokens by cache column, models used, priced cost). Agent-tool subagents still do not.
|
||||
|
||||
## Notes added 2026-10-16
|
||||
|
||||
- Plan mode (`--permission-mode plan`) silently upgrades a Haiku session to Sonnet; `init.model` still shows Haiku, so read `modelUsage` for what ran. The docs only imply it (research `F2a`, `F2b`).
|
||||
- Aliases map to model versions per CLI release: `haiku` is Haiku 4.5 on `claude` 2.1.283 and Haiku 5.5 on 2.1.299 (research `F2c`). Pin a full id where the version matters.
|
||||
- Opus 5.5 may refuse a bare "run this blocking command" brief as pointless; say why the command is wanted (observed in the Phase 0 trunk notes, preflight report, 2026-10-16).
|
||||
|
||||
Reference in New Issue
Block a user