You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While on plan mode and a plan is proposed, as soon as I accept, the session title gets changed and it loses all context of the conversation and appears to have context from other conversations. This is after clearing context and starting new sessions. This behavior persists across new session creation.
I can reproduce this consistently. Here's what's actually happening under the hood:
Setup: Claude enters plan mode, writes a plan file, and calls ExitPlanMode. The app shows the plan and prompts for approval.
On approval: Instead of sending the approval back to the existing session, the app appears to spawn a new session. The new session receives a message like "continue with plan" but has no conversation history — no access to the plan file path, the prior discussion, or any context about what the plan contains.
Meanwhile, the original session keeps running on the computer. It received the plan approval and is executing normally — making edits, progressing through the plan. But it's completely invisible and inaccessible from the app. The app only shows the orphaned new session, which is stuck asking "what plan?"
The result:
The user sees a broken session in the app that lost all context
The real session is silently executing on the machine with no way to monitor or interact from mobile
The user has no indication that work is actually proceeding
Key distinction from a simple context-loss bug: the original session isn't lost or corrupted. It's running fine. The bug is that plan approval triggers a session fork — the app attaches to the new (empty) session instead of continuing with the original.
Environment: Happy 0.14.x, macOS, Claude Code, remote mode from iOS
Activity
[-]New Chat Created Mid Conversation.[/-][+]New Chat Created Mid Session[/+]n0rthwood commentedon Jan 21, 2026
I have the same issue
seth-with-zest commentedon Feb 22, 2026
Additional technical detail
I can reproduce this consistently. Here's what's actually happening under the hood:
Setup: Claude enters plan mode, writes a plan file, and calls
ExitPlanMode. The app shows the plan and prompts for approval.On approval: Instead of sending the approval back to the existing session, the app appears to spawn a new session. The new session receives a message like "continue with plan" but has no conversation history — no access to the plan file path, the prior discussion, or any context about what the plan contains.
Meanwhile, the original session keeps running on the computer. It received the plan approval and is executing normally — making edits, progressing through the plan. But it's completely invisible and inaccessible from the app. The app only shows the orphaned new session, which is stuck asking "what plan?"
The result:
Key distinction from a simple context-loss bug: the original session isn't lost or corrupted. It's running fine. The bug is that plan approval triggers a session fork — the app attaches to the new (empty) session instead of continuing with the original.
Environment: Happy 0.14.x, macOS, Claude Code, remote mode from iOS