Expose several chats in a channel's UI #19

Activity

1. iamnbutler

   added a parent issue on Oct 4, 2026

   • [Meta] Restore features from old Ace #6
2. iamnbutler

   removed a parent issue on Oct 5, 2026

   • [Meta] Restore features from old Ace #6
3. iamnbutler

   added a parent issue on Oct 5, 2026

   • [Meta] Dogfood Ace end to end #5
4. iamnbutler commented on Oct 15, 2026

   

   iamnbutler

   on Oct 15, 2026

   ContributorAuthor

   More actions

   Two-person study (#218, scenario 11) on Canary 0.0.28. Tester B wanted separate agent work in A's shared talk without interrupting A's run. In the app, New tab → Chat reopened the existing chat; details and context menus had no chat selector. With the CLI, ace chat talk printed 168 and ace ask talk --chat 168 … streamed the answer, and ace info talk listed chats 1 and 168. Neither tester could find or open chat 168 in the app (both 3/3). The work was there, but only the CLI could see it.

   Expected: New tab → Chat offers a new chat and lists the channel's other chats, including teammates'.
5. iamnbutler commented on Oct 15, 2026

   

   iamnbutler

   on Oct 15, 2026

   ContributorAuthor

   More actions

   Still accurate on main (102fb15). The channel side is ready: op: "chat" creates a chat, info lists every chat with ChatInfo.parent for subagent chats (packages/channel/src/protocol.ts), and the CLI uses it (ace chat, ace ask --chat). The app hardcodes const chat = 1 in apps/app/src/channel.tsx, and the Diff and Terminal tabs follow that chat. Remaining work is all in the app: a chat route or tab per chat, New tab → Chat creating one, and a list of the channel's chats (including teammates' and subagents').