#For the life in me I can't get moltbot to work

1 messages · Page 1 of 1 (latest)

ebon egret
#

Either it stops responding because maybe Anthropic it throttling. Or it doesn't remember anything. I keep starting over. Probably done it 12 times by now. Not sure how to make this thing work.

eager vectorBOT
#

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

reef cedarBOT
# ebon egret Either it stops responding because maybe Anthropic it throttling. Or it doesn't ...

Hey! I hear you — restarting 12 times is rough. 🦐 Let me help you diagnose this.

First, I need the version: moltbot --version

This matters a lot — version mismatches are the #1 cause of weird behavior like you're describing.

While you check that, here are the most common culprits:

For "stops responding" (possible throttling)

  • Check your Anthropic API quota in the console
  • Some plans have lower rate limits during high-traffic periods
  • If it's truly throttled, you'll see errors in the logs

For "doesn't remember"

  • Moltbot has short-term and long-term memory systems
  • Short-term = current conversation (should work automatically)
  • Long-term = stored memories (check ~/.moltbot/memory/ if configured)
ebon egret
#

when i go into terminal it doesn't show me

ebon egret
#

openclaw status

#

OpenClaw 2026.1.30 (76b5208)

reef cedarBOT
# ebon egret OpenClaw 2026.1.30 (76b5208)

Thanks! That's a recent version (Jan 30) — so it's not a stale install issue.

A few clarifying questions to narrow this down:

On "doesn't remember":

  1. Does it forget things within a conversation, or only after you restart Moltbot entirely?
  2. If you ask something early in a convo, then 10 messages later ask again — does it respond fresh?

On "stops responding":
3. When it stops, is the process still running (moltbot status)?
4. Do you see any error messages in the output, or just... silence?

Quick config check:
Run moltbot configure show — especially the memory section. Is it configured with a disk path, or disabled?

The most common memory issue: if long-term memory isn't set up, Moltbot only remembers the current session. A restart wipes short-term context too unless memory is persisted to disk.

#

What do you see in your config? 🦐

ebon egret
#

2 - it forgot our entire work from yesterday.
3. sometimes i get no output. i think this is related to teh model? using opus 4.5 or haiku 3.5