### Preflight Checklist - [x] I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) and this hasn't been reported yet - [x] This is a single bug report (please file separate reports for different bugs) - [x] I am using the latest version of Claude Code ### What's Wrong? **Actual:** Remote client never received the Plan Mode change; answering there flipped the local session out of Plan Mode without notice. The agent then b

[BUG] Permission mode not synced across devices for the same session — remote instance stays in default mode

Status Fixed / completed

Maintainer reply ✓ Yes — bcherny

Activity 3 comments · opened Jul 29, 2026 · closed Aug 19, 2026

💡 Likely answer: A maintainer (bcherny, collaborator) responded on this thread — see the highlighted reply below.

Preflight Checklist

[x] I have searched existing issues and this hasn't been reported yet
[x] This is a single bug report (please file separate reports for different bugs)
[x] I am using the latest version of Claude Code

What's Wrong?

Actual: Remote client never received the Plan Mode change; answering there flipped the local session out of Plan Mode without notice. The agent then began making edits that Plan Mode was meant to prevent.

There appears to be a bug with Claudi.AI that if you have two apps open. One locally, one on a remote machine. I changed a local instance to Plan Mode. I then entered my prompt on my local machine and let claude work on a response. I later checked my remote app to review questions prompted to continue. I answered those questions on my remote machine. However, I didn't notice that remote machine didn't change to Plan Mode, even though I set that on my local machine. When I answered remotely, Claude changed the mode on my local machine. Instead of staying in Plan Mode it switched to Accept Changes and then started to make modifications to my code base and burn through tokens.

What Should Happen?

Expected: Permission mode is session state and propagates to every attached client; answering from a second client does not silently downgrade Plan Mode.

Error Messages/Logs

Impact: Loss of the safety guarantee Plan Mode exists to provide — unintended file writes and token spend.

Suggested fix: Propagate mode changes to all attached clients, and/or reject an answer from a client whose mode is stale rather than adopting it.

Steps to Reproduce

Open the same session on two machines (local desktop + remote).
On the local machine, switch to Plan Mode.
Agent asks a question (AskUserQuestion); answer it on the remote machine, which is still in the default/Accept Edits mode.
The session's effective mode becomes the remote machine's mode.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.2.220

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

Reference ID: 6cdbad27-aa3c-46a4-8dc3-468bcabd885a

Local Windows Claudi.AI App: 1.24012.9 (03c61d)
Remote Mac Claudi.AI App: 1.24012.9 (03c61d)

View original on GitHub ↗

3 Comments

bcherny collaborator · 1 month ago

Thanks for the detailed report. I couldn't stage this one end to end — it needs the same session attached from two machines, and I only had a single Linux box (2.1.233), so I checked the documented behavior instead.

One thing stands out: the outcome you describe is what approving a plan is supposed to do. When a plan is ready, Claude asks how to proceed and the options are "Yes, and use auto mode" (shown as "Yes, auto-accept edits" when auto mode isn't available), "Yes, manually approve edits", and "No, keep planning". Choosing either "yes" option intentionally exits plan mode, switches the session to that mode, and lets Claude start editing — see https://code.claude.com/docs/en/permission-modes#review-and-approve-a-plan. Answering it from a second device does the same thing as answering it locally.

Separately, the mode itself is meant to be shared: since v2.1.202 the mode selector in the app reflects the session's actual mode, including one set from the terminal, and updates when it changes on either side (bypass permissions is the one mode never reported).

So the question is which prompt you answered on the Mac. Could you confirm:

Was it the plan-approval prompt (the three approve / keep-planning options), or an ordinary mid-turn question?
What mode did the Mac app's selector show at that moment, and what did the Windows one show?
The exact version from claude doctor on the host machine (2.2.220 isn't a released version, so that field may have picked up the desktop app build).

If it wasn't the plan-approval prompt, that's a real bug and we'll dig in — just reply and we'll reopen the investigation.

🤖 Generated with Claude Code

RossLieberman · 1 month ago

Thanks for looking into it. It was 3 weeks ago and I'm too wrapped up to troubleshoot further. I'm going to close this ticket. I'm much more careful with this scenario but if I reproduce it, I'll add to the ticket.

github-actions[bot] · 5 days ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.