How do i switch from claude to minimax?

[upbeat hatch]

i have my API key ready how do i do that?

@wispy reef do you know?

@wispy reef checking in?

[wispy reef]

Hey Max! 🦐 To switch from Claude to MiniMax, you have a few options:

In chat (session-only):

/model minimax/MiniMax-M2.1

CLI (permanent):

clawdbot models set minimax/MiniMax-M2.1

Config file (~/.clawdbot/agents/<agentId>/agent.json5):

{
  agents: {

    defaults: {
      model: { primary: "minimax/MiniMax-M2.1" }
    }
  }
}

MiniMax is great for writing and "vibes" according to the docs! 🎯

If you want to test it first without committing, use /model in the chat — it only affects the current session.

Let me know if you need help with anything else! 🦐

[upbeat hatch]

can i have it so that it defaults to claude but then falls back to minimax when claude returns error or runs out of capacity?

[wispy reef]

Absolutely! You can configure fallbacks like this:

CLI (easiest):

# Set Claude as primary, MiniMax as fallback
clawdbot models set anthropic/claude-sonnet-4-5
clawdbot models fallbacks add minimax/MiniMax-M2.1

Or in one go:

clawdbot models set anthropic/claude-sonnet-4-5 --fallback minimax/MiniMax-M2.1

Config file:

{
  agents: {
    defaults: {
      model: {
        primary: "anthropic/claude-sonnet-4-5",
        fallbacks: ["minimax/MiniMax-M2.1"]
      }
    }
  }
}

Clawdbot will try Claude first, and if it hits an error or runs out of capacity, it'll automatically fall back to MiniMax. The order in fallbacks matters — it's a priority chain. 🔥

[upbeat hatch]

ok i did it

how do i provide my minimax api key?

[wispy reef]

You can provide your MiniMax API key in a few ways:

Option 1: Environment variable (recommended)

export MINIMAX_API_KEY="your-api-key-here"

Option 2: Add to ~/.clawdbot/.env

MINIMAX_API_KEY=your-api-key-here

Option 3: In your config file (~/.clawdbot/agents/<agentId>/agent.json5)

{
  env: {

    vars: {
      MINIMAX_API_KEY: "your-api-key-here"
    }
  }
}

After setting it, restart the gateway:

clawdbot gateway restart

Then verify with:

clawdbot models status

It should show MiniMax auth as configured! 🎯

[upbeat hatch]

how do i shut down imessage as a connection?

should minimax api key appear also in auth-profiles.json?

[wispy reef]

Not automatically! Here's the deal:

auth-profiles.json stores:

• OAuth tokens (auto-synced from Claude Code CLI, Codex CLI, etc.)
• Explicitly stored API keys

Environment variables (like MINIMAX_API_KEY) are read directly from:

• .env files
• Process environment
• Config env block

So if you're using MINIMAX_API_KEY as an env var, it stays in your env — it doesn't get written to auth-profiles.json. That's actually better for security! 🔐

To verify it's working:

clawdbot models status

It should show MiniMax under "auth candidates" without needing to touch auth-profiles.json directly.

If you do want it in auth-profiles.json for some reason, you could use clawdbot config set or manually add it, but env vars are the cleaner approach!

[upbeat hatch]

how do i shut down imessage as a connection?

[wispy reef]

Just set enabled: false for the iMessage channel:

CLI (quickest):

clawdbot config set channels.imessage.enabled false

Or manually in ~/.clawdbot/clawdbot.json:

{
  channels: {
    imessage: {
      enabled: false
    }
  }
}

Then restart:

clawdbot gateway restart

That's it! The iMessage channel will be disabled. 🚀

[tight rain]

@wispy reef Subject: Issues with Google Antigravity token expiry & configuration questions

Hi support team,

I'm running Clawdbot (v2026.1.24-3) on macOS and I'm facing a few issues regarding the google-antigravity provider and general configuration. Could you please help clarify the following?

1. Antigravity Token Instability I'm using the google-antigravity/claude-opus-4-5-thinking model. It works great initially, but the authentication token seems to expire very quickly (often within an hour).

Symptoms: The gateway is running, but requests fail with "No API key found" or similar auth errors after a short period.

Current Workaround: I have to frequently stop the gateway and run clawdbot doctor to refresh the OAuth tokens, then restart the gateway.

Question: Is there a way to keep the session alive longer or auto-refresh the token without manual intervention?

2. Disabling iMessage Connection I want to completely disable the iMessage integration so the bot stops listening to/intercepting my messages.

Question: What is the correct config command? Is clawdbot config set channels.imessage.enabled false sufficient, or do I need to remove the configuration block entirely?

3. MiniMax API Key Storage I am also setting up the MiniMax provider.

Question: Can I just set MINIMAX_API_KEY as an environment variable? Does it need to be present in auth-profiles.json, or will the bot automatically pick it up from the environment?

Context / Recent Logs:

I previously encountered a "Missing workspace template: AGENTS.md" error, which I resolved by running npm install -g clawdbot@latest.

My current config uses agents.defaults.model.primary.

Thanks for your help!

[wispy reef]

Hey SHAW! 🦐 Let me tackle these:

1. Antigravity Token Expiry
Unfortunately, OAuth tokens for google-antigravity do expire and there's no auto-refresh built in. Your options:

• Use an API key instead (more stable)
• Keep using clawdbot doctor to refresh when needed
• The CLI auto-sync from gcloud credentials might help if you have those set up

2. Disabling iMessage
Yes, clawdbot config set channels.imessage.enabled false is sufficient! No need to remove the whole block.

3. MiniMax API Key
Just export MINIMAX_API_KEY="your-key" — env vars work perfectly. No need for auth-profiles.json. The bot picks it up automatically.

Quick checklist: