DEDUPED Hot AI repos. Real use cases. What people build. Get the Monday 5

How to switch IronClaw to another model provider safely with Ironclaw

Change the provider and model after onboarding without putting the key in your shell history.

Short answer: Check the current setup with ironclaw models status and ironclaw config list; then run ironclaw models set-provider openai --model gpt-5-mini (or your provider and model); Store the key with ironclaw config set openai.api_key; it prompts without echoing. All steps.

Who it is forA user moving from one LLM provider to another, or trying a cheaper model.

The problemPasting keys into config files or command lines leaves them in history and backups.

The outcomeIronClaw routed to the new provider, with the key stored through a hidden prompt.

What you need first

  • macOS, Linux or Windows (installer, MSI or WSL)
  • An API key for an LLM provider, entered in a hidden prompt
  • Rust 1.96+ and Node.js 22+ only for source builds

Steps

  1. Check the current setup with ironclaw models status and ironclaw config list
  2. Run ironclaw models set-provider openai --model gpt-5-mini (or your provider and model)
  3. Store the key with ironclaw config set openai.api_key; it prompts without echoing
  4. Rotate the WebUI token if needed with ironclaw config set webui.token --rotate

Prompt for your agent

Switch my nearai/ironclaw setup to <provider and model> using models set-provider and config set with the hidden prompt, then confirm with models status.

Caveat.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for nearai/ironclaw and "Switch IronClaw to another model provider safely"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer