Skip to content

fix(tui): unify thinking and patch progress lines - #49250

Open
holny wants to merge 1 commit into
anomalyco:v2from
holny:thinking-patch-line
Open

holny wants to merge 1 commit into
anomalyco:v2from
holny:thinking-patch-line

Conversation

@holny

@holny holny commented Sep 16, 2026

Copy link
Copy Markdown

Issue for this PR

Closes #44164

Type of change

  • Bug fix

What does this PR do?

When a thinking block is open and a patch tool is running in the same message, the timeline drew two live lines: the thinking header spinner plus the patch row spinner.

While both are active they now merge into one line — the thinking header reads Thinking · Patch <target> and the running patch row is hidden. The row comes back as soon as either side settles (thinking completed, or patch finished/failed), so completed states are unchanged. Both layouts are covered: the expanded reasoning block and the collapsed thinking row.

How did you verify your code works?

Ran the tui suite locally: 1334 pass, 4 failures that are plugin-reload / dialog-shell-output flakes failing the same way on the base commit (checked by stashing the change). typecheck clean for packages/tui.

Screenshots / recordings

Not applicable — terminal rendering change, no stable screenshot.

Checklist

  • I have tested my changes locally
  • I have not included unrelated changes in this PR

Supersedes #49163 — identical commit (a95453128b), closed earlier because the description was missing the template sections.

When a thinking block is open while a patch tool runs, the timeline showed a spinner on the thinking header and a second one on the patch row. Absorb the running patch into the thinking line ("Thinking · Patch <target>") and hide the duplicate patch row, reappearing as usual once either side settles.

Fixes anomalyco#44164
@github-actions

Copy link
Copy Markdown
Contributor

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

  1. Open an issue describing the bug/feature (if one doesn't exist)
  2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant