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

[acrookston]

Summary

When running Claude Code in a Docker sandbox, I'd like to combine remote-control with --dangerously-skip-permissions so I can monitor and control sandboxed agents from the web or mobile app.

Current behavior

The two features are incompatible:

• claude remote-control --dangerously-skip-permissions → Error: Unknown argument: --dangerously-skip-permissions
• claude --dangerously-skip-permissions remote-control → doesn't start remote control

Expected behavior

A single command that enables both, e.g.:

claude remote-control --dangerously-skip-permissions --name my-sandbox

Use case

Running multiple isolated Claude agents in Docker containers (each with its own git clone and branch). --dangerously-skip-permissions is needed because the containers are sandboxed. remote-control would let me monitor and steer each agent from the web/mobile UI without needing terminal access to the container.

[github-actions]

Found 1 possible duplicate issue:

1. Remote Control: mobile app shows permission prompts despite --dangerously-skip-permissions #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

[robinsadeghpour]

same issue here

[brando90]

agreed! This feature is highly needed!

[1st8]

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

[maribox]

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

[brando90]

What works?

…

On Mon, Mar 23, 2026, 6:40 AM Marius Bosler ***@***.***> wrote: *maribox* left a comment (anthropics/claude-code#31908) <#31908 (comment)> 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 <#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: ***@***.***>

[ryparker]

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

[haynzz]

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?

[sundaycrafts]

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

[sudeepan]

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)

[andkorsh]

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'.

[sudeepan]

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