fix(app): remove background running indicator - #46972
Merged
Merged
Conversation
opencode-agent
Bot
requested review from
Brendonovich and
Hona
as code owners
September 3, 2026 03:39
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Runninglabel and spinner below the transcript.Workingcondition and presentation unchanged: an idle session with background shell/subagent work shows no bottom-of-transcript busy indicator.Validation
session-timeline-working.spec.tsbrowser tests passed during validation. The added regression cases were removed at the requester's direction; the test file is identical to the base and no test changes are included in this PR. E2E typecheck and formatting passed again after removal.4680a4aa6f84f4f2680b267b0607b26218fb921bwith1bda2831578cfd1a233aef9d52a09b56cda17510, using Chromium 147 on Linux and deterministic mocked backend data. The subsequent update only removes the added tests; production code is unchanged. Browser checks use Node 22; the host's Node 18 could not run this harness correctly.Requested by: @Hona (Hona via Slack)