Circuits

Circuits let you run a prompt on a repeating schedule. Use them for recurring tasks like running tests, checking for new issues, summarizing recent changes, or any other work that benefits from periodic execution.

Creating a circuit

/circuit "run the test suite and report failures" --interval 30m

The --interval flag accepts values like 30m, 1h, 6h. Once created, the circuit runs on that schedule for the lifetime of the session.

Use /circuits to list all active circuits, pause or resume individual ones, or cancel them.

In-session vs persistent

By default, circuits are in-session: they run inside the current TUI session and stop when you exit.

Add --persist to keep a circuit running after you close Caboose:

/circuit "check for new GitHub issues and summarize" --interval 1h --persist

Persistent circuits are handed off to the background daemon, which continues running them as a TCP server in the background.

The daemon

The Caboose daemon is a lightweight background process that manages persistent circuits. It starts automatically when you create a --persist circuit, or you can start it manually:

caboose daemon start
caboose daemon status
caboose daemon stop

The daemon uses a lockfile (~/.config/caboose/daemon.lock) for discovery. Stale lockfiles from crashed daemons are detected via PID liveness checks and cleaned up automatically.

Managing circuits

/circuits

Opens the circuit manager panel. From here you can:

• See all active circuits (in-session and persistent)
• View the last run time and next scheduled run
• Pause, resume, or cancel individual circuits

Circuit IDs are unique — you can reference them by ID to manage specific circuits from the command line or other sessions.