claude-code - 💡(How to fix) Fix [Bug] Post-/compact continue references wrong session context (cross-session memory bleed) [1 comments, 2 participants]

[{"error":"McpToolCallError: ### Error\nError: browserBackend.callTool: net::ERR_CONNECTION_REFUSED at http://[REDACTED]:3210/\nCall log:\n\u001b[2m - navigating to "http://[REDACTED]:3210/", waiting until "domcontentloaded"\u001b[22m\n\n at mh9 (/$bunfs/root/src/entrypoints/cli.js:1772:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-14T23:52:43.466Z"},{"error":"McpToolCallError: ### Error\nTimeoutError: locator.textContent: Timeout 30000ms exceeded.\nCall log:\n\u001b[2m - waiting for locator('[role=region][aria-label*="Notifications"]')\u001b[22m\n\n at mh9 (/$bunfs/root/src/entrypoints/cli.js:1772:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-14T23:54:38.085Z"},{"error":"Error: EISDIR: illegal operation on a directory, read '/Users/lee/dev/dk-web-agent-next/src/features/chat-filter/lib'\n at E1H (/$bunfs/root/src/entrypoints/cli.js:4438:15399)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-15T00:20:07.958Z"},{"error":"Error: Error normalizing tool input: ZodError: [\n {\n "expected": "string",\n "code": "invalid_type",\n "path": [\n "command"\n ],\n "message": "Invalid input: expected string, received undefined"\n }\n]\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:4866:1005)\n at map (native:1:11)\n at eK_ (/$bunfs/root/src/entrypoints/cli.js:4866:556)\n at Jp7 (/$bunfs/root/src/entrypoints/cli.js:8037:7769)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-15T00:33:07.054Z"},{"error":"McpToolCallError: ### Error\nError: Ref e21 not found in the current page snapshot. Try capturing new snapshot.\n at mh9 (/$bunfs/root/src/entrypoints/cli.js:1772:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-15T00:41:38.955Z"}]

TL;DR

The issue can be mitigated by reprompting after the /compact command to recover the correct session context.

Guidance

• The error logs provided do not directly point to the cause of the cross-session bleed, suggesting the issue might be related to how session contexts are managed internally.
• Reprompting after the /compact command has been observed to recover the correct session context, indicating a potential workaround.
• To further diagnose the issue, providing the raw JSONL transcripts as offered could be helpful for maintainers to understand the session management and context switching better.
• The environment and version information (Platform: darwin, Terminal: WarpTerminal, Version: 2.1.108) should be considered when reproducing and debugging the issue.

Example

No specific code snippet can be provided without more details on the internal implementation of session management and the /compact command.

Notes

The provided error logs seem unrelated to the primary issue of cross-session context bleed, suggesting that the root cause might be in the application's logic for managing and switching between session contexts.

Recommendation

Apply the workaround of reprompting after the /compact command, as it has been observed to recover the correct session context. This approach allows for continued use of the application while awaiting a more permanent fix.