What happened
In the side conversation (the quote-companion side-chat panel), sending a message gives no immediate feedback, and the panel opens itself for unrelated conversations:
-
The submitted message shows up late. After you send a question in the side conversation, your own message bubble does not appear right away — it only shows once the assistant's whole answer has completed. The main conversation shows the user message immediately (optimistically).
-
The "working" progress indicator is missing during the wait. The running-status line (spinner + working phrase + elapsed clock, e.g. "正在琢磨… · 3s") barely appears in the side conversation. From the second message onward it only shows up around the time the answer starts settling, not during the connect-to-first-token wait — so a slow first token looks like nothing is happening. The main conversation shows this indicator promptly for the whole turn.
-
The side panel auto-opens for a brand-new conversation. The workbar's collapsed/expanded state is a single app-global sticky flag. If you open the side conversation in conversation A and then create a new conversation B, the side panel is still shown in B. Each conversation's side-panel open/collapsed state should be independent; a new conversation should not inherit another conversation's open panel.
How to reproduce
- Open a session, open the side conversation panel, and ask a question → your message bubble only appears after the assistant's answer finishes (expected: appears immediately on send).
- Ask a second question in the same side conversation → before the first token arrives, the "working"/thinking progress indicator does not show (expected: shows promptly, like the main conversation).
- Open the side conversation in conversation A, then create a new conversation B → the side panel is still visible in B (expected: B starts with its own collapsed side panel; switching back to A restores A's state).
Environment
- Maka commit: from source,
main
- OS and version: macOS 14 (Darwin 24.6)
- Surface: Desktop
- Node.js: running from source
Logs, screenshots, or additional context
All three are UX/state issues in the Desktop renderer's side-conversation feature; no crash. The main conversation already behaves correctly for (1) and (2), so the fix is to bring the side conversation to parity, and to make the workbar collapsed state per-conversation for (3).
What happened
In the side conversation (the quote-companion side-chat panel), sending a message gives no immediate feedback, and the panel opens itself for unrelated conversations:
The submitted message shows up late. After you send a question in the side conversation, your own message bubble does not appear right away — it only shows once the assistant's whole answer has completed. The main conversation shows the user message immediately (optimistically).
The "working" progress indicator is missing during the wait. The running-status line (spinner + working phrase + elapsed clock, e.g. "正在琢磨… · 3s") barely appears in the side conversation. From the second message onward it only shows up around the time the answer starts settling, not during the connect-to-first-token wait — so a slow first token looks like nothing is happening. The main conversation shows this indicator promptly for the whole turn.
The side panel auto-opens for a brand-new conversation. The workbar's collapsed/expanded state is a single app-global sticky flag. If you open the side conversation in conversation A and then create a new conversation B, the side panel is still shown in B. Each conversation's side-panel open/collapsed state should be independent; a new conversation should not inherit another conversation's open panel.
How to reproduce
Environment
mainLogs, screenshots, or additional context
All three are UX/state issues in the Desktop renderer's side-conversation feature; no crash. The main conversation already behaves correctly for (1) and (2), so the fix is to bring the side conversation to parity, and to make the workbar collapsed state per-conversation for (3).