You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
lighten mobile Thinking and tool-call rows, render ask-user-question interactions, and surface Todo projections
add mobile model and Preset settings with first-message Preset locking, plus optimistic user-message rendering
polish the composer and empty-session flow, and pin the running “Deep diving...” state directly above the composer instead of inside the scrolling message list
expose the required mobile RPC adapters for pending interactions, model selection, Preset selection, and projection data
Verification
npm run typecheck
npm test -- --run (27 files, 170 tests)
npm run build
The desktop app was intentionally left stopped after verification.
Fixed the missing mobile ask_user_question delivery path. The real network Harness serves /api/events.mux as a downlink-only WebSocket and returns HTTP 426 to ordinary GET requests; the bridge had incorrectly implemented that stream as SSE. The regression fixture now mirrors the production WebSocket upgrade and verifies replay, answer, resolution, cancellation, and validation.
Fixed the settings popover jumping upward when Todo and running-status docks are present. The popover now remains anchored 76px above the composer trigger; Todo expansion and Deep diving... only affect message clearance, not popover placement. Typecheck, all 170 tests, and the production build pass.
Restored the original mobile Deep diving... behavior after product review: it is again rendered as the final item in the scrolling message flow, rather than a fixed composer dock. The Todo/settings positioning and WebSocket question-delivery fixes remain unchanged. Typecheck, all 170 tests, and the production build pass.
Removed the stray native file-picker control from the Agent presets header. The hidden input remains as the backing control for the styled Import button, and the patch now explicitly applies display:none. Patch reverse-check, typecheck, all 170 tests, and the production build pass.
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
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
Verification
npm run typechecknpm test -- --run(27 files, 170 tests)npm run buildThe desktop app was intentionally left stopped after verification.