9691c9834b
Fixes #212 <!-- CURSOR_SUMMARY --> --- > [!NOTE] > Add concurrent chat support with per-chat state, chat activity UI, IPC per-chat handling, and accompanying tests. > > - **Frontend (Chat concurrency)** > - Replace global chat atoms with per-chat maps: `chatMessagesByIdAtom`, `isStreamingByIdAtom`, `chatErrorByIdAtom`, `chatStreamCountByIdAtom`, `recentStreamChatIdsAtom`. > - Update `ChatPanel`, `ChatInput`, `MessagesList`, `DyadMarkdownParser`, and `useVersions` to read/write per-chat state. > - Add `useSelectChat` to centralize selecting/navigating chats; wire into `ChatList`. > - **UI** > - Add chat activity popover: `ChatActivityButton` and list; integrate into `preview_panel/ActionHeader` (renamed from `PreviewHeader`) and swap in `TitleBar`. > - **IPC/Main** > - Send error payloads with `chatId` on `chat:response:error`; update `ipc_client` to route errors per chat. > - Persist streaming partial assistant content periodically; improve cancellation/end handling. > - Make `FileUploadsState` per-chat (`addFileUpload({chatId,fileId}, ...)`, `clear(chatId)`, `getFileUploadsForChat(chatId)`); update handlers/processors accordingly. > - **Testing** > - Add e2e `concurrent_chat.spec.ts` and snapshots; extend helpers (`snapshotMessages` timeout, chat activity helpers). > - Fake LLM server: support `tc=` with options, optional sleep delay to simulate concurrency. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 9035f30b73a1f2e5a366a0cac1c63411742b16f3. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY -->
Fake stdio MCP server
This directory contains a minimal stdio MCP server for local testing.
- Tools:
- calculator_add: adds two numbers. Inputs:
a(number),b(number). - print_envs: returns all environment variables visible to the server as pretty JSON.
- calculator_add: adds two numbers. Inputs:
Requirements
- Node 20+ (same as the repo engines)
- Uses the repo dependency
@modelcontextprotocol/sdkandzod
Launch
-
Via Node:
node testing/fake-stdio-mcp-server.mjs -
Via script (adds a stable entrypoint path):
testing/run-fake-stdio-mcp-server.sh
Passing environment variables
Environment variables provided when launching (either from your shell or by the app) will be visible to the print_envs tool.
export FOO=bar
export SECRET_TOKEN=example
testing/run-fake-stdio-mcp-server.sh
Integrating with Dyad (stdio MCP)
When adding a stdio MCP server in the app, use:
- Command:
testing/run-fake-stdio-mcp-server.sh(absolute path recommended) - Transport:
stdio - Args: leave empty (not required)
- Env: optional key/values (e.g.,
FOO=bar)
Once connected, you should see the two tools listed:
calculator_addprint_envs