mirror of
https://github.com/NanmiCoder/cc-haha
synced 2026-07-16 13:03:31 +08:00
761031c036
Desktop sessions could show MCP configuration in the UI while the CLI SDK child process still started cold on the first user message. Start eligible desktop chat sessions as soon as their websocket is connected, keep init metadata cached but muted, and wait briefly for MCP startup in SDK print mode so turn one sees the tools. Constraint: Desktop wraps the existing CLI SDK bridge rather than owning MCP startup directly. Rejected: Prewarm every restored tab | synthetic tabs such as settings would start unnecessary CLI subprocesses. Confidence: high Scope-risk: moderate Directive: Do not remove the synthetic-tab guard without validating restored settings and scheduled-task tabs in the browser. Tested: bun test src/server/__tests__/conversations.test.ts src/server/__tests__/conversation-service.test.ts src/server/__tests__/mcp.test.ts Tested: cd desktop && bun run test -- chatStore.test.ts mcpSettings.test.tsx Tested: cd desktop && bun run lint Tested: cd desktop && bun run build Tested: agent-browser E2E new session prewarm plus first message reuse with mock CLI Not-tested: Full desktop Vitest suite still has pre-existing English-vs-Chinese copy assertion failures.