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
{{ message }}
Repository navigation
Commit 1259a9d
Browse filesBrowse the repository at this point in the historyBrowse files
fix(mobile): a caret move in one composer no longer moves another draft's insert point
The draft store kept one module-level "last composer selection" for every
draft. Moving the caret in a second composer replaced it, so context inserted
into the first draft afterwards (terminal output, a pasted file reference)
landed at the end of that draft instead of at its caret. The command menu
also pulled that selection in through two effects that wrote it back into
local state after every draft change and on every owner switch.
The store now keeps the caret per draft in a keyed atom. The command menu
derives its selection in render: a stored caret that still matches the draft
text wins, otherwise its own caret clamped to the draft, and a caret from a
different owner starts at the end of the draft.
Effects: use-composer-command-menu.ts 3 -> 1 (both selection-sync effects
removed; the workspace snapshot refresh effect stays).
Co-Authored-By: Claude Opus 5.5 <[email protected]>
0 commit comments