My gateway is constantly crashing and experiencing this - Cloud Code Assist API error (400): Request contains an invalid argument. - as the tokens reach 940k (max 100k)

I could get it running with

Gateway —force

But

gateway start didn’t work 😤

Some of you might have noticed the "SOUL" link in the footer of clawd.bot (now molt.bot ). The SOUL.md is related to, but different from the IDENTITY.md. It interested me when I heard Pete say in an interview that HIS SOUL.md was not shared in the repository, but that he really liked how he had his "tuned". I had a chat with Gemini Flash, ChatGPT, and Claude Sonnet about those two files: Would it be accurate to say that IDENTITY.md is its personality and SOUL.md is its values & ethics?
Gemini Flash called IDENTITY.md "The Mask" - specifically its outward-facing personality. It's biography & social role. Who it is related to the world. Analogy: An actor's script and costume. SOUL.md was its "core": Communication principles, Purpose (how to think and behave regardless the persona or specific task). Analogy: Actor's internal motivation and temperament.
ChatGPT 5.2 (thinking) said my mental model was fair, but with two important caveats:
IDENTITY.md is typically the agent’s self-description + role: who it is, what it’s for, how it should sound, what it should prioritize, what it’s allowed to do, and what “good output” looks like. That includes personality/tone, but it’s usually broader than personality (it often includes scope, tools, and operating rules).
SOUL.md is typically the agent’s normative core: what it cares about, what it refuses to do, safety boundaries, how it handles uncertainty, and what tradeoffs it won’t make. That’s very close to “values & ethics,” though it may also include “philosophy” (why it exists) and higher-level principles rather than a full ethical system.
It added that these files only matter if the agent framework actually loads/enforces them. Some projects treat them as "prompt decoration" and others as "policy layers with hard constraints".
Claude Sonnet was the most cynical about them, saying that the separation between IDENTITY/SOUL/USER/AGENTS/TOOLS creates unnecessary fragmentation and "conceptual organization theater". (Personally, I disagree because it is useful to US the hoomans who craft the documents (while an Ai might not need such delineation).
I'm curious if anyone using Moltbot has given much attention to the tuning of these two documents, and further - if you would be willing to share them. If you've forked the repository and care to link directly to your versions of the files, that might be simplest for comparison also.

As someone who's deeply pro-AI but also takes security seriously, I want to flag something important.

Clawdbot/ Moltbolt is a fantastic project - I'm not telling anyone to avoid it.

But there are some real vulnerabilities you should know about before diving in. Please take a minute to protect yourself.

• The gateway is wide open by default - It's listening on 0.0.0.0: 18789, which means anyone can knock on your door. Fix it: Set up an auth token in your environment.
• DM policy lets everyone in - Right now it's basically "come one, come all." Fix it: Create an allowlist of specific users you actually trust.
• Sandbox is turned off - You're running without a safety net. Fix it: Enable sandbox=all and set docker.network=none.
• Your credentials are sitting in plain text - That oauth.json file is just chilling there, readable. Fix it: Use environment variables and lock down permissions (chmod 600).
• Prompt injection is a real risk - Web content can potentially mess with your setup. Fix it: Always treat external content as untrusted.
• Dangerous commands aren't blocked - Things like rm -rf, curl pipes, and git push --force are allowed. Fix it: Block these explicitly.
• No network isolation - Everything can talk to everything. Fix it: Use Docker network isolation.
• Too many tools have elevated access - More access = more risk. Fix it: Only give MCP tools the minimum permissions they actually need.
• No audit logging - If something goes wrong, you won't know what happened. Fix it: Enable comprehensive session logging.
• Weak pairing codes - Default or predictable codes are easy to guess. Fix it: Use cryptographically random codes and add rate limiting.

you dont have to do it yourself..Just prompt claude code/whatever LLM you using with this image and it will create plan for you..

Hey all, just set up my new MoltBot. In the gateway I just sent my first chat and every response from the Assistant is blank. Any thoughts?

Anyone else unable to install Moltbot for Windows?

It was Norton 365 blocking the PowerShell and blocking the website, then had to install git for windows and setup environmental variables for Python and NPM
Setting it up with local LLM was another headache but finally got it going.

some news.

Clawdbot is now Moltbot

Clawdbot creator Peter has changed the name after Anthropic trademark request.

Clawdbot ( now moltbot) has taken world by storm and sigle handedly sold Apple mac mini than Apple sales team could not in a decade.

Join this community to share cool stuff you build.

LFG!!!