Monitoring
Watch every step as it happens.
Autonomous mode runs through your coding client, with progress recorded in the project. Sometimes it freezes waiting on a permission prompt. Sometimes it loops. The Mac app displays reported session state and activity. Use the coding client to inspect prompts or failures; the dashboard cannot infer every reason a client has stopped.
Written guide available · Video coming soon
Follow along
- 1.
Open the live monitor
Open the project in the Mac app while autonomous mode runs. Inspect its recorded stage, activity, and registered subprocesses. These records come from CLI/MCP reports and supported hooks.
- 2.
Watch the heartbeat
The agent reports stage transitions through storybloq_autonomous_guide. A quiet period is a reason to inspect the client, not proof of a freeze: a build, review, or permission prompt may be pending.
- 3.
Check the subprocess
Registered subprocesses help distinguish a running build from an idle agent. Inspect the command and the coding client’s output before interrupting it. Unregistered processes may not appear.
- 4.
Follow the live log
Inspect recorded session events and your coding client’s output for tests, reviews, and changes. If you interrupt a run, inspect Git status and the latest commits before continuing: FINALIZE may already have committed.
- 5.
Read the latest handover
Read the latest handover and persisted session state to see what finished and what remains. A sudden interruption may occur before a new handover is written. Invoke /story in Claude Code or $story in Codex to load the available record.