Restrictive permissions / no bypass permissions on Claude Projects

What happened
What happened:
In Claude Projects / Remote Control sessions (folder-connected cloud threads), the session is forced into Auto mode with no option to switch to Bypass permissions (--dangerously-skip-permissions).

The Auto mode classifier is also overly conservative and blocks SSH, production deploy scripts, and other commands that previously worked — even when explicit allow rules exist in project settings / settings.json. Compound commands, slight variations, or commands that follow other actions frequently fall through to the classifier and get blocked. It evaluates calls in isolation and doesn’t seem to respect prior approvals given in the same thread.

What I expected:

Ability to set Bypass permissions for a Project / Remote Control thread (at least when starting from the terminal), the same way it’s possible in regular Claude Code sessions.
Allow rules in settings to actually exempt the listed commands (including reasonable variations) from the classifier.
Or, at minimum, the classifier to ask instead of hard-blocking when it is uncertain, and to honor prior chat approvals.
This is currently making production and remote workflows significantly more painful than regular Claude Code sessions. Happy to provide specific command examples or thread IDs if useful.

Environment

• Filed from: Report a problem in Claude Code