Hook-backed supervision
Hook processes write journals, snapshots, and periodic reviews; bounded daemon IPC serves deterministic gates. Replay, diagnostics, and signal-driven review also exist.
Experimental · local-first · open source
Spotter supervises coding agents while they work. It watches the trajectory—not only the final diff—so weak assumptions, repeated failures, and unsafe actions can be caught before their cost compounds.
Prototype status: deterministic gates are active. Semantic advisories remain off by default; recovery controls are not shipped.
The cost of late feedback
A weak assumption shapes the next search. The search shapes the next edit. By the time review catches the result, the agent may have spent minutes, tokens, and repository churn defending the wrong path.
Post-hoc review asks whether the output is acceptable. Runtime supervision asks whether the work is still heading somewhere worth going—and whether the next action is safe.
Supervision loop
Spotter keeps deterministic enforcement fast and local while slower semantic review stays off the synchronous tool path.
Collect actions, evidence, edits, validation, and runtime identity into a durable trajectory.
Find repeated failures, stalled exploration, scope growth, missing validation, and stale hypotheses.
Block deterministic violations now; evaluate careful semantic guidance before broader use.
Preserve snapshots and replay material today while live interrupt and restart remain target capabilities.
Intervention ladder
Current and target
Hook processes write journals, snapshots, and periodic reviews; bounded daemon IPC serves deterministic gates. Replay, diagnostics, and signal-driven review also exist.
App Server ingestion and control foundations are partial. Broad live advisories, interrupt, and verified restart remain gated by evidence and hardening.
Honest by design
This is a stable summary, not a duplicate changelog. The repository status document is the source of truth for exact capability boundaries.
Evidence before escalation
Each outcome has an evidence gate. Implementing a mechanism is not the same as proving it improves results.
Explore the roadmap and evidence gates →Get started
Install the CLI and daemon from the official Homebrew tap. Setup is explicit, transactional, and does not silently change Codex during package installation.
$ brew install spotter-agent/spotter/spotter
$ spotter setup codex --dry-run
$ spotter setup codex
$ spotter doctor