Expand description
Live progress: what a run is doing while it does it.
Events are a side channel — not journaled, not evidence — so replay and
verdicts are untouched. Live keeps live.json in the project’s state
directory up to date (read by speccoder report --live from another terminal),
prices token counts when [model] has prices, and forwards each event to
the CLI’s printer.
Structs§
- Live
- Keeps
live.json, prices usage, forwards to a printer. - Live
State - What
live.jsonholds. - Planned
Task - One task of a feature run’s plan.
- Shown
Reproduction - A reproduction as the stream shows it: never its content.
- Shown
Special Case - A special case as the stream shows it.
- Statement
Class - One statement’s class in a reproduce try.
Enums§
- BugEvent
- A bug’s step.
- Event
- Something a run did.
- Oracle
Event - A step of the oracle at review.
Constants§
- FILE
- The live file in a project’s state directory.
- RECENT
- Tool calls
live.jsonkeeps for watchers (speccoder tui).
Traits§
- Progress
- Receives events as they happen.
Functions§
- alive
- Whether process
pidis alive. - read_
live - The project’s
live.jsonand whether its process is still alive. - stage_
word verify,attempt 1/2, orstarting.- status
status_within the default state directory.- status_
with speccoder report --live: the project’s current (or last) run, fromlive.json, in the state directorystate.- tail
- The last lines of command output worth showing: at most five non-empty lines, each at most 200 characters, control characters removed.
- target
- The target of a tool call, for one line.
- usd
- USD for token counts (input includes cache reads and writes).