feat(chat): make cross-conversation requests explicit and expandable - #848
Merged
Merged
Conversation
Retain the convenience of answering questions and permissions across conversations while making ownership explicit. External and sessionless project requests start compact and require deliberate expansion. Expanded requests show the source name prominently, distinguish subagents and their parent conversation, and offer explicit source navigation without moving the user when a request arrives or is answered. Extract keyed dock selection state, retain hidden drafts, keep the current request stable during arrivals, and leave foreign settlement fallbacks compact. Use one bounded external preview beside a local request. The red project badge expands the selected request in place, including recovery from the Info surface. Add localized provenance labels in all ten locales and preserve short-keyboard footer reachability. Validate 71 affected browser checks plus six targeted Info-badge regressions, UI TypeScript and diff checks. Inspect desktop and Android-touch compact, expanded, concurrent and short-keyboard captures. This implements the explicitly approved UX revision to PR847; it does not claim to fix the separately reported mobile reconnect behavior.
pascalandr
commented
Oct 4, 2026
pascalandr
left a comment
pascalandr
left a comment
Contributor
Author
There was a problem hiding this comment.
Independent gatekeeper: ZERO FINDINGS on a7eb464 (complete diff 74e6a02..a7eb464).
Reviewed selection/draft lifecycle, explicit external/project expansion, persistent provenance, native reply authority, Info-view red-badge entry, mobile sizing and all ten locale additions. Independently ran 30 browser tests: all passed. Inspected desktop/mobile captures. Read-only review; working tree clean.
Targeted implementation suites and production UI build also passed. Proceeding with the explicitly requested admin merge without waiting for full CI. Installed application deployment remains separate.
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.
Approved UX
I found cross-conversation authorization useful after trying it, but could not clearly identify the source. They explicitly approved revising #847: keep in-place replies with compact external previews and prominent persistent provenance.
Behavior
Validation
Scope and maintenance
This implements the revised interaction preference, not a claimed fix for the separate Android reconnect disappearance. Installation remains separate. Existing oversized component touched: packages/ui/src/components/instance/instance-shell2.tsx (~1335 lines).