Feature: persistent --channels config in settings.json

Summary

Currently, --channels must be passed as a CLI flag every time a session starts. There is no way to persist channel configuration so that a plugin (e.g., plugin:discord@claude-plugins-official) is automatically enabled.

Use Case

Users who regularly use Discord/Telegram channels want them active by default without remembering the flag. The current workaround is a shell alias:

alias claude-discord='claude --channels plugin:discord@claude-plugins-official'

This works but is fragile — it doesn't compose with other flags, doesn't help IDE integrations, and isn't discoverable.

Proposal

Allow configuring default channels in settings.json (user or project level):

{
  "channels": [
    "plugin:discord@claude-plugins-official"
  ]
}

The CLI flag would still override/extend this list. This preserves the opt-in security model while removing the ergonomic friction for daily users.

Alternatives Considered

• Shell alias: Works but not composable or discoverable
• Wrapper script: Same limitations
• tmux automation: Overcomplicated for the common case

Environment

• Claude Code v2.1.81
• macOS