Unhandled promise rejection | Friends of the Crustacean 🦞🤝 | Page 1

brazen latch Jan 29, 2026, 12:22 PM

#

keep getting this after updating for kimi and entering my api. using minimax as well. why is this happening?

[clawdbot] Unhandled promise rejection: Error: Unhandled API in mapOptionsForApi: undefined
at mapOptionsForApi (file:///opt/homebrew/lib/node_modules/clawdbot/node_modules/@mariozechner/pi-ai/src/stream.ts:471:10)
at streamSimple (file:///opt/homebrew/lib/node_modules/clawdbot/node_modules/@mariozechner/pi-ai/src/stream.ts:218:26)
at streamAssistantResponse (file:///opt/homebrew/lib/node_modules/clawdbot/node_modules/@mariozechner/pi-agent-core/src/agent-loop.ts:233:25)
at runLoop (file:///opt/homebrew/lib/node_modules/clawdbot/node_modules/@mariozechner/pi-agent-core/src/agent-loop.ts:141:20)
at file:///opt/homebrew/lib/node_modules/clawdbot/node_modules/@mariozechner/pi-agent-core/src/agent-loop.ts:51:3

queen gazelleBOT Jan 29, 2026, 12:22 PM

#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

brazen latch Jan 29, 2026, 12:23 PM

#

@waxen nacelle please help.

waxen nacelleBOT Jan 29, 2026, 12:23 PM

#

brazen latch keep getting this after updating for kimi and entering my api. using minimax as ...

This error indicates Clawdbot received an undefined/unrecognized API type when trying to route your request. Here's how to troubleshoot:

Quick Checks

Verify your config - Make sure you haven't accidentally deleted or corrupted the api section. Check for:
- Missing closing brackets or commas
- Extra/missing quotes around API names
- Using old config keys from a previous version
Test API keys individually - Try one provider at a time:
```
clawdbot model --list
```
This shows available models and can reveal config issues.
Run a version check:

#

   clawdbot --version

Sometimes updates don't fully apply until you restart the gateway.

Common Causes

Kimi support was just added - your config might have an old structure that's incompatible
Misspelled API name in your config (e.g., "minimax" vs "MiniMax" - check case sensitivity)
Corrupted config file - try renaming ~/.clawdbot/config.json5 to backup and letting it regenerate with defaults, then reconfigure

Next Steps

Can you share:

Your clawdbot version (clawdbot --version)
Your relevant config (api section) - remove the actual API keys but show the structure

#

This will help pinpoint whether it's a config format issue or a Kimi-specific compatibility problem.

waxen nacelleBOT Jan 29, 2026, 12:24 PM

#

brazen latch <@1457407575476801641> please help.

Hey! 🦐 Let me help you debug this. That error means Clawdbot is getting undefined when trying to figure out which API to use.

Immediate Steps

Check your version:
```
clawdbot --version
```
If you're on an old version, run:
```
clawdbot gateway update
```
Test with just one API - Comment out/remove Kimi from your config and test with Minimax alone. Does it work then?
Verify config structure - Here's a working example format:

#

   api: {
     kimi: {
       apiKey: "your-key-here",
       model: "moonshot-v1-8k" // or moonshot-v1-32k, moonshot-v1-128k
     },
     minimax: {
       apiKey: "your-minimax-key",
       model: "MiniMax-M2.1"
     }
   }

Try resetting:
```
clawdbot gateway restart
```

#

If That Doesn't Work

Run this and share the output (hide API keys):

clawdbot config.get api

This will show us exactly what Clawdbot is seeing. The "undefined" suggests either a bad config entry or a Kimi integration bug that just shipped. Which version are you on?

brazen latch Jan 29, 2026, 12:25 PM

#

2026.1.24-3

where can i find my config structure

waxen nacelleBOT Jan 29, 2026, 12:26 PM

#

brazen latch 1. 2026.1.24-3 where can i find my config structure

Version is good! Here's where your config lives:

Config Locations

macOS (Homebrew like you have):

~/.clawdbot/config.json5

Linux:

~/.config/clawdbot/config.json5

Quick Commands

Check your current API config:

#

clawdbot config.get api

Edit the config:

clawdbot config.edit

(Or open the file directly in your editor of choice)

What to Look For

Make sure your Kimi/Minimax entries look something like this:

api: {

#

  kimi: {
    apiKey: "sk-...",
    model: "moonshot-v1-8k"  // Check this matches actual Kimi model names
  },
  minimax: {
    apiKey: "...",
    model: "MiniMax-M2.1"
  }
}

Common pitfalls:

model value might be wrong for Kimi (it's not "kimi", it's one of: moonshot-v1-8k, moonshot-v1-32k, moonshot-v1-128k)
Extra commas or missing quotes
Case sensitivity on "MiniMax" vs "minimax"

#

Run clawdbot config.get api and paste the output here (hide your API keys) and I'll spot the issue!

brazen latch Jan 29, 2026, 12:27 PM

#

clawdbot config.edit
clawdbot config.get api

invalid commands

waxen nacelleBOT Jan 29, 2026, 12:28 PM

#

brazen latch clawdbot config.edit clawdbot config.get api invalid commands

Ah, got it! Let me help you find the commands and file directly.

Find the Config File

cat ~/.clawdbot/config.json5

Or if that doesn't exist:

find ~/.clawdbot -name "*.json5" -o -name "*.json"

Quick Fix - Edit Manually

Open it directly:

#

nano ~/.clawdbot/config.json5
# or
vim ~/.clawdbot/config.json5
# or
code ~/.clawdbot/config.json5  # if you have VS Code

Check Available Commands

clawdbot --help

This will show you what commands your version supports.

#

While you do that, share:

What OS are you on? (macOS/Linux?)
Did you install via Homebrew (brew install clawdbot) or another way?

That'll help me get you the exact right commands. The "invalid command" suggests either the CLI is structured differently on your install, or there's a path issue.

brazen latch Jan 29, 2026, 12:29 PM

#

i updated my models API key via clawdbot config. am i creating conflict?

#

@waxen nacelle

waxen nacelleBOT Jan 29, 2026, 12:30 PM

#

I can't see the image content directly in this chat. Can you paste the text content of your config here? Specifically the api section.

Something like:

{
  api: {
    kimi: { ... },
    minimax: { ... }
  }
}

Or just share what you see in that file and I'll spot the issue!

waxen nacelleBOT Jan 29, 2026, 12:30 PM

#

brazen latch <@1457407575476801641>

Hey! I see you shared a screenshot but I can't view images in this chat interface.

Can you copy and paste the text from your config file here? Just the api section would be fine.

The error Unhandled API in mapOptionsForApi: undefined almost always means:

A missing comma
A typo in the API name
An unsupported model name

Paste what you have and I'll find it immediately! 🦐

brazen latch Jan 29, 2026, 12:56 PM

#

@waxen nacelle

waxen nacelleBOT Jan 29, 2026, 12:57 PM

#

brazen latch <@1457407575476801641>

I see you! No worries, let's get this sorted. 🦐

I really need you to copy/paste the text - I can't access the screenshot.

Just run this and send me the output:

cat ~/.clawdbot/config.json5

Or if you can type it out manually, the api section should look like:

api: {
  kimi: {
    apiKey: "sk-..."
    model: "moonshot-v1-8k"
  },

#

  minimax: {
    apiKey: "..."
    model: "MiniMax-M2.1"
  }
}

The most likely culprit: Kimi model names need to be one of:

moonshot-v1-8k
moonshot-v1-32k
moonshot-v1-128k

Not "kimi", not "KimAI", not just any random string.

Can you paste your config and I'll find exactly what's wrong?

brazen latch Jan 30, 2026, 2:59 AM

#

waxen nacelle ```json5 minimax: { apiKey: "..." model: "MiniMax-M2.1" } } ``` **T...

No such file or directory

#

how do i reset my config without losing my memory?

#

@waxen nacelle

waxen nacelleBOT Jan 30, 2026, 3:04 AM

#

brazen latch how do i reset my config without losing my memory?

Easy! Your memory is stored separately from config.

Backup & Reset

# 1. Backup your current config
cp ~/.clawdbot/config.json5 ~/.clawdbot/config.json5.backup

# 2. Remove the config (will regenerate defaults)
rm ~/.clawdbot/config.json5

# 3. Restart clawdbot to generate new config
clawdbot gateway restart

After Restart

#

# 4. Check the new default config structure
cat ~/.clawdbot/config.json5

Then just add your API keys back:

api: {
  kimi: {
    apiKey: "sk-your-key-here",
    model: "moonshot-v1-8k"
  },
  minimax: {
    apiKey: "your-minimax-key",
    model: "MiniMax-M2.1"
  }

#

Verify Memory is Safe

Your memories are in ~/.clawdbot/memory/ - that folder stays untouched.

ls ~/.clawdbot/memory/

Good to go! Let me know if you hit any issues. 🦐

waxen nacelleBOT Jan 30, 2026, 3:05 AM

#

brazen latch <@1457407575476801641>

Hey! Did the reset work, or do you need help with the commands?

If you're stuck, just paste what you have in your config now and I'll help fix it directly. No reset needed if we can spot the issue! 🦐

brazen latch Jan 30, 2026, 1:00 PM

#

i tried kimi code it cannot be configured properly. ive set up the api key via clawdbot config and under moonshot for models

waxen nacelleBOT Jan 30, 2026, 1:04 PM

#

brazen latch i tried kimi code it cannot be configured properly. ive set up the api key via c...

This is a known bug tracked in GitHub issue #1695. The error happens because the api field from provider config isn't properly reaching the stream code.

Good news: There's already a fix merged in PR #3322 that should be in the next release.

Temporary workaround for now:

For LM Studio users - explicitly set api in your provider config:

"models": {
  "providers": {
    "lmstudio": {
      "baseUrl": "http://127.0.0.1:1234/v1",
      "apiKey": "LMSTUDIO_KEY",
      "api": "openai-completions",
      "models": [...]
    }

#

}
}

Make sure your primary model uses the provider prefix, e.g.:

"agents": {
  "defaults": {
    "model": {
      "primary": "lmstudio/minimax-m2.1-gs32"
    }
  }
}

The issue affects any custom/OpenAI-compatible provider (LM Studio, Kimi/Moonshot, local models) when the api field isn't explicitly declared or isn't being read from config properly.

#

To get the fix now: Watch for version 2026.1.24+ or update when available. The PR merges the provider config api field into the registry model properly.

https://github.com/moltbot/moltbot/pull/3322

brazen latch Jan 30, 2026, 1:10 PM

#

how do i reintate my memory and skills

#

{"0":"{"subsystem":"gateway/ws"}","1":{"cause":"invalid-handshake","handshake":"failed","durationMs":13,"lastFrameType":"req","lastFrameMethod":"connect","lastFrameId":"C323D20E-82B1-4286-99A1-

getting these type of errors. whats going on

waxen nacelleBOT Jan 30, 2026, 1:14 PM

#

brazen latch {"0":"{\"subsystem\":\"gateway/ws\"}","1":{"cause":"invalid-handshake","handshak...

That's a WebSocket handshake failure - the gateway can't establish a connection. This usually means:

Gateway crashed or restarted - Run clawdbot gateway status to check
Port conflict - Something else is using the gateway port
Network issue - Especially if connecting remotely

Quick checks:

# Check if gateway is running
clawdbot gateway status

# If not running, start it
clawdbot gateway start

# If stuck, force restart

#Unhandled promise rejection

Quick Checks

Common Causes

Next Steps

Immediate Steps

If That Doesn't Work

Config Locations

Quick Commands

What to Look For

Find the Config File

Quick Fix - Edit Manually

Check Available Commands

Backup & Reset

After Restart

Verify Memory is Safe