Feature: combine remote-control with --dangerously-skip-permissions

Found 1 possible duplicate issue:

1. https://github.com/anthropics/claude-code/issues/29214

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

same issue here

agreed! This feature is highly needed!

docker sandbox exec -it claude-kitchen_sink claude remote-control --permission-mode bypassPermissions

Doesn't seem to apply to the default started session, though, so maybe add --no-create-session-in-dir

It works for me when I use --remote-control (so start an actual claude code session) and run it in tmux

What works?

On Mon, Mar 23, 2026, 6:40 AM Marius Bosler @.***>
wrote:

maribox left a comment (anthropics/claude-code#31908) <https://github.com/anthropics/claude-code/issues/31908#issuecomment-4109981728> It works for me when I use --remote-control (so start an actual claude code session) and run it in tmux — Reply to this email directly, view it on GitHub <https://github.com/anthropics/claude-code/issues/31908?email_source=notifications&email_token=AAOE6LTN6WT4AWAYEIQSQBT4SEPB3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJQHE4TQMJXGI4KM4TFMFZW63VGNVQW45LBNSSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4109981728>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAOE6LS5B4B6JNW2TDC4J7T4SEPB3AVCNFSM6AAAAACWKQQGR6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCMBZHE4DCNZSHA> . You are receiving this because you are subscribed to this thread.Message ID: @.***>

@brando90 claude --dangerously-skip-permissions --remote-control --name "always workin"

From DX perspective the remote control for me doesn't work well, because I am constantly switching between threads and just confirming prompts for simple tasks.
Has anyone tried workarounds by making a bigger allowlist for tools or so?

I also confirmed it works fine with these two options. We can close this issue now.

Is there any update on this?

I tried out the snippet suggested by @ryparker as follows:

sbx exec -it claude-claudexperiment claude --dangerously-skip-permissions --remote-control --name "MyTry" 

Upon running this, the Claude Code tui opens up and so does a tab in my remote control web interface with the name MyTry, but the interface session does not work at all. That's traceable to a error appearing in the tui which says:

 Remote Control disconnected · Transport closed: server rejected connection (code 403)

Is there any update on this? I tried out the snippet suggested by @ryparker as follows: `` sbx exec -it claude-claudexperiment claude --dangerously-skip-permissions --remote-control --name "MyTry" ` Upon running this, the Claude Code tui opens up and so does a tab in my remote control web interface with the name MyTry, but the interface session does not work at all. That's traceable to a error appearing in the tui which says: ` Remote Control disconnected · Transport closed: server rejected connection (code 403) ``

This way works: 'claude remote-control --permission-mode bypassPermissions'.

@andkorsh I tried it in the docker sandbox. It did not work.

@andkorsh I tried it in the docker sandbox. It did not work.

Could you please elaborate on "did not work"? Does it not start? Does it start but not skipping permission approvals? Does it even start without the bypass flag (in rc or a regular tui way)? If it starts, does it ask you to authenticate every time you start it?

Based on the error 403 you are getting, I believe your claude cli is not authenticated with your claude subscription. You might have to adjust your sandbox configuration to use persistent filesystem for the claude config folder and then run 'claude' once to authenticate, before running 'claude remote-control'.

Good test would be to run it either on a bare metal or inside a regular docker container, to eliminate problems related to the remote-control and it's bypass permissions flag and pinpoint the problem down to the sandbox environment.

It accepts the switch just fine, i.e. this works:

claude remote-control --no-create-session-in-dir --permission-mode bypassPermission

The problem is that when you then connect to that session from Claude Code desktop app and try to create a new session on that host, there's no "bypass permission" option in the selector in the GUI. It defaults to "Accept Edits" and can only be raised up to "Auto".