--dangerously-load-development-channels should support skipping the confirmation dialog

Problem

Every time I launch claude --dangerously-load-development-channels server:my-channel, the startup dialog forces me to manually select "I am using this for local development" before Claude Code proceeds. There's no way to persist this choice or skip it via a flag.

For workflows that frequently restart Claude Code with the same local channel server (e.g. a custom dispatch tool that launches multiple agents), this adds unnecessary friction — especially since the user has already opted in by typing --dangerously-load-development-channels in the first place.

Current behavior

1. Run claude --dangerously-load-development-channels server:my-channel
2. Dialog appears: "WARNING: Loading development channels"
3. Must manually select option 1 and press Enter
4. Claude Code starts

This happens on every launch, no persistent approval.

Expected behavior

One of:

• A --yes flag (or similar) that auto-accepts the dialog: claude --dangerously-load-development-channels server:my-channel --yes
• A persistent per-server approval stored in ~/.claude/settings.json or similar, so the dialog is shown once and remembered
• Respect --dangerously-skip-permissions as an implicit acceptance (the user is already opting out of safety prompts)

Use case

I'm building a TUI that launches Claude Code agents in separate terminal windows with --dangerously-load-development-channels server:my-channel for coordination. Each agent launch requires manual intervention to click through the dialog, which breaks the automation flow.

server: entries can't use --channels (blocked by the plugin-only allowlist), so --dangerously-load-development-channels is the only option for local MCP channel servers.

Environment

• Claude Code v2.1.90
• Windows 11