let5see/clawdbot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refactor: rename clawdbot to moltbot with legacy compat

Browse Source
This commit is contained in:
Peter Steinberger
2026-01-27 12:19:58 +00:00
parent 83460df96f
commit 6d16a658e5
1839 changed files with 11250 additions and 11199 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
docs/platforms/mac/bundled-gateway.md
View File

@@ -1,24 +1,24 @@
---
summary: "Gateway runtime on macOS (external launchd service)"
read_when:
- Packaging Clawdbot.app
- Packaging Moltbot.app
- Debugging the macOS gateway launchd service
- Installing the gateway CLI for macOS
---
# Gateway on macOS (external launchd)
Clawdbot.app no longer bundles Node/Bun or the Gateway runtime. The macOS app
expects an **external** `clawdbot` CLI install, does not spawn the Gateway as a
Moltbot.app no longer bundles Node/Bun or the Gateway runtime. The macOS app
expects an **external** `moltbot` CLI install, does not spawn the Gateway as a
child process, and manages a per‑user launchd service to keep the Gateway
running (or attaches to an existing local Gateway if one is already running).
## Install the CLI (required for local mode)
You need Node 22+ on the Mac, then install `clawdbot` globally:
You need Node 22+ on the Mac, then install `moltbot` globally:
```bash
npm install -g clawdbot@<version>
npm install -g moltbot@<version>
```
The macOS app’s **Install CLI** button runs the same flow via npm/pnpm (bun not recommended for Gateway runtime).
@@ -34,16 +34,16 @@ Plist location (per‑user):
Manager:
- The macOS app owns LaunchAgent install/update in Local mode.
- The CLI can also install it: `clawdbot gateway install`.
- The CLI can also install it: `moltbot gateway install`.
Behavior:
- “Clawdbot Active” enables/disables the LaunchAgent.
- “Moltbot Active” enables/disables the LaunchAgent.
- App quit does **not** stop the gateway (launchd keeps it alive).
- If a Gateway is already running on the configured port, the app attaches to
it instead of starting a new one.
Logging:
- launchd stdout/err: `/tmp/clawdbot/clawdbot-gateway.log`
- launchd stdout/err: `/tmp/moltbot/moltbot-gateway.log`
## Version compatibility
@@ -53,15 +53,15 @@ incompatible, update the global CLI to match the app version.
## Smoke check
```bash
clawdbot --version
moltbot --version
CLAWDBOT_SKIP_CHANNELS=1 \
CLAWDBOT_SKIP_CANVAS_HOST=1 \
clawdbot gateway --port 18999 --bind loopback
moltbot gateway --port 18999 --bind loopback
```
Then:
```bash
clawdbot gateway call health --url ws://127.0.0.1:18999 --timeout 3000
moltbot gateway call health --url ws://127.0.0.1:18999 --timeout 3000
```