Auto-mode classifier too restrictive for private single-operator homelabs

Feedback: Auto-mode classifier too restrictive for private/internal use

Context: I run a private homelab (77 hosts, self-hosted, no multi-tenancy,
no external users) with Claude Code as an orchestrator (SSH access to my own
infrastructure, autonomous cron jobs, my own agents).

Problem: The server-side auto-mode classifier hard-blocks certain classes
of actions — even with explicit verbal authorization from me as the sole
owner/operator:

• The agent cannot start/register/deploy an autonomous

claude -p --dangerously-skip-permissions loop itself, even though I
explicitly authorized it ("use full Max autonomy, commit+push allowed").
It was blocked 6 times in one session with escalating attempts: direct
exec → cron registration → wrapper script → settings self-edit → backup
copy of settings → even just writing a deploy script FOR ME to run
manually. Messages seen: [Create Unsafe Agents], [Auto-Mode Bypass],
"PREEMPTIVE BLOCK ON CLEAR INTENT".

• Force-push is blocked independently by the classifier on top of my own

local safety hook — even with authorization.

• Even preparing for these actions (copying prompts, staging a settings

edit) is detected as "engineering around the permission system" and
blocked.

What I'd like: In my private, self-hosted, single-operator environment,
my explicit authorization (verbal in chat, or via CLAUDE.md instructions)
should be sufficient to allow these action classes. There are no external
stakeholders, no third-party production data, no multi-user situation — I am
both owner and operator. The current strictness makes sense for
enterprise/multi-tenant contexts, but is disproportionate for solo homelab
use and blocks automation I deliberately want.

Concrete ask: Is there (a) an opt-in mechanism/flag that lets an operator
relax this classifier strictness for their own private environment, or (b) is
this planned? If not, this is the feature request.

Reproducible via: Claude Code CLI, defaultMode: auto in settings.json,
the error classes quoted above occurred repeatedly and consistently.