Repository navigation
Keep a channel's composer mode and unsent model choice across relaunch #273
Description
From the two-person study (#218, scenarios 4–6) on Canary 0.0.27. The composer keeps a deliberate Chat/Ace mode choice and, since #265, a picked model only for the app session (module maps in apps/app/src/composer.tsx).
- Tester A's
studychannel, used only for chat, came back in Ace mode after the update relaunch and again after a quit. - Tester B picked
claude-opus-5-5in an emptygames-b, quit and reopened Ace, and the picker showed Automatic. The next invoke would have used the default model.
Drafts already survive relaunch (#165). Expected: the mode and an unsent model pick restore with the draft. Low priority; once a chat has run, its model shows from the chat itself.
Part of #5.
Activity
iamnbutler commentedon Oct 15, 2026
Picked up by the overnight issue watcher (Claude Code session, outside Ace — this Mac's Canary is a study participant). A PR will link here.
iamnbutler commentedon Oct 15, 2026
Composer is clear again after #282, so the overnight watcher is working on this now, building on #282's per-chat picks map.
fix(app): keep a channel's composer mode and unsent model pick across…
iamnbutler commentedon Oct 15, 2026
The composer now stores a channel's Chat/Ace mode and each chat's unsent model/effort pick in localStorage beside the channel's draft, so both survive a quit or update relaunch (#284).
iamnbutler commentedon Oct 15, 2026
More evidence from two-person study scenario 14 (#218): after Cmd+Q and reopening Ace, Tester A's
studychannel came back in Ace / Automatic, although it had been in Chat. They had to switch back before posting. Confusion 2/3.