Dynamic settings file

[iuriguilherme]

Implement a way to load different settings.json files. This is handy for multiple bulk settings such as authentication to different LLM providers.

1. A cli option to choose which settings file to load during startup, allowing the user to choose which settings to load:

openclaude --settings .claude/settings/openrouter.json

2. A slash command to load a new settings file, overwrite settings and reload

[Vasanthdev2004]

This would be pretty useful.

Right now, switching between substantially different provider setups can be awkward because users are really switching an entire bundle of state at once:

• provider
• model
• auth
• routing
• local vs cloud preferences
• possibly MCP/plugin-related defaults too

A --settings <path> option, plus an in-app reload/switch flow, would make multi-profile use much cleaner.

I would probably think about this as a profile/config selection feature rather than only “load a different JSON file,” because from a product point of view users usually want named environments such as:

• local-ollama
• openrouter-fast
• codex-work
• gemini-exp

But the use case here makes a lot of sense.

[sankrant]

I'm a little confused, does openclaude store its global settings differently from claude, how to separate claude cli settings from openclaude.