Allow an opt-in to let Claude Code write secret values to credential stores (blocks remote/mobile workflows)

What happens

Claude Code refuses to run any command that writes a raw secret value into a credential store, even when I provide the value and explicitly authorize it in the session. Examples it blocks:

• gh secret set <SECRET_NAME> --env <env> --repo <org>/<repo> (with the value)
• Snowflake ALTER SECRET ... SET PASSWORD = '...'

It will run essentially everything else (SQL DDL, grants, gh/snow/terraform, deploys), but this one shape is a hard stop that I cannot authorize past.

Why it's a problem

I frequently drive Claude Code from my phone over a remote connection. When it hits this block, the only remediation is "go to your computer and run it yourself" — which defeats the point of the remote session and stops an otherwise fully-automated workflow dead. I've used Claude for 3+ years and this has become a recurring friction.

Request

Please make this configurable / opt-in rather than an absolute block — e.g. a permission rule or settings flag (like existing allow-rules) that lets a trusted session run secret-writing commands the user has explicitly provided. Removing it outright is fine too, but an opt-in would preserve the safety default for those who want it while unblocking the rest of us.

Environment

• Claude Code (Opus 4.8), driving a remote session from mobile