Repository navigation
Keep the progress bar alive while the agent is waiting - #36
Merged
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
completedorpending. Nothing isin_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_progressforever, 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 --noEmitandnpm run buildpass. 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