Repository navigation
fix(sidebar): show Input for blocking questions during live turns - #53
Merged
Merged
Conversation
github-actions
Bot
added
vouch:trusted
alexcstark
added a commit
that referenced
this pull request
Oct 11, 2026
…debar fix(sidebar): show Input for blocking questions during live turns
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
1 participant
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.
A provider can still report a running turn while a native question blocks it for an answer. The sidebar previously showed Working in that case, hiding the need for input. Blocking questions now show Input on web, desktop, and mobile; asynchronous questions keep showing Working while the agent continues.
The shell summary carries the existing response-capability type through the server projection and shared client model. Both sidebar views, the working-thread inbox, and mobile’s detail fallback use it. The field is optional, so clients retain the existing behavior when connected to an older server. No provider protocol or database migration changes are required.
Validation: 286 focused tests passed during implementation; independent review ran 389 focused tests plus contracts and client-runtime typechecks and found no actionable regressions. Contracts, client-runtime, web, server, and mobile typechecks, targeted lint, formatting, and diff checks passed. The corrected native Mac and Linux builds are installed; authenticated shell and WebSocket checks passed on both. Desktop verification confirmed an asynchronous question remains Working. GitHub CI passed lint, typecheck, build, the full web/server test jobs, Rust, and release smoke (run). Alex waived before/after screenshots for this PR; native mobile UI was not exercised.
The Puget reconnect repair restored omitted public T3 Connect settings in the packaged builds; it required no additional source-code change.
Model: GPT-6. Harness: Codex.