Skip to content

Keep the progress bar alive while the agent is waiting - #36

Merged
savvasioakeim merged 1 commit into
mainfrom
fix/progress-pulse
Oct 31, 2026
Merged

savvasioakeim merged 1 commit into
mainfrom
fix/progress-pulse

Conversation

@savvasioakeim

Copy link
Copy Markdown
Owner

The pulse was keyed off a step being marked in_progress. But "a step is in_progress" and "the agent is working" are not the same thing, and they come apart in both directions.

Reported case. An agent that finishes a step and then waits — on CI, on an approval — leaves every step either completed or pending. Nothing is in_progress, so nothing pulsed, and the bar went completely still at the moment it most needed to say it was alive. Seen on a 4/5 task waiting for CI: the title correctly named the fifth step while the bar looked dead.

The other direction, found while fixing it. A stopped agent leaves its last step in_progress forever, and that kept pulsing as though it were still running.

The fix

The focal node is now the step in progress, or, when none is, the step the agent is about to reach — the same index the title has always used. It pulses only while agentBusy, which the call site already had and simply wasn't passing down.

A focal step that hasn't started stays hollow rather than filled, so it reads as where we are waiting and not as work already done.

Verification

npx tsc --noEmit and npm run build pass. The four states to eyeball: a step running (filled, pulsing), waiting between steps (hollow, pulsing), agent stopped mid-step (filled, still), and all done (no focal node, ✓ in the title).

🤖 Generated with Claude Code

The pulse was keyed off a step being marked in_progress, but "a step is
in_progress" and "the agent is working" are not the same thing, and they
come apart in both directions.

An agent that finishes a step and then waits — on CI, on an approval —
leaves every step either completed or pending. No node was in_progress, so
nothing pulsed, and the bar went completely still at the moment it most
needed to say it was alive. Reported on a 4/5 task waiting for CI, where
the title correctly named the fifth step while the bar looked dead.

The other direction was already wrong too: a stopped agent leaves its last
step in_progress forever, and that kept pulsing as though it were running.

The focal node is now the step in progress, or, when none is, the step the
agent is about to reach — the same index the title has always used. It
pulses only while agentBusy, which the call site already had and simply
wasn't passing down. A focal step that hasn't started stays hollow rather
than filled, so it reads as where we are waiting and not as work done.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@savvasioakeim
savvasioakeim merged commit af290f3 into main Oct 31, 2026
3 checks passed
@savvasioakeim
savvasioakeim deleted the fix/progress-pulse branch October 31, 2026 18:28
@github-actions github-actions Bot locked and limited conversation to collaborators Oct 31, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant