Monitoring
Watch every step as it happens.
Autonomous mode is not magic - it's a subprocess on your machine. Sometimes it freezes waiting on a permission prompt. Sometimes it loops. The Mac app shows you exactly where it is, when it last moved, and what it's stuck on, so you can step in within seconds instead of hours.
Follow along
- 1.
Open the live monitor
When /story auto is running, the Storybloq Mac app automatically shows a live monitor pane. Current phase (PLAN, IMPLEMENT, CODE_REVIEW, etc.) at the top. Heartbeat timestamp next to it. Subprocess state (running, waiting, blocked) under that.
- 2.
Watch the heartbeat
The state machine pings storybloq_autonomous_guide on every transition. If the heartbeat hasn't updated in a few minutes, something's up. Usually a permission dialog hidden behind another window, or a subprocess waiting on input.
- 3.
Check the subprocess
Click the subprocess badge to see the actual command and its output. If it's wedged on a prompt, answer it. If it's looping, cancel and restart from the last clean state.
- 4.
Follow the live log
Below the phase panel, the live log streams every action: files touched, tests run, reviewers invoked. Scan it for surprises. If something looks wrong, hit stop - you haven't committed yet.
- 5.
Read the final handover
When the run finishes (clean or interrupted), a handover lands in .story/handovers. It's the single most useful thing to read: what shipped, what was skipped, what blocked, and what to do next. Every future /story will load it automatically.