[FEATURE] Agent view dispatch should support --allow-dangerously-skip-permissions

Found 1 possible duplicate issue:

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

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

Not a duplicate. #39889 is about mobile/desktop dispatch ignoring the user's saved model and permission-mode preferences. This is about the CLI claude agents TUI having no mechanism at all to specify --allow-dangerously-skip-permissions when dispatching a session from the input.

+1 on this one.

Also: once you're inside a session that was dispatched from agent view (without the flag), Shift+Tab cycling doesn't include bypass permissions either (since its never started that way), so there's no in-session recovery.

Anything started from agent view is effectively locked out from using --dangerously-skip-permissions, which greatly reduces it's usefulness.

Simplest fix imo would have it be persistent. If I have a session running with certain permissions, I would rarely want to change them and would almost always prefer to start again with the last permissions used (and can easily cycle to something different inside the session in the few occasions when I don't).

Same here, agents is pretty much unusable for me without this feature, I guess I'll stick to 6 terminal tabs for now.

+1. Adding another shape of this same problem:

If I launch the parent session with claude --permission-mode bypassPermissions in a separate terminal
and then dispatch a child via /bg, the child still prompts — consistently for
every Bash call, and intermittently for other tool uses (file edits etc.). The
parent's mode doesn't inherit; the child falls back to defaultMode from
settings or the subagent's permissionMode frontmatter, per the docs.

That means even users who have already accepted bypass interactively (and
launched the parent with it) can't get a /bg-dispatched session to run
unattended without editing settings.json or creating a subagent definition for
what should be a one-off.

Two ways this could be solved, either would work for me:

1. Inherit from parent session — if the parent was launched with

bypassPermissions (and the user has accepted that mode previously), /bg
dispatches inherit it by default.

1. The flag/keybinding approach already proposed in the OP — e.g. a prefix

in the dispatch input, or Ctrl+P to cycle modes before Enter.

(1) feels like the least-surprise behavior since the parent shell explicitly
opted in. Running multiple agent-view windows is the main use case the feature
seems designed for, and right now each /bg dispatch needs the user back at
the keyboard for Bash calls in particular, which defeats the point.

Thanks for the request — landed.

claude agents now accepts --permission-mode, --model, and --effort to set defaults for every session you dispatch from that view:

claude agents --permission-mode plan --model opus --effort high

The active defaults appear in the footer below the dispatch input, and the header shows the model that dispatched sessions will use. The existing bypass/auto consent guard still applies — those modes are refused until you've accepted them once interactively.

Shipping in v2.1.142 (tomorrow).

@bogini, claude agents --allow-dangerously-skip-permissions does not work properly.

1. It defaults to bypass permissions for new chats, which is not the expected functionality for --allow-dangerously-skip-permissions. That is only expected for --dangeously-skip-permissions.
2. It does not allow you to choose bypass permissions for existing chats.

@jonathanlaniado Found that you can run claude agents --permission-mode bypassPermissions which allows you to dispatch agents with bypass permissions; FYI that any existing agents in the view will not inherit bypass permissions -- you will have to redispatch another agent to handle that task autonomously

@goutham1220 Right, --permission-mode bypassPermissions works for new sessions. The issue is specifically with --allow-dangerously-skip-permissions, which should only make bypass available in the Shift+Tab cycle without defaulting to it. Right now it behaves identically to --dangerously-skip-permissions, which defeats the purpose of having two separate flags.

The existing session limitation is also a gap since there's no way to opt an already-running session into bypass after the fact.

Filed #59406 to track both.

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.