- Who it helps
- Developers experimenting with long-running repository work.
- Availability
- The public runner documents Node.js 22.18+ and an already configured Claude Code or Codex CLI on supported desktop environments.
What keeps the runner working
Its README distinguishes pause-after-cycle and immediate stop. Closing the dashboard leaves the runner working. Codex usage does not provide an enforced dollar budget here.
Rehearse the stopping controls
Before a real run, rehearse a stop in a disposable project and confirm the process exits. Record the provider’s separate spending controls.
What you can do
- Find the pause and stop commands in the README and record which one terminates the active cycle. Open reference ↗
Where the evidence stops
The runner was not installed. Cycle and time limits do not by themselves establish permission isolation or a reliable spending cap.
Sources read. Public evidence checked October 18, 2026. The product, external code and reported outcomes were not independently executed.
Sources & further reading
GitHub · implementation
Epoptes README ↗
Read the runner’s control commands, cycle limits and Codex budget limitations; no installation was performed.
ramigb · page checked 2026-10-18
Coverage note: The linked evidence is a bounded sample. Independent execution and current cross-platform discussion remain incomplete.
The record over time (1)
Dated source checks and published explanations. An observation date can differ from the original release date.
Epoptes runs coding-agent work in repeated cycles with local state and a dashboard.