diff --git a/.github/dependabot.yml b/.github/dependabot.yml index c0e1d465b..829604b4c 100644 --- a/.github/dependabot.yml +++ b/.github/dependabot.yml @@ -64,9 +64,9 @@ updates: - patch open-pull-requests-limit: 5 - # Swift Package Manager - shared ClawdbotKit + # Swift Package Manager - shared MoltbotKit - package-ecosystem: swift - directory: /apps/shared/ClawdbotKit + directory: /apps/shared/MoltbotKit schedule: interval: weekly cooldown: diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 3ef430e67..3bda11de7 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -76,7 +76,7 @@ jobs: command: pnpm lint - runtime: node task: test - command: pnpm test + command: pnpm canvas:a2ui:bundle && pnpm test - runtime: node task: build command: pnpm build @@ -88,7 +88,7 @@ jobs: command: pnpm format - runtime: bun task: test - command: bunx vitest run + command: pnpm canvas:a2ui:bundle && bunx vitest run - runtime: bun task: build command: bunx tsc -p tsconfig.json @@ -188,6 +188,7 @@ jobs: runs-on: blacksmith-4vcpu-windows-2025 env: NODE_OPTIONS: --max-old-space-size=4096 + CLAWDBOT_TEST_WORKERS: 1 defaults: run: shell: bash @@ -200,7 +201,7 @@ jobs: command: pnpm lint - runtime: node task: test - command: pnpm test + command: pnpm canvas:a2ui:bundle && pnpm test - runtime: node task: build command: pnpm build diff --git a/.github/workflows/install-smoke.yml b/.github/workflows/install-smoke.yml index 16eba4eed..0347c7810 100644 --- a/.github/workflows/install-smoke.yml +++ b/.github/workflows/install-smoke.yml @@ -37,5 +37,5 @@ jobs: CLAWDBOT_NO_ONBOARD: "1" CLAWDBOT_INSTALL_SMOKE_SKIP_CLI: "1" CLAWDBOT_INSTALL_SMOKE_SKIP_NONROOT: ${{ github.event_name == 'pull_request' && '1' || '0' }} - CLAWDBOT_INSTALL_SMOKE_PREVIOUS: "2026.1.11-4" + CLAWDBOT_INSTALL_SMOKE_SKIP_PREVIOUS: "1" run: pnpm test:install:smoke diff --git a/.gitignore b/.gitignore index d3fdee6b5..9dc547c9c 100644 --- a/.gitignore +++ b/.gitignore @@ -19,14 +19,14 @@ ui/test-results/ # Bun build artifacts *.bun-build apps/macos/.build/ -apps/shared/ClawdbotKit/.build/ +apps/shared/MoltbotKit/.build/ **/ModuleCache/ bin/ bin/clawdbot-mac bin/docs-list apps/macos/.build-local/ apps/macos/.swiftpm/ -apps/shared/ClawdbotKit/.swiftpm/ +apps/shared/MoltbotKit/.swiftpm/ Core/ apps/ios/*.xcodeproj/ apps/ios/*.xcworkspace/ diff --git a/.swiftformat b/.swiftformat index 6622d0b01..fd8c0e631 100644 --- a/.swiftformat +++ b/.swiftformat @@ -48,4 +48,4 @@ --allman false # Exclusions ---exclude .build,.swiftpm,DerivedData,node_modules,dist,coverage,xcuserdata,Peekaboo,Swabble,apps/android,apps/ios,apps/shared,apps/macos/Sources/ClawdisProtocol,apps/macos/Sources/ClawdbotProtocol +--exclude .build,.swiftpm,DerivedData,node_modules,dist,coverage,xcuserdata,Peekaboo,Swabble,apps/android,apps/ios,apps/shared,apps/macos/Sources/MoltbotProtocol diff --git a/.swiftlint.yml b/.swiftlint.yml index 12500f4c7..b56228801 100644 --- a/.swiftlint.yml +++ b/.swiftlint.yml @@ -18,7 +18,7 @@ excluded: - coverage - "*.playground" # Generated (protocol-gen-swift.ts) - - apps/macos/Sources/ClawdbotProtocol/GatewayModels.swift + - apps/macos/Sources/MoltbotProtocol/GatewayModels.swift analyzer_rules: - unused_declaration diff --git a/AGENTS.md b/AGENTS.md index ac85a00d8..44b0149fd 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -1,5 +1,5 @@ # Repository Guidelines -- Repo: https://github.com/clawdbot/clawdbot +- Repo: https://github.com/moltbot/moltbot - GitHub issues/comments/PR comments: use literal multiline strings or `-F - <<'EOF'` (or $'...') for real newlines; never embed "\\n". ## Project Structure & Module Organization @@ -7,8 +7,8 @@ - Tests: colocated `*.test.ts`. - Docs: `docs/` (images, queue, Pi config). Built output lives in `dist/`. - Plugins/extensions: live under `extensions/*` (workspace packages). Keep plugin-only deps in the extension `package.json`; do not add them to the root `package.json` unless core uses them. -- Plugins: install runs `npm install --omit=dev` in plugin dir; runtime deps must live in `dependencies`. Avoid `workspace:*` in `dependencies` (npm install breaks); put `clawdbot` in `devDependencies` or `peerDependencies` instead (runtime resolves `clawdbot/plugin-sdk` via jiti alias). -- Installers served from `https://clawd.bot/*`: live in the sibling repo `../clawd.bot` (`public/install.sh`, `public/install-cli.sh`, `public/install.ps1`). +- Plugins: install runs `npm install --omit=dev` in plugin dir; runtime deps must live in `dependencies`. Avoid `workspace:*` in `dependencies` (npm install breaks); put `moltbot` in `devDependencies` or `peerDependencies` instead (runtime resolves `clawdbot/plugin-sdk` via jiti alias). +- Installers served from `https://molt.bot/*`: live in the sibling repo `../molt.bot` (`public/install.sh`, `public/install-cli.sh`, `public/install.ps1`). - Messaging channels: always consider **all** built-in + extension channels when refactoring shared logic (routing, allowlists, pairing, command gating, onboarding, docs). - Core channel docs: `docs/channels/` - Core channel code: `src/telegram`, `src/discord`, `src/slack`, `src/signal`, `src/imessage`, `src/web` (WhatsApp web), `src/channels`, `src/routing` @@ -16,24 +16,24 @@ - When adding channels/extensions/apps/docs, review `.github/labeler.yml` for label coverage. ## Docs Linking (Mintlify) -- Docs are hosted on Mintlify (docs.clawd.bot). +- Docs are hosted on Mintlify (docs.molt.bot). - Internal doc links in `docs/**/*.md`: root-relative, no `.md`/`.mdx` (example: `[Config](/configuration)`). - Section cross-references: use anchors on root-relative paths (example: `[Hooks](/configuration#hooks)`). - Doc headings and anchors: avoid em dashes and apostrophes in headings because they break Mintlify anchor links. -- When Peter asks for links, reply with full `https://docs.clawd.bot/...` URLs (not root-relative). -- When you touch docs, end the reply with the `https://docs.clawd.bot/...` URLs you referenced. -- README (GitHub): keep absolute docs URLs (`https://docs.clawd.bot/...`) so links work on GitHub. +- When Peter asks for links, reply with full `https://docs.molt.bot/...` URLs (not root-relative). +- When you touch docs, end the reply with the `https://docs.molt.bot/...` URLs you referenced. +- README (GitHub): keep absolute docs URLs (`https://docs.molt.bot/...`) so links work on GitHub. - Docs content must be generic: no personal device names/hostnames/paths; use placeholders like `user@gateway-host` and “gateway host”. ## exe.dev VM ops (general) - Access: stable path is `ssh exe.dev` then `ssh vm-name` (assume SSH key already set). - SSH flaky: use exe.dev web terminal or Shelley (web agent); keep a tmux session for long ops. -- Update: `sudo npm i -g clawdbot@latest` (global install needs root on `/usr/lib/node_modules`). -- Config: use `clawdbot config set ...`; ensure `gateway.mode=local` is set. +- Update: `sudo npm i -g moltbot@latest` (global install needs root on `/usr/lib/node_modules`). +- Config: use `moltbot config set ...`; ensure `gateway.mode=local` is set. - Discord: store raw token only (no `DISCORD_BOT_TOKEN=` prefix). - Restart: stop old gateway and run: - `pkill -9 -f clawdbot-gateway || true; nohup clawdbot gateway run --bind loopback --port 18789 --force > /tmp/clawdbot-gateway.log 2>&1 &` -- Verify: `clawdbot channels status --probe`, `ss -ltnp | rg 18789`, `tail -n 120 /tmp/clawdbot-gateway.log`. + `pkill -9 -f moltbot-gateway || true; nohup moltbot gateway run --bind loopback --port 18789 --force > /tmp/moltbot-gateway.log 2>&1 &` +- Verify: `moltbot channels status --probe`, `ss -ltnp | rg 18789`, `tail -n 120 /tmp/moltbot-gateway.log`. ## Build, Test, and Development Commands - Runtime baseline: Node **22+** (keep Node + Bun paths working). @@ -41,7 +41,7 @@ - Pre-commit hooks: `prek install` (runs same checks as CI) - Also supported: `bun install` (keep `pnpm-lock.yaml` + Bun patching in sync when touching deps/patches). - Prefer Bun for TypeScript execution (scripts, dev, tests): `bun ` / `bunx `. -- Run CLI in dev: `pnpm clawdbot ...` (bun) or `pnpm dev`. +- Run CLI in dev: `pnpm moltbot ...` (bun) or `pnpm dev`. - Node remains supported for running built output (`dist/*`) and production installs. - Mac packaging (dev): `scripts/package-mac-app.sh` defaults to current arch. Release checklist: `docs/platforms/mac/release.md`. - Type-check/build: `pnpm build` (tsc) @@ -54,7 +54,7 @@ - Add brief code comments for tricky or non-obvious logic. - Keep files concise; extract helpers instead of “V2” copies. Use existing patterns for CLI options and dependency injection via `createDefaultDeps`. - Aim to keep files under ~700 LOC; guideline only (not a hard guardrail). Split/refactor when it improves clarity or testability. -- Naming: use **Clawdbot** for product/app/docs headings; use `clawdbot` for CLI command, package/binary, paths, and config keys. +- Naming: use **Moltbot** for product/app/docs headings; use `moltbot` for CLI command, package/binary, paths, and config keys. ## Release Channels (Naming) - stable: tagged releases only (e.g. `vYYYY.M.D`), npm dist-tag `latest`. @@ -66,7 +66,7 @@ - Naming: match source names with `*.test.ts`; e2e in `*.e2e.test.ts`. - Run `pnpm test` (or `pnpm test:coverage`) before pushing when you touch logic. - Do not set test workers above 16; tried already. -- Live tests (real keys): `CLAWDBOT_LIVE_TEST=1 pnpm test:live` (Clawdbot-only) or `LIVE=1 pnpm test:live` (includes provider live tests). Docker: `pnpm test:docker:live-models`, `pnpm test:docker:live-gateway`. Onboarding Docker E2E: `pnpm test:docker:onboard`. +- Live tests (real keys): `CLAWDBOT_LIVE_TEST=1 pnpm test:live` (Moltbot-only) or `LIVE=1 pnpm test:live` (includes provider live tests). Docker: `pnpm test:docker:live-models`, `pnpm test:docker:live-gateway`. Onboarding Docker E2E: `pnpm test:docker:onboard`. - Full kit + what’s covered: `docs/testing.md`. - Pure test additions/fixes generally do **not** need a changelog entry unless they alter user-facing behavior or the user asks for one. - Mobile: before using a simulator, check for connected real devices (iOS + Android) and prefer them when available. @@ -97,19 +97,19 @@ - **Landing mode:** create an integration branch from `main`, bring in PR commits (**prefer rebase** for linear history; **merge allowed** when complexity/conflicts make it safer), apply fixes, add changelog (+ thanks + PR #), run full gate **locally before committing** (`pnpm lint && pnpm build && pnpm test`), commit, merge back to `main`, then `git switch main` (never stay on a topic branch after landing). Important: contributor needs to be in git graph after this! ## Security & Configuration Tips -- Web provider stores creds at `~/.clawdbot/credentials/`; rerun `clawdbot login` if logged out. +- Web provider stores creds at `~/.clawdbot/credentials/`; rerun `moltbot login` if logged out. - Pi sessions live under `~/.clawdbot/sessions/` by default; the base directory is not configurable. - Environment variables: see `~/.profile`. - Never commit or publish real phone numbers, videos, or live configuration values. Use obviously fake placeholders in docs, tests, and examples. - Release flow: always read `docs/reference/RELEASING.md` and `docs/platforms/mac/release.md` before any release work; do not ask routine questions once those docs answer them. ## Troubleshooting -- Rebrand/migration issues or legacy config/service warnings: run `clawdbot doctor` (see `docs/gateway/doctor.md`). +- Rebrand/migration issues or legacy config/service warnings: run `moltbot doctor` (see `docs/gateway/doctor.md`). ## Agent-Specific Notes - Vocabulary: "makeup" = "mac app". - Never edit `node_modules` (global/Homebrew/npm/git installs too). Updates overwrite. Skill notes go in `tools.md` or `AGENTS.md`. -- Signal: "update fly" => `fly ssh console -a flawd-bot -C "bash -lc 'cd /data/clawd/clawdbot && git pull --rebase origin main'"` then `fly machines restart e825232f34d058 -a flawd-bot`. +- Signal: "update fly" => `fly ssh console -a flawd-bot -C "bash -lc 'cd /data/clawd/moltbot && git pull --rebase origin main'"` then `fly machines restart e825232f34d058 -a flawd-bot`. - When working on a GitHub Issue or PR, print the full URL at the end of the task. - When answering questions, respond with high-confidence answers only: verify in code; do not guess. - Never update the Carbon dependency. @@ -117,12 +117,12 @@ - Patching dependencies (pnpm patches, overrides, or vendored changes) requires explicit approval; do not do this by default. - CLI progress: use `src/cli/progress.ts` (`osc-progress` + `@clack/prompts` spinner); don’t hand-roll spinners/bars. - Status output: keep tables + ANSI-safe wrapping (`src/terminal/table.ts`); `status --all` = read-only/pasteable, `status --deep` = probes. -- Gateway currently runs only as the menubar app; there is no separate LaunchAgent/helper label installed. Restart via the Clawdbot Mac app or `scripts/restart-mac.sh`; to verify/kill use `launchctl print gui/$UID | grep clawdbot` rather than assuming a fixed label. **When debugging on macOS, start/stop the gateway via the app, not ad-hoc tmux sessions; kill any temporary tunnels before handoff.** -- macOS logs: use `./scripts/clawlog.sh` to query unified logs for the Clawdbot subsystem; it supports follow/tail/category filters and expects passwordless sudo for `/usr/bin/log`. +- Gateway currently runs only as the menubar app; there is no separate LaunchAgent/helper label installed. Restart via the Moltbot Mac app or `scripts/restart-mac.sh`; to verify/kill use `launchctl print gui/$UID | grep moltbot` rather than assuming a fixed label. **When debugging on macOS, start/stop the gateway via the app, not ad-hoc tmux sessions; kill any temporary tunnels before handoff.** +- macOS logs: use `./scripts/clawlog.sh` to query unified logs for the Moltbot subsystem; it supports follow/tail/category filters and expects passwordless sudo for `/usr/bin/log`. - If shared guardrails are available locally, review them; otherwise follow this repo's guidance. - SwiftUI state management (iOS/macOS): prefer the `Observation` framework (`@Observable`, `@Bindable`) over `ObservableObject`/`@StateObject`; don’t introduce new `ObservableObject` unless required for compatibility, and migrate existing usages when touching related code. - Connection providers: when adding a new connection, update every UI surface and docs (macOS app, web UI, mobile if applicable, onboarding/overview docs) and add matching status + configuration forms so provider lists and settings stay in sync. -- Version locations: `package.json` (CLI), `apps/android/app/build.gradle.kts` (versionName/versionCode), `apps/ios/Sources/Info.plist` + `apps/ios/Tests/Info.plist` (CFBundleShortVersionString/CFBundleVersion), `apps/macos/Sources/Clawdbot/Resources/Info.plist` (CFBundleShortVersionString/CFBundleVersion), `docs/install/updating.md` (pinned npm version), `docs/platforms/mac/release.md` (APP_VERSION/APP_BUILD examples), Peekaboo Xcode projects/Info.plists (MARKETING_VERSION/CURRENT_PROJECT_VERSION). +- Version locations: `package.json` (CLI), `apps/android/app/build.gradle.kts` (versionName/versionCode), `apps/ios/Sources/Info.plist` + `apps/ios/Tests/Info.plist` (CFBundleShortVersionString/CFBundleVersion), `apps/macos/Sources/Moltbot/Resources/Info.plist` (CFBundleShortVersionString/CFBundleVersion), `docs/install/updating.md` (pinned npm version), `docs/platforms/mac/release.md` (APP_VERSION/APP_BUILD examples), Peekaboo Xcode projects/Info.plists (MARKETING_VERSION/CURRENT_PROJECT_VERSION). - **Restart apps:** “restart iOS/Android apps” means rebuild (recompile/install) and relaunch, not just kill/launch. - **Device checks:** before testing, verify connected real devices (iOS/Android) before reaching for simulators/emulators. - iOS Team ID lookup: `security find-identity -p codesigning -v` → use Apple Development (…) TEAMID. Fallback: `defaults read com.apple.dt.Xcode IDEProvisioningTeamIdentifiers`. @@ -149,9 +149,9 @@ - Do not rebuild the macOS app over SSH; rebuilds must be run directly on the Mac. - Never send streaming/partial replies to external messaging surfaces (WhatsApp, Telegram); only final replies should be delivered there. Streaming/tool events may still go to internal UIs/control channel. - Voice wake forwarding tips: - - Command template should stay `clawdbot-mac agent --message "${text}" --thinking low`; `VoiceWakeForwarder` already shell-escapes `${text}`. Don’t add extra quotes. - - launchd PATH is minimal; ensure the app’s launch agent PATH includes standard system paths plus your pnpm bin (typically `$HOME/Library/pnpm`) so `pnpm`/`clawdbot` binaries resolve when invoked via `clawdbot-mac`. -- For manual `clawdbot message send` messages that include `!`, use the heredoc pattern noted below to avoid the Bash tool’s escaping. + - Command template should stay `moltbot-mac agent --message "${text}" --thinking low`; `VoiceWakeForwarder` already shell-escapes `${text}`. Don’t add extra quotes. + - launchd PATH is minimal; ensure the app’s launch agent PATH includes standard system paths plus your pnpm bin (typically `$HOME/Library/pnpm`) so `pnpm`/`moltbot` binaries resolve when invoked via `moltbot-mac`. +- For manual `moltbot message send` messages that include `!`, use the heredoc pattern noted below to avoid the Bash tool’s escaping. - Release guardrails: do not change version numbers without operator’s explicit consent; always ask permission before running any npm publish/release step. ## NPM + 1Password (publish/verify) diff --git a/CHANGELOG.md b/CHANGELOG.md index e6bb640bc..ac2e62360 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,12 +1,16 @@ # Changelog -Docs: https://docs.clawd.bot +Docs: https://docs.molt.bot -## 2026.1.25 -Status: unreleased. +## 2026.1.27-beta.1 +Status: beta. ### Changes +- Rebrand: rename the npm package/CLI to `moltbot`, add a `moltbot` compatibility shim, and move extensions to the `@moltbot/*` scope. +- Commands: group /help and /commands output with Telegram paging. (#2504) Thanks @hougangdev. - macOS: limit project-local `node_modules/.bin` PATH preference to debug builds (reduce PATH hijacking risk). +- macOS: finish Moltbot app rename for macOS sources, bundle identifiers, and shared kit paths. (#2844) Thanks @fal3. +- Branding: update launchd labels, mobile bundle IDs, and logging subsystems to bot.molt (legacy com.clawdbot migrations). Thanks @thewilloftheshadow. - Tools: add per-sender group tool policies and fix precedence. (#1757) Thanks @adam91holt. - Agents: summarize dropped messages during compaction safeguard pruning. (#2509) Thanks @jogi47. - Skills: add multi-image input support to Nano Banana Pro skill. (#1958) Thanks @tyler6204. @@ -18,6 +22,7 @@ Status: unreleased. - Gateway: warn on hook tokens via query params; document header auth preference. (#2200) Thanks @YuriNachos. - Gateway: add dangerous Control UI device auth bypass flag + audit warnings. (#2248) - Doctor: warn on gateway exposure without auth. (#2016) Thanks @Alex-Alaniz. +- Config: auto-migrate legacy state/config paths and keep config resolution consistent across legacy filenames. - Discord: add configurable privileged gateway intents for presences/members. (#2266) Thanks @kentaro. - Docs: add Vercel AI Gateway to providers sidebar. (#1901) Thanks @jerilynzheng. - Agents: expand cron tool description with full schema docs. (#1988) Thanks @tomascupr. @@ -46,6 +51,7 @@ Status: unreleased. - Telegram: support plugin sendPayload channelData (media/buttons) and validate plugin commands. (#1917) Thanks @JoshuaLelon. - Telegram: avoid block replies when streaming is disabled. (#1885) Thanks @ivancasco. - Docs: keep docs header sticky so navbar stays visible while scrolling. (#2445) Thanks @chenyuan99. +- Docs: update exe.dev install instructions. (#https://github.com/moltbot/moltbot/pull/3047) Thanks @zackerthescar. - Security: use Windows ACLs for permission audits and fixes on Windows. (#1957) - Auth: show copyable Google auth URL after ASCII prompt. (#1787) Thanks @robbyczgw-cla. - Routing: precompile session key regexes. (#1697) Thanks @Ray0907. @@ -53,21 +59,37 @@ Status: unreleased. - Telegram: keep topic IDs in restart sentinel notifications. (#1807) Thanks @hsrvc. - Telegram: add optional silent send flag (disable notifications). (#2382) Thanks @Suksham-sharma. - Telegram: support editing sent messages via message(action="edit"). (#2394) Thanks @marcelomar21. +- Telegram: support quote replies for message tool and inbound context. (#2900) Thanks @aduk059. +- Telegram: add sticker receive/send with vision caching. (#2629) Thanks @longjos. +- Telegram: send sticker pixels to vision models. (#2650) - Config: apply config.env before ${VAR} substitution. (#1813) Thanks @spanishflu-est1918. - Slack: clear ack reaction after streamed replies. (#2044) Thanks @fancyboi999. - macOS: keep custom SSH usernames in remote target. (#2046) Thanks @algal. +- CLI: use Node's module compile cache for faster startup. (#2808) Thanks @pi0. ### Breaking - **BREAKING:** Gateway auth mode "none" is removed; gateway now requires token/password (Tailscale Serve identity still allowed). ### Fixes +- Agents: prevent retries on oversized image errors and surface size limits. (#2871) Thanks @Suksham-sharma. +- Agents: inherit provider baseUrl/api for inline models. (#2740) Thanks @lploc94. - Memory Search: keep auto provider model defaults and only include remote when configured. (#2576) Thanks @papago2355. - macOS: auto-scroll to bottom when sending a new message while scrolled up. (#2471) Thanks @kennyklee. +- Web UI: auto-expand the chat compose textarea while typing (with sensible max height). (#2950) Thanks @shivamraut101. +- Gateway: prevent crashes on transient network errors (fetch failures, timeouts, DNS). Added fatal error detection to only exit on truly critical errors. Fixes #2895, #2879, #2873. (#2980) Thanks @elliotsecops. +- Agents: guard channel tool listActions to avoid plugin crashes. (#2859) Thanks @mbelinky. +- Discord: avoid resolving bare channel names to user DMs when a username matches. Thanks @thewilloftheshadow. +- Discord: fix directory config type import for target resolution. Thanks @thewilloftheshadow. +- Providers: update MiniMax API endpoint and compatibility mode. (#3064) Thanks @hlbbbbbbb. +- Telegram: treat more network errors as recoverable in polling. (#3013) Thanks @ryancontent. +- Discord: resolve usernames to user IDs for outbound messages. (#2649) Thanks @nonggialiang. +- Providers: update Moonshot Kimi model references to kimi-k2.5. (#2762) Thanks @MarvinCui. - Gateway: suppress AbortError and transient network errors in unhandled rejections. (#2451) Thanks @Glucksberg. - TTS: keep /tts status replies on text-only commands and avoid duplicate block-stream audio. (#2451) Thanks @Glucksberg. - Security: pin npm overrides to keep tar@7.5.4 for install toolchains. - Security: properly test Windows ACL audit for config includes. (#2403) Thanks @dominicnunez. - CLI: recognize versioned Node executables when parsing argv. (#2490) Thanks @David-Marsh-Photo. +- CLI: avoid prompting for gateway runtime under the spinner. (#2874) - BlueBubbles: coalesce inbound URL link preview messages. (#1981) Thanks @tyler6204. - Cron: allow payloads containing "heartbeat" in event filter. (#2219) Thanks @dwfinkelstein. - CLI: avoid loading config for global help/version while registering plugin commands. (#2212) Thanks @dial481. @@ -75,6 +97,7 @@ Status: unreleased. - Agents: release session locks on process termination and cover more signals. (#2483) Thanks @janeexai. - Agents: skip cooldowned providers during model failover. (#2143) Thanks @YiWang24. - Telegram: harden polling + retry behavior for transient network errors and Node 22 transport issues. (#2420) Thanks @techboss. +- Telegram: ignore non-forum group message_thread_id while preserving DM thread sessions. (#2731) Thanks @dylanneve1. - Telegram: wrap reasoning italics per line to avoid raw underscores. (#2181) Thanks @YuriNachos. - Telegram: centralize API error logging for delivery and bot calls. (#2492) Thanks @altryne. - Voice Call: enforce Twilio webhook signature verification for ngrok URLs; disable ngrok free tier bypass by default. @@ -109,27 +132,27 @@ Status: unreleased. ## 2026.1.24 ### Highlights -- Providers: Ollama discovery + docs; Venice guide upgrades + cross-links. (#1606) Thanks @abhaymundhara. https://docs.clawd.bot/providers/ollama https://docs.clawd.bot/providers/venice +- Providers: Ollama discovery + docs; Venice guide upgrades + cross-links. (#1606) Thanks @abhaymundhara. https://docs.molt.bot/providers/ollama https://docs.molt.bot/providers/venice - Channels: LINE plugin (Messaging API) with rich replies + quick replies. (#1630) Thanks @plum-dawg. -- TTS: Edge fallback (keyless) + `/tts` auto modes. (#1668, #1667) Thanks @steipete, @sebslight. https://docs.clawd.bot/tts -- Exec approvals: approve in-chat via `/approve` across all channels (including plugins). (#1621) Thanks @czekaj. https://docs.clawd.bot/tools/exec-approvals https://docs.clawd.bot/tools/slash-commands -- Telegram: DM topics as separate sessions + outbound link preview toggle. (#1597, #1700) Thanks @rohannagpal, @zerone0x. https://docs.clawd.bot/channels/telegram +- TTS: Edge fallback (keyless) + `/tts` auto modes. (#1668, #1667) Thanks @steipete, @sebslight. https://docs.molt.bot/tts +- Exec approvals: approve in-chat via `/approve` across all channels (including plugins). (#1621) Thanks @czekaj. https://docs.molt.bot/tools/exec-approvals https://docs.molt.bot/tools/slash-commands +- Telegram: DM topics as separate sessions + outbound link preview toggle. (#1597, #1700) Thanks @rohannagpal, @zerone0x. https://docs.molt.bot/channels/telegram ### Changes - Channels: add LINE plugin (Messaging API) with rich replies, quick replies, and plugin HTTP registry. (#1630) Thanks @plum-dawg. -- TTS: add Edge TTS provider fallback, defaulting to keyless Edge with MP3 retry on format failures. (#1668) Thanks @steipete. https://docs.clawd.bot/tts -- TTS: add auto mode enum (off/always/inbound/tagged) with per-session `/tts` override. (#1667) Thanks @sebslight. https://docs.clawd.bot/tts +- TTS: add Edge TTS provider fallback, defaulting to keyless Edge with MP3 retry on format failures. (#1668) Thanks @steipete. https://docs.molt.bot/tts +- TTS: add auto mode enum (off/always/inbound/tagged) with per-session `/tts` override. (#1667) Thanks @sebslight. https://docs.molt.bot/tts - Telegram: treat DM topics as separate sessions and keep DM history limits stable with thread suffixes. (#1597) Thanks @rohannagpal. -- Telegram: add `channels.telegram.linkPreview` to toggle outbound link previews. (#1700) Thanks @zerone0x. https://docs.clawd.bot/channels/telegram -- Web search: add Brave freshness filter parameter for time-scoped results. (#1688) Thanks @JonUleis. https://docs.clawd.bot/tools/web +- Telegram: add `channels.telegram.linkPreview` to toggle outbound link previews. (#1700) Thanks @zerone0x. https://docs.molt.bot/channels/telegram +- Web search: add Brave freshness filter parameter for time-scoped results. (#1688) Thanks @JonUleis. https://docs.molt.bot/tools/web - UI: refresh Control UI dashboard design system (colors, icons, typography). (#1745, #1786) Thanks @EnzeD, @mousberg. -- Exec approvals: forward approval prompts to chat with `/approve` for all channels (including plugins). (#1621) Thanks @czekaj. https://docs.clawd.bot/tools/exec-approvals https://docs.clawd.bot/tools/slash-commands +- Exec approvals: forward approval prompts to chat with `/approve` for all channels (including plugins). (#1621) Thanks @czekaj. https://docs.molt.bot/tools/exec-approvals https://docs.molt.bot/tools/slash-commands - Gateway: expose config.patch in the gateway tool with safe partial updates + restart sentinel. (#1653) Thanks @Glucksberg. -- Diagnostics: add diagnostic flags for targeted debug logs (config + env override). https://docs.clawd.bot/diagnostics/flags +- Diagnostics: add diagnostic flags for targeted debug logs (config + env override). https://docs.molt.bot/diagnostics/flags - Docs: expand FAQ (migration, scheduling, concurrency, model recommendations, OpenAI subscription auth, Pi sizing, hackable install, docs SSL workaround). - Docs: add verbose installer troubleshooting guidance. - Docs: add macOS VM guide with local/hosted options + VPS/nodes guidance. (#1693) Thanks @f-trycua. -- Docs: add Bedrock EC2 instance role setup + IAM steps. (#1625) Thanks @sergical. https://docs.clawd.bot/bedrock +- Docs: add Bedrock EC2 instance role setup + IAM steps. (#1625) Thanks @sergical. https://docs.molt.bot/bedrock - Docs: update Fly.io guide notes. - Dev: add prek pre-commit hooks + dependabot config for weekly updates. (#1720) Thanks @dguido. @@ -140,11 +163,11 @@ Status: unreleased. - Web UI: hide internal `message_id` hints in chat bubbles. - Gateway: allow Control UI token-only auth to skip device pairing even when device identity is present (`gateway.controlUi.allowInsecureAuth`). (#1679) Thanks @steipete. - Matrix: decrypt E2EE media attachments with preflight size guard. (#1744) Thanks @araa47. -- BlueBubbles: route phone-number targets to DMs, avoid leaking routing IDs, and auto-create missing DMs (Private API required). (#1751) Thanks @tyler6204. https://docs.clawd.bot/channels/bluebubbles +- BlueBubbles: route phone-number targets to DMs, avoid leaking routing IDs, and auto-create missing DMs (Private API required). (#1751) Thanks @tyler6204. https://docs.molt.bot/channels/bluebubbles - BlueBubbles: keep part-index GUIDs in reply tags when short IDs are missing. - iMessage: normalize chat_id/chat_guid/chat_identifier prefixes case-insensitively and keep service-prefixed handles stable. (#1708) Thanks @aaronn. - Signal: repair reaction sends (group/UUID targets + CLI author flags). (#1651) Thanks @vilkasdev. -- Signal: add configurable signal-cli startup timeout + external daemon mode docs. (#1677) https://docs.clawd.bot/channels/signal +- Signal: add configurable signal-cli startup timeout + external daemon mode docs. (#1677) https://docs.molt.bot/channels/signal - Telegram: set fetch duplex="half" for uploads on Node 22 to avoid sendPhoto failures. (#1684) Thanks @commdata2338. - Telegram: use wrapped fetch for long-polling on Node to normalize AbortSignal handling. (#1639) - Telegram: honor per-account proxy for outbound API calls. (#1774) Thanks @radek-paclt. @@ -182,25 +205,25 @@ Status: unreleased. ## 2026.1.23 ### Highlights -- TTS: move Telegram TTS into core + enable model-driven TTS tags by default for expressive audio replies. (#1559) Thanks @Glucksberg. https://docs.clawd.bot/tts -- Gateway: add `/tools/invoke` HTTP endpoint for direct tool calls (auth + tool policy enforced). (#1575) Thanks @vignesh07. https://docs.clawd.bot/gateway/tools-invoke-http-api -- Heartbeat: per-channel visibility controls (OK/alerts/indicator). (#1452) Thanks @dlauer. https://docs.clawd.bot/gateway/heartbeat -- Deploy: add Fly.io deployment support + guide. (#1570) https://docs.clawd.bot/platforms/fly -- Channels: add Tlon/Urbit channel plugin (DMs, group mentions, thread replies). (#1544) Thanks @wca4a. https://docs.clawd.bot/channels/tlon +- TTS: move Telegram TTS into core + enable model-driven TTS tags by default for expressive audio replies. (#1559) Thanks @Glucksberg. https://docs.molt.bot/tts +- Gateway: add `/tools/invoke` HTTP endpoint for direct tool calls (auth + tool policy enforced). (#1575) Thanks @vignesh07. https://docs.molt.bot/gateway/tools-invoke-http-api +- Heartbeat: per-channel visibility controls (OK/alerts/indicator). (#1452) Thanks @dlauer. https://docs.molt.bot/gateway/heartbeat +- Deploy: add Fly.io deployment support + guide. (#1570) https://docs.molt.bot/platforms/fly +- Channels: add Tlon/Urbit channel plugin (DMs, group mentions, thread replies). (#1544) Thanks @wca4a. https://docs.molt.bot/channels/tlon ### Changes -- Channels: allow per-group tool allow/deny policies across built-in + plugin channels. (#1546) Thanks @adam91holt. https://docs.clawd.bot/multi-agent-sandbox-tools -- Agents: add Bedrock auto-discovery defaults + config overrides. (#1553) Thanks @fal3. https://docs.clawd.bot/bedrock -- CLI: add `clawdbot system` for system events + heartbeat controls; remove standalone `wake`. (commit 71203829d) https://docs.clawd.bot/cli/system -- CLI: add live auth probes to `clawdbot models status` for per-profile verification. (commit 40181afde) https://docs.clawd.bot/cli/models -- CLI: restart the gateway by default after `clawdbot update`; add `--no-restart` to skip it. (commit 2c85b1b40) +- Channels: allow per-group tool allow/deny policies across built-in + plugin channels. (#1546) Thanks @adam91holt. https://docs.molt.bot/multi-agent-sandbox-tools +- Agents: add Bedrock auto-discovery defaults + config overrides. (#1553) Thanks @fal3. https://docs.molt.bot/bedrock +- CLI: add `moltbot system` for system events + heartbeat controls; remove standalone `wake`. (commit 71203829d) https://docs.molt.bot/cli/system +- CLI: add live auth probes to `moltbot models status` for per-profile verification. (commit 40181afde) https://docs.molt.bot/cli/models +- CLI: restart the gateway by default after `moltbot update`; add `--no-restart` to skip it. (commit 2c85b1b40) - Browser: add node-host proxy auto-routing for remote gateways (configurable per gateway/node). (commit c3cb26f7c) -- Plugins: add optional `llm-task` JSON-only tool for workflows. (#1498) Thanks @vignesh07. https://docs.clawd.bot/tools/llm-task +- Plugins: add optional `llm-task` JSON-only tool for workflows. (#1498) Thanks @vignesh07. https://docs.molt.bot/tools/llm-task - Markdown: add per-channel table conversion (bullets for Signal/WhatsApp, code blocks elsewhere). (#1495) Thanks @odysseus0. - Agents: keep system prompt time zone-only and move current time to `session_status` for better cache hits. (commit 66eec295b) - Agents: remove redundant bash tool alias from tool registration/display. (#1571) Thanks @Takhoffman. -- Docs: add cron vs heartbeat decision guide (with Lobster workflow notes). (#1533) Thanks @JustYannicc. https://docs.clawd.bot/automation/cron-vs-heartbeat -- Docs: clarify HEARTBEAT.md empty file skips heartbeats, missing file still runs. (#1535) Thanks @JustYannicc. https://docs.clawd.bot/gateway/heartbeat +- Docs: add cron vs heartbeat decision guide (with Lobster workflow notes). (#1533) Thanks @JustYannicc. https://docs.molt.bot/automation/cron-vs-heartbeat +- Docs: clarify HEARTBEAT.md empty file skips heartbeats, missing file still runs. (#1535) Thanks @JustYannicc. https://docs.molt.bot/gateway/heartbeat ### Fixes - Sessions: accept non-UUID sessionIds for history/send/status while preserving agent scoping. (#1518) @@ -233,7 +256,7 @@ Status: unreleased. - UI: keep the Control UI sidebar visible while scrolling long pages. (#1515) Thanks @pookNast. - UI: cache Control UI markdown rendering + memoize chat text extraction to reduce Safari typing jank. (commit d57cb2e1a) - TUI: forward unknown slash commands, include Gateway commands in autocomplete, and render slash replies as system output. (commit 1af227b61, commit 8195497ce, commit 6fba598ea) -- CLI: auth probe output polish (table output, inline errors, reduced noise, and wrap fixes in `clawdbot models status`). (commit da3f2b489, commit 00ae21bed, commit 31e59cd58, commit f7dc27f2d, commit 438e782f8, commit 886752217, commit aabe0bed3, commit 81535d512, commit c63144ab1) +- CLI: auth probe output polish (table output, inline errors, reduced noise, and wrap fixes in `moltbot models status`). (commit da3f2b489, commit 00ae21bed, commit 31e59cd58, commit f7dc27f2d, commit 438e782f8, commit 886752217, commit aabe0bed3, commit 81535d512, commit c63144ab1) - Media: only parse `MEDIA:` tags when they start the line to avoid stripping prose mentions. (#1206) - Media: preserve PNG alpha when possible; fall back to JPEG when still over size cap. (#1491) Thanks @robbyczgw-cla. - Skills: gate bird Homebrew install to macOS. (#1569) Thanks @bradleypriest. @@ -278,35 +301,35 @@ Status: unreleased. ## 2026.1.21-2 ### Fixes -- Control UI: ignore bootstrap identity placeholder text for avatar values and fall back to the default avatar. https://docs.clawd.bot/cli/agents https://docs.clawd.bot/web/control-ui +- Control UI: ignore bootstrap identity placeholder text for avatar values and fall back to the default avatar. https://docs.molt.bot/cli/agents https://docs.molt.bot/web/control-ui - Slack: remove deprecated `filetype` field from `files.uploadV2` to eliminate API warnings. (#1447) ## 2026.1.21 ### Changes -- Highlight: Lobster optional plugin tool for typed workflows + approval gates. https://docs.clawd.bot/tools/lobster -- Lobster: allow workflow file args via `argsJson` in the plugin tool. https://docs.clawd.bot/tools/lobster +- Highlight: Lobster optional plugin tool for typed workflows + approval gates. https://docs.molt.bot/tools/lobster +- Lobster: allow workflow file args via `argsJson` in the plugin tool. https://docs.molt.bot/tools/lobster - Heartbeat: allow running heartbeats in an explicit session key. (#1256) Thanks @zknicker. - CLI: default exec approvals to the local host, add gateway/node targeting flags, and show target details in allowlist output. - CLI: exec approvals mutations render tables instead of raw JSON. - Exec approvals: support wildcard agent allowlists (`*`) across all agents. - Exec approvals: allowlist matches resolved binary paths only, add safe stdin-only bins, and tighten allowlist shell parsing. - Nodes: expose node PATH in status/describe and bootstrap PATH for node-host execution. -- CLI: flatten node service commands under `clawdbot node` and remove `service node` docs. -- CLI: move gateway service commands under `clawdbot gateway` and add `gateway probe` for reachability. +- CLI: flatten node service commands under `moltbot node` and remove `service node` docs. +- CLI: move gateway service commands under `moltbot gateway` and add `gateway probe` for reachability. - Sessions: add per-channel reset overrides via `session.resetByChannel`. (#1353) Thanks @cash-echo-bot. - Agents: add identity avatar config support and Control UI avatar rendering. (#1329, #1424) Thanks @dlauer. - UI: show per-session assistant identity in the Control UI. (#1420) Thanks @robbyczgw-cla. -- CLI: add `clawdbot update wizard` for interactive channel selection and restart prompts. https://docs.clawd.bot/cli/update +- CLI: add `moltbot update wizard` for interactive channel selection and restart prompts. https://docs.molt.bot/cli/update - Signal: add typing indicators and DM read receipts via signal-cli. - MSTeams: add file uploads, adaptive cards, and attachment handling improvements. (#1410) Thanks @Evizero. - Onboarding: remove the run setup-token auth option (paste setup-token or reuse CLI creds instead). -- Docs: add troubleshooting entry for gateway.mode blocking gateway start. https://docs.clawd.bot/gateway/troubleshooting +- Docs: add troubleshooting entry for gateway.mode blocking gateway start. https://docs.molt.bot/gateway/troubleshooting - Docs: add /model allowlist troubleshooting note. (#1405) - Docs: add per-message Gmail search example for gog. (#1220) Thanks @mbelinky. ### Breaking -- **BREAKING:** Control UI now rejects insecure HTTP without device identity by default. Use HTTPS (Tailscale Serve) or set `gateway.controlUi.allowInsecureAuth: true` to allow token-only auth. https://docs.clawd.bot/web/control-ui#insecure-http +- **BREAKING:** Control UI now rejects insecure HTTP without device identity by default. Use HTTPS (Tailscale Serve) or set `gateway.controlUi.allowInsecureAuth: true` to allow token-only auth. https://docs.molt.bot/web/control-ui#insecure-http - **BREAKING:** Envelope and system event timestamps now default to host-local time (was UTC) so agents don’t have to constantly convert. ### Fixes @@ -332,68 +355,68 @@ Status: unreleased. ## 2026.1.20 ### Changes -- Control UI: add copy-as-markdown with error feedback. (#1345) https://docs.clawd.bot/web/control-ui -- Control UI: drop the legacy list view. (#1345) https://docs.clawd.bot/web/control-ui -- TUI: add syntax highlighting for code blocks. (#1200) https://docs.clawd.bot/tui -- TUI: session picker shows derived titles, fuzzy search, relative times, and last message preview. (#1271) https://docs.clawd.bot/tui -- TUI: add a searchable model picker for quicker model selection. (#1198) https://docs.clawd.bot/tui -- TUI: add input history (up/down) for submitted messages. (#1348) https://docs.clawd.bot/tui -- ACP: add `clawdbot acp` for IDE integrations. https://docs.clawd.bot/cli/acp -- ACP: add `clawdbot acp client` interactive harness for debugging. https://docs.clawd.bot/cli/acp -- Skills: add download installs with OS-filtered options. https://docs.clawd.bot/tools/skills -- Skills: add the local sherpa-onnx-tts skill. https://docs.clawd.bot/tools/skills -- Memory: add hybrid BM25 + vector search (FTS5) with weighted merging and fallback. https://docs.clawd.bot/concepts/memory -- Memory: add SQLite embedding cache to speed up reindexing and frequent updates. https://docs.clawd.bot/concepts/memory -- Memory: add OpenAI batch indexing for embeddings when configured. https://docs.clawd.bot/concepts/memory -- Memory: enable OpenAI batch indexing by default for OpenAI embeddings. https://docs.clawd.bot/concepts/memory -- Memory: allow parallel OpenAI batch indexing jobs (default concurrency: 2). https://docs.clawd.bot/concepts/memory -- Memory: render progress immediately, color batch statuses in verbose logs, and poll OpenAI batch status every 2s by default. https://docs.clawd.bot/concepts/memory -- Memory: add `--verbose` logging for memory status + batch indexing details. https://docs.clawd.bot/concepts/memory -- Memory: add native Gemini embeddings provider for memory search. (#1151) https://docs.clawd.bot/concepts/memory -- Browser: allow config defaults for efficient snapshots in the tool/CLI. (#1336) https://docs.clawd.bot/tools/browser -- Nostr: add the Nostr channel plugin with profile management + onboarding defaults. (#1323) https://docs.clawd.bot/channels/nostr -- Matrix: migrate to matrix-bot-sdk with E2EE support, location handling, and group allowlist upgrades. (#1298) https://docs.clawd.bot/channels/matrix -- Slack: add HTTP webhook mode via Bolt HTTP receiver. (#1143) https://docs.clawd.bot/channels/slack -- Telegram: enrich forwarded-message context with normalized origin details + legacy fallback. (#1090) https://docs.clawd.bot/channels/telegram +- Control UI: add copy-as-markdown with error feedback. (#1345) https://docs.molt.bot/web/control-ui +- Control UI: drop the legacy list view. (#1345) https://docs.molt.bot/web/control-ui +- TUI: add syntax highlighting for code blocks. (#1200) https://docs.molt.bot/tui +- TUI: session picker shows derived titles, fuzzy search, relative times, and last message preview. (#1271) https://docs.molt.bot/tui +- TUI: add a searchable model picker for quicker model selection. (#1198) https://docs.molt.bot/tui +- TUI: add input history (up/down) for submitted messages. (#1348) https://docs.molt.bot/tui +- ACP: add `moltbot acp` for IDE integrations. https://docs.molt.bot/cli/acp +- ACP: add `moltbot acp client` interactive harness for debugging. https://docs.molt.bot/cli/acp +- Skills: add download installs with OS-filtered options. https://docs.molt.bot/tools/skills +- Skills: add the local sherpa-onnx-tts skill. https://docs.molt.bot/tools/skills +- Memory: add hybrid BM25 + vector search (FTS5) with weighted merging and fallback. https://docs.molt.bot/concepts/memory +- Memory: add SQLite embedding cache to speed up reindexing and frequent updates. https://docs.molt.bot/concepts/memory +- Memory: add OpenAI batch indexing for embeddings when configured. https://docs.molt.bot/concepts/memory +- Memory: enable OpenAI batch indexing by default for OpenAI embeddings. https://docs.molt.bot/concepts/memory +- Memory: allow parallel OpenAI batch indexing jobs (default concurrency: 2). https://docs.molt.bot/concepts/memory +- Memory: render progress immediately, color batch statuses in verbose logs, and poll OpenAI batch status every 2s by default. https://docs.molt.bot/concepts/memory +- Memory: add `--verbose` logging for memory status + batch indexing details. https://docs.molt.bot/concepts/memory +- Memory: add native Gemini embeddings provider for memory search. (#1151) https://docs.molt.bot/concepts/memory +- Browser: allow config defaults for efficient snapshots in the tool/CLI. (#1336) https://docs.molt.bot/tools/browser +- Nostr: add the Nostr channel plugin with profile management + onboarding defaults. (#1323) https://docs.molt.bot/channels/nostr +- Matrix: migrate to matrix-bot-sdk with E2EE support, location handling, and group allowlist upgrades. (#1298) https://docs.molt.bot/channels/matrix +- Slack: add HTTP webhook mode via Bolt HTTP receiver. (#1143) https://docs.molt.bot/channels/slack +- Telegram: enrich forwarded-message context with normalized origin details + legacy fallback. (#1090) https://docs.molt.bot/channels/telegram - Discord: fall back to `/skill` when native command limits are exceeded. (#1287) - Discord: expose `/skill` globally. (#1287) -- Zalouser: add channel dock metadata, config schema, setup wiring, probe, and status issues. (#1219) https://docs.clawd.bot/plugins/zalouser -- Plugins: require manifest-embedded config schemas with preflight validation warnings. (#1272) https://docs.clawd.bot/plugins/manifest -- Plugins: move channel catalog metadata into plugin manifests. (#1290) https://docs.clawd.bot/plugins/manifest -- Plugins: align Nextcloud Talk policy helpers with core patterns. (#1290) https://docs.clawd.bot/plugins/manifest -- Plugins/UI: let channel plugin metadata drive UI labels/icons and cron channel options. (#1306) https://docs.clawd.bot/web/control-ui -- Agents/UI: add agent avatar support in identity config, IDENTITY.md, and the Control UI. (#1329) https://docs.clawd.bot/gateway/configuration -- Plugins: add plugin slots with a dedicated memory slot selector. https://docs.clawd.bot/plugins/agent-tools -- Plugins: ship the bundled BlueBubbles channel plugin (disabled by default). https://docs.clawd.bot/channels/bluebubbles +- Zalouser: add channel dock metadata, config schema, setup wiring, probe, and status issues. (#1219) https://docs.molt.bot/plugins/zalouser +- Plugins: require manifest-embedded config schemas with preflight validation warnings. (#1272) https://docs.molt.bot/plugins/manifest +- Plugins: move channel catalog metadata into plugin manifests. (#1290) https://docs.molt.bot/plugins/manifest +- Plugins: align Nextcloud Talk policy helpers with core patterns. (#1290) https://docs.molt.bot/plugins/manifest +- Plugins/UI: let channel plugin metadata drive UI labels/icons and cron channel options. (#1306) https://docs.molt.bot/web/control-ui +- Agents/UI: add agent avatar support in identity config, IDENTITY.md, and the Control UI. (#1329) https://docs.molt.bot/gateway/configuration +- Plugins: add plugin slots with a dedicated memory slot selector. https://docs.molt.bot/plugins/agent-tools +- Plugins: ship the bundled BlueBubbles channel plugin (disabled by default). https://docs.molt.bot/channels/bluebubbles - Plugins: migrate bundled messaging extensions to the plugin SDK and resolve plugin-sdk imports in the loader. -- Plugins: migrate the Zalo plugin to the shared plugin SDK runtime. https://docs.clawd.bot/channels/zalo -- Plugins: migrate the Zalo Personal plugin to the shared plugin SDK runtime. https://docs.clawd.bot/plugins/zalouser -- Plugins: allow optional agent tools with explicit allowlists and add the plugin tool authoring guide. https://docs.clawd.bot/plugins/agent-tools +- Plugins: migrate the Zalo plugin to the shared plugin SDK runtime. https://docs.molt.bot/channels/zalo +- Plugins: migrate the Zalo Personal plugin to the shared plugin SDK runtime. https://docs.molt.bot/plugins/zalouser +- Plugins: allow optional agent tools with explicit allowlists and add the plugin tool authoring guide. https://docs.molt.bot/plugins/agent-tools - Plugins: auto-enable bundled channel/provider plugins when configuration is present. -- Plugins: sync plugin sources on channel switches and update npm-installed plugins during `clawdbot update`. -- Plugins: share npm plugin update logic between `clawdbot update` and `clawdbot plugins update`. +- Plugins: sync plugin sources on channel switches and update npm-installed plugins during `moltbot update`. +- Plugins: share npm plugin update logic between `moltbot update` and `moltbot plugins update`. - Gateway/API: add `/v1/responses` (OpenResponses) with item-based input + semantic streaming events. (#1229) - Gateway/API: expand `/v1/responses` to support file/image inputs, tool_choice, usage, and output limits. (#1229) -- Usage: add `/usage cost` summaries and macOS menu cost charts. https://docs.clawd.bot/reference/api-usage-costs -- Security: warn when <=300B models run without sandboxing while web tools are enabled. https://docs.clawd.bot/cli/security -- Exec: add host/security/ask routing for gateway + node exec. https://docs.clawd.bot/tools/exec -- Exec: add `/exec` directive for per-session exec defaults (host/security/ask/node). https://docs.clawd.bot/tools/exec -- Exec approvals: migrate approvals to `~/.clawdbot/exec-approvals.json` with per-agent allowlists + skill auto-allow toggle, and add approvals UI + node exec lifecycle events. https://docs.clawd.bot/tools/exec-approvals -- Nodes: add headless node host (`clawdbot node start`) for `system.run`/`system.which`. https://docs.clawd.bot/cli/node -- Nodes: add node daemon service install/status/start/stop/restart. https://docs.clawd.bot/cli/node +- Usage: add `/usage cost` summaries and macOS menu cost charts. https://docs.molt.bot/reference/api-usage-costs +- Security: warn when <=300B models run without sandboxing while web tools are enabled. https://docs.molt.bot/cli/security +- Exec: add host/security/ask routing for gateway + node exec. https://docs.molt.bot/tools/exec +- Exec: add `/exec` directive for per-session exec defaults (host/security/ask/node). https://docs.molt.bot/tools/exec +- Exec approvals: migrate approvals to `~/.clawdbot/exec-approvals.json` with per-agent allowlists + skill auto-allow toggle, and add approvals UI + node exec lifecycle events. https://docs.molt.bot/tools/exec-approvals +- Nodes: add headless node host (`moltbot node start`) for `system.run`/`system.which`. https://docs.molt.bot/cli/node +- Nodes: add node daemon service install/status/start/stop/restart. https://docs.molt.bot/cli/node - Bridge: add `skills.bins` RPC to support node host auto-allow skill bins. -- Sessions: add daily reset policy with per-type overrides and idle windows (default 4am local), preserving legacy idle-only configs. (#1146) https://docs.clawd.bot/concepts/session -- Sessions: allow `sessions_spawn` to override thinking level for sub-agent runs. https://docs.clawd.bot/tools/subagents -- Channels: unify thread/topic allowlist matching + command/mention gating helpers across core providers. https://docs.clawd.bot/concepts/groups -- Models: add Qwen Portal OAuth provider support. (#1120) https://docs.clawd.bot/providers/qwen -- Onboarding: add allowlist prompts and username-to-id resolution across core and extension channels. https://docs.clawd.bot/start/onboarding -- Docs: clarify allowlist input types and onboarding behavior for messaging channels. https://docs.clawd.bot/start/onboarding -- Docs: refresh Android node discovery docs for the Gateway WS service type. https://docs.clawd.bot/platforms/android -- Docs: surface Amazon Bedrock in provider lists and clarify Bedrock auth env vars. (#1289) https://docs.clawd.bot/bedrock -- Docs: clarify WhatsApp voice notes. https://docs.clawd.bot/channels/whatsapp -- Docs: clarify Windows WSL portproxy LAN access notes. https://docs.clawd.bot/platforms/windows -- Docs: refresh bird skill install metadata and usage notes. (#1302) https://docs.clawd.bot/tools/browser-login +- Sessions: add daily reset policy with per-type overrides and idle windows (default 4am local), preserving legacy idle-only configs. (#1146) https://docs.molt.bot/concepts/session +- Sessions: allow `sessions_spawn` to override thinking level for sub-agent runs. https://docs.molt.bot/tools/subagents +- Channels: unify thread/topic allowlist matching + command/mention gating helpers across core providers. https://docs.molt.bot/concepts/groups +- Models: add Qwen Portal OAuth provider support. (#1120) https://docs.molt.bot/providers/qwen +- Onboarding: add allowlist prompts and username-to-id resolution across core and extension channels. https://docs.molt.bot/start/onboarding +- Docs: clarify allowlist input types and onboarding behavior for messaging channels. https://docs.molt.bot/start/onboarding +- Docs: refresh Android node discovery docs for the Gateway WS service type. https://docs.molt.bot/platforms/android +- Docs: surface Amazon Bedrock in provider lists and clarify Bedrock auth env vars. (#1289) https://docs.molt.bot/bedrock +- Docs: clarify WhatsApp voice notes. https://docs.molt.bot/channels/whatsapp +- Docs: clarify Windows WSL portproxy LAN access notes. https://docs.molt.bot/platforms/windows +- Docs: refresh bird skill install metadata and usage notes. (#1302) https://docs.molt.bot/tools/browser-login - Agents: add local docs path resolution and include docs/mirror/source/community pointers in the system prompt. - Agents: clarify node_modules read-only guidance in agent instructions. - Config: stamp last-touched metadata on write and warn if the config is newer than the running build. @@ -410,10 +433,10 @@ Status: unreleased. - Swabble: use the tagged Commander Swift package release. ### Breaking -- **BREAKING:** Reject invalid/unknown config entries and refuse to start the gateway for safety. Run `clawdbot doctor --fix` to repair, then update plugins (`clawdbot plugins update`) if you use any. +- **BREAKING:** Reject invalid/unknown config entries and refuse to start the gateway for safety. Run `moltbot doctor --fix` to repair, then update plugins (`moltbot plugins update`) if you use any. ### Fixes -- Discovery: shorten Bonjour DNS-SD service type to `_clawdbot-gw._tcp` and update discovery clients/docs. +- Discovery: shorten Bonjour DNS-SD service type to `_moltbot-gw._tcp` and update discovery clients/docs. - Diagnostics: export OTLP logs, correct queue depth tracking, and document message-flow telemetry. - Diagnostics: emit message-flow diagnostics across channels via shared dispatch. (#1244) - Diagnostics: gate heartbeat/webhook logging. (#1244) @@ -440,7 +463,7 @@ Status: unreleased. - Plugins: add Nextcloud Talk manifest for plugin config validation. (#1297) - Plugins: surface plugin load/register/config errors in gateway logs with plugin/source context. - CLI: preserve cron delivery settings when editing message payloads. (#1322) -- CLI: keep `clawdbot logs` output resilient to broken pipes while preserving progress output. +- CLI: keep `moltbot logs` output resilient to broken pipes while preserving progress output. - CLI: avoid duplicating --profile/--dev flags when formatting commands. - CLI: centralize CLI command registration to keep fast-path routing and program wiring in sync. (#1207) - CLI: keep banners on routed commands, restore config guarding outside fast-path routing, and tighten fast-path flag parsing while skipping console capture for extra speed. (#1195) @@ -458,7 +481,7 @@ Status: unreleased. - TUI: show generic empty-state text for searchable pickers. (#1201) - TUI: highlight model search matches and stabilize search ordering. - Configure: hide OpenRouter auto routing model from the model picker. (#1182) -- Memory: show total file counts + scan issues in `clawdbot memory status`. +- Memory: show total file counts + scan issues in `moltbot memory status`. - Memory: fall back to non-batch embeddings after repeated batch failures. - Memory: apply OpenAI batch defaults even without explicit remote config. - Memory: index atomically so failed reindex preserves the previous memory database. (#1151) @@ -468,7 +491,7 @@ Status: unreleased. - Memory: split overly long lines to keep embeddings under token limits. - Memory: skip empty chunks to avoid invalid embedding inputs. - Memory: split embedding batches to avoid OpenAI token limits during indexing. -- Memory: probe sqlite-vec availability in `clawdbot memory status`. +- Memory: probe sqlite-vec availability in `moltbot memory status`. - Exec approvals: enforce allowlist when ask is off. - Exec approvals: prefer raw command for node approvals/events. - Tools: show exec elevated flag before the command and keep it outside markdown in tool summaries. @@ -518,20 +541,20 @@ Thanks @AlexMikhalev, @CoreyH, @John-Rood, @KrauseFx, @MaudeBot, @Nachx639, @Nic ## 2026.1.16-1 ### Highlights -- Hooks: add hooks system with bundled hooks, CLI tooling, and docs. (#1028) — thanks @ThomsenDrake. https://docs.clawd.bot/hooks -- Media: add inbound media understanding (image/audio/video) with provider + CLI fallbacks. https://docs.clawd.bot/nodes/media-understanding -- Plugins: add Zalo Personal plugin (`@clawdbot/zalouser`) and unify channel directory for plugins. (#1032) — thanks @suminhthanh. https://docs.clawd.bot/plugins/zalouser -- Models: add Vercel AI Gateway auth choice + onboarding updates. (#1016) — thanks @timolins. https://docs.clawd.bot/providers/vercel-ai-gateway -- Sessions: add `session.identityLinks` for cross-platform DM session li nking. (#1033) — thanks @thewilloftheshadow. https://docs.clawd.bot/concepts/session -- Web search: add `country`/`language` parameters (schema + Brave API) and docs. (#1046) — thanks @YuriNachos. https://docs.clawd.bot/tools/web +- Hooks: add hooks system with bundled hooks, CLI tooling, and docs. (#1028) — thanks @ThomsenDrake. https://docs.molt.bot/hooks +- Media: add inbound media understanding (image/audio/video) with provider + CLI fallbacks. https://docs.molt.bot/nodes/media-understanding +- Plugins: add Zalo Personal plugin (`@moltbot/zalouser`) and unify channel directory for plugins. (#1032) — thanks @suminhthanh. https://docs.molt.bot/plugins/zalouser +- Models: add Vercel AI Gateway auth choice + onboarding updates. (#1016) — thanks @timolins. https://docs.molt.bot/providers/vercel-ai-gateway +- Sessions: add `session.identityLinks` for cross-platform DM session li nking. (#1033) — thanks @thewilloftheshadow. https://docs.molt.bot/concepts/session +- Web search: add `country`/`language` parameters (schema + Brave API) and docs. (#1046) — thanks @YuriNachos. https://docs.molt.bot/tools/web ### Breaking -- **BREAKING:** `clawdbot message` and message tool now require `target` (dropping `to`/`channelId` for destinations). (#1034) — thanks @tobalsan. +- **BREAKING:** `moltbot message` and message tool now require `target` (dropping `to`/`channelId` for destinations). (#1034) — thanks @tobalsan. - **BREAKING:** Channel auth now prefers config over env for Discord/Telegram/Matrix (env is fallback only). (#1040) — thanks @thewilloftheshadow. - **BREAKING:** Drop legacy `chatType: "room"` support; use `chatType: "channel"`. - **BREAKING:** remove legacy provider-specific target resolution fallbacks; target resolution is centralized with plugin hints + directory lookups. -- **BREAKING:** `clawdbot hooks` is now `clawdbot webhooks`; hooks live under `clawdbot hooks`. https://docs.clawd.bot/cli/webhooks -- **BREAKING:** `clawdbot plugins install ` now copies into `~/.clawdbot/extensions` (use `--link` to keep path-based loading). +- **BREAKING:** `moltbot hooks` is now `moltbot webhooks`; hooks live under `moltbot hooks`. https://docs.molt.bot/cli/webhooks +- **BREAKING:** `moltbot plugins install ` now copies into `~/.clawdbot/extensions` (use `--link` to keep path-based loading). ### Changes - Plugins: ship bundled plugins disabled by default and allow overrides by installed versions. (#1066) — thanks @ItzR3NO. @@ -541,7 +564,7 @@ Thanks @AlexMikhalev, @CoreyH, @John-Rood, @KrauseFx, @MaudeBot, @Nachx639, @Nic - Tools: send Chrome-like headers by default for `web_fetch` to improve extraction on bot-sensitive sites. - Tools: Firecrawl fallback now uses bot-circumvention + cache by default; remove basic HTML fallback when extraction fails. - Tools: default `exec` exit notifications and auto-migrate legacy `tools.bash` to `tools.exec`. -- Tools: add `exec` PTY support for interactive sessions. https://docs.clawd.bot/tools/exec +- Tools: add `exec` PTY support for interactive sessions. https://docs.molt.bot/tools/exec - Tools: add tmux-style `process send-keys` and bracketed paste helpers for PTY sessions. - Tools: add `process submit` helper to send CR for PTY sessions. - Tools: respond to PTY cursor position queries to unblock interactive TUIs. @@ -549,7 +572,7 @@ Thanks @AlexMikhalev, @CoreyH, @John-Rood, @KrauseFx, @MaudeBot, @Nachx639, @Nic - Skills: update coding-agent guidance to prefer PTY-enabled exec runs and simplify tmux usage. - TUI: refresh session token counts after runs complete or fail. (#1079) — thanks @d-ploutarchos. - Status: trim `/status` to current-provider usage only and drop the OAuth/token block. -- Directory: unify `clawdbot directory` across channels and plugin channels. +- Directory: unify `moltbot directory` across channels and plugin channels. - UI: allow deleting sessions from the Control UI. - Memory: add sqlite-vec vector acceleration with CLI status details. - Memory: add experimental session transcript indexing for memory_search (opt-in via memorySearch.experimental.sessionMemory + sources). @@ -565,7 +588,7 @@ Thanks @AlexMikhalev, @CoreyH, @John-Rood, @KrauseFx, @MaudeBot, @Nachx639, @Nic - Docs: add `/help` hub, Node/npm PATH guide, and expand directory CLI docs. - Config: support env var substitution in config values. (#1044) — thanks @sebslight. - Health: add per-agent session summaries and account-level health details, and allow selective probes. (#1047) — thanks @gumadeiras. -- Hooks: add hook pack installs (npm/path/zip/tar) with `clawdbot.hooks` manifests and `clawdbot hooks install/update`. +- Hooks: add hook pack installs (npm/path/zip/tar) with `moltbot.hooks` manifests and `moltbot hooks install/update`. - Plugins: add zip installs and `--link` to avoid copying local paths. ### Fixes @@ -596,10 +619,10 @@ Thanks @AlexMikhalev, @CoreyH, @John-Rood, @KrauseFx, @MaudeBot, @Nachx639, @Nic - Sessions: hard-stop `sessions.delete` cleanup. - Channels: treat replies to the bot as implicit mentions across supported channels. - Channels: normalize object-format capabilities in channel capability parsing. -- Security: default-deny slash/control commands unless a channel computed `CommandAuthorized` (fixes accidental “open” behavior), and ensure WhatsApp + Zalo plugin channels gate inline `/…` tokens correctly. https://docs.clawd.bot/gateway/security +- Security: default-deny slash/control commands unless a channel computed `CommandAuthorized` (fixes accidental “open” behavior), and ensure WhatsApp + Zalo plugin channels gate inline `/…` tokens correctly. https://docs.molt.bot/gateway/security - Security: redact sensitive text in gateway WS logs. - Tools: cap pending `exec` process output to avoid unbounded buffers. -- CLI: speed up `clawdbot sandbox-explain` by avoiding heavy plugin imports when normalizing channel ids. +- CLI: speed up `moltbot sandbox-explain` by avoiding heavy plugin imports when normalizing channel ids. - Browser: remote profile tab operations prefer persistent Playwright and avoid silent HTTP fallbacks. (#1057) — thanks @mukhtharcm. - Browser: remote profile tab ops follow-up: shared Playwright loader, Playwright-based focus, and more coverage (incl. opt-in live Browserless test). (follow-up to #1057) — thanks @mukhtharcm. - Browser: refresh extension relay tab metadata after navigation so `/json/list` stays current. (#1073) — thanks @roshanasingh4. @@ -625,19 +648,19 @@ Thanks @AlexMikhalev, @CoreyH, @John-Rood, @KrauseFx, @MaudeBot, @Nachx639, @Nic ## 2026.1.15 ### Highlights -- Plugins: add provider auth registry + `clawdbot models auth login` for plugin-driven OAuth/API key flows. +- Plugins: add provider auth registry + `moltbot models auth login` for plugin-driven OAuth/API key flows. - Browser: improve remote CDP/Browserless support (auth passthrough, `wss` upgrade, timeouts, clearer errors). - Heartbeat: per-agent configuration + 24h duplicate suppression. (#980) — thanks @voidserf. - Security: audit warns on weak model tiers; app nodes store auth tokens encrypted (Keychain/SecurePrefs). ### Breaking - **BREAKING:** iOS minimum version is now 18.0 to support Textual markdown rendering in native chat. (#702) -- **BREAKING:** Microsoft Teams is now a plugin; install `@clawdbot/msteams` via `clawdbot plugins install @clawdbot/msteams`. +- **BREAKING:** Microsoft Teams is now a plugin; install `@moltbot/msteams` via `moltbot plugins install @moltbot/msteams`. - **BREAKING:** Channel auth now prefers config over env for Discord/Telegram/Matrix (env is fallback only). (#1040) — thanks @thewilloftheshadow. ### Changes - UI/Apps: move channel/config settings to schema-driven forms and rename Connections → Channels. (#1040) — thanks @thewilloftheshadow. -- CLI: set process titles to `clawdbot-` for clearer process listings. +- CLI: set process titles to `moltbot-` for clearer process listings. - CLI/macOS: sync remote SSH target/identity to config and let `gateway status` auto-infer SSH targets (ssh-config aware). - Telegram: scope inline buttons with allowlist default + callback gating in DMs/groups. - Telegram: default reaction notifications to own. @@ -645,13 +668,13 @@ Thanks @AlexMikhalev, @CoreyH, @John-Rood, @KrauseFx, @MaudeBot, @Nachx639, @Nic - Heartbeat: tighten prompt guidance + suppress duplicate alerts for 24h. (#980) — thanks @voidserf. - Repo: ignore local identity files to avoid accidental commits. (#1001) — thanks @gerardward2007. - Sessions/Security: add `session.dmScope` for multi-user DM isolation and audit warnings. (#948) — thanks @Alphonse-arianee. -- Plugins: add provider auth registry + `clawdbot models auth login` for plugin-driven OAuth/API key flows. +- Plugins: add provider auth registry + `moltbot models auth login` for plugin-driven OAuth/API key flows. - Onboarding: switch channels setup to a single-select loop with per-channel actions and disabled hints in the picker. - TUI: show provider/model labels for the active session and default model. - Heartbeat: add per-agent heartbeat configuration and multi-agent docs example. - UI: show gateway auth guidance + doc link on unauthorized Control UI connections. - UI: add session deletion action in Control UI sessions list. (#1017) — thanks @Szpadel. -- Security: warn on weak model tiers (Haiku, below GPT-5, below Claude 4.5) in `clawdbot security audit`. +- Security: warn on weak model tiers (Haiku, below GPT-5, below Claude 4.5) in `moltbot security audit`. - Apps: store node auth tokens encrypted (Keychain/SecurePrefs). - Daemon: share profile/state-dir resolution across service helpers and honor `CLAWDBOT_STATE_DIR` for Windows task scripts. - Docs: clarify multi-gateway rescue bot guidance. (#969) — thanks @bjesuiter. @@ -661,8 +684,8 @@ Thanks @AlexMikhalev, @CoreyH, @John-Rood, @KrauseFx, @MaudeBot, @Nachx639, @Nic - Docs: add Date & Time guide and update prompt/timezone configuration docs. - Messages: debounce rapid inbound messages across channels with per-connector overrides. (#971) — thanks @juanpablodlc. - Messages: allow media-only sends (CLI/tool) and show Telegram voice recording status for voice notes. (#957) — thanks @rdev. -- Auth/Status: keep auth profiles sticky per session (rotate on compaction/new), surface provider usage headers in `/status` and `clawdbot models status`, and update docs. -- CLI: add `--json` output for `clawdbot daemon` lifecycle/install commands. +- Auth/Status: keep auth profiles sticky per session (rotate on compaction/new), surface provider usage headers in `/status` and `moltbot models status`, and update docs. +- CLI: add `--json` output for `moltbot daemon` lifecycle/install commands. - Memory: make `node-llama-cpp` an optional dependency (avoid Node 25 install failures) and improve local-embeddings fallback/errors. - Browser: add `snapshot refs=aria` (Playwright aria-ref ids) for self-resolving refs across `snapshot` → `act`. - Browser: `profile="chrome"` now defaults to host control and returns clearer “attach a tab” errors. @@ -685,10 +708,10 @@ Thanks @AlexMikhalev, @CoreyH, @John-Rood, @KrauseFx, @MaudeBot, @Nachx639, @Nic - iMessage: treat missing `imsg rpc` support as fatal to avoid restart loops. - Auth: merge main auth profiles into per-agent stores for sub-agents and document inheritance. (#1013) — thanks @marcmarg. - Agents: avoid JSON Schema `format` collisions in tool params by renaming snapshot format fields. (#1013) — thanks @marcmarg. -- Fix: make `clawdbot update` auto-update global installs when installed via a package manager. +- Fix: make `moltbot update` auto-update global installs when installed via a package manager. - Fix: list model picker entries as provider/model pairs for explicit selection. (#970) — thanks @mcinteerj. - Fix: align OpenAI image-gen defaults with DALL-E 3 standard quality and document output formats. (#880) — thanks @mkbehr. -- Fix: persist `gateway.mode=local` after selecting Local run mode in `clawdbot configure`, even if no other sections are chosen. +- Fix: persist `gateway.mode=local` after selecting Local run mode in `moltbot configure`, even if no other sections are chosen. - Daemon: fix profile-aware service label resolution (env-driven) and add coverage for launchd/systemd/schtasks. (#969) — thanks @bjesuiter. - Agents: avoid false positives when logging unsupported Google tool schema keywords. - Agents: skip Gemini history downgrades for google-antigravity to preserve tool calls. (#894) — thanks @mukhtharcm. @@ -714,13 +737,13 @@ Thanks @AlexMikhalev, @CoreyH, @John-Rood, @KrauseFx, @MaudeBot, @Nachx639, @Nic - Web search: `web_search`/`web_fetch` tools (Brave API) + first-time setup in onboarding/configure. - Browser control: Chrome extension relay takeover mode + remote browser control support. - Plugins: channel plugins (gateway HTTP hooks) + Zalo plugin + onboarding install flow. (#854) — thanks @longmaba. -- Security: expanded `clawdbot security audit` (+ `--fix`), detect-secrets CI scan, and a `SECURITY.md` reporting policy. +- Security: expanded `moltbot security audit` (+ `--fix`), detect-secrets CI scan, and a `SECURITY.md` reporting policy. ### Changes - Docs: clarify per-agent auth stores, sandboxed skill binaries, and elevated semantics. - Docs: add FAQ entries for missing provider auth after adding agents and Gemini thinking signature errors. - Agents: add optional auth-profile copy prompt on `agents add` and improve auth error messaging. -- Security: expand `clawdbot security audit` checks (model hygiene, config includes, plugin allowlists, exposure matrix) and extend `--fix` to tighten more sensitive state paths. +- Security: expand `moltbot security audit` checks (model hygiene, config includes, plugin allowlists, exposure matrix) and extend `--fix` to tighten more sensitive state paths. - Security: add `SECURITY.md` reporting policy. - Channels: add Matrix plugin (external) with docs + onboarding hooks. - Plugins: add Zalo channel plugin with gateway HTTP hooks and onboarding install prompt. (#854) — thanks @longmaba. @@ -730,7 +753,7 @@ Thanks @AlexMikhalev, @CoreyH, @John-Rood, @KrauseFx, @MaudeBot, @Nachx639, @Nic - Security: add detect-secrets CI scan and baseline guidance. (#227) — thanks @Hyaxia. - Tools: add `web_search`/`web_fetch` (Brave API), auto-enable `web_fetch` for sandboxed sessions, and remove the `brave-search` skill. - CLI/Docs: add a web tools configure section for storing Brave API keys and update onboarding tips. -- Browser: add Chrome extension relay takeover mode (toolbar button), plus `clawdbot browser extension install/path` and remote browser control (standalone server + token auth). +- Browser: add Chrome extension relay takeover mode (toolbar button), plus `moltbot browser extension install/path` and remote browser control (standalone server + token auth). ### Fixes - Sessions: refactor session store updates to lock + mutate per-entry, add chat.inject, and harden subagent cleanup flow. (#944) — thanks @tyler6204. @@ -827,19 +850,19 @@ Thanks @AlexMikhalev, @CoreyH, @John-Rood, @KrauseFx, @MaudeBot, @Nachx639, @Nic ### New & Improved - Memory: add custom OpenAI-compatible embedding endpoints; support OpenAI/local `node-llama-cpp` embeddings with per-agent overrides and provider metadata in tools/CLI. (#819) — thanks @mukhtharcm. -- Memory: new `clawdbot memory` CLI plus `memory_search`/`memory_get` tools with snippets + line ranges; index stored under `~/.clawdbot/memory/{agentId}.sqlite` with watch-on-by-default. +- Memory: new `moltbot memory` CLI plus `memory_search`/`memory_get` tools with snippets + line ranges; index stored under `~/.clawdbot/memory/{agentId}.sqlite` with watch-on-by-default. - Agents: strengthen memory recall guidance; make workspace bootstrap truncation configurable (default 20k) with warnings; add default sub-agent model config. - Tools/Sandbox: add tool profiles + group shorthands; support tool-policy groups in `tools.sandbox.tools`; drop legacy `memory` shorthand; allow Docker bind mounts via `docker.binds`. (#790) — thanks @akonyer. - Tools: add provider/model-specific tool policy overrides (`tools.byProvider`) to trim tool exposure per provider. - Tools: add browser `scrollintoview` action; allow Claude/Gemini tool param aliases; allow thinking `xhigh` for GPT-5.2/Codex with safe downgrades. (#793) — thanks @hsrvc; (#444) — thanks @grp06. -- Gateway/CLI: add Tailscale binary discovery, custom bind mode, and probe auth retry; add `clawdbot dashboard` auto-open flow; default native slash commands to `"auto"` with per-provider overrides. (#740) — thanks @jeffersonwarrior. +- Gateway/CLI: add Tailscale binary discovery, custom bind mode, and probe auth retry; add `moltbot dashboard` auto-open flow; default native slash commands to `"auto"` with per-provider overrides. (#740) — thanks @jeffersonwarrior. - Auth/Onboarding: add Chutes OAuth (PKCE + refresh + onboarding choice); normalize API key inputs; default TUI onboarding to `deliver: false`. (#726) — thanks @FrieSei; (#791) — thanks @roshanasingh4. - Providers: add `discord.allowBots`; trim legacy MiniMax M2 from default catalogs; route MiniMax vision to the Coding Plan VLM endpoint (also accepts `@/path/to/file.png` inputs). (#802) — thanks @zknicker. - Gateway: allow Tailscale Serve identity headers to satisfy token auth; rebuild Control UI assets when protocol schema is newer. (#823) — thanks @roshanasingh4; (#786) — thanks @meaningfool. - Heartbeat: default `ackMaxChars` to 300 so short `HEARTBEAT_OK` replies stay internal. ### Installer -- Install: run `clawdbot doctor --non-interactive` after git installs/updates and nudge daemon restarts when detected. +- Install: run `moltbot doctor --non-interactive` after git installs/updates and nudge daemon restarts when detected. ### Fixes - Doctor: warn on pnpm workspace mismatches, missing Control UI assets, and missing tsx binaries; offer UI rebuilds. @@ -860,7 +883,7 @@ Thanks @AlexMikhalev, @CoreyH, @John-Rood, @KrauseFx, @MaudeBot, @Nachx639, @Nic - Telegram: preserve forum topic thread ids, persist polling offsets, respect account bindings in webhook mode, and show typing indicator in General topics. (#727, #739) — thanks @thewilloftheshadow; (#821) — thanks @gumadeiras; (#779) — thanks @azade-c. - Slack: accept slash commands with or without leading `/` for custom command configs. (#798) — thanks @thewilloftheshadow. - Cron: persist disabled jobs correctly; accept `jobId` aliases for update/run/remove params. (#205, #252) — thanks @thewilloftheshadow. -- Gateway/CLI: honor `CLAWDBOT_LAUNCHD_LABEL` / `CLAWDBOT_SYSTEMD_UNIT` overrides; `agents.list` respects explicit config; reduce noisy loopback WS logs during tests; run `clawdbot doctor --non-interactive` during updates. (#781) — thanks @ronyrus. +- Gateway/CLI: honor `CLAWDBOT_LAUNCHD_LABEL` / `CLAWDBOT_SYSTEMD_UNIT` overrides; `agents.list` respects explicit config; reduce noisy loopback WS logs during tests; run `moltbot doctor --non-interactive` during updates. (#781) — thanks @ronyrus. - Onboarding/Control UI: refuse invalid configs (run doctor first); quote Windows browser URLs for OAuth; keep chat scroll position unless the user is near the bottom. (#764) — thanks @mukhtharcm; (#794) — thanks @roshanasingh4; (#217) — thanks @thewilloftheshadow. - Tools/UI: harden tool input schemas for strict providers; drop null-only union variants for Gemini schema cleanup; treat `maxChars: 0` as unlimited; keep TUI last streamed response instead of "(no output)". (#782) — thanks @AbhisekBasu1; (#796) — thanks @gabriel-trigo; (#747) — thanks @thewilloftheshadow. - Connections UI: polish multi-account account cards. (#816) — thanks @steipete. @@ -889,7 +912,7 @@ Thanks @AlexMikhalev, @CoreyH, @John-Rood, @KrauseFx, @MaudeBot, @Nachx639, @Nic - Auto-reply: add compact `/model` picker (models + available providers) and show provider endpoints in `/model status`. - Control UI: add Config tab model presets (MiniMax M2.1, GLM 4.7, Kimi) for one-click setup. - Plugins: add extension loader (tools/RPC/CLI/services), discovery paths, and config schema + Control UI labels (uiHints). -- Plugins: add `clawdbot plugins install` (path/tgz/npm), plus `list|info|enable|disable|doctor` UX. +- Plugins: add `moltbot plugins install` (path/tgz/npm), plus `list|info|enable|disable|doctor` UX. - Plugins: voice-call plugin now real (Twilio/log), adds start/status RPC/CLI/tool + tests. - Docs: add plugins doc + cross-links from tools/skills/gateway config. - Docs: add beginner-friendly plugin quick start + expand Voice Call plugin docs. @@ -902,7 +925,7 @@ Thanks @AlexMikhalev, @CoreyH, @John-Rood, @KrauseFx, @MaudeBot, @Nachx639, @Nic - Agents: add pre-compaction memory flush config (`agents.defaults.compaction.*`) with a soft threshold + system prompt. - Config: add `$include` directive for modular config files. (#731) — thanks @pasogott. - Build: set pnpm minimum release age to 2880 minutes (2 days). (#718) — thanks @dan-dr. -- macOS: prompt to install the global `clawdbot` CLI when missing in local mode; install via `clawd.bot/install-cli.sh` (no onboarding) and use external launchd/CLI instead of the embedded gateway runtime. +- macOS: prompt to install the global `moltbot` CLI when missing in local mode; install via `molt.bot/install-cli.sh` (no onboarding) and use external launchd/CLI instead of the embedded gateway runtime. - Docs: add gog calendar event color IDs from `gog calendar colors`. (#715) — thanks @mjrussell. - Cron/CLI: add `--model` flag to cron add/edit commands. (#711) — thanks @mjrussell. - Cron/CLI: trim model overrides on cron edits and document main-session guidance. (#711) — thanks @mjrussell. @@ -916,7 +939,7 @@ Thanks @AlexMikhalev, @CoreyH, @John-Rood, @KrauseFx, @MaudeBot, @Nachx639, @Nic ### Installer - Postinstall: replace `git apply` with builtin JS patcher (works npm/pnpm/bun; no git dependency) plus regression tests. - Postinstall: skip pnpm patch fallback when the new patcher is active. -- Installer tests: add root+non-root docker smokes, CI workflow to fetch clawd.bot scripts and run install sh/cli with onboarding skipped. +- Installer tests: add root+non-root docker smokes, CI workflow to fetch molt.bot scripts and run install sh/cli with onboarding skipped. - Installer UX: support `CLAWDBOT_NO_ONBOARD=1` for non-interactive installs; fix npm prefix on Linux and auto-install git. - Installer UX: add `install.sh --help` with flags/env and git install hint. - Installer UX: add `--install-method git|npm` and auto-detect source checkouts (prompt to update git checkout vs migrate to npm). @@ -932,7 +955,7 @@ Thanks @AlexMikhalev, @CoreyH, @John-Rood, @KrauseFx, @MaudeBot, @Nachx639, @Nic - Auth: read Codex keychain credentials and make the lookup platform-aware. - macOS/Release: avoid bundling dist artifacts in relay builds and generate appcasts from zip-only sources. - Doctor: surface plugin diagnostics in the report. -- Plugins: treat `plugins.load.paths` directory entries as package roots when they contain `package.json` + `clawdbot.extensions`; load plugin packages from config dirs; extract archives without system tar. +- Plugins: treat `plugins.load.paths` directory entries as package roots when they contain `package.json` + `moltbot.extensions`; load plugin packages from config dirs; extract archives without system tar. - Config: expand `~` in `CLAWDBOT_CONFIG_PATH` and common path-like config fields (including `plugins.load.paths`); guard invalid `$include` paths. (#731) — thanks @pasogott. - Agents: stop pre-creating session transcripts so first user messages persist in JSONL history. - Agents: skip pre-compaction memory flush when the session workspace is read-only. @@ -961,9 +984,9 @@ Thanks @AlexMikhalev, @CoreyH, @John-Rood, @KrauseFx, @MaudeBot, @Nachx639, @Nic ## 2026.1.10 ### Highlights -- CLI: `clawdbot status` now table-based + shows OS/update/gateway/daemon/agents/sessions; `status --all` adds a full read-only debug report (tables, log tails, Tailscale summary, and scan progress via OSC-9 + spinner). +- CLI: `moltbot status` now table-based + shows OS/update/gateway/daemon/agents/sessions; `status --all` adds a full read-only debug report (tables, log tails, Tailscale summary, and scan progress via OSC-9 + spinner). - CLI Backends: add Codex CLI fallback with resume support (text output) and JSONL parsing for new runs, plus a live CLI resume probe. -- CLI: add `clawdbot update` (safe-ish git checkout update) + `--update` shorthand. (#673) — thanks @fm1randa. +- CLI: add `moltbot update` (safe-ish git checkout update) + `--update` shorthand. (#673) — thanks @fm1randa. - Gateway: add OpenAI-compatible `/v1/chat/completions` HTTP endpoint (auth, SSE streaming, per-agent routing). (#680). ### Changes @@ -973,7 +996,7 @@ Thanks @AlexMikhalev, @CoreyH, @John-Rood, @KrauseFx, @MaudeBot, @Nachx639, @Nic - Agents/Browser: add `browser.target` (sandbox/host/custom) with sandbox host-control gating via `agents.defaults.sandbox.browser.allowHostControl`, allowlists for custom control URLs/hosts/ports, and expand browser tool docs (remote control, profiles, internals). - Onboarding/Models: add catalog-backed default model picker to onboarding + configure. (#611) — thanks @jonasjancarik. - Agents/OpenCode Zen: update fallback models + defaults, keep legacy alias mappings. (#669) — thanks @magimetal. -- CLI: add `clawdbot reset` and `clawdbot uninstall` flows (interactive + non-interactive) plus docker cleanup smoke test. +- CLI: add `moltbot reset` and `moltbot uninstall` flows (interactive + non-interactive) plus docker cleanup smoke test. - Providers: move provider wiring to a plugin architecture. (#661). - Providers: unify group history context wrappers across providers with per-provider/per-account `historyLimit` overrides (fallback to `messages.groupChat.historyLimit`). Set `0` to disable. (#672). - Gateway/Heartbeat: optionally deliver heartbeat `Reasoning:` output (`agents.defaults.heartbeat.includeReasoning`). (#690) @@ -982,7 +1005,7 @@ Thanks @AlexMikhalev, @CoreyH, @John-Rood, @KrauseFx, @MaudeBot, @Nachx639, @Nic ### Fixes - Auto-reply: suppress draft/typing streaming for `NO_REPLY` (silent system ops) so it doesn’t leak partial output. - CLI/Status: expand tables to full terminal width; clarify provider setup vs runtime warnings; richer per-provider detail; token previews in `status` while keeping `status --all` redacted; add troubleshooting link footer; keep log tails pasteable; show gateway auth used when reachable; surface provider runtime errors (Signal/iMessage/Slack); harden `tailscale status --json` parsing; make `status --all` scan progress determinate; and replace the footer with a 3-line “Next steps” recommendation (share/debug/probe). -- CLI/Gateway: clarify that `clawdbot gateway status` reports RPC health (connect + RPC) and shows RPC failures separately from connect failures. +- CLI/Gateway: clarify that `moltbot gateway status` reports RPC health (connect + RPC) and shows RPC failures separately from connect failures. - CLI/Update: gate progress spinner on stdout TTY and align clean-check step label. (#701) — thanks @bjesuiter. - Telegram: add `/whoami` + `/id` commands to reveal sender id for allowlists; allow `@username` and prefixed ids in `allowFrom` prompts (with stability warning). - Heartbeat: strip markup-wrapped `HEARTBEAT_OK` so acks don’t leak to external providers (e.g., Telegram). @@ -995,7 +1018,7 @@ Thanks @AlexMikhalev, @CoreyH, @John-Rood, @KrauseFx, @MaudeBot, @Nachx639, @Nic - Agents/Pi: inject config `temperature`/`maxTokens` into streaming without replacing the session streamFn; cover with live maxTokens probe. (#732) — thanks @peschee. - macOS: clear unsigned launchd overrides on signed restarts and warn via doctor when attach-only/disable markers are set. (#695) — thanks @jeffersonwarrior. - Agents: enforce single-writer session locks and drop orphan tool results to prevent tool-call ID failures (MiniMax/Anthropic-compatible APIs). -- Docs: make `clawdbot status` the first diagnostic step, clarify `status --deep` behavior, and document `/whoami` + `/id`. +- Docs: make `moltbot status` the first diagnostic step, clarify `status --deep` behavior, and document `/whoami` + `/id`. - Docs/Testing: clarify live tool+image probes and how to list your testable `provider/model` ids. - Tests/Live: make gateway bash+read probes resilient to provider formatting while still validating real tool calls. - WhatsApp: detect @lid mentions in groups using authDir reverse mapping + resolve self JID E.164 for mention gating. (#692) — thanks @peschee. @@ -1015,7 +1038,7 @@ Thanks @AlexMikhalev, @CoreyH, @John-Rood, @KrauseFx, @MaudeBot, @Nachx639, @Nic - WhatsApp: expose group participant IDs to the model so reactions can target the right sender. - Cron: `wakeMode: "now"` waits for heartbeat completion (and retries when the main lane is busy). (#666) — thanks @roshanasingh4. - Agents/OpenAI: fix Responses tool-only → follow-up turn handling (avoid standalone `reasoning` items that trigger 400 “required following item”) and replay reasoning items in Responses/Codex Responses history for tool-call-only turns. -- Sandbox: add `clawdbot sandbox explain` (effective policy inspector + fix-it keys); improve “sandbox jail” tool-policy/elevated errors with actionable config key paths; link to docs. +- Sandbox: add `moltbot sandbox explain` (effective policy inspector + fix-it keys); improve “sandbox jail” tool-policy/elevated errors with actionable config key paths; link to docs. - Hooks/Gmail: keep Tailscale serve path at `/` while preserving the public path. (#668) — thanks @antons. - Hooks/Gmail: allow Tailscale target URLs to preserve internal serve paths. - Auth: update Claude Code keychain credentials in-place during refresh sync; share JSON file helpers; add CLI fallback coverage. @@ -1027,12 +1050,12 @@ Thanks @AlexMikhalev, @CoreyH, @John-Rood, @KrauseFx, @MaudeBot, @Nachx639, @Nic - Gateway/Control UI: sniff image attachments for chat.send, drop non-images, and log mismatches. (#670) — thanks @cristip73. - macOS: force `restart-mac.sh --sign` to require identities and keep bundled Node signed for relay verification. (#580) — thanks @jeffersonwarrior. - Gateway/Agent: accept image attachments on `agent` (multimodal message) and add live gateway image probe (`CLAWDBOT_LIVE_GATEWAY_IMAGE_PROBE=1`). -- CLI: `clawdbot sessions` now includes `elev:*` + `usage:*` flags in the table output. +- CLI: `moltbot sessions` now includes `elev:*` + `usage:*` flags in the table output. - CLI/Pairing: accept positional provider for `pairing list|approve` (npm-run compatible); update docs/bot hints. -- Branding: normalize user-facing “ClawdBot”/“CLAWDBOT” → “Clawdbot” (CLI, status, docs). +- Branding: normalize legacy casing/branding to “Moltbot” (CLI, status, docs). - Auto-reply: fix native `/model` not updating the actual chat session (Telegram/Slack/Discord). (#646) -- Doctor: offer to run `clawdbot update` first on git installs (keeps doctor output aligned with latest). -- Doctor: avoid false legacy workspace warning when install dir is `~/clawdbot`. (#660) +- Doctor: offer to run `moltbot update` first on git installs (keeps doctor output aligned with latest). +- Doctor: avoid false legacy workspace warning when install dir is `~/moltbot`. (#660) - iMessage: fix reasoning persistence across DMs; avoid partial/duplicate replies when reasoning is enabled. (#655) — thanks @antons. - Models/Auth: allow MiniMax API configs without `models.providers.minimax.apiKey` (auth profiles / `MINIMAX_API_KEY`). (#656) — thanks @mneves75. - Agents: avoid duplicate replies when the message tool sends. (#659) — thanks @mickahouan. @@ -1063,12 +1086,12 @@ Thanks @AlexMikhalev, @CoreyH, @John-Rood, @KrauseFx, @MaudeBot, @Nachx639, @Nic - Control UI/TUI: queued messages, session links, reasoning view, mobile polish, logs UX. ### Breaking -- CLI: `clawdbot message` now subcommands (`message send|poll|...`) and requires `--provider` unless only one provider configured. +- CLI: `moltbot message` now subcommands (`message send|poll|...`) and requires `--provider` unless only one provider configured. - Commands/Tools: `/restart` and gateway restart tool disabled by default; enable with `commands.restart=true`. ### New Features and Changes - Models/Auth: OpenCode Zen onboarding (#623) — thanks @magimetal; MiniMax Anthropic-compatible API + hosted onboarding (#590, #495) — thanks @mneves75, @tobiasbischoff. -- Models/Auth: setup-token + token auth profiles; `clawdbot models auth order {get,set,clear}`; per-agent auth candidates in `/model status`; OAuth expiry checks in doctor/status. +- Models/Auth: setup-token + token auth profiles; `moltbot models auth order {get,set,clear}`; per-agent auth candidates in `/model status`; OAuth expiry checks in doctor/status. - Agent/System: claude-cli runner; `session_status` tool (and sandbox allow); adaptive context pruning default; system prompt messaging guidance + no auto self-update; eligible skills list injection; sub-agent context trimmed. - Commands: `/commands` list; `/models` alias; `/usage` alias; `/debug` runtime overrides + effective config view; `/config` chat updates + `/config get`; `config --section`. - CLI/Gateway: unified message tool + message subcommands; gateway discover (local + wide-area DNS-SD) with JSON/timeout; gateway status human-readable + JSON + SSH loopback; wide-area records include gatewayPort/sshPort/cliPath + tailnet DNS fallback. @@ -1100,7 +1123,7 @@ Thanks @AlexMikhalev, @CoreyH, @John-Rood, @KrauseFx, @MaudeBot, @Nachx639, @Nic - Signal: reaction handling safety; own-reaction matching (uuid+phone); UUID-only senders accepted; ignore reaction-only messages. - MS Teams: download image attachments reliably; fix top-level replies; stop on shutdown + honor chunk limits; normalize poll providers/deps; pairing label fixes. - iMessage: isolate group-ish threads by chat_id. -- Gateway/Daemon/Doctor: atomic config writes; repair gateway service entrypoint + install switches; non-interactive legacy migrations; systemd unit alignment + KillMode=process; node bridge keepalive/pings; Launch at Login persistence; bundle ClawdbotKit resources + Swift 6.2 compat dylib; relay version check + remove smoke test; regen Swift GatewayModels + keep agent provider string; cron jobId alias + channel alias migration + main session key normalization; heartbeat Telegram accountId resolution; avoid WhatsApp fallback for internal runs; gateway listener error wording; serveBaseUrl param; honor gateway --dev; fix wide-area discovery updates; align agents.defaults schema; provider account metadata in daemon status; refresh Carbon patch for gateway fixes; restore doctor prompter initialValue handling. +- Gateway/Daemon/Doctor: atomic config writes; repair gateway service entrypoint + install switches; non-interactive legacy migrations; systemd unit alignment + KillMode=process; node bridge keepalive/pings; Launch at Login persistence; bundle MoltbotKit resources + Swift 6.2 compat dylib; relay version check + remove smoke test; regen Swift GatewayModels + keep agent provider string; cron jobId alias + channel alias migration + main session key normalization; heartbeat Telegram accountId resolution; avoid WhatsApp fallback for internal runs; gateway listener error wording; serveBaseUrl param; honor gateway --dev; fix wide-area discovery updates; align agents.defaults schema; provider account metadata in daemon status; refresh Carbon patch for gateway fixes; restore doctor prompter initialValue handling. - Control UI/TUI: persist per-session verbose off + hide tool cards; logs tab opens at bottom; relative asset paths + landing cleanup; session labels lookup/persistence; stop pinning main session in recents; start logs at bottom; TUI status bar refresh + timeout handling + hide reasoning label when off. - Onboarding/Configure: QuickStart single-select provider picker; avoid Codex CLI false-expiry warnings; clarify WhatsApp owner prompt; fix Minimax hosted onboarding (agents.defaults + msteams heartbeat target); remove configure Control UI prompt; honor gateway --dev flag. @@ -1126,7 +1149,7 @@ Thanks @AlexMikhalev, @CoreyH, @John-Rood, @KrauseFx, @MaudeBot, @Nachx639, @Nic - Previously, if you didn’t configure an allowlist, your bot could be **open to anyone** (especially discoverable Telegram bots). - New default: DM pairing (`dmPolicy="pairing"` / `discord.dm.policy="pairing"` / `slack.dm.policy="pairing"`). - To keep old “open to everyone” behavior: set `dmPolicy="open"` and include `"*"` in the relevant `allowFrom` (Discord/Slack: `discord.dm.allowFrom` / `slack.dm.allowFrom`). - - Approve requests via `clawdbot pairing list ` + `clawdbot pairing approve `. + - Approve requests via `moltbot pairing list ` + `moltbot pairing approve `. - Sandbox: default `agent.sandbox.scope` to `"agent"` (one container/workspace per agent). Use `"session"` for per-session isolation; `"shared"` disables cross-session isolation. - Timestamps in agent envelopes are now UTC (compact `YYYY-MM-DDTHH:mmZ`); removed `messages.timestampPrefix`. Add `agent.userTimezone` to tell the model the user’s local time (system prompt only). - Model config schema changes (auth profiles + model lists); doctor auto-migrates and the gateway rewrites legacy configs on startup. @@ -1140,7 +1163,7 @@ Thanks @AlexMikhalev, @CoreyH, @John-Rood, @KrauseFx, @MaudeBot, @Nachx639, @Nic - **Agent loop + compaction:** compaction/pruning tuning, overflow handling, safer bootstrap context, and per-provider threading/confirmations; opt-in tool-result pruning + compact tracking. - **Sandbox + tools:** per-agent sandbox overrides, workspaceAccess controls, session tool visibility, tool policy overrides, process isolation, and tool schema/timeout/reaction unification. - **Providers (Telegram/WhatsApp/Discord/Slack/Signal/iMessage):** retry/backoff, threading, reactions, media groups/attachments, mention gating, typing behavior, and error/log stability; long polling + forum topic isolation for Telegram. -- **Gateway/CLI UX:** `clawdbot logs`, cron list colors/aliases, docs search, agents list/add/delete flows, status usage snapshots, runtime/auth source display, and `/status`/commands auth unification. +- **Gateway/CLI UX:** `moltbot logs`, cron list colors/aliases, docs search, agents list/add/delete flows, status usage snapshots, runtime/auth source display, and `/status`/commands auth unification. - **Control UI/Web:** logs tab, focus mode polish, config form resilience, streaming stability, tool output caps, windowed chat history, and reconnect/password URL auth. - **macOS/Android/TUI/Build:** macOS gateway races, QR bundling, JSON5 config safety, Voice Wake hardening; Android EXIF rotation + APK naming/versioning; TUI key handling; tooling/bundling fixes. - **Packaging/compat:** npm dist folder coverage, Node 25 qrcode-terminal import fixes, Bun/Playwright/WebSocket patches, and Docker Bun install. @@ -1182,4 +1205,4 @@ Thanks @AlexMikhalev, @CoreyH, @John-Rood, @KrauseFx, @MaudeBot, @Nachx639, @Nic - Agent tools: honor `agent.tools` allow/deny policy even when sandbox is off. - Discord: avoid duplicate replies when OpenAI emits repeated `message_end` events. - Commands: unify /status (inline) and command auth across providers; group bypass for authorized control commands; remove Discord /clawd slash handler. -- CLI: run `clawdbot agent` via the Gateway by default; use `--local` to force embedded mode. +- CLI: run `moltbot agent` via the Gateway by default; use `--local` to force embedded mode. diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index d6eb0532f..509d5b11a 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,11 +1,11 @@ -# Contributing to Clawdbot +# Contributing to Moltbot Welcome to the lobster tank! 🦞 ## Quick Links -- **GitHub:** https://github.com/clawdbot/clawdbot +- **GitHub:** https://github.com/moltbot/moltbot - **Discord:** https://discord.gg/qkhbAGHRBT -- **X/Twitter:** [@steipete](https://x.com/steipete) / [@clawdbot](https://x.com/clawdbot) +- **X/Twitter:** [@steipete](https://x.com/steipete) / [@moltbot](https://x.com/moltbot) ## Maintainers @@ -20,11 +20,11 @@ Welcome to the lobster tank! 🦞 ## How to Contribute 1. **Bugs & small fixes** → Open a PR! -2. **New features / architecture** → Start a [GitHub Discussion](https://github.com/clawdbot/clawdbot/discussions) or ask in Discord first +2. **New features / architecture** → Start a [GitHub Discussion](https://github.com/moltbot/moltbot/discussions) or ask in Discord first 3. **Questions** → Discord #setup-help ## Before You PR -- Test locally with your Clawdbot instance +- Test locally with your Moltbot instance - Run linter: `npm run lint` - Keep PRs focused (one thing per PR) - Describe what & why @@ -49,4 +49,4 @@ We are currently prioritizing: - **Skills**: Expanding the library of bundled skills and improving the Skill Creation developer experience. - **Performance**: Optimizing token usage and compaction logic. -Check the [GitHub Issues](https://github.com/clawdbot/clawdbot/issues) for "good first issue" labels! +Check the [GitHub Issues](https://github.com/moltbot/moltbot/issues) for "good first issue" labels! diff --git a/Dockerfile b/Dockerfile index 642cfd612..9c6aa7036 100644 --- a/Dockerfile +++ b/Dockerfile @@ -24,7 +24,7 @@ COPY scripts ./scripts RUN pnpm install --frozen-lockfile COPY . . -RUN pnpm build +RUN CLAWDBOT_A2UI_SKIP_MISSING=1 pnpm build # Force pnpm for UI build (Bun may fail on ARM/Synology architectures) ENV CLAWDBOT_PREFER_PNPM=1 RUN pnpm ui:install diff --git a/Dockerfile.sandbox-browser b/Dockerfile.sandbox-browser index 3b18917b1..8d8a08701 100644 --- a/Dockerfile.sandbox-browser +++ b/Dockerfile.sandbox-browser @@ -20,9 +20,9 @@ RUN apt-get update \ xvfb \ && rm -rf /var/lib/apt/lists/* -COPY scripts/sandbox-browser-entrypoint.sh /usr/local/bin/clawdbot-sandbox-browser -RUN chmod +x /usr/local/bin/clawdbot-sandbox-browser +COPY scripts/sandbox-browser-entrypoint.sh /usr/local/bin/moltbot-sandbox-browser +RUN chmod +x /usr/local/bin/moltbot-sandbox-browser EXPOSE 9222 5900 6080 -CMD ["clawdbot-sandbox-browser"] +CMD ["moltbot-sandbox-browser"] diff --git a/README.md b/README.md index a3f0b11d1..7e884be33 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,7 @@ -# 🦞 Clawdbot — Personal AI Assistant +# 🦞 Moltbot — Personal AI Assistant

- Clawdbot + Clawdbot

@@ -9,67 +9,68 @@

- CI status - GitHub release - DeepWiki + CI status + GitHub release + DeepWiki Discord MIT License

-**Clawdbot** is a *personal AI assistant* you run on your own devices. +**Moltbot** is a *personal AI assistant* you run on your own devices. It answers you on the channels you already use (WhatsApp, Telegram, Slack, Discord, Google Chat, Signal, iMessage, Microsoft Teams, WebChat), plus extension channels like BlueBubbles, Matrix, Zalo, and Zalo Personal. It can speak and listen on macOS/iOS/Android, and can render a live Canvas you control. The Gateway is just the control plane — the product is the assistant. If you want a personal, single-user assistant that feels local, fast, and always-on, this is it. -[Website](https://clawdbot.com) · [Docs](https://docs.clawd.bot) · [Getting Started](https://docs.clawd.bot/start/getting-started) · [Updating](https://docs.clawd.bot/install/updating) · [Showcase](https://docs.clawd.bot/start/showcase) · [FAQ](https://docs.clawd.bot/start/faq) · [Wizard](https://docs.clawd.bot/start/wizard) · [Nix](https://github.com/clawdbot/nix-clawdbot) · [Docker](https://docs.clawd.bot/install/docker) · [Discord](https://discord.gg/clawd) +[Website](https://molt.bot) · [Docs](https://docs.molt.bot) · [Getting Started](https://docs.molt.bot/start/getting-started) · [Updating](https://docs.molt.bot/install/updating) · [Showcase](https://docs.molt.bot/start/showcase) · [FAQ](https://docs.molt.bot/start/faq) · [Wizard](https://docs.molt.bot/start/wizard) · [Nix](https://github.com/moltbot/nix-clawdbot) · [Docker](https://docs.molt.bot/install/docker) · [Discord](https://discord.gg/clawd) -Preferred setup: run the onboarding wizard (`clawdbot onboard`). It walks through gateway, workspace, channels, and skills. The CLI wizard is the recommended path and works on **macOS, Linux, and Windows (via WSL2; strongly recommended)**. +Preferred setup: run the onboarding wizard (`moltbot onboard`). It walks through gateway, workspace, channels, and skills. The CLI wizard is the recommended path and works on **macOS, Linux, and Windows (via WSL2; strongly recommended)**. Works with npm, pnpm, or bun. -New install? Start here: [Getting started](https://docs.clawd.bot/start/getting-started) +New install? Start here: [Getting started](https://docs.molt.bot/start/getting-started) **Subscriptions (OAuth):** - **[Anthropic](https://www.anthropic.com/)** (Claude Pro/Max) - **[OpenAI](https://openai.com/)** (ChatGPT/Codex) -Model note: while any model is supported, I strongly recommend **Anthropic Pro/Max (100/200) + Opus 4.5** for long‑context strength and better prompt‑injection resistance. See [Onboarding](https://docs.clawd.bot/start/onboarding). +Model note: while any model is supported, I strongly recommend **Anthropic Pro/Max (100/200) + Opus 4.5** for long‑context strength and better prompt‑injection resistance. See [Onboarding](https://docs.molt.bot/start/onboarding). ## Models (selection + auth) -- Models config + CLI: [Models](https://docs.clawd.bot/concepts/models) -- Auth profile rotation (OAuth vs API keys) + fallbacks: [Model failover](https://docs.clawd.bot/concepts/model-failover) +- Models config + CLI: [Models](https://docs.molt.bot/concepts/models) +- Auth profile rotation (OAuth vs API keys) + fallbacks: [Model failover](https://docs.molt.bot/concepts/model-failover) ## Install (recommended) Runtime: **Node ≥22**. ```bash -npm install -g clawdbot@latest -# or: pnpm add -g clawdbot@latest +npm install -g moltbot@latest +# or: pnpm add -g moltbot@latest -clawdbot onboard --install-daemon +moltbot onboard --install-daemon ``` The wizard installs the Gateway daemon (launchd/systemd user service) so it stays running. +Legacy note: `clawdbot` remains available as a compatibility shim. ## Quick start (TL;DR) Runtime: **Node ≥22**. -Full beginner guide (auth, pairing, channels): [Getting started](https://docs.clawd.bot/start/getting-started) +Full beginner guide (auth, pairing, channels): [Getting started](https://docs.molt.bot/start/getting-started) ```bash -clawdbot onboard --install-daemon +moltbot onboard --install-daemon -clawdbot gateway --port 18789 --verbose +moltbot gateway --port 18789 --verbose # Send a message -clawdbot message send --to +1234567890 --message "Hello from Clawdbot" +moltbot message send --to +1234567890 --message "Hello from Moltbot" # Talk to the assistant (optionally deliver back to any connected channel: WhatsApp/Telegram/Slack/Discord/Google Chat/Signal/iMessage/BlueBubbles/Microsoft Teams/Matrix/Zalo/Zalo Personal/WebChat) -clawdbot agent --message "Ship checklist" --thinking high +moltbot agent --message "Ship checklist" --thinking high ``` -Upgrading? [Updating guide](https://docs.clawd.bot/install/updating) (and run `clawdbot doctor`). +Upgrading? [Updating guide](https://docs.molt.bot/install/updating) (and run `moltbot doctor`). ## Development channels @@ -77,94 +78,94 @@ Upgrading? [Updating guide](https://docs.clawd.bot/install/updating) (and run `c - **beta**: prerelease tags (`vYYYY.M.D-beta.N`), npm dist-tag `beta` (macOS app may be missing). - **dev**: moving head of `main`, npm dist-tag `dev` (when published). -Switch channels (git + npm): `clawdbot update --channel stable|beta|dev`. -Details: [Development channels](https://docs.clawd.bot/install/development-channels). +Switch channels (git + npm): `moltbot update --channel stable|beta|dev`. +Details: [Development channels](https://docs.molt.bot/install/development-channels). ## From source (development) Prefer `pnpm` for builds from source. Bun is optional for running TypeScript directly. ```bash -git clone https://github.com/clawdbot/clawdbot.git -cd clawdbot +git clone https://github.com/moltbot/moltbot.git +cd moltbot pnpm install pnpm ui:build # auto-installs UI deps on first run pnpm build -pnpm clawdbot onboard --install-daemon +pnpm moltbot onboard --install-daemon # Dev loop (auto-reload on TS changes) pnpm gateway:watch ``` -Note: `pnpm clawdbot ...` runs TypeScript directly (via `tsx`). `pnpm build` produces `dist/` for running via Node / the packaged `clawdbot` binary. +Note: `pnpm moltbot ...` runs TypeScript directly (via `tsx`). `pnpm build` produces `dist/` for running via Node / the packaged `moltbot` binary. ## Security defaults (DM access) -Clawdbot connects to real messaging surfaces. Treat inbound DMs as **untrusted input**. +Moltbot connects to real messaging surfaces. Treat inbound DMs as **untrusted input**. -Full security guide: [Security](https://docs.clawd.bot/gateway/security) +Full security guide: [Security](https://docs.molt.bot/gateway/security) Default behavior on Telegram/WhatsApp/Signal/iMessage/Microsoft Teams/Discord/Google Chat/Slack: - **DM pairing** (`dmPolicy="pairing"` / `channels.discord.dm.policy="pairing"` / `channels.slack.dm.policy="pairing"`): unknown senders receive a short pairing code and the bot does not process their message. -- Approve with: `clawdbot pairing approve ` (then the sender is added to a local allowlist store). +- Approve with: `moltbot pairing approve ` (then the sender is added to a local allowlist store). - Public inbound DMs require an explicit opt-in: set `dmPolicy="open"` and include `"*"` in the channel allowlist (`allowFrom` / `channels.discord.dm.allowFrom` / `channels.slack.dm.allowFrom`). -Run `clawdbot doctor` to surface risky/misconfigured DM policies. +Run `moltbot doctor` to surface risky/misconfigured DM policies. ## Highlights -- **[Local-first Gateway](https://docs.clawd.bot/gateway)** — single control plane for sessions, channels, tools, and events. -- **[Multi-channel inbox](https://docs.clawd.bot/channels)** — WhatsApp, Telegram, Slack, Discord, Google Chat, Signal, iMessage, BlueBubbles, Microsoft Teams, Matrix, Zalo, Zalo Personal, WebChat, macOS, iOS/Android. -- **[Multi-agent routing](https://docs.clawd.bot/gateway/configuration)** — route inbound channels/accounts/peers to isolated agents (workspaces + per-agent sessions). -- **[Voice Wake](https://docs.clawd.bot/nodes/voicewake) + [Talk Mode](https://docs.clawd.bot/nodes/talk)** — always-on speech for macOS/iOS/Android with ElevenLabs. -- **[Live Canvas](https://docs.clawd.bot/platforms/mac/canvas)** — agent-driven visual workspace with [A2UI](https://docs.clawd.bot/platforms/mac/canvas#canvas-a2ui). -- **[First-class tools](https://docs.clawd.bot/tools)** — browser, canvas, nodes, cron, sessions, and Discord/Slack actions. -- **[Companion apps](https://docs.clawd.bot/platforms/macos)** — macOS menu bar app + iOS/Android [nodes](https://docs.clawd.bot/nodes). -- **[Onboarding](https://docs.clawd.bot/start/wizard) + [skills](https://docs.clawd.bot/tools/skills)** — wizard-driven setup with bundled/managed/workspace skills. +- **[Local-first Gateway](https://docs.molt.bot/gateway)** — single control plane for sessions, channels, tools, and events. +- **[Multi-channel inbox](https://docs.molt.bot/channels)** — WhatsApp, Telegram, Slack, Discord, Google Chat, Signal, iMessage, BlueBubbles, Microsoft Teams, Matrix, Zalo, Zalo Personal, WebChat, macOS, iOS/Android. +- **[Multi-agent routing](https://docs.molt.bot/gateway/configuration)** — route inbound channels/accounts/peers to isolated agents (workspaces + per-agent sessions). +- **[Voice Wake](https://docs.molt.bot/nodes/voicewake) + [Talk Mode](https://docs.molt.bot/nodes/talk)** — always-on speech for macOS/iOS/Android with ElevenLabs. +- **[Live Canvas](https://docs.molt.bot/platforms/mac/canvas)** — agent-driven visual workspace with [A2UI](https://docs.molt.bot/platforms/mac/canvas#canvas-a2ui). +- **[First-class tools](https://docs.molt.bot/tools)** — browser, canvas, nodes, cron, sessions, and Discord/Slack actions. +- **[Companion apps](https://docs.molt.bot/platforms/macos)** — macOS menu bar app + iOS/Android [nodes](https://docs.molt.bot/nodes). +- **[Onboarding](https://docs.molt.bot/start/wizard) + [skills](https://docs.molt.bot/tools/skills)** — wizard-driven setup with bundled/managed/workspace skills. ## Star History -[![Star History Chart](https://api.star-history.com/svg?repos=clawdbot/clawdbot&type=date&legend=top-left)](https://www.star-history.com/#clawdbot/clawdbot&type=date&legend=top-left) +[![Star History Chart](https://api.star-history.com/svg?repos=moltbot/moltbot&type=date&legend=top-left)](https://www.star-history.com/#moltbot/moltbot&type=date&legend=top-left) ## Everything we built so far ### Core platform -- [Gateway WS control plane](https://docs.clawd.bot/gateway) with sessions, presence, config, cron, webhooks, [Control UI](https://docs.clawd.bot/web), and [Canvas host](https://docs.clawd.bot/platforms/mac/canvas#canvas-a2ui). -- [CLI surface](https://docs.clawd.bot/tools/agent-send): gateway, agent, send, [wizard](https://docs.clawd.bot/start/wizard), and [doctor](https://docs.clawd.bot/gateway/doctor). -- [Pi agent runtime](https://docs.clawd.bot/concepts/agent) in RPC mode with tool streaming and block streaming. -- [Session model](https://docs.clawd.bot/concepts/session): `main` for direct chats, group isolation, activation modes, queue modes, reply-back. Group rules: [Groups](https://docs.clawd.bot/concepts/groups). -- [Media pipeline](https://docs.clawd.bot/nodes/images): images/audio/video, transcription hooks, size caps, temp file lifecycle. Audio details: [Audio](https://docs.clawd.bot/nodes/audio). +- [Gateway WS control plane](https://docs.molt.bot/gateway) with sessions, presence, config, cron, webhooks, [Control UI](https://docs.molt.bot/web), and [Canvas host](https://docs.molt.bot/platforms/mac/canvas#canvas-a2ui). +- [CLI surface](https://docs.molt.bot/tools/agent-send): gateway, agent, send, [wizard](https://docs.molt.bot/start/wizard), and [doctor](https://docs.molt.bot/gateway/doctor). +- [Pi agent runtime](https://docs.molt.bot/concepts/agent) in RPC mode with tool streaming and block streaming. +- [Session model](https://docs.molt.bot/concepts/session): `main` for direct chats, group isolation, activation modes, queue modes, reply-back. Group rules: [Groups](https://docs.molt.bot/concepts/groups). +- [Media pipeline](https://docs.molt.bot/nodes/images): images/audio/video, transcription hooks, size caps, temp file lifecycle. Audio details: [Audio](https://docs.molt.bot/nodes/audio). ### Channels -- [Channels](https://docs.clawd.bot/channels): [WhatsApp](https://docs.clawd.bot/channels/whatsapp) (Baileys), [Telegram](https://docs.clawd.bot/channels/telegram) (grammY), [Slack](https://docs.clawd.bot/channels/slack) (Bolt), [Discord](https://docs.clawd.bot/channels/discord) (discord.js), [Google Chat](https://docs.clawd.bot/channels/googlechat) (Chat API), [Signal](https://docs.clawd.bot/channels/signal) (signal-cli), [iMessage](https://docs.clawd.bot/channels/imessage) (imsg), [BlueBubbles](https://docs.clawd.bot/channels/bluebubbles) (extension), [Microsoft Teams](https://docs.clawd.bot/channels/msteams) (extension), [Matrix](https://docs.clawd.bot/channels/matrix) (extension), [Zalo](https://docs.clawd.bot/channels/zalo) (extension), [Zalo Personal](https://docs.clawd.bot/channels/zalouser) (extension), [WebChat](https://docs.clawd.bot/web/webchat). -- [Group routing](https://docs.clawd.bot/concepts/group-messages): mention gating, reply tags, per-channel chunking and routing. Channel rules: [Channels](https://docs.clawd.bot/channels). +- [Channels](https://docs.molt.bot/channels): [WhatsApp](https://docs.molt.bot/channels/whatsapp) (Baileys), [Telegram](https://docs.molt.bot/channels/telegram) (grammY), [Slack](https://docs.molt.bot/channels/slack) (Bolt), [Discord](https://docs.molt.bot/channels/discord) (discord.js), [Google Chat](https://docs.molt.bot/channels/googlechat) (Chat API), [Signal](https://docs.molt.bot/channels/signal) (signal-cli), [iMessage](https://docs.molt.bot/channels/imessage) (imsg), [BlueBubbles](https://docs.molt.bot/channels/bluebubbles) (extension), [Microsoft Teams](https://docs.molt.bot/channels/msteams) (extension), [Matrix](https://docs.molt.bot/channels/matrix) (extension), [Zalo](https://docs.molt.bot/channels/zalo) (extension), [Zalo Personal](https://docs.molt.bot/channels/zalouser) (extension), [WebChat](https://docs.molt.bot/web/webchat). +- [Group routing](https://docs.molt.bot/concepts/group-messages): mention gating, reply tags, per-channel chunking and routing. Channel rules: [Channels](https://docs.molt.bot/channels). ### Apps + nodes -- [macOS app](https://docs.clawd.bot/platforms/macos): menu bar control plane, [Voice Wake](https://docs.clawd.bot/nodes/voicewake)/PTT, [Talk Mode](https://docs.clawd.bot/nodes/talk) overlay, [WebChat](https://docs.clawd.bot/web/webchat), debug tools, [remote gateway](https://docs.clawd.bot/gateway/remote) control. -- [iOS node](https://docs.clawd.bot/platforms/ios): [Canvas](https://docs.clawd.bot/platforms/mac/canvas), [Voice Wake](https://docs.clawd.bot/nodes/voicewake), [Talk Mode](https://docs.clawd.bot/nodes/talk), camera, screen recording, Bonjour pairing. -- [Android node](https://docs.clawd.bot/platforms/android): [Canvas](https://docs.clawd.bot/platforms/mac/canvas), [Talk Mode](https://docs.clawd.bot/nodes/talk), camera, screen recording, optional SMS. -- [macOS node mode](https://docs.clawd.bot/nodes): system.run/notify + canvas/camera exposure. +- [macOS app](https://docs.molt.bot/platforms/macos): menu bar control plane, [Voice Wake](https://docs.molt.bot/nodes/voicewake)/PTT, [Talk Mode](https://docs.molt.bot/nodes/talk) overlay, [WebChat](https://docs.molt.bot/web/webchat), debug tools, [remote gateway](https://docs.molt.bot/gateway/remote) control. +- [iOS node](https://docs.molt.bot/platforms/ios): [Canvas](https://docs.molt.bot/platforms/mac/canvas), [Voice Wake](https://docs.molt.bot/nodes/voicewake), [Talk Mode](https://docs.molt.bot/nodes/talk), camera, screen recording, Bonjour pairing. +- [Android node](https://docs.molt.bot/platforms/android): [Canvas](https://docs.molt.bot/platforms/mac/canvas), [Talk Mode](https://docs.molt.bot/nodes/talk), camera, screen recording, optional SMS. +- [macOS node mode](https://docs.molt.bot/nodes): system.run/notify + canvas/camera exposure. ### Tools + automation -- [Browser control](https://docs.clawd.bot/tools/browser): dedicated clawd Chrome/Chromium, snapshots, actions, uploads, profiles. -- [Canvas](https://docs.clawd.bot/platforms/mac/canvas): [A2UI](https://docs.clawd.bot/platforms/mac/canvas#canvas-a2ui) push/reset, eval, snapshot. -- [Nodes](https://docs.clawd.bot/nodes): camera snap/clip, screen record, [location.get](https://docs.clawd.bot/nodes/location-command), notifications. -- [Cron + wakeups](https://docs.clawd.bot/automation/cron-jobs); [webhooks](https://docs.clawd.bot/automation/webhook); [Gmail Pub/Sub](https://docs.clawd.bot/automation/gmail-pubsub). -- [Skills platform](https://docs.clawd.bot/tools/skills): bundled, managed, and workspace skills with install gating + UI. +- [Browser control](https://docs.molt.bot/tools/browser): dedicated moltbot Chrome/Chromium, snapshots, actions, uploads, profiles. +- [Canvas](https://docs.molt.bot/platforms/mac/canvas): [A2UI](https://docs.molt.bot/platforms/mac/canvas#canvas-a2ui) push/reset, eval, snapshot. +- [Nodes](https://docs.molt.bot/nodes): camera snap/clip, screen record, [location.get](https://docs.molt.bot/nodes/location-command), notifications. +- [Cron + wakeups](https://docs.molt.bot/automation/cron-jobs); [webhooks](https://docs.molt.bot/automation/webhook); [Gmail Pub/Sub](https://docs.molt.bot/automation/gmail-pubsub). +- [Skills platform](https://docs.molt.bot/tools/skills): bundled, managed, and workspace skills with install gating + UI. ### Runtime + safety -- [Channel routing](https://docs.clawd.bot/concepts/channel-routing), [retry policy](https://docs.clawd.bot/concepts/retry), and [streaming/chunking](https://docs.clawd.bot/concepts/streaming). -- [Presence](https://docs.clawd.bot/concepts/presence), [typing indicators](https://docs.clawd.bot/concepts/typing-indicators), and [usage tracking](https://docs.clawd.bot/concepts/usage-tracking). -- [Models](https://docs.clawd.bot/concepts/models), [model failover](https://docs.clawd.bot/concepts/model-failover), and [session pruning](https://docs.clawd.bot/concepts/session-pruning). -- [Security](https://docs.clawd.bot/gateway/security) and [troubleshooting](https://docs.clawd.bot/channels/troubleshooting). +- [Channel routing](https://docs.molt.bot/concepts/channel-routing), [retry policy](https://docs.molt.bot/concepts/retry), and [streaming/chunking](https://docs.molt.bot/concepts/streaming). +- [Presence](https://docs.molt.bot/concepts/presence), [typing indicators](https://docs.molt.bot/concepts/typing-indicators), and [usage tracking](https://docs.molt.bot/concepts/usage-tracking). +- [Models](https://docs.molt.bot/concepts/models), [model failover](https://docs.molt.bot/concepts/model-failover), and [session pruning](https://docs.molt.bot/concepts/session-pruning). +- [Security](https://docs.molt.bot/gateway/security) and [troubleshooting](https://docs.molt.bot/channels/troubleshooting). ### Ops + packaging -- [Control UI](https://docs.clawd.bot/web) + [WebChat](https://docs.clawd.bot/web/webchat) served directly from the Gateway. -- [Tailscale Serve/Funnel](https://docs.clawd.bot/gateway/tailscale) or [SSH tunnels](https://docs.clawd.bot/gateway/remote) with token/password auth. -- [Nix mode](https://docs.clawd.bot/install/nix) for declarative config; [Docker](https://docs.clawd.bot/install/docker)-based installs. -- [Doctor](https://docs.clawd.bot/gateway/doctor) migrations, [logging](https://docs.clawd.bot/logging). +- [Control UI](https://docs.molt.bot/web) + [WebChat](https://docs.molt.bot/web/webchat) served directly from the Gateway. +- [Tailscale Serve/Funnel](https://docs.molt.bot/gateway/tailscale) or [SSH tunnels](https://docs.molt.bot/gateway/remote) with token/password auth. +- [Nix mode](https://docs.molt.bot/install/nix) for declarative config; [Docker](https://docs.molt.bot/install/docker)-based installs. +- [Doctor](https://docs.molt.bot/gateway/doctor) migrations, [logging](https://docs.molt.bot/logging). ## How it works (short) @@ -179,7 +180,7 @@ WhatsApp / Telegram / Slack / Discord / Google Chat / Signal / iMessage / BlueBu └──────────────┬────────────────┘ │ ├─ Pi agent (RPC) - ├─ CLI (clawdbot …) + ├─ CLI (moltbot …) ├─ WebChat UI ├─ macOS app └─ iOS / Android nodes @@ -187,28 +188,28 @@ WhatsApp / Telegram / Slack / Discord / Google Chat / Signal / iMessage / BlueBu ## Key subsystems -- **[Gateway WebSocket network](https://docs.clawd.bot/concepts/architecture)** — single WS control plane for clients, tools, and events (plus ops: [Gateway runbook](https://docs.clawd.bot/gateway)). -- **[Tailscale exposure](https://docs.clawd.bot/gateway/tailscale)** — Serve/Funnel for the Gateway dashboard + WS (remote access: [Remote](https://docs.clawd.bot/gateway/remote)). -- **[Browser control](https://docs.clawd.bot/tools/browser)** — clawd‑managed Chrome/Chromium with CDP control. -- **[Canvas + A2UI](https://docs.clawd.bot/platforms/mac/canvas)** — agent‑driven visual workspace (A2UI host: [Canvas/A2UI](https://docs.clawd.bot/platforms/mac/canvas#canvas-a2ui)). -- **[Voice Wake](https://docs.clawd.bot/nodes/voicewake) + [Talk Mode](https://docs.clawd.bot/nodes/talk)** — always‑on speech and continuous conversation. -- **[Nodes](https://docs.clawd.bot/nodes)** — Canvas, camera snap/clip, screen record, `location.get`, notifications, plus macOS‑only `system.run`/`system.notify`. +- **[Gateway WebSocket network](https://docs.molt.bot/concepts/architecture)** — single WS control plane for clients, tools, and events (plus ops: [Gateway runbook](https://docs.molt.bot/gateway)). +- **[Tailscale exposure](https://docs.molt.bot/gateway/tailscale)** — Serve/Funnel for the Gateway dashboard + WS (remote access: [Remote](https://docs.molt.bot/gateway/remote)). +- **[Browser control](https://docs.molt.bot/tools/browser)** — moltbot‑managed Chrome/Chromium with CDP control. +- **[Canvas + A2UI](https://docs.molt.bot/platforms/mac/canvas)** — agent‑driven visual workspace (A2UI host: [Canvas/A2UI](https://docs.molt.bot/platforms/mac/canvas#canvas-a2ui)). +- **[Voice Wake](https://docs.molt.bot/nodes/voicewake) + [Talk Mode](https://docs.molt.bot/nodes/talk)** — always‑on speech and continuous conversation. +- **[Nodes](https://docs.molt.bot/nodes)** — Canvas, camera snap/clip, screen record, `location.get`, notifications, plus macOS‑only `system.run`/`system.notify`. ## Tailscale access (Gateway dashboard) -Clawdbot can auto-configure Tailscale **Serve** (tailnet-only) or **Funnel** (public) while the Gateway stays bound to loopback. Configure `gateway.tailscale.mode`: +Moltbot can auto-configure Tailscale **Serve** (tailnet-only) or **Funnel** (public) while the Gateway stays bound to loopback. Configure `gateway.tailscale.mode`: - `off`: no Tailscale automation (default). - `serve`: tailnet-only HTTPS via `tailscale serve` (uses Tailscale identity headers by default). - `funnel`: public HTTPS via `tailscale funnel` (requires shared password auth). Notes: -- `gateway.bind` must stay `loopback` when Serve/Funnel is enabled (Clawdbot enforces this). +- `gateway.bind` must stay `loopback` when Serve/Funnel is enabled (Moltbot enforces this). - Serve can be forced to require a password by setting `gateway.auth.mode: "password"` or `gateway.auth.allowTailscale: false`. - Funnel refuses to start unless `gateway.auth.mode: "password"` is set. - Optional: `gateway.tailscale.resetOnExit` to undo Serve/Funnel on shutdown. -Details: [Tailscale guide](https://docs.clawd.bot/gateway/tailscale) · [Web surfaces](https://docs.clawd.bot/web) +Details: [Tailscale guide](https://docs.molt.bot/gateway/tailscale) · [Web surfaces](https://docs.molt.bot/web) ## Remote Gateway (Linux is great) @@ -218,7 +219,7 @@ It’s perfectly fine to run the Gateway on a small Linux instance. Clients (mac - **Device nodes** run device‑local actions (`system.run`, camera, screen recording, notifications) via `node.invoke`. In short: exec runs where the Gateway lives; device actions run where the device lives. -Details: [Remote access](https://docs.clawd.bot/gateway/remote) · [Nodes](https://docs.clawd.bot/nodes) · [Security](https://docs.clawd.bot/gateway/security) +Details: [Remote access](https://docs.molt.bot/gateway/remote) · [Nodes](https://docs.molt.bot/nodes) · [Security](https://docs.molt.bot/gateway/security) ## macOS permissions via the Gateway protocol @@ -233,7 +234,7 @@ Elevated bash (host permissions) is separate from macOS TCC: - Use `/elevated on|off` to toggle per‑session elevated access when enabled + allowlisted. - Gateway persists the per‑session toggle via `sessions.patch` (WS method) alongside `thinkingLevel`, `verboseLevel`, `model`, `sendPolicy`, and `groupActivation`. -Details: [Nodes](https://docs.clawd.bot/nodes) · [macOS app](https://docs.clawd.bot/platforms/macos) · [Gateway protocol](https://docs.clawd.bot/concepts/architecture) +Details: [Nodes](https://docs.molt.bot/nodes) · [macOS app](https://docs.molt.bot/platforms/macos) · [Gateway protocol](https://docs.molt.bot/concepts/architecture) ## Agent to Agent (sessions_* tools) @@ -242,7 +243,7 @@ Details: [Nodes](https://docs.clawd.bot/nodes) · [macOS app](https://docs.clawd - `sessions_history` — fetch transcript logs for a session. - `sessions_send` — message another session; optional reply‑back ping‑pong + announce step (`REPLY_SKIP`, `ANNOUNCE_SKIP`). -Details: [Session tools](https://docs.clawd.bot/concepts/session-tool) +Details: [Session tools](https://docs.molt.bot/concepts/session-tool) ## Skills registry (ClawdHub) @@ -269,7 +270,7 @@ The Gateway alone delivers a great experience. All apps are optional and add ext If you plan to build/run companion apps, follow the platform runbooks below. -### macOS (Clawdbot.app) (optional) +### macOS (Moltbot.app) (optional) - Menu bar control for the Gateway and health. - Voice Wake + push-to-talk overlay. @@ -282,15 +283,15 @@ Note: signed builds required for macOS permissions to stick across rebuilds (see - Pairs as a node via the Bridge. - Voice trigger forwarding + Canvas surface. -- Controlled via `clawdbot nodes …`. +- Controlled via `moltbot nodes …`. -Runbook: [iOS connect](https://docs.clawd.bot/platforms/ios). +Runbook: [iOS connect](https://docs.molt.bot/platforms/ios). ### Android node (optional) - Pairs via the same Bridge + pairing flow as iOS. - Exposes Canvas, Camera, and Screen capture commands. -- Runbook: [Android connect](https://docs.clawd.bot/platforms/android). +- Runbook: [Android connect](https://docs.molt.bot/platforms/android). ## Agent workspace + skills @@ -300,7 +301,7 @@ Runbook: [iOS connect](https://docs.clawd.bot/platforms/ios). ## Configuration -Minimal `~/.clawdbot/clawdbot.json` (model + defaults): +Minimal `~/.clawdbot/moltbot.json` (model + defaults): ```json5 { @@ -310,7 +311,7 @@ Minimal `~/.clawdbot/clawdbot.json` (model + defaults): } ``` -[Full configuration reference (all keys + examples).](https://docs.clawd.bot/gateway/configuration) +[Full configuration reference (all keys + examples).](https://docs.molt.bot/gateway/configuration) ## Security model (important) @@ -318,15 +319,15 @@ Minimal `~/.clawdbot/clawdbot.json` (model + defaults): - **Group/channel safety:** set `agents.defaults.sandbox.mode: "non-main"` to run **non‑main sessions** (groups/channels) inside per‑session Docker sandboxes; bash then runs in Docker for those sessions. - **Sandbox defaults:** allowlist `bash`, `process`, `read`, `write`, `edit`, `sessions_list`, `sessions_history`, `sessions_send`, `sessions_spawn`; denylist `browser`, `canvas`, `nodes`, `cron`, `discord`, `gateway`. -Details: [Security guide](https://docs.clawd.bot/gateway/security) · [Docker + sandboxing](https://docs.clawd.bot/install/docker) · [Sandbox config](https://docs.clawd.bot/gateway/configuration) +Details: [Security guide](https://docs.molt.bot/gateway/security) · [Docker + sandboxing](https://docs.molt.bot/install/docker) · [Sandbox config](https://docs.molt.bot/gateway/configuration) -### [WhatsApp](https://docs.clawd.bot/channels/whatsapp) +### [WhatsApp](https://docs.molt.bot/channels/whatsapp) -- Link the device: `pnpm clawdbot channels login` (stores creds in `~/.clawdbot/credentials`). +- Link the device: `pnpm moltbot channels login` (stores creds in `~/.clawdbot/credentials`). - Allowlist who can talk to the assistant via `channels.whatsapp.allowFrom`. - If `channels.whatsapp.groups` is set, it becomes a group allowlist; include `"*"` to allow all. -### [Telegram](https://docs.clawd.bot/channels/telegram) +### [Telegram](https://docs.molt.bot/channels/telegram) - Set `TELEGRAM_BOT_TOKEN` or `channels.telegram.botToken` (env wins). - Optional: set `channels.telegram.groups` (with `channels.telegram.groups."*".requireMention`); when set, it is a group allowlist (include `"*"` to allow all). Also `channels.telegram.allowFrom` or `channels.telegram.webhookUrl` as needed. @@ -341,11 +342,11 @@ Details: [Security guide](https://docs.clawd.bot/gateway/security) · [Docker + } ``` -### [Slack](https://docs.clawd.bot/channels/slack) +### [Slack](https://docs.molt.bot/channels/slack) - Set `SLACK_BOT_TOKEN` + `SLACK_APP_TOKEN` (or `channels.slack.botToken` + `channels.slack.appToken`). -### [Discord](https://docs.clawd.bot/channels/discord) +### [Discord](https://docs.molt.bot/channels/discord) - Set `DISCORD_BOT_TOKEN` or `channels.discord.token` (env wins). - Optional: set `commands.native`, `commands.text`, or `commands.useAccessGroups`, plus `channels.discord.dm.allowFrom`, `channels.discord.guilds`, or `channels.discord.mediaMaxMb` as needed. @@ -360,21 +361,21 @@ Details: [Security guide](https://docs.clawd.bot/gateway/security) · [Docker + } ``` -### [Signal](https://docs.clawd.bot/channels/signal) +### [Signal](https://docs.molt.bot/channels/signal) - Requires `signal-cli` and a `channels.signal` config section. -### [iMessage](https://docs.clawd.bot/channels/imessage) +### [iMessage](https://docs.molt.bot/channels/imessage) - macOS only; Messages must be signed in. - If `channels.imessage.groups` is set, it becomes a group allowlist; include `"*"` to allow all. -### [Microsoft Teams](https://docs.clawd.bot/channels/msteams) +### [Microsoft Teams](https://docs.molt.bot/channels/msteams) - Configure a Teams app + Bot Framework, then add a `msteams` config section. - Allowlist who can talk via `msteams.allowFrom`; group access via `msteams.groupAllowFrom` or `msteams.groupPolicy: "open"`. -### [WebChat](https://docs.clawd.bot/web/webchat) +### [WebChat](https://docs.molt.bot/web/webchat) - Uses the Gateway WebSocket; no separate WebChat port/config. @@ -392,78 +393,79 @@ Browser control (optional): ## Docs Use these when you’re past the onboarding flow and want the deeper reference. -- [Start with the docs index for navigation and “what’s where.”](https://docs.clawd.bot) -- [Read the architecture overview for the gateway + protocol model.](https://docs.clawd.bot/concepts/architecture) -- [Use the full configuration reference when you need every key and example.](https://docs.clawd.bot/gateway/configuration) -- [Run the Gateway by the book with the operational runbook.](https://docs.clawd.bot/gateway) -- [Learn how the Control UI/Web surfaces work and how to expose them safely.](https://docs.clawd.bot/web) -- [Understand remote access over SSH tunnels or tailnets.](https://docs.clawd.bot/gateway/remote) -- [Follow the onboarding wizard flow for a guided setup.](https://docs.clawd.bot/start/wizard) -- [Wire external triggers via the webhook surface.](https://docs.clawd.bot/automation/webhook) -- [Set up Gmail Pub/Sub triggers.](https://docs.clawd.bot/automation/gmail-pubsub) -- [Learn the macOS menu bar companion details.](https://docs.clawd.bot/platforms/mac/menu-bar) -- [Platform guides: Windows (WSL2)](https://docs.clawd.bot/platforms/windows), [Linux](https://docs.clawd.bot/platforms/linux), [macOS](https://docs.clawd.bot/platforms/macos), [iOS](https://docs.clawd.bot/platforms/ios), [Android](https://docs.clawd.bot/platforms/android) -- [Debug common failures with the troubleshooting guide.](https://docs.clawd.bot/channels/troubleshooting) -- [Review security guidance before exposing anything.](https://docs.clawd.bot/gateway/security) +- [Start with the docs index for navigation and “what’s where.”](https://docs.molt.bot) +- [Read the architecture overview for the gateway + protocol model.](https://docs.molt.bot/concepts/architecture) +- [Use the full configuration reference when you need every key and example.](https://docs.molt.bot/gateway/configuration) +- [Run the Gateway by the book with the operational runbook.](https://docs.molt.bot/gateway) +- [Learn how the Control UI/Web surfaces work and how to expose them safely.](https://docs.molt.bot/web) +- [Understand remote access over SSH tunnels or tailnets.](https://docs.molt.bot/gateway/remote) +- [Follow the onboarding wizard flow for a guided setup.](https://docs.molt.bot/start/wizard) +- [Wire external triggers via the webhook surface.](https://docs.molt.bot/automation/webhook) +- [Set up Gmail Pub/Sub triggers.](https://docs.molt.bot/automation/gmail-pubsub) +- [Learn the macOS menu bar companion details.](https://docs.molt.bot/platforms/mac/menu-bar) +- [Platform guides: Windows (WSL2)](https://docs.molt.bot/platforms/windows), [Linux](https://docs.molt.bot/platforms/linux), [macOS](https://docs.molt.bot/platforms/macos), [iOS](https://docs.molt.bot/platforms/ios), [Android](https://docs.molt.bot/platforms/android) +- [Debug common failures with the troubleshooting guide.](https://docs.molt.bot/channels/troubleshooting) +- [Review security guidance before exposing anything.](https://docs.molt.bot/gateway/security) ## Advanced docs (discovery + control) -- [Discovery + transports](https://docs.clawd.bot/gateway/discovery) -- [Bonjour/mDNS](https://docs.clawd.bot/gateway/bonjour) -- [Gateway pairing](https://docs.clawd.bot/gateway/pairing) -- [Remote gateway README](https://docs.clawd.bot/gateway/remote-gateway-readme) -- [Control UI](https://docs.clawd.bot/web/control-ui) -- [Dashboard](https://docs.clawd.bot/web/dashboard) +- [Discovery + transports](https://docs.molt.bot/gateway/discovery) +- [Bonjour/mDNS](https://docs.molt.bot/gateway/bonjour) +- [Gateway pairing](https://docs.molt.bot/gateway/pairing) +- [Remote gateway README](https://docs.molt.bot/gateway/remote-gateway-readme) +- [Control UI](https://docs.molt.bot/web/control-ui) +- [Dashboard](https://docs.molt.bot/web/dashboard) ## Operations & troubleshooting -- [Health checks](https://docs.clawd.bot/gateway/health) -- [Gateway lock](https://docs.clawd.bot/gateway/gateway-lock) -- [Background process](https://docs.clawd.bot/gateway/background-process) -- [Browser troubleshooting (Linux)](https://docs.clawd.bot/tools/browser-linux-troubleshooting) -- [Logging](https://docs.clawd.bot/logging) +- [Health checks](https://docs.molt.bot/gateway/health) +- [Gateway lock](https://docs.molt.bot/gateway/gateway-lock) +- [Background process](https://docs.molt.bot/gateway/background-process) +- [Browser troubleshooting (Linux)](https://docs.molt.bot/tools/browser-linux-troubleshooting) +- [Logging](https://docs.molt.bot/logging) ## Deep dives -- [Agent loop](https://docs.clawd.bot/concepts/agent-loop) -- [Presence](https://docs.clawd.bot/concepts/presence) -- [TypeBox schemas](https://docs.clawd.bot/concepts/typebox) -- [RPC adapters](https://docs.clawd.bot/reference/rpc) -- [Queue](https://docs.clawd.bot/concepts/queue) +- [Agent loop](https://docs.molt.bot/concepts/agent-loop) +- [Presence](https://docs.molt.bot/concepts/presence) +- [TypeBox schemas](https://docs.molt.bot/concepts/typebox) +- [RPC adapters](https://docs.molt.bot/reference/rpc) +- [Queue](https://docs.molt.bot/concepts/queue) ## Workspace & skills -- [Skills config](https://docs.clawd.bot/tools/skills-config) -- [Default AGENTS](https://docs.clawd.bot/reference/AGENTS.default) -- [Templates: AGENTS](https://docs.clawd.bot/reference/templates/AGENTS) -- [Templates: BOOTSTRAP](https://docs.clawd.bot/reference/templates/BOOTSTRAP) -- [Templates: IDENTITY](https://docs.clawd.bot/reference/templates/IDENTITY) -- [Templates: SOUL](https://docs.clawd.bot/reference/templates/SOUL) -- [Templates: TOOLS](https://docs.clawd.bot/reference/templates/TOOLS) -- [Templates: USER](https://docs.clawd.bot/reference/templates/USER) +- [Skills config](https://docs.molt.bot/tools/skills-config) +- [Default AGENTS](https://docs.molt.bot/reference/AGENTS.default) +- [Templates: AGENTS](https://docs.molt.bot/reference/templates/AGENTS) +- [Templates: BOOTSTRAP](https://docs.molt.bot/reference/templates/BOOTSTRAP) +- [Templates: IDENTITY](https://docs.molt.bot/reference/templates/IDENTITY) +- [Templates: SOUL](https://docs.molt.bot/reference/templates/SOUL) +- [Templates: TOOLS](https://docs.molt.bot/reference/templates/TOOLS) +- [Templates: USER](https://docs.molt.bot/reference/templates/USER) ## Platform internals -- [macOS dev setup](https://docs.clawd.bot/platforms/mac/dev-setup) -- [macOS menu bar](https://docs.clawd.bot/platforms/mac/menu-bar) -- [macOS voice wake](https://docs.clawd.bot/platforms/mac/voicewake) -- [iOS node](https://docs.clawd.bot/platforms/ios) -- [Android node](https://docs.clawd.bot/platforms/android) -- [Windows (WSL2)](https://docs.clawd.bot/platforms/windows) -- [Linux app](https://docs.clawd.bot/platforms/linux) +- [macOS dev setup](https://docs.molt.bot/platforms/mac/dev-setup) +- [macOS menu bar](https://docs.molt.bot/platforms/mac/menu-bar) +- [macOS voice wake](https://docs.molt.bot/platforms/mac/voicewake) +- [iOS node](https://docs.molt.bot/platforms/ios) +- [Android node](https://docs.molt.bot/platforms/android) +- [Windows (WSL2)](https://docs.molt.bot/platforms/windows) +- [Linux app](https://docs.molt.bot/platforms/linux) ## Email hooks (Gmail) -- [docs.clawd.bot/gmail-pubsub](https://docs.clawd.bot/automation/gmail-pubsub) +- [docs.molt.bot/gmail-pubsub](https://docs.molt.bot/automation/gmail-pubsub) -## Clawd +## Molty -Clawdbot was built for **Clawd**, a space lobster AI assistant. 🦞 +Moltbot was built for **Molty**, a space lobster AI assistant. 🦞 by Peter Steinberger and the community. - [clawd.me](https://clawd.me) - [soul.md](https://soul.md) - [steipete.me](https://steipete.me) +- [@moltbot](https://x.com/moltbot) ## Community @@ -477,35 +479,36 @@ Thanks to all clawtributors:

steipete plum-dawg bohdanpodvirnyi iHildy jaydenfyi joaohlisboa mneves75 MatthieuBizien MaudeBot Glucksberg - rahthakor vrknetha radek-paclt Tobias Bischoff joshp123 czekaj mukhtharcm sebslight maxsumrall xadenryan - rodrigouroz juanpablodlc hsrvc magimetal zerone0x meaningfool tyler6204 vignesh07 patelhiren NicholasSpisak + rahthakor vrknetha radek-paclt Tobias Bischoff joshp123 vignesh07 czekaj mukhtharcm sebslight maxsumrall + xadenryan rodrigouroz juanpablodlc hsrvc magimetal zerone0x meaningfool tyler6204 patelhiren NicholasSpisak jonisjongithub abhisekbasu1 jamesgroat claude JustYannicc Hyaxia dantelex SocialNerd42069 daveonkels google-labs-jules[bot] - lc0rp mousberg mteam88 hirefrank joeynyc orlyjamie dbhurley Mariano Belinky Eng. Juan Combetto TSavo - julianengel bradleypriest benithors rohannagpal timolins f-trycua benostein nachx639 pvoo sreekaransrinath - gupsammy cristip73 stefangalescu nachoiacovino Vasanth Rao Naik Sabavat petter-b cpojer scald gumadeiras andranik-sahakyan - davidguttman thewilloftheshadow sleontenko denysvitali shakkernerd sircrumpet peschee rafaelreis-r dominicnunez ratulsarna - lutr0 danielz1z AdeboyeDN Alg0rix emanuelst KristijanJovanovski rdev rhuanssauro joshrad-dev kiranjd - osolmaz adityashaw2 CashWilliams sheeek artuskg Takhoffman onutc pauloportella neooriginal manuelhettich - minghinmatthewlam myfunc travisirby buddyh connorshea kyleok mcinteerj dependabot[bot] John-Rood obviyus - timkrase uos-status gerardward2007 roshanasingh4 tosh-hamburg azade-c JonUleis bjesuiter cheeeee robbyczgw-cla - dlauer Josh Phillips YuriNachos pookNast Whoaa512 chriseidhof ngutman ysqander aj47 superman32432432 - Yurii Chukhlib grp06 antons austinm911 blacksmith-sh[bot] damoahdominic dan-dr HeimdallStrategy imfing jalehman - jarvis-medmatic kkarimi mahmoudashraf93 pkrmf RandyVentures Ryan Lisse dougvk erikpr1994 Ghost jonasjancarik - Keith the Silly Goose L36 Server Marc mitschabaude-bot mkbehr neist sibbl chrisrodz Friederike Seiler gabriel-trigo - iamadig Jonathan D. Rhyne (DJ-D) Joshua Mitchell Kit koala73 manmal ogulcancelik pasogott petradonka rubyrunsstuff - siddhantjain suminhthanh svkozak VACInc wes-davis zats 24601 adam91holt ameno- Chris Taylor - dguido Django Navarro evalexpr henrino3 humanwritten larlyssa odysseus0 oswalpalash pcty-nextgen-service-account rmorse - Syhids Aaron Konyer aaronveklabs andreabadesso Andrii cash-echo-bot Clawd ClawdFx EnzeD erik-agens - Evizero fcatuhe itsjaydesu ivancasco ivanrvpereira jayhickey jeffersonwarrior jeffersonwarrior jverdi longmaba - mickahouan mjrussell odnxe p6l-richard philipp-spiess Pocket Clawd robaxelsen Sash Catanzarite T5-AndyML travisp - VAC william arzt zknicker abhaymundhara alejandro maza Alex-Alaniz alexstyl andrewting19 anpoirier arthyn - Asleep123 bolismauro chenyuan99 Clawdbot Maintainers conhecendoia dasilva333 David-Marsh-Photo Developer Dimitrios Ploutarchos Drake Thomsen - fal3 Felix Krause foeken ganghyun kim grrowl gtsifrikas HazAT hrdwdmrbl hugobarauna Jamie Openshaw - Jane Jarvis Jefferson Nunn kentaro Kevin Lin kitze Kiwitwitter levifig Lloyd loukotal - louzhixian martinpucik Matt mini mertcicekci0 Miles mrdbstn MSch Mustafa Tag Eldeen ndraiman nexty5870 - Noctivoro ppamment prathamdby ptn1411 reeltimeapps RLTCmpe Rolf Fredheim Rony Kelner Samrat Jha senoldogann - Seredeep sergical shiv19 shiyuanhai siraht snopoke Suksham-sharma techboss testingabc321 The Admiral - thesash Ubuntu voidserf Vultr-Clawd Admin Wimmie wolfred wstock yazinsai ymat19 Zach Knickerbocker - 0xJonHoldsCrypto aaronn Alphonse-arianee atalovesyou Azade carlulsoe ddyo Erik hougangdev latitudeki5223 - Manuel Maly Mourad Boustani odrobnik pcty-nextgen-ios-builder Quentin Randy Torres rhjoh ronak-guliani William Stock + lc0rp mousberg adam91holt hougangdev gumadeiras mteam88 hirefrank joeynyc orlyjamie dbhurley + Mariano Belinky Eng. Juan Combetto TSavo julianengel bradleypriest benithors rohannagpal timolins f-trycua benostein + nachx639 shakkernerd pvoo sreekaransrinath gupsammy cristip73 stefangalescu nachoiacovino Vasanth Rao Naik Sabavat petter-b + cpojer scald thewilloftheshadow andranik-sahakyan davidguttman sleontenko denysvitali sircrumpet peschee rafaelreis-r + dominicnunez ratulsarna lutr0 danielz1z AdeboyeDN Alg0rix papago2355 emanuelst KristijanJovanovski rdev + rhuanssauro joshrad-dev kiranjd osolmaz adityashaw2 CashWilliams sheeek artuskg Takhoffman onutc + pauloportella neooriginal manuelhettich minghinmatthewlam myfunc travisirby buddyh connorshea kyleok obviyus + mcinteerj dependabot[bot] John-Rood timkrase uos-status gerardward2007 roshanasingh4 tosh-hamburg azade-c dlauer + JonUleis bjesuiter cheeeee robbyczgw-cla Josh Phillips YuriNachos pookNast Whoaa512 chriseidhof ngutman + ysqander aj47 kennyklee superman32432432 Yurii Chukhlib grp06 antons austinm911 blacksmith-sh[bot] damoahdominic + dan-dr HeimdallStrategy imfing jalehman jarvis-medmatic kkarimi mahmoudashraf93 pkrmf RandyVentures Ryan Lisse + dougvk erikpr1994 fal3 Ghost jonasjancarik Keith the Silly Goose L36 Server Marc mitschabaude-bot mkbehr + neist sibbl chrisrodz Friederike Seiler gabriel-trigo iamadig Jonathan D. Rhyne (DJ-D) Joshua Mitchell Kit koala73 + manmal ogulcancelik pasogott petradonka rubyrunsstuff siddhantjain suminhthanh svkozak VACInc wes-davis + zats 24601 ameno- Chris Taylor dguido Django Navarro evalexpr henrino3 humanwritten larlyssa + odysseus0 oswalpalash pcty-nextgen-service-account rmorse Syhids Aaron Konyer aaronveklabs andreabadesso Andrii cash-echo-bot + Clawd ClawdFx EnzeD erik-agens Evizero fcatuhe itsjaydesu ivancasco ivanrvpereira jayhickey + jeffersonwarrior jeffersonwarrior jverdi longmaba mickahouan mjrussell odnxe p6l-richard philipp-spiess Pocket Clawd + robaxelsen Sash Catanzarite T5-AndyML travisp VAC william arzt zknicker 0oAstro abhaymundhara alejandro maza + Alex-Alaniz alexstyl andrewting19 anpoirier arthyn Asleep123 bolismauro chenyuan99 Clawdbot Maintainers conhecendoia + dasilva333 David-Marsh-Photo Developer Dimitrios Ploutarchos Drake Thomsen Felix Krause foeken ganghyun kim grrowl gtsifrikas + HazAT hrdwdmrbl hugobarauna Jamie Openshaw Jane Jarvis Jefferson Nunn jogi47 kentaro Kevin Lin + kitze Kiwitwitter levifig Lloyd longjos loukotal louzhixian martinpucik Matt mini mertcicekci0 + Miles mrdbstn MSch Mustafa Tag Eldeen ndraiman nexty5870 Noctivoro ppamment prathamdby ptn1411 + reeltimeapps RLTCmpe Rolf Fredheim Rony Kelner Samrat Jha senoldogann Seredeep sergical shiv19 shiyuanhai + siraht snopoke Suksham-sharma techboss testingabc321 The Admiral thesash Ubuntu voidserf Vultr-Clawd Admin + Wimmie wolfred wstock yazinsai YiWang24 ymat19 Zach Knickerbocker 0xJonHoldsCrypto aaronn Alphonse-arianee + atalovesyou Azade carlulsoe ddyo Erik latitudeki5223 Manuel Maly Mourad Boustani odrobnik pcty-nextgen-ios-builder + Quentin Randy Torres rhjoh ronak-guliani William Stock

diff --git a/SECURITY.md b/SECURITY.md index 5bc9c9112..414def17f 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -1,6 +1,6 @@ # Security Policy -If you believe you've found a security issue in Clawdbot, please report it privately. +If you believe you've found a security issue in Moltbot, please report it privately. ## Reporting @@ -9,19 +9,19 @@ If you believe you've found a security issue in Clawdbot, please report it priva ## Operational Guidance -For threat model + hardening guidance (including `clawdbot security audit --deep` and `--fix`), see: +For threat model + hardening guidance (including `moltbot security audit --deep` and `--fix`), see: -- `https://docs.clawd.bot/gateway/security` +- `https://docs.molt.bot/gateway/security` ### Web Interface Safety -Clawdbot's web interface is intended for local use only. Do **not** bind it to the public internet; it is not hardened for public exposure. +Moltbot's web interface is intended for local use only. Do **not** bind it to the public internet; it is not hardened for public exposure. ## Runtime Requirements ### Node.js Version -Clawdbot requires **Node.js 22.12.0 or later** (LTS). This version includes important security patches: +Moltbot requires **Node.js 22.12.0 or later** (LTS). This version includes important security patches: - CVE-2025-59466: async_hooks DoS vulnerability - CVE-2026-21636: Permission model bypass vulnerability @@ -34,7 +34,7 @@ node --version # Should be v22.12.0 or later ### Docker Security -When running Clawdbot in Docker: +When running Moltbot in Docker: 1. The official image runs as a non-root user (`node`) for reduced attack surface 2. Use `--read-only` flag when possible for additional filesystem protection @@ -44,8 +44,8 @@ Example secure Docker run: ```bash docker run --read-only --cap-drop=ALL \ - -v clawdbot-data:/app/data \ - clawdbot/clawdbot:latest + -v moltbot-data:/app/data \ + moltbot/moltbot:latest ``` ## Security Scanning diff --git a/appcast.xml b/appcast.xml index 8158ac244..568632fd7 100644 --- a/appcast.xml +++ b/appcast.xml @@ -1,55 +1,55 @@ - Clawdbot + Moltbot 2026.1.24-1 Sun, 25 Jan 2026 14:05:25 +0000 - https://raw.githubusercontent.com/clawdbot/clawdbot/main/appcast.xml + https://raw.githubusercontent.com/moltbot/moltbot/main/appcast.xml 7952 2026.1.24-1 15.0 - Clawdbot 2026.1.24-1 + Moltbot 2026.1.24-1

Fixes

  • Packaging: include dist/shared output in npm tarball (fixes missing reasoning-tags import on install).
-

View full changelog

+

View full changelog

]]> - + 2026.1.24 Sun, 25 Jan 2026 13:31:05 +0000 - https://raw.githubusercontent.com/clawdbot/clawdbot/main/appcast.xml + https://raw.githubusercontent.com/moltbot/moltbot/main/appcast.xml 7944 2026.1.24 15.0 - Clawdbot 2026.1.24 + Moltbot 2026.1.24

Highlights

    -
  • Providers: Ollama discovery + docs; Venice guide upgrades + cross-links. (#1606) Thanks @abhaymundhara. https://docs.clawd.bot/providers/ollama https://docs.clawd.bot/providers/venice
    • +
  • Providers: Ollama discovery + docs; Venice guide upgrades + cross-links. (#1606) Thanks @abhaymundhara. https://docs.molt.bot/providers/ollama https://docs.molt.bot/providers/venice
  • Channels: LINE plugin (Messaging API) with rich replies + quick replies. (#1630) Thanks @plum-dawg.
    • -
  • TTS: Edge fallback (keyless) + /tts auto modes. (#1668, #1667) Thanks @steipete, @sebslight. https://docs.clawd.bot/tts
    • -
  • Exec approvals: approve in-chat via /approve across all channels (including plugins). (#1621) Thanks @czekaj. https://docs.clawd.bot/tools/exec-approvals https://docs.clawd.bot/tools/slash-commands
    • -
  • Telegram: DM topics as separate sessions + outbound link preview toggle. (#1597, #1700) Thanks @rohannagpal, @zerone0x. https://docs.clawd.bot/channels/telegram
    • +
  • TTS: Edge fallback (keyless) + /tts auto modes. (#1668, #1667) Thanks @steipete, @sebslight. https://docs.molt.bot/tts
    • +
  • Exec approvals: approve in-chat via /approve across all channels (including plugins). (#1621) Thanks @czekaj. https://docs.molt.bot/tools/exec-approvals https://docs.molt.bot/tools/slash-commands
    • +
  • Telegram: DM topics as separate sessions + outbound link preview toggle. (#1597, #1700) Thanks @rohannagpal, @zerone0x. https://docs.molt.bot/channels/telegram

Changes

  • Channels: add LINE plugin (Messaging API) with rich replies, quick replies, and plugin HTTP registry. (#1630) Thanks @plum-dawg.
    • -
  • TTS: add Edge TTS provider fallback, defaulting to keyless Edge with MP3 retry on format failures. (#1668) Thanks @steipete. https://docs.clawd.bot/tts
    • -
  • TTS: add auto mode enum (off/always/inbound/tagged) with per-session /tts override. (#1667) Thanks @sebslight. https://docs.clawd.bot/tts
    • +
  • TTS: add Edge TTS provider fallback, defaulting to keyless Edge with MP3 retry on format failures. (#1668) Thanks @steipete. https://docs.molt.bot/tts
    • +
  • TTS: add auto mode enum (off/always/inbound/tagged) with per-session /tts override. (#1667) Thanks @sebslight. https://docs.molt.bot/tts
  • Telegram: treat DM topics as separate sessions and keep DM history limits stable with thread suffixes. (#1597) Thanks @rohannagpal.
    • -
  • Telegram: add channels.telegram.linkPreview to toggle outbound link previews. (#1700) Thanks @zerone0x. https://docs.clawd.bot/channels/telegram
    • -
  • Web search: add Brave freshness filter parameter for time-scoped results. (#1688) Thanks @JonUleis. https://docs.clawd.bot/tools/web
    • +
  • Telegram: add channels.telegram.linkPreview to toggle outbound link previews. (#1700) Thanks @zerone0x. https://docs.molt.bot/channels/telegram
    • +
  • Web search: add Brave freshness filter parameter for time-scoped results. (#1688) Thanks @JonUleis. https://docs.molt.bot/tools/web
  • UI: refresh Control UI dashboard design system (typography, colors, spacing). (#1786) Thanks @mousberg.
    • -
  • Exec approvals: forward approval prompts to chat with /approve for all channels (including plugins). (#1621) Thanks @czekaj. https://docs.clawd.bot/tools/exec-approvals https://docs.clawd.bot/tools/slash-commands
    • +
  • Exec approvals: forward approval prompts to chat with /approve for all channels (including plugins). (#1621) Thanks @czekaj. https://docs.molt.bot/tools/exec-approvals https://docs.molt.bot/tools/slash-commands
  • Gateway: expose config.patch in the gateway tool with safe partial updates + restart sentinel. (#1653) Thanks @Glucksberg.
    • -
  • Diagnostics: add diagnostic flags for targeted debug logs (config + env override). https://docs.clawd.bot/diagnostics/flags
    • +
  • Diagnostics: add diagnostic flags for targeted debug logs (config + env override). https://docs.molt.bot/diagnostics/flags
  • Docs: expand FAQ (migration, scheduling, concurrency, model recommendations, OpenAI subscription auth, Pi sizing, hackable install, docs SSL workaround).
  • Docs: add verbose installer troubleshooting guidance.
  • Docs: add macOS VM guide with local/hosted options + VPS/nodes guidance. (#1693) Thanks @f-trycua.
    • -
  • Docs: add Bedrock EC2 instance role setup + IAM steps. (#1625) Thanks @sergical. https://docs.clawd.bot/bedrock
    • +
  • Docs: add Bedrock EC2 instance role setup + IAM steps. (#1625) Thanks @sergical. https://docs.molt.bot/bedrock
  • Docs: update Fly.io guide notes.
  • Dev: add prek pre-commit hooks + dependabot config for weekly updates. (#1720) Thanks @dguido.
@@ -61,10 +61,10 @@
  • Web UI: hide internal message_id hints in chat bubbles.
  • Gateway: allow Control UI token-only auth to skip device pairing even when device identity is present (gateway.controlUi.allowInsecureAuth). (#1679) Thanks @steipete.
  • Matrix: decrypt E2EE media attachments with preflight size guard. (#1744) Thanks @araa47.
    • -
  • BlueBubbles: route phone-number targets to DMs, avoid leaking routing IDs, and auto-create missing DMs (Private API required). (#1751) Thanks @tyler6204. https://docs.clawd.bot/channels/bluebubbles
    • +
  • BlueBubbles: route phone-number targets to DMs, avoid leaking routing IDs, and auto-create missing DMs (Private API required). (#1751) Thanks @tyler6204. https://docs.molt.bot/channels/bluebubbles
  • BlueBubbles: keep part-index GUIDs in reply tags when short IDs are missing.
  • Signal: repair reaction sends (group/UUID targets + CLI author flags). (#1651) Thanks @vilkasdev.
    • -
  • Signal: add configurable signal-cli startup timeout + external daemon mode docs. (#1677) https://docs.clawd.bot/channels/signal
    • +
  • Signal: add configurable signal-cli startup timeout + external daemon mode docs. (#1677) https://docs.molt.bot/channels/signal
  • Telegram: set fetch duplex="half" for uploads on Node 22 to avoid sendPhoto failures. (#1684) Thanks @commdata2338.
  • Telegram: use wrapped fetch for long-polling on Node to normalize AbortSignal handling. (#1639)
  • Telegram: honor per-account proxy for outbound API calls. (#1774) Thanks @radek-paclt.
    • @@ -93,18 +93,18 @@
  • Tests: avoid fake-timer dependency in embedded runner stream mock to reduce CI flakes. (#1597) Thanks @rohannagpal.
  • Tests: increase embedded runner ordering test timeout to reduce CI flakes. (#1597) Thanks @rohannagpal.
    • -

    View full changelog

    +

    View full changelog

    ]]>     - +     2026.1.23 Sat, 24 Jan 2026 13:02:18 +0000 - https://raw.githubusercontent.com/clawdbot/clawdbot/main/appcast.xml + https://raw.githubusercontent.com/moltbot/moltbot/main/appcast.xml 7750 2026.1.23 15.0 - Clawdbot 2026.1.23 + Moltbot 2026.1.23

    Highlights

    • TTS: allow model-driven TTS tags by default for expressive audio replies (laughter, singing cues, etc.).
      • @@ -117,9 +117,9 @@
    • Browser: add node-host proxy auto-routing for remote gateways (configurable per gateway/node).
    • Heartbeat: add per-channel visibility controls (OK/alerts/indicator). (#1452) Thanks @dlauer.
    • Plugins: add optional llm-task JSON-only tool for workflows. (#1498) Thanks @vignesh07.
      • -
    • CLI: restart the gateway by default after clawdbot update; add --no-restart to skip it.
      • -
    • CLI: add live auth probes to clawdbot models status for per-profile verification.
      • -
    • CLI: add clawdbot system for system events + heartbeat controls; remove standalone wake.
      • +
    • CLI: restart the gateway by default after moltbot update; add --no-restart to skip it.
      • +
    • CLI: add live auth probes to moltbot models status for per-profile verification.
      • +
    • CLI: add moltbot system for system events + heartbeat controls; remove standalone wake.
    • Agents: add Bedrock auto-discovery defaults + config overrides. (#1553) Thanks @fal3.
    • Docs: add cron vs heartbeat decision guide (with Lobster workflow notes). (#1533) Thanks @JustYannicc.
    • Docs: clarify HEARTBEAT.md empty file skips heartbeats, missing file still runs. (#1535) Thanks @JustYannicc.
      • @@ -154,10 +154,10 @@
    • Exec: honor tools.exec ask/security defaults for elevated approvals (avoid unwanted prompts).
    • TUI: forward unknown slash commands (for example, /context) to the Gateway.
    • TUI: include Gateway slash commands in autocomplete and /help.
      • -
    • CLI: skip usage lines in clawdbot models status when provider usage is unavailable.
      • +
    • CLI: skip usage lines in moltbot models status when provider usage is unavailable.
    • CLI: suppress diagnostic session/run noise during auth probes.
    • CLI: hide auth probe timeout warnings from embedded runs.
      • -
    • CLI: render auth probe results as a table in clawdbot models status.
      • +
    • CLI: render auth probe results as a table in moltbot models status.
    • CLI: suppress probe-only embedded logs unless --verbose is set.
    • CLI: move auth probe errors below the table to reduce wrapping.
    • CLI: prevent ANSI color bleed when table cells wrap.
      • @@ -180,9 +180,9 @@
    • Browser: keep extension relay tabs controllable when the extension reuses a session id after switching tabs. (#1160)
    • Agents: warn and ignore tool allowlists that only reference unknown or unloaded plugin tools. (#1566)
    -

    View full changelog

    +

    View full changelog

    ]]>     - +     \ No newline at end of file diff --git a/apps/android/app/build.gradle.kts b/apps/android/app/build.gradle.kts index a015c0e36..3ddcb3b81 100644 --- a/apps/android/app/build.gradle.kts +++ b/apps/android/app/build.gradle.kts @@ -8,21 +8,21 @@ plugins { } android { - namespace = "com.clawdbot.android" + namespace = "bot.molt.android" compileSdk = 36 sourceSets { getByName("main") { - assets.srcDir(file("../../shared/ClawdbotKit/Sources/ClawdbotKit/Resources")) + assets.srcDir(file("../../shared/MoltbotKit/Sources/MoltbotKit/Resources")) } } defaultConfig { - applicationId = "com.clawdbot.android" + applicationId = "bot.molt.android" minSdk = 31 targetSdk = 36 - versionCode = 202601250 - versionName = "2026.1.25" + versionCode = 202601260 + versionName = "2026.1.27-beta.1" } buildTypes { @@ -65,7 +65,7 @@ androidComponents { val versionName = output.versionName.orNull ?: "0" val buildType = variant.buildType - val outputFileName = "clawdbot-${versionName}-${buildType}.apk" + val outputFileName = "moltbot-${versionName}-${buildType}.apk" output.outputFileName = outputFileName } } diff --git a/apps/android/app/src/main/AndroidManifest.xml b/apps/android/app/src/main/AndroidManifest.xml index df2aa94b3..e0aab841e 100644 --- a/apps/android/app/src/main/AndroidManifest.xml +++ b/apps/android/app/src/main/AndroidManifest.xml @@ -32,7 +32,7 @@ android:label="@string/app_name" android:supportsRtl="true" android:networkSecurityConfig="@xml/network_security_config" - android:theme="@style/Theme.ClawdbotNode"> + android:theme="@style/Theme.MoltbotNode"> Quint(status, server, connected, voiceMode, voiceListening) }.collect { (status, server, connected, voiceMode, voiceListening) -> - val title = if (connected) "Clawdbot Node · Connected" else "Clawdbot Node" + val title = if (connected) "Moltbot Node · Connected" else "Moltbot Node" val voiceSuffix = if (voiceMode == VoiceWakeMode.Always) { if (voiceListening) " · Voice Wake: Listening" else " · Voice Wake: Paused" @@ -91,7 +91,7 @@ class NodeForegroundService : Service() { "Connection", NotificationManager.IMPORTANCE_LOW, ).apply { - description = "Clawdbot node connection status" + description = "Moltbot node connection status" setShowBadge(false) } mgr.createNotificationChannel(channel) @@ -163,7 +163,7 @@ class NodeForegroundService : Service() { private const val CHANNEL_ID = "connection" private const val NOTIFICATION_ID = 1 - private const val ACTION_STOP = "com.clawdbot.android.action.STOP" + private const val ACTION_STOP = "bot.molt.android.action.STOP" fun start(context: Context) { val intent = Intent(context, NodeForegroundService::class.java) diff --git a/apps/android/app/src/main/java/com/clawdbot/android/NodeRuntime.kt b/apps/android/app/src/main/java/bot/molt/android/NodeRuntime.kt similarity index 90% rename from apps/android/app/src/main/java/com/clawdbot/android/NodeRuntime.kt rename to apps/android/app/src/main/java/bot/molt/android/NodeRuntime.kt index 603e4b82b..5fd429e9e 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/NodeRuntime.kt +++ b/apps/android/app/src/main/java/bot/molt/android/NodeRuntime.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android +package bot.molt.android import android.Manifest import android.content.Context @@ -7,35 +7,35 @@ import android.location.LocationManager import android.os.Build import android.os.SystemClock import androidx.core.content.ContextCompat -import com.clawdbot.android.chat.ChatController -import com.clawdbot.android.chat.ChatMessage -import com.clawdbot.android.chat.ChatPendingToolCall -import com.clawdbot.android.chat.ChatSessionEntry -import com.clawdbot.android.chat.OutgoingAttachment -import com.clawdbot.android.gateway.DeviceAuthStore -import com.clawdbot.android.gateway.DeviceIdentityStore -import com.clawdbot.android.gateway.GatewayClientInfo -import com.clawdbot.android.gateway.GatewayConnectOptions -import com.clawdbot.android.gateway.GatewayDiscovery -import com.clawdbot.android.gateway.GatewayEndpoint -import com.clawdbot.android.gateway.GatewaySession -import com.clawdbot.android.gateway.GatewayTlsParams -import com.clawdbot.android.node.CameraCaptureManager -import com.clawdbot.android.node.LocationCaptureManager -import com.clawdbot.android.BuildConfig -import com.clawdbot.android.node.CanvasController -import com.clawdbot.android.node.ScreenRecordManager -import com.clawdbot.android.node.SmsManager -import com.clawdbot.android.protocol.ClawdbotCapability -import com.clawdbot.android.protocol.ClawdbotCameraCommand -import com.clawdbot.android.protocol.ClawdbotCanvasA2UIAction -import com.clawdbot.android.protocol.ClawdbotCanvasA2UICommand -import com.clawdbot.android.protocol.ClawdbotCanvasCommand -import com.clawdbot.android.protocol.ClawdbotScreenCommand -import com.clawdbot.android.protocol.ClawdbotLocationCommand -import com.clawdbot.android.protocol.ClawdbotSmsCommand -import com.clawdbot.android.voice.TalkModeManager -import com.clawdbot.android.voice.VoiceWakeManager +import bot.molt.android.chat.ChatController +import bot.molt.android.chat.ChatMessage +import bot.molt.android.chat.ChatPendingToolCall +import bot.molt.android.chat.ChatSessionEntry +import bot.molt.android.chat.OutgoingAttachment +import bot.molt.android.gateway.DeviceAuthStore +import bot.molt.android.gateway.DeviceIdentityStore +import bot.molt.android.gateway.GatewayClientInfo +import bot.molt.android.gateway.GatewayConnectOptions +import bot.molt.android.gateway.GatewayDiscovery +import bot.molt.android.gateway.GatewayEndpoint +import bot.molt.android.gateway.GatewaySession +import bot.molt.android.gateway.GatewayTlsParams +import bot.molt.android.node.CameraCaptureManager +import bot.molt.android.node.LocationCaptureManager +import bot.molt.android.BuildConfig +import bot.molt.android.node.CanvasController +import bot.molt.android.node.ScreenRecordManager +import bot.molt.android.node.SmsManager +import bot.molt.android.protocol.MoltbotCapability +import bot.molt.android.protocol.MoltbotCameraCommand +import bot.molt.android.protocol.MoltbotCanvasA2UIAction +import bot.molt.android.protocol.MoltbotCanvasA2UICommand +import bot.molt.android.protocol.MoltbotCanvasCommand +import bot.molt.android.protocol.MoltbotScreenCommand +import bot.molt.android.protocol.MoltbotLocationCommand +import bot.molt.android.protocol.MoltbotSmsCommand +import bot.molt.android.voice.TalkModeManager +import bot.molt.android.voice.VoiceWakeManager import kotlinx.coroutines.CoroutineScope import kotlinx.coroutines.Dispatchers import kotlinx.coroutines.Job @@ -451,38 +451,38 @@ class NodeRuntime(context: Context) { private fun buildInvokeCommands(): List = buildList { - add(ClawdbotCanvasCommand.Present.rawValue) - add(ClawdbotCanvasCommand.Hide.rawValue) - add(ClawdbotCanvasCommand.Navigate.rawValue) - add(ClawdbotCanvasCommand.Eval.rawValue) - add(ClawdbotCanvasCommand.Snapshot.rawValue) - add(ClawdbotCanvasA2UICommand.Push.rawValue) - add(ClawdbotCanvasA2UICommand.PushJSONL.rawValue) - add(ClawdbotCanvasA2UICommand.Reset.rawValue) - add(ClawdbotScreenCommand.Record.rawValue) + add(MoltbotCanvasCommand.Present.rawValue) + add(MoltbotCanvasCommand.Hide.rawValue) + add(MoltbotCanvasCommand.Navigate.rawValue) + add(MoltbotCanvasCommand.Eval.rawValue) + add(MoltbotCanvasCommand.Snapshot.rawValue) + add(MoltbotCanvasA2UICommand.Push.rawValue) + add(MoltbotCanvasA2UICommand.PushJSONL.rawValue) + add(MoltbotCanvasA2UICommand.Reset.rawValue) + add(MoltbotScreenCommand.Record.rawValue) if (cameraEnabled.value) { - add(ClawdbotCameraCommand.Snap.rawValue) - add(ClawdbotCameraCommand.Clip.rawValue) + add(MoltbotCameraCommand.Snap.rawValue) + add(MoltbotCameraCommand.Clip.rawValue) } if (locationMode.value != LocationMode.Off) { - add(ClawdbotLocationCommand.Get.rawValue) + add(MoltbotLocationCommand.Get.rawValue) } if (sms.canSendSms()) { - add(ClawdbotSmsCommand.Send.rawValue) + add(MoltbotSmsCommand.Send.rawValue) } } private fun buildCapabilities(): List = buildList { - add(ClawdbotCapability.Canvas.rawValue) - add(ClawdbotCapability.Screen.rawValue) - if (cameraEnabled.value) add(ClawdbotCapability.Camera.rawValue) - if (sms.canSendSms()) add(ClawdbotCapability.Sms.rawValue) + add(MoltbotCapability.Canvas.rawValue) + add(MoltbotCapability.Screen.rawValue) + if (cameraEnabled.value) add(MoltbotCapability.Camera.rawValue) + if (sms.canSendSms()) add(MoltbotCapability.Sms.rawValue) if (voiceWakeMode.value != VoiceWakeMode.Off && hasRecordAudioPermission()) { - add(ClawdbotCapability.VoiceWake.rawValue) + add(MoltbotCapability.VoiceWake.rawValue) } if (locationMode.value != LocationMode.Off) { - add(ClawdbotCapability.Location.rawValue) + add(MoltbotCapability.Location.rawValue) } } @@ -506,7 +506,7 @@ class NodeRuntime(context: Context) { val version = resolvedVersionName() val release = Build.VERSION.RELEASE?.trim().orEmpty() val releaseLabel = if (release.isEmpty()) "unknown" else release - return "ClawdbotAndroid/$version (Android $releaseLabel; SDK ${Build.VERSION.SDK_INT})" + return "MoltbotAndroid/$version (Android $releaseLabel; SDK ${Build.VERSION.SDK_INT})" } private fun buildClientInfo(clientId: String, clientMode: String): GatewayClientInfo { @@ -529,7 +529,7 @@ class NodeRuntime(context: Context) { caps = buildCapabilities(), commands = buildInvokeCommands(), permissions = emptyMap(), - client = buildClientInfo(clientId = "clawdbot-android", clientMode = "node"), + client = buildClientInfo(clientId = "moltbot-android", clientMode = "node"), userAgent = buildUserAgent(), ) } @@ -541,7 +541,7 @@ class NodeRuntime(context: Context) { caps = emptyList(), commands = emptyList(), permissions = emptyMap(), - client = buildClientInfo(clientId = "clawdbot-control-ui", clientMode = "ui"), + client = buildClientInfo(clientId = "moltbot-control-ui", clientMode = "ui"), userAgent = buildUserAgent(), ) } @@ -665,7 +665,7 @@ class NodeRuntime(context: Context) { val actionId = (userActionObj["id"] as? JsonPrimitive)?.content?.trim().orEmpty().ifEmpty { java.util.UUID.randomUUID().toString() } - val name = ClawdbotCanvasA2UIAction.extractActionName(userActionObj) ?: return@launch + val name = MoltbotCanvasA2UIAction.extractActionName(userActionObj) ?: return@launch val surfaceId = (userActionObj["surfaceId"] as? JsonPrimitive)?.content?.trim().orEmpty().ifEmpty { "main" } @@ -675,7 +675,7 @@ class NodeRuntime(context: Context) { val sessionKey = resolveMainSessionKey() val message = - ClawdbotCanvasA2UIAction.formatAgentMessage( + MoltbotCanvasA2UIAction.formatAgentMessage( actionName = name, sessionKey = sessionKey, surfaceId = surfaceId, @@ -709,7 +709,7 @@ class NodeRuntime(context: Context) { try { canvas.eval( - ClawdbotCanvasA2UIAction.jsDispatchA2UIActionStatus( + MoltbotCanvasA2UIAction.jsDispatchA2UIActionStatus( actionId = actionId, ok = connected && error == null, error = error, @@ -827,10 +827,10 @@ class NodeRuntime(context: Context) { private suspend fun handleInvoke(command: String, paramsJson: String?): GatewaySession.InvokeResult { if ( - command.startsWith(ClawdbotCanvasCommand.NamespacePrefix) || - command.startsWith(ClawdbotCanvasA2UICommand.NamespacePrefix) || - command.startsWith(ClawdbotCameraCommand.NamespacePrefix) || - command.startsWith(ClawdbotScreenCommand.NamespacePrefix) + command.startsWith(MoltbotCanvasCommand.NamespacePrefix) || + command.startsWith(MoltbotCanvasA2UICommand.NamespacePrefix) || + command.startsWith(MoltbotCameraCommand.NamespacePrefix) || + command.startsWith(MoltbotScreenCommand.NamespacePrefix) ) { if (!isForeground.value) { return GatewaySession.InvokeResult.error( @@ -839,13 +839,13 @@ class NodeRuntime(context: Context) { ) } } - if (command.startsWith(ClawdbotCameraCommand.NamespacePrefix) && !cameraEnabled.value) { + if (command.startsWith(MoltbotCameraCommand.NamespacePrefix) && !cameraEnabled.value) { return GatewaySession.InvokeResult.error( code = "CAMERA_DISABLED", message = "CAMERA_DISABLED: enable Camera in Settings", ) } - if (command.startsWith(ClawdbotLocationCommand.NamespacePrefix) && + if (command.startsWith(MoltbotLocationCommand.NamespacePrefix) && locationMode.value == LocationMode.Off ) { return GatewaySession.InvokeResult.error( @@ -855,18 +855,18 @@ class NodeRuntime(context: Context) { } return when (command) { - ClawdbotCanvasCommand.Present.rawValue -> { + MoltbotCanvasCommand.Present.rawValue -> { val url = CanvasController.parseNavigateUrl(paramsJson) canvas.navigate(url) GatewaySession.InvokeResult.ok(null) } - ClawdbotCanvasCommand.Hide.rawValue -> GatewaySession.InvokeResult.ok(null) - ClawdbotCanvasCommand.Navigate.rawValue -> { + MoltbotCanvasCommand.Hide.rawValue -> GatewaySession.InvokeResult.ok(null) + MoltbotCanvasCommand.Navigate.rawValue -> { val url = CanvasController.parseNavigateUrl(paramsJson) canvas.navigate(url) GatewaySession.InvokeResult.ok(null) } - ClawdbotCanvasCommand.Eval.rawValue -> { + MoltbotCanvasCommand.Eval.rawValue -> { val js = CanvasController.parseEvalJs(paramsJson) ?: return GatewaySession.InvokeResult.error( @@ -884,7 +884,7 @@ class NodeRuntime(context: Context) { } GatewaySession.InvokeResult.ok("""{"result":${result.toJsonString()}}""") } - ClawdbotCanvasCommand.Snapshot.rawValue -> { + MoltbotCanvasCommand.Snapshot.rawValue -> { val snapshotParams = CanvasController.parseSnapshotParams(paramsJson) val base64 = try { @@ -901,7 +901,7 @@ class NodeRuntime(context: Context) { } GatewaySession.InvokeResult.ok("""{"format":"${snapshotParams.format.rawValue}","base64":"$base64"}""") } - ClawdbotCanvasA2UICommand.Reset.rawValue -> { + MoltbotCanvasA2UICommand.Reset.rawValue -> { val a2uiUrl = resolveA2uiHostUrl() ?: return GatewaySession.InvokeResult.error( code = "A2UI_HOST_NOT_CONFIGURED", @@ -917,7 +917,7 @@ class NodeRuntime(context: Context) { val res = canvas.eval(a2uiResetJS) GatewaySession.InvokeResult.ok(res) } - ClawdbotCanvasA2UICommand.Push.rawValue, ClawdbotCanvasA2UICommand.PushJSONL.rawValue -> { + MoltbotCanvasA2UICommand.Push.rawValue, MoltbotCanvasA2UICommand.PushJSONL.rawValue -> { val messages = try { decodeA2uiMessages(command, paramsJson) @@ -940,7 +940,7 @@ class NodeRuntime(context: Context) { val res = canvas.eval(js) GatewaySession.InvokeResult.ok(res) } - ClawdbotCameraCommand.Snap.rawValue -> { + MoltbotCameraCommand.Snap.rawValue -> { showCameraHud(message = "Taking photo…", kind = CameraHudKind.Photo) triggerCameraFlash() val res = @@ -954,7 +954,7 @@ class NodeRuntime(context: Context) { showCameraHud(message = "Photo captured", kind = CameraHudKind.Success, autoHideMs = 1600) GatewaySession.InvokeResult.ok(res.payloadJson) } - ClawdbotCameraCommand.Clip.rawValue -> { + MoltbotCameraCommand.Clip.rawValue -> { val includeAudio = paramsJson?.contains("\"includeAudio\":true") != false if (includeAudio) externalAudioCaptureActive.value = true try { @@ -973,7 +973,7 @@ class NodeRuntime(context: Context) { if (includeAudio) externalAudioCaptureActive.value = false } } - ClawdbotLocationCommand.Get.rawValue -> { + MoltbotLocationCommand.Get.rawValue -> { val mode = locationMode.value if (!isForeground.value && mode != LocationMode.Always) { return GatewaySession.InvokeResult.error( @@ -1026,7 +1026,7 @@ class NodeRuntime(context: Context) { GatewaySession.InvokeResult.error(code = "LOCATION_UNAVAILABLE", message = message) } } - ClawdbotScreenCommand.Record.rawValue -> { + MoltbotScreenCommand.Record.rawValue -> { // Status pill mirrors screen recording state so it stays visible without overlay stacking. _screenRecordActive.value = true try { @@ -1042,7 +1042,7 @@ class NodeRuntime(context: Context) { _screenRecordActive.value = false } } - ClawdbotSmsCommand.Send.rawValue -> { + MoltbotSmsCommand.Send.rawValue -> { val res = sms.send(paramsJson) if (res.ok) { GatewaySession.InvokeResult.ok(res.payloadJson) @@ -1115,7 +1115,7 @@ class NodeRuntime(context: Context) { val raw = if (nodeRaw.isNotBlank()) nodeRaw else operatorRaw if (raw.isBlank()) return null val base = raw.trimEnd('/') - return "${base}/__clawdbot__/a2ui/?platform=android" + return "${base}/__moltbot__/a2ui/?platform=android" } private suspend fun ensureA2uiReady(a2uiUrl: String): Boolean { @@ -1150,7 +1150,7 @@ class NodeRuntime(context: Context) { val jsonlField = (obj["jsonl"] as? JsonPrimitive)?.content?.trim().orEmpty() val hasMessagesArray = obj["messages"] is JsonArray - if (command == ClawdbotCanvasA2UICommand.PushJSONL.rawValue || (!hasMessagesArray && jsonlField.isNotBlank())) { + if (command == MoltbotCanvasA2UICommand.PushJSONL.rawValue || (!hasMessagesArray && jsonlField.isNotBlank())) { val jsonl = jsonlField if (jsonl.isBlank()) throw IllegalArgumentException("INVALID_REQUEST: jsonl required") val messages = @@ -1218,7 +1218,7 @@ private const val a2uiResetJS: String = """ (() => { try { - if (!globalThis.clawdbotA2UI) return { ok: false, error: "missing clawdbotA2UI" }; + if (!globalThis.clawdbotA2UI) return { ok: false, error: "missing moltbotA2UI" }; return globalThis.clawdbotA2UI.reset(); } catch (e) { return { ok: false, error: String(e?.message ?? e) }; @@ -1230,7 +1230,7 @@ private fun a2uiApplyMessagesJS(messagesJson: String): String { return """ (() => { try { - if (!globalThis.clawdbotA2UI) return { ok: false, error: "missing clawdbotA2UI" }; + if (!globalThis.clawdbotA2UI) return { ok: false, error: "missing moltbotA2UI" }; const messages = $messagesJson; return globalThis.clawdbotA2UI.applyMessages(messages); } catch (e) { diff --git a/apps/android/app/src/main/java/com/clawdbot/android/PermissionRequester.kt b/apps/android/app/src/main/java/bot/molt/android/PermissionRequester.kt similarity index 97% rename from apps/android/app/src/main/java/com/clawdbot/android/PermissionRequester.kt rename to apps/android/app/src/main/java/bot/molt/android/PermissionRequester.kt index fa294aa24..78ae0b62b 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/PermissionRequester.kt +++ b/apps/android/app/src/main/java/bot/molt/android/PermissionRequester.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android +package bot.molt.android import android.content.pm.PackageManager import android.content.Intent @@ -115,7 +115,7 @@ class PermissionRequester(private val activity: ComponentActivity) { private fun buildRationaleMessage(permissions: List): String { val labels = permissions.map { permissionLabel(it) } - return "Clawdbot needs ${labels.joinToString(", ")} permissions to continue." + return "Moltbot needs ${labels.joinToString(", ")} permissions to continue." } private fun buildSettingsMessage(permissions: List): String { diff --git a/apps/android/app/src/main/java/com/clawdbot/android/ScreenCaptureRequester.kt b/apps/android/app/src/main/java/bot/molt/android/ScreenCaptureRequester.kt similarity index 95% rename from apps/android/app/src/main/java/com/clawdbot/android/ScreenCaptureRequester.kt rename to apps/android/app/src/main/java/bot/molt/android/ScreenCaptureRequester.kt index d270d5273..29d662044 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/ScreenCaptureRequester.kt +++ b/apps/android/app/src/main/java/bot/molt/android/ScreenCaptureRequester.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android +package bot.molt.android import android.app.Activity import android.content.Context @@ -55,7 +55,7 @@ class ScreenCaptureRequester(private val activity: ComponentActivity) { suspendCancellableCoroutine { cont -> AlertDialog.Builder(activity) .setTitle("Screen recording required") - .setMessage("Clawdbot needs to record the screen for this command.") + .setMessage("Moltbot needs to record the screen for this command.") .setPositiveButton("Continue") { _, _ -> cont.resume(true) } .setNegativeButton("Not now") { _, _ -> cont.resume(false) } .setOnCancelListener { cont.resume(false) } diff --git a/apps/android/app/src/main/java/com/clawdbot/android/SecurePrefs.kt b/apps/android/app/src/main/java/bot/molt/android/SecurePrefs.kt similarity index 99% rename from apps/android/app/src/main/java/com/clawdbot/android/SecurePrefs.kt rename to apps/android/app/src/main/java/bot/molt/android/SecurePrefs.kt index cd6270dd5..7ee3294dc 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/SecurePrefs.kt +++ b/apps/android/app/src/main/java/bot/molt/android/SecurePrefs.kt @@ -1,6 +1,6 @@ @file:Suppress("DEPRECATION") -package com.clawdbot.android +package bot.molt.android import android.content.Context import androidx.core.content.edit @@ -31,7 +31,7 @@ class SecurePrefs(context: Context) { private val prefs = EncryptedSharedPreferences.create( context, - "clawdbot.node.secure", + "moltbot.node.secure", masterKey, EncryptedSharedPreferences.PrefKeyEncryptionScheme.AES256_SIV, EncryptedSharedPreferences.PrefValueEncryptionScheme.AES256_GCM, diff --git a/apps/android/app/src/main/java/com/clawdbot/android/SessionKey.kt b/apps/android/app/src/main/java/bot/molt/android/SessionKey.kt similarity index 92% rename from apps/android/app/src/main/java/com/clawdbot/android/SessionKey.kt rename to apps/android/app/src/main/java/bot/molt/android/SessionKey.kt index e1aae9ec0..e64051649 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/SessionKey.kt +++ b/apps/android/app/src/main/java/bot/molt/android/SessionKey.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android +package bot.molt.android internal fun normalizeMainKey(raw: String?): String { val trimmed = raw?.trim() diff --git a/apps/android/app/src/main/java/com/clawdbot/android/VoiceWakeMode.kt b/apps/android/app/src/main/java/bot/molt/android/VoiceWakeMode.kt similarity index 90% rename from apps/android/app/src/main/java/com/clawdbot/android/VoiceWakeMode.kt rename to apps/android/app/src/main/java/bot/molt/android/VoiceWakeMode.kt index 6c3e2c201..e0862cc25 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/VoiceWakeMode.kt +++ b/apps/android/app/src/main/java/bot/molt/android/VoiceWakeMode.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android +package bot.molt.android enum class VoiceWakeMode(val rawValue: String) { Off("off"), diff --git a/apps/android/app/src/main/java/com/clawdbot/android/WakeWords.kt b/apps/android/app/src/main/java/bot/molt/android/WakeWords.kt similarity index 95% rename from apps/android/app/src/main/java/com/clawdbot/android/WakeWords.kt rename to apps/android/app/src/main/java/bot/molt/android/WakeWords.kt index d54ed1e08..56b85a5df 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/WakeWords.kt +++ b/apps/android/app/src/main/java/bot/molt/android/WakeWords.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android +package bot.molt.android object WakeWords { const val maxWords: Int = 32 diff --git a/apps/android/app/src/main/java/com/clawdbot/android/chat/ChatController.kt b/apps/android/app/src/main/java/bot/molt/android/chat/ChatController.kt similarity index 99% rename from apps/android/app/src/main/java/com/clawdbot/android/chat/ChatController.kt rename to apps/android/app/src/main/java/bot/molt/android/chat/ChatController.kt index a8e64048c..eef66fece 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/chat/ChatController.kt +++ b/apps/android/app/src/main/java/bot/molt/android/chat/ChatController.kt @@ -1,6 +1,6 @@ -package com.clawdbot.android.chat +package bot.molt.android.chat -import com.clawdbot.android.gateway.GatewaySession +import bot.molt.android.gateway.GatewaySession import java.util.UUID import java.util.concurrent.ConcurrentHashMap import kotlinx.coroutines.CoroutineScope diff --git a/apps/android/app/src/main/java/com/clawdbot/android/chat/ChatModels.kt b/apps/android/app/src/main/java/bot/molt/android/chat/ChatModels.kt similarity index 96% rename from apps/android/app/src/main/java/com/clawdbot/android/chat/ChatModels.kt rename to apps/android/app/src/main/java/bot/molt/android/chat/ChatModels.kt index ad84e8c69..340624452 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/chat/ChatModels.kt +++ b/apps/android/app/src/main/java/bot/molt/android/chat/ChatModels.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.chat +package bot.molt.android.chat data class ChatMessage( val id: String, diff --git a/apps/android/app/src/main/java/com/clawdbot/android/gateway/BonjourEscapes.kt b/apps/android/app/src/main/java/bot/molt/android/gateway/BonjourEscapes.kt similarity index 96% rename from apps/android/app/src/main/java/com/clawdbot/android/gateway/BonjourEscapes.kt rename to apps/android/app/src/main/java/bot/molt/android/gateway/BonjourEscapes.kt index c05d41b4b..2c0c34d68 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/gateway/BonjourEscapes.kt +++ b/apps/android/app/src/main/java/bot/molt/android/gateway/BonjourEscapes.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.gateway +package bot.molt.android.gateway object BonjourEscapes { fun decode(input: String): String { diff --git a/apps/android/app/src/main/java/com/clawdbot/android/gateway/DeviceAuthStore.kt b/apps/android/app/src/main/java/bot/molt/android/gateway/DeviceAuthStore.kt similarity index 90% rename from apps/android/app/src/main/java/com/clawdbot/android/gateway/DeviceAuthStore.kt rename to apps/android/app/src/main/java/bot/molt/android/gateway/DeviceAuthStore.kt index 88643d8d7..6b90b4672 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/gateway/DeviceAuthStore.kt +++ b/apps/android/app/src/main/java/bot/molt/android/gateway/DeviceAuthStore.kt @@ -1,6 +1,6 @@ -package com.clawdbot.android.gateway +package bot.molt.android.gateway -import com.clawdbot.android.SecurePrefs +import bot.molt.android.SecurePrefs class DeviceAuthStore(private val prefs: SecurePrefs) { fun loadToken(deviceId: String, role: String): String? { diff --git a/apps/android/app/src/main/java/com/clawdbot/android/gateway/DeviceIdentityStore.kt b/apps/android/app/src/main/java/bot/molt/android/gateway/DeviceIdentityStore.kt similarity index 97% rename from apps/android/app/src/main/java/com/clawdbot/android/gateway/DeviceIdentityStore.kt rename to apps/android/app/src/main/java/bot/molt/android/gateway/DeviceIdentityStore.kt index 72500b750..58a0aceff 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/gateway/DeviceIdentityStore.kt +++ b/apps/android/app/src/main/java/bot/molt/android/gateway/DeviceIdentityStore.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.gateway +package bot.molt.android.gateway import android.content.Context import android.util.Base64 @@ -21,7 +21,7 @@ data class DeviceIdentity( class DeviceIdentityStore(context: Context) { private val json = Json { ignoreUnknownKeys = true } - private val identityFile = File(context.filesDir, "clawdbot/identity/device.json") + private val identityFile = File(context.filesDir, "moltbot/identity/device.json") @Synchronized fun loadOrCreate(): DeviceIdentity { diff --git a/apps/android/app/src/main/java/com/clawdbot/android/gateway/GatewayDiscovery.kt b/apps/android/app/src/main/java/bot/molt/android/gateway/GatewayDiscovery.kt similarity index 98% rename from apps/android/app/src/main/java/com/clawdbot/android/gateway/GatewayDiscovery.kt rename to apps/android/app/src/main/java/bot/molt/android/gateway/GatewayDiscovery.kt index 121a95485..53bdb5588 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/gateway/GatewayDiscovery.kt +++ b/apps/android/app/src/main/java/bot/molt/android/gateway/GatewayDiscovery.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.gateway +package bot.molt.android.gateway import android.content.Context import android.net.ConnectivityManager @@ -51,9 +51,9 @@ class GatewayDiscovery( private val nsd = context.getSystemService(NsdManager::class.java) private val connectivity = context.getSystemService(ConnectivityManager::class.java) private val dns = DnsResolver.getInstance() - private val serviceType = "_clawdbot-gw._tcp." - private val wideAreaDomain = "clawdbot.internal." - private val logTag = "Clawdbot/GatewayDiscovery" + private val serviceType = "_moltbot-gw._tcp." + private val wideAreaDomain = "moltbot.internal." + private val logTag = "Moltbot/GatewayDiscovery" private val localById = ConcurrentHashMap() private val unicastById = ConcurrentHashMap() diff --git a/apps/android/app/src/main/java/com/clawdbot/android/gateway/GatewayEndpoint.kt b/apps/android/app/src/main/java/bot/molt/android/gateway/GatewayEndpoint.kt similarity index 94% rename from apps/android/app/src/main/java/com/clawdbot/android/gateway/GatewayEndpoint.kt rename to apps/android/app/src/main/java/bot/molt/android/gateway/GatewayEndpoint.kt index ab8aeacc9..2c524cc67 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/gateway/GatewayEndpoint.kt +++ b/apps/android/app/src/main/java/bot/molt/android/gateway/GatewayEndpoint.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.gateway +package bot.molt.android.gateway data class GatewayEndpoint( val stableId: String, diff --git a/apps/android/app/src/main/java/com/clawdbot/android/gateway/GatewayProtocol.kt b/apps/android/app/src/main/java/bot/molt/android/gateway/GatewayProtocol.kt similarity index 51% rename from apps/android/app/src/main/java/com/clawdbot/android/gateway/GatewayProtocol.kt rename to apps/android/app/src/main/java/bot/molt/android/gateway/GatewayProtocol.kt index 4873de122..6836331be 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/gateway/GatewayProtocol.kt +++ b/apps/android/app/src/main/java/bot/molt/android/gateway/GatewayProtocol.kt @@ -1,3 +1,3 @@ -package com.clawdbot.android.gateway +package bot.molt.android.gateway const val GATEWAY_PROTOCOL_VERSION = 3 diff --git a/apps/android/app/src/main/java/com/clawdbot/android/gateway/GatewaySession.kt b/apps/android/app/src/main/java/bot/molt/android/gateway/GatewaySession.kt similarity index 99% rename from apps/android/app/src/main/java/com/clawdbot/android/gateway/GatewaySession.kt rename to apps/android/app/src/main/java/bot/molt/android/gateway/GatewaySession.kt index ddd249a8e..13074b918 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/gateway/GatewaySession.kt +++ b/apps/android/app/src/main/java/bot/molt/android/gateway/GatewaySession.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.gateway +package bot.molt.android.gateway import android.util.Log import java.util.Locale @@ -148,7 +148,7 @@ class GatewaySession( try { conn.request("node.event", params, timeoutMs = 8_000) } catch (err: Throwable) { - Log.w("ClawdbotGateway", "node.event failed: ${err.message ?: err::class.java.simpleName}") + Log.w("MoltbotGateway", "node.event failed: ${err.message ?: err::class.java.simpleName}") } } @@ -181,7 +181,7 @@ class GatewaySession( private val connectNonceDeferred = CompletableDeferred() private val client: OkHttpClient = buildClient() private var socket: WebSocket? = null - private val loggerTag = "ClawdbotGateway" + private val loggerTag = "MoltbotGateway" val remoteAddress: String = if (endpoint.host.contains(":")) { diff --git a/apps/android/app/src/main/java/com/clawdbot/android/gateway/GatewayTls.kt b/apps/android/app/src/main/java/bot/molt/android/gateway/GatewayTls.kt similarity index 98% rename from apps/android/app/src/main/java/com/clawdbot/android/gateway/GatewayTls.kt rename to apps/android/app/src/main/java/bot/molt/android/gateway/GatewayTls.kt index bcca51583..673d60c8f 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/gateway/GatewayTls.kt +++ b/apps/android/app/src/main/java/bot/molt/android/gateway/GatewayTls.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.gateway +package bot.molt.android.gateway import android.annotation.SuppressLint import java.security.MessageDigest diff --git a/apps/android/app/src/main/java/com/clawdbot/android/node/CameraCaptureManager.kt b/apps/android/app/src/main/java/bot/molt/android/node/CameraCaptureManager.kt similarity index 98% rename from apps/android/app/src/main/java/com/clawdbot/android/node/CameraCaptureManager.kt rename to apps/android/app/src/main/java/bot/molt/android/node/CameraCaptureManager.kt index 0361c2e55..cb15a3915 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/node/CameraCaptureManager.kt +++ b/apps/android/app/src/main/java/bot/molt/android/node/CameraCaptureManager.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.node +package bot.molt.android.node import android.Manifest import android.content.Context @@ -22,7 +22,7 @@ import androidx.camera.video.VideoRecordEvent import androidx.core.content.ContextCompat import androidx.core.content.ContextCompat.checkSelfPermission import androidx.core.graphics.scale -import com.clawdbot.android.PermissionRequester +import bot.molt.android.PermissionRequester import kotlinx.coroutines.Dispatchers import kotlinx.coroutines.suspendCancellableCoroutine import kotlinx.coroutines.withTimeout @@ -155,7 +155,7 @@ class CameraCaptureManager(private val context: Context) { provider.unbindAll() provider.bindToLifecycle(owner, selector, videoCapture) - val file = File.createTempFile("clawdbot-clip-", ".mp4") + val file = File.createTempFile("moltbot-clip-", ".mp4") val outputOptions = FileOutputOptions.Builder(file).build() val finalized = kotlinx.coroutines.CompletableDeferred() @@ -285,7 +285,7 @@ private suspend fun Context.cameraProvider(): ProcessCameraProvider = /** Returns (jpegBytes, exifOrientation) so caller can rotate the decoded bitmap. */ private suspend fun ImageCapture.takeJpegWithExif(executor: Executor): Pair = suspendCancellableCoroutine { cont -> - val file = File.createTempFile("clawdbot-snap-", ".jpg") + val file = File.createTempFile("moltbot-snap-", ".jpg") val options = ImageCapture.OutputFileOptions.Builder(file).build() takePicture( options, diff --git a/apps/android/app/src/main/java/com/clawdbot/android/node/CanvasController.kt b/apps/android/app/src/main/java/bot/molt/android/node/CanvasController.kt similarity index 97% rename from apps/android/app/src/main/java/com/clawdbot/android/node/CanvasController.kt rename to apps/android/app/src/main/java/bot/molt/android/node/CanvasController.kt index c7c7a76e1..4d33ed0a6 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/node/CanvasController.kt +++ b/apps/android/app/src/main/java/bot/molt/android/node/CanvasController.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.node +package bot.molt.android.node import android.graphics.Bitmap import android.graphics.Canvas @@ -17,7 +17,7 @@ import kotlinx.serialization.json.Json import kotlinx.serialization.json.JsonElement import kotlinx.serialization.json.JsonObject import kotlinx.serialization.json.JsonPrimitive -import com.clawdbot.android.BuildConfig +import bot.molt.android.BuildConfig import kotlin.coroutines.resume class CanvasController { @@ -84,12 +84,12 @@ class CanvasController { withWebViewOnMain { wv -> if (currentUrl == null) { if (BuildConfig.DEBUG) { - Log.d("ClawdbotCanvas", "load scaffold: $scaffoldAssetUrl") + Log.d("MoltbotCanvas", "load scaffold: $scaffoldAssetUrl") } wv.loadUrl(scaffoldAssetUrl) } else { if (BuildConfig.DEBUG) { - Log.d("ClawdbotCanvas", "load url: $currentUrl") + Log.d("MoltbotCanvas", "load url: $currentUrl") } wv.loadUrl(currentUrl) } @@ -106,7 +106,7 @@ class CanvasController { val js = """ (() => { try { - const api = globalThis.__clawdbot; + const api = globalThis.__moltbot; if (!api) return; if (typeof api.setDebugStatusEnabled === 'function') { api.setDebugStatusEnabled(${if (enabled) "true" else "false"}); diff --git a/apps/android/app/src/main/java/com/clawdbot/android/node/JpegSizeLimiter.kt b/apps/android/app/src/main/java/bot/molt/android/node/JpegSizeLimiter.kt similarity index 98% rename from apps/android/app/src/main/java/com/clawdbot/android/node/JpegSizeLimiter.kt rename to apps/android/app/src/main/java/bot/molt/android/node/JpegSizeLimiter.kt index ec71e9a4b..8fb6c35d4 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/node/JpegSizeLimiter.kt +++ b/apps/android/app/src/main/java/bot/molt/android/node/JpegSizeLimiter.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.node +package bot.molt.android.node import kotlin.math.max import kotlin.math.min diff --git a/apps/android/app/src/main/java/com/clawdbot/android/node/LocationCaptureManager.kt b/apps/android/app/src/main/java/bot/molt/android/node/LocationCaptureManager.kt similarity index 99% rename from apps/android/app/src/main/java/com/clawdbot/android/node/LocationCaptureManager.kt rename to apps/android/app/src/main/java/bot/molt/android/node/LocationCaptureManager.kt index c701be70d..c56eee03a 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/node/LocationCaptureManager.kt +++ b/apps/android/app/src/main/java/bot/molt/android/node/LocationCaptureManager.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.node +package bot.molt.android.node import android.Manifest import android.content.Context diff --git a/apps/android/app/src/main/java/com/clawdbot/android/node/ScreenRecordManager.kt b/apps/android/app/src/main/java/bot/molt/android/node/ScreenRecordManager.kt similarity index 95% rename from apps/android/app/src/main/java/com/clawdbot/android/node/ScreenRecordManager.kt rename to apps/android/app/src/main/java/bot/molt/android/node/ScreenRecordManager.kt index 82e805530..0e785c245 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/node/ScreenRecordManager.kt +++ b/apps/android/app/src/main/java/bot/molt/android/node/ScreenRecordManager.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.node +package bot.molt.android.node import android.content.Context import android.hardware.display.DisplayManager @@ -6,7 +6,7 @@ import android.media.MediaRecorder import android.media.projection.MediaProjectionManager import android.os.Build import android.util.Base64 -import com.clawdbot.android.ScreenCaptureRequester +import bot.molt.android.ScreenCaptureRequester import kotlinx.coroutines.Dispatchers import kotlinx.coroutines.delay import kotlinx.coroutines.withContext @@ -17,13 +17,13 @@ class ScreenRecordManager(private val context: Context) { data class Payload(val payloadJson: String) @Volatile private var screenCaptureRequester: ScreenCaptureRequester? = null - @Volatile private var permissionRequester: com.clawdbot.android.PermissionRequester? = null + @Volatile private var permissionRequester: bot.molt.android.PermissionRequester? = null fun attachScreenCaptureRequester(requester: ScreenCaptureRequester) { screenCaptureRequester = requester } - fun attachPermissionRequester(requester: com.clawdbot.android.PermissionRequester) { + fun attachPermissionRequester(requester: bot.molt.android.PermissionRequester) { permissionRequester = requester } @@ -63,7 +63,7 @@ class ScreenRecordManager(private val context: Context) { val height = metrics.heightPixels val densityDpi = metrics.densityDpi - val file = File.createTempFile("clawdbot-screen-", ".mp4") + val file = File.createTempFile("moltbot-screen-", ".mp4") if (includeAudio) ensureMicPermission() val recorder = createMediaRecorder() @@ -90,7 +90,7 @@ class ScreenRecordManager(private val context: Context) { val surface = recorder.surface virtualDisplay = projection.createVirtualDisplay( - "clawdbot-screen", + "moltbot-screen", width, height, densityDpi, diff --git a/apps/android/app/src/main/java/com/clawdbot/android/node/SmsManager.kt b/apps/android/app/src/main/java/bot/molt/android/node/SmsManager.kt similarity index 98% rename from apps/android/app/src/main/java/com/clawdbot/android/node/SmsManager.kt rename to apps/android/app/src/main/java/bot/molt/android/node/SmsManager.kt index 3e12a56df..0314ee1a7 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/node/SmsManager.kt +++ b/apps/android/app/src/main/java/bot/molt/android/node/SmsManager.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.node +package bot.molt.android.node import android.Manifest import android.content.Context @@ -11,7 +11,7 @@ import kotlinx.serialization.json.JsonObject import kotlinx.serialization.json.JsonPrimitive import kotlinx.serialization.json.jsonObject import kotlinx.serialization.encodeToString -import com.clawdbot.android.PermissionRequester +import bot.molt.android.PermissionRequester /** * Sends SMS messages via the Android SMS API. diff --git a/apps/android/app/src/main/java/com/clawdbot/android/protocol/ClawdbotCanvasA2UIAction.kt b/apps/android/app/src/main/java/bot/molt/android/protocol/ClawdbotCanvasA2UIAction.kt similarity index 89% rename from apps/android/app/src/main/java/com/clawdbot/android/protocol/ClawdbotCanvasA2UIAction.kt rename to apps/android/app/src/main/java/bot/molt/android/protocol/ClawdbotCanvasA2UIAction.kt index a6d6ee136..f73879bb2 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/protocol/ClawdbotCanvasA2UIAction.kt +++ b/apps/android/app/src/main/java/bot/molt/android/protocol/ClawdbotCanvasA2UIAction.kt @@ -1,9 +1,9 @@ -package com.clawdbot.android.protocol +package bot.molt.android.protocol import kotlinx.serialization.json.JsonObject import kotlinx.serialization.json.JsonPrimitive -object ClawdbotCanvasA2UIAction { +object MoltbotCanvasA2UIAction { fun extractActionName(userAction: JsonObject): String? { val name = (userAction["name"] as? JsonPrimitive) @@ -61,6 +61,6 @@ object ClawdbotCanvasA2UIAction { val err = (error ?: "").replace("\\", "\\\\").replace("\"", "\\\"") val okLiteral = if (ok) "true" else "false" val idEscaped = actionId.replace("\\", "\\\\").replace("\"", "\\\"") - return "window.dispatchEvent(new CustomEvent('clawdbot:a2ui-action-status', { detail: { id: \"${idEscaped}\", ok: ${okLiteral}, error: \"${err}\" } }));" + return "window.dispatchEvent(new CustomEvent('moltbot:a2ui-action-status', { detail: { id: \"${idEscaped}\", ok: ${okLiteral}, error: \"${err}\" } }));" } } diff --git a/apps/android/app/src/main/java/com/clawdbot/android/protocol/ClawdbotProtocolConstants.kt b/apps/android/app/src/main/java/bot/molt/android/protocol/ClawdbotProtocolConstants.kt similarity index 69% rename from apps/android/app/src/main/java/com/clawdbot/android/protocol/ClawdbotProtocolConstants.kt rename to apps/android/app/src/main/java/bot/molt/android/protocol/ClawdbotProtocolConstants.kt index bfdb5f782..27d46c3f1 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/protocol/ClawdbotProtocolConstants.kt +++ b/apps/android/app/src/main/java/bot/molt/android/protocol/ClawdbotProtocolConstants.kt @@ -1,6 +1,6 @@ -package com.clawdbot.android.protocol +package bot.molt.android.protocol -enum class ClawdbotCapability(val rawValue: String) { +enum class MoltbotCapability(val rawValue: String) { Canvas("canvas"), Camera("camera"), Screen("screen"), @@ -9,7 +9,7 @@ enum class ClawdbotCapability(val rawValue: String) { Location("location"), } -enum class ClawdbotCanvasCommand(val rawValue: String) { +enum class MoltbotCanvasCommand(val rawValue: String) { Present("canvas.present"), Hide("canvas.hide"), Navigate("canvas.navigate"), @@ -22,7 +22,7 @@ enum class ClawdbotCanvasCommand(val rawValue: String) { } } -enum class ClawdbotCanvasA2UICommand(val rawValue: String) { +enum class MoltbotCanvasA2UICommand(val rawValue: String) { Push("canvas.a2ui.push"), PushJSONL("canvas.a2ui.pushJSONL"), Reset("canvas.a2ui.reset"), @@ -33,7 +33,7 @@ enum class ClawdbotCanvasA2UICommand(val rawValue: String) { } } -enum class ClawdbotCameraCommand(val rawValue: String) { +enum class MoltbotCameraCommand(val rawValue: String) { Snap("camera.snap"), Clip("camera.clip"), ; @@ -43,7 +43,7 @@ enum class ClawdbotCameraCommand(val rawValue: String) { } } -enum class ClawdbotScreenCommand(val rawValue: String) { +enum class MoltbotScreenCommand(val rawValue: String) { Record("screen.record"), ; @@ -52,7 +52,7 @@ enum class ClawdbotScreenCommand(val rawValue: String) { } } -enum class ClawdbotSmsCommand(val rawValue: String) { +enum class MoltbotSmsCommand(val rawValue: String) { Send("sms.send"), ; @@ -61,7 +61,7 @@ enum class ClawdbotSmsCommand(val rawValue: String) { } } -enum class ClawdbotLocationCommand(val rawValue: String) { +enum class MoltbotLocationCommand(val rawValue: String) { Get("location.get"), ; diff --git a/apps/android/app/src/main/java/com/clawdbot/android/tools/ToolDisplay.kt b/apps/android/app/src/main/java/bot/molt/android/tools/ToolDisplay.kt similarity index 99% rename from apps/android/app/src/main/java/com/clawdbot/android/tools/ToolDisplay.kt rename to apps/android/app/src/main/java/bot/molt/android/tools/ToolDisplay.kt index aed5d0b4b..6f4862887 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/tools/ToolDisplay.kt +++ b/apps/android/app/src/main/java/bot/molt/android/tools/ToolDisplay.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.tools +package bot.molt.android.tools import android.content.Context import kotlinx.serialization.Serializable diff --git a/apps/android/app/src/main/java/com/clawdbot/android/ui/CameraHudOverlay.kt b/apps/android/app/src/main/java/bot/molt/android/ui/CameraHudOverlay.kt similarity index 97% rename from apps/android/app/src/main/java/com/clawdbot/android/ui/CameraHudOverlay.kt rename to apps/android/app/src/main/java/bot/molt/android/ui/CameraHudOverlay.kt index 2143ba7f8..7b45efae9 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/ui/CameraHudOverlay.kt +++ b/apps/android/app/src/main/java/bot/molt/android/ui/CameraHudOverlay.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.ui +package bot.molt.android.ui import androidx.compose.foundation.background import androidx.compose.foundation.layout.Box diff --git a/apps/android/app/src/main/java/com/clawdbot/android/ui/ChatSheet.kt b/apps/android/app/src/main/java/bot/molt/android/ui/ChatSheet.kt similarity index 52% rename from apps/android/app/src/main/java/com/clawdbot/android/ui/ChatSheet.kt rename to apps/android/app/src/main/java/bot/molt/android/ui/ChatSheet.kt index 6f15e5922..21af1a4c6 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/ui/ChatSheet.kt +++ b/apps/android/app/src/main/java/bot/molt/android/ui/ChatSheet.kt @@ -1,8 +1,8 @@ -package com.clawdbot.android.ui +package bot.molt.android.ui import androidx.compose.runtime.Composable -import com.clawdbot.android.MainViewModel -import com.clawdbot.android.ui.chat.ChatSheetContent +import bot.molt.android.MainViewModel +import bot.molt.android.ui.chat.ChatSheetContent @Composable fun ChatSheet(viewModel: MainViewModel) { diff --git a/apps/android/app/src/main/java/com/clawdbot/android/ui/ClawdbotTheme.kt b/apps/android/app/src/main/java/bot/molt/android/ui/ClawdbotTheme.kt similarity index 92% rename from apps/android/app/src/main/java/com/clawdbot/android/ui/ClawdbotTheme.kt rename to apps/android/app/src/main/java/bot/molt/android/ui/ClawdbotTheme.kt index 0eea8da39..c292aa25d 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/ui/ClawdbotTheme.kt +++ b/apps/android/app/src/main/java/bot/molt/android/ui/ClawdbotTheme.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.ui +package bot.molt.android.ui import androidx.compose.foundation.isSystemInDarkTheme import androidx.compose.material3.MaterialTheme @@ -9,7 +9,7 @@ import androidx.compose.ui.graphics.Color import androidx.compose.ui.platform.LocalContext @Composable -fun ClawdbotTheme(content: @Composable () -> Unit) { +fun MoltbotTheme(content: @Composable () -> Unit) { val context = LocalContext.current val isDark = isSystemInDarkTheme() val colorScheme = if (isDark) dynamicDarkColorScheme(context) else dynamicLightColorScheme(context) diff --git a/apps/android/app/src/main/java/com/clawdbot/android/ui/RootScreen.kt b/apps/android/app/src/main/java/bot/molt/android/ui/RootScreen.kt similarity index 96% rename from apps/android/app/src/main/java/com/clawdbot/android/ui/RootScreen.kt rename to apps/android/app/src/main/java/bot/molt/android/ui/RootScreen.kt index 96d2543a7..67d76b82f 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/ui/RootScreen.kt +++ b/apps/android/app/src/main/java/bot/molt/android/ui/RootScreen.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.ui +package bot.molt.android.ui import android.annotation.SuppressLint import android.Manifest @@ -65,8 +65,8 @@ import androidx.compose.ui.viewinterop.AndroidView import androidx.compose.ui.window.Popup import androidx.compose.ui.window.PopupProperties import androidx.core.content.ContextCompat -import com.clawdbot.android.CameraHudKind -import com.clawdbot.android.MainViewModel +import bot.molt.android.CameraHudKind +import bot.molt.android.MainViewModel @OptIn(ExperimentalMaterial3Api::class) @Composable @@ -333,7 +333,7 @@ private fun CanvasView(viewModel: MainViewModel, modifier: Modifier = Modifier) disableForceDarkIfSupported(settings) } if (isDebuggable) { - Log.d("ClawdbotWebView", "userAgent: ${settings.userAgentString}") + Log.d("MoltbotWebView", "userAgent: ${settings.userAgentString}") } isScrollContainer = true overScrollMode = View.OVER_SCROLL_IF_CONTENT_SCROLLS @@ -348,7 +348,7 @@ private fun CanvasView(viewModel: MainViewModel, modifier: Modifier = Modifier) ) { if (!isDebuggable) return if (!request.isForMainFrame) return - Log.e("ClawdbotWebView", "onReceivedError: ${error.errorCode} ${error.description} ${request.url}") + Log.e("MoltbotWebView", "onReceivedError: ${error.errorCode} ${error.description} ${request.url}") } override fun onReceivedHttpError( @@ -359,14 +359,14 @@ private fun CanvasView(viewModel: MainViewModel, modifier: Modifier = Modifier) if (!isDebuggable) return if (!request.isForMainFrame) return Log.e( - "ClawdbotWebView", + "MoltbotWebView", "onReceivedHttpError: ${errorResponse.statusCode} ${errorResponse.reasonPhrase} ${request.url}", ) } override fun onPageFinished(view: WebView, url: String?) { if (isDebuggable) { - Log.d("ClawdbotWebView", "onPageFinished: $url") + Log.d("MoltbotWebView", "onPageFinished: $url") } viewModel.canvas.onPageFinished() } @@ -377,7 +377,7 @@ private fun CanvasView(viewModel: MainViewModel, modifier: Modifier = Modifier) ): Boolean { if (isDebuggable) { Log.e( - "ClawdbotWebView", + "MoltbotWebView", "onRenderProcessGone didCrash=${detail.didCrash()} priorityAtExit=${detail.rendererPriorityAtExit()}", ) } @@ -390,7 +390,7 @@ private fun CanvasView(viewModel: MainViewModel, modifier: Modifier = Modifier) if (!isDebuggable) return false val msg = consoleMessage ?: return false Log.d( - "ClawdbotWebView", + "MoltbotWebView", "console ${msg.messageLevel()} @ ${msg.sourceId()}:${msg.lineNumber()} ${msg.message()}", ) return false @@ -428,7 +428,7 @@ private class CanvasA2UIActionBridge(private val onMessage: (String) -> Unit) { } companion object { - const val interfaceName: String = "clawdbotCanvasA2UIAction" + const val interfaceName: String = "moltbotCanvasA2UIAction" } } diff --git a/apps/android/app/src/main/java/com/clawdbot/android/ui/SettingsSheet.kt b/apps/android/app/src/main/java/bot/molt/android/ui/SettingsSheet.kt similarity index 98% rename from apps/android/app/src/main/java/com/clawdbot/android/ui/SettingsSheet.kt rename to apps/android/app/src/main/java/bot/molt/android/ui/SettingsSheet.kt index e3a9b3ecb..f96731acf 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/ui/SettingsSheet.kt +++ b/apps/android/app/src/main/java/bot/molt/android/ui/SettingsSheet.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.ui +package bot.molt.android.ui import android.Manifest import android.content.Context @@ -58,12 +58,12 @@ import androidx.compose.ui.text.input.ImeAction import androidx.compose.ui.text.style.TextAlign import androidx.compose.ui.unit.dp import androidx.core.content.ContextCompat -import com.clawdbot.android.BuildConfig -import com.clawdbot.android.LocationMode -import com.clawdbot.android.MainViewModel -import com.clawdbot.android.NodeForegroundService -import com.clawdbot.android.VoiceWakeMode -import com.clawdbot.android.WakeWords +import bot.molt.android.BuildConfig +import bot.molt.android.LocationMode +import bot.molt.android.MainViewModel +import bot.molt.android.NodeForegroundService +import bot.molt.android.VoiceWakeMode +import bot.molt.android.WakeWords @Composable fun SettingsSheet(viewModel: MainViewModel) { @@ -457,7 +457,7 @@ fun SettingsSheet(viewModel: MainViewModel) { Column(verticalArrangement = Arrangement.spacedBy(6.dp), modifier = Modifier.fillMaxWidth()) { ListItem( headlineContent = { Text("Foreground Only") }, - supportingContent = { Text("Listens only while Clawdbot is open.") }, + supportingContent = { Text("Listens only while Moltbot is open.") }, trailingContent = { RadioButton( selected = voiceWakeMode == VoiceWakeMode.Foreground, @@ -603,7 +603,7 @@ fun SettingsSheet(viewModel: MainViewModel) { ) ListItem( headlineContent = { Text("While Using") }, - supportingContent = { Text("Only while Clawdbot is open.") }, + supportingContent = { Text("Only while Moltbot is open.") }, trailingContent = { RadioButton( selected = locationMode == LocationMode.WhileUsing, @@ -650,7 +650,7 @@ fun SettingsSheet(viewModel: MainViewModel) { item { ListItem( headlineContent = { Text("Prevent Sleep") }, - supportingContent = { Text("Keeps the screen awake while Clawdbot is open.") }, + supportingContent = { Text("Keeps the screen awake while Moltbot is open.") }, trailingContent = { Switch(checked = preventSleep, onCheckedChange = viewModel::setPreventSleep) }, ) } diff --git a/apps/android/app/src/main/java/com/clawdbot/android/ui/StatusPill.kt b/apps/android/app/src/main/java/bot/molt/android/ui/StatusPill.kt similarity index 99% rename from apps/android/app/src/main/java/com/clawdbot/android/ui/StatusPill.kt rename to apps/android/app/src/main/java/bot/molt/android/ui/StatusPill.kt index 564d96b52..199bcbf82 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/ui/StatusPill.kt +++ b/apps/android/app/src/main/java/bot/molt/android/ui/StatusPill.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.ui +package bot.molt.android.ui import androidx.compose.foundation.layout.Arrangement import androidx.compose.foundation.layout.Row diff --git a/apps/android/app/src/main/java/com/clawdbot/android/ui/TalkOrbOverlay.kt b/apps/android/app/src/main/java/bot/molt/android/ui/TalkOrbOverlay.kt similarity index 99% rename from apps/android/app/src/main/java/com/clawdbot/android/ui/TalkOrbOverlay.kt rename to apps/android/app/src/main/java/bot/molt/android/ui/TalkOrbOverlay.kt index 32225b486..9098c06ff 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/ui/TalkOrbOverlay.kt +++ b/apps/android/app/src/main/java/bot/molt/android/ui/TalkOrbOverlay.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.ui +package bot.molt.android.ui import androidx.compose.animation.core.LinearEasing import androidx.compose.animation.core.RepeatMode diff --git a/apps/android/app/src/main/java/com/clawdbot/android/ui/chat/ChatComposer.kt b/apps/android/app/src/main/java/bot/molt/android/ui/chat/ChatComposer.kt similarity index 99% rename from apps/android/app/src/main/java/com/clawdbot/android/ui/chat/ChatComposer.kt rename to apps/android/app/src/main/java/bot/molt/android/ui/chat/ChatComposer.kt index 1f30938e0..bc0d9917f 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/ui/chat/ChatComposer.kt +++ b/apps/android/app/src/main/java/bot/molt/android/ui/chat/ChatComposer.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.ui.chat +package bot.molt.android.ui.chat import androidx.compose.foundation.layout.Arrangement import androidx.compose.foundation.layout.Box @@ -38,7 +38,7 @@ import androidx.compose.ui.Alignment import androidx.compose.ui.Modifier import androidx.compose.ui.graphics.Color import androidx.compose.ui.unit.dp -import com.clawdbot.android.chat.ChatSessionEntry +import bot.molt.android.chat.ChatSessionEntry @Composable fun ChatComposer( diff --git a/apps/android/app/src/main/java/com/clawdbot/android/ui/chat/ChatMarkdown.kt b/apps/android/app/src/main/java/bot/molt/android/ui/chat/ChatMarkdown.kt similarity index 99% rename from apps/android/app/src/main/java/com/clawdbot/android/ui/chat/ChatMarkdown.kt rename to apps/android/app/src/main/java/bot/molt/android/ui/chat/ChatMarkdown.kt index f15673fb3..10cf25b81 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/ui/chat/ChatMarkdown.kt +++ b/apps/android/app/src/main/java/bot/molt/android/ui/chat/ChatMarkdown.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.ui.chat +package bot.molt.android.ui.chat import android.graphics.BitmapFactory import android.util.Base64 diff --git a/apps/android/app/src/main/java/com/clawdbot/android/ui/chat/ChatMessageListCard.kt b/apps/android/app/src/main/java/bot/molt/android/ui/chat/ChatMessageListCard.kt similarity index 96% rename from apps/android/app/src/main/java/com/clawdbot/android/ui/chat/ChatMessageListCard.kt rename to apps/android/app/src/main/java/bot/molt/android/ui/chat/ChatMessageListCard.kt index a3229d4a2..1091de6c8 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/ui/chat/ChatMessageListCard.kt +++ b/apps/android/app/src/main/java/bot/molt/android/ui/chat/ChatMessageListCard.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.ui.chat +package bot.molt.android.ui.chat import androidx.compose.foundation.layout.Arrangement import androidx.compose.foundation.layout.Box @@ -20,8 +20,8 @@ import androidx.compose.ui.Alignment import androidx.compose.ui.Modifier import androidx.compose.ui.draw.alpha import androidx.compose.ui.unit.dp -import com.clawdbot.android.chat.ChatMessage -import com.clawdbot.android.chat.ChatPendingToolCall +import bot.molt.android.chat.ChatMessage +import bot.molt.android.chat.ChatPendingToolCall @Composable fun ChatMessageListCard( diff --git a/apps/android/app/src/main/java/com/clawdbot/android/ui/chat/ChatMessageViews.kt b/apps/android/app/src/main/java/bot/molt/android/ui/chat/ChatMessageViews.kt similarity index 97% rename from apps/android/app/src/main/java/com/clawdbot/android/ui/chat/ChatMessageViews.kt rename to apps/android/app/src/main/java/bot/molt/android/ui/chat/ChatMessageViews.kt index 59479744e..59445be37 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/ui/chat/ChatMessageViews.kt +++ b/apps/android/app/src/main/java/bot/molt/android/ui/chat/ChatMessageViews.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.ui.chat +package bot.molt.android.ui.chat import android.graphics.BitmapFactory import android.util.Base64 @@ -31,10 +31,10 @@ import androidx.compose.ui.layout.ContentScale import androidx.compose.ui.text.font.FontFamily import androidx.compose.ui.unit.dp import androidx.compose.foundation.Image -import com.clawdbot.android.chat.ChatMessage -import com.clawdbot.android.chat.ChatMessageContent -import com.clawdbot.android.chat.ChatPendingToolCall -import com.clawdbot.android.tools.ToolDisplayRegistry +import bot.molt.android.chat.ChatMessage +import bot.molt.android.chat.ChatMessageContent +import bot.molt.android.chat.ChatPendingToolCall +import bot.molt.android.tools.ToolDisplayRegistry import kotlinx.coroutines.Dispatchers import kotlinx.coroutines.withContext import androidx.compose.ui.platform.LocalContext diff --git a/apps/android/app/src/main/java/com/clawdbot/android/ui/chat/ChatSessionsDialog.kt b/apps/android/app/src/main/java/bot/molt/android/ui/chat/ChatSessionsDialog.kt similarity index 97% rename from apps/android/app/src/main/java/com/clawdbot/android/ui/chat/ChatSessionsDialog.kt rename to apps/android/app/src/main/java/bot/molt/android/ui/chat/ChatSessionsDialog.kt index 9474b2362..377a13daa 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/ui/chat/ChatSessionsDialog.kt +++ b/apps/android/app/src/main/java/bot/molt/android/ui/chat/ChatSessionsDialog.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.ui.chat +package bot.molt.android.ui.chat import androidx.compose.foundation.layout.Arrangement import androidx.compose.foundation.layout.Column @@ -20,7 +20,7 @@ import androidx.compose.runtime.Composable import androidx.compose.ui.Alignment import androidx.compose.ui.Modifier import androidx.compose.ui.unit.dp -import com.clawdbot.android.chat.ChatSessionEntry +import bot.molt.android.chat.ChatSessionEntry @Composable fun ChatSessionsDialog( diff --git a/apps/android/app/src/main/java/com/clawdbot/android/ui/chat/ChatSheetContent.kt b/apps/android/app/src/main/java/bot/molt/android/ui/chat/ChatSheetContent.kt similarity index 97% rename from apps/android/app/src/main/java/com/clawdbot/android/ui/chat/ChatSheetContent.kt rename to apps/android/app/src/main/java/bot/molt/android/ui/chat/ChatSheetContent.kt index 2b58c626b..5632be70f 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/ui/chat/ChatSheetContent.kt +++ b/apps/android/app/src/main/java/bot/molt/android/ui/chat/ChatSheetContent.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.ui.chat +package bot.molt.android.ui.chat import android.content.ContentResolver import android.net.Uri @@ -19,8 +19,8 @@ import androidx.compose.runtime.rememberCoroutineScope import androidx.compose.ui.Modifier import androidx.compose.ui.platform.LocalContext import androidx.compose.ui.unit.dp -import com.clawdbot.android.MainViewModel -import com.clawdbot.android.chat.OutgoingAttachment +import bot.molt.android.MainViewModel +import bot.molt.android.chat.OutgoingAttachment import java.io.ByteArrayOutputStream import kotlinx.coroutines.Dispatchers import kotlinx.coroutines.launch diff --git a/apps/android/app/src/main/java/com/clawdbot/android/ui/chat/SessionFilters.kt b/apps/android/app/src/main/java/bot/molt/android/ui/chat/SessionFilters.kt similarity index 94% rename from apps/android/app/src/main/java/com/clawdbot/android/ui/chat/SessionFilters.kt rename to apps/android/app/src/main/java/bot/molt/android/ui/chat/SessionFilters.kt index da08dbd1e..227fb0a02 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/ui/chat/SessionFilters.kt +++ b/apps/android/app/src/main/java/bot/molt/android/ui/chat/SessionFilters.kt @@ -1,6 +1,6 @@ -package com.clawdbot.android.ui.chat +package bot.molt.android.ui.chat -import com.clawdbot.android.chat.ChatSessionEntry +import bot.molt.android.chat.ChatSessionEntry private const val RECENT_WINDOW_MS = 24 * 60 * 60 * 1000L diff --git a/apps/android/app/src/main/java/com/clawdbot/android/voice/StreamingMediaDataSource.kt b/apps/android/app/src/main/java/bot/molt/android/voice/StreamingMediaDataSource.kt similarity index 98% rename from apps/android/app/src/main/java/com/clawdbot/android/voice/StreamingMediaDataSource.kt rename to apps/android/app/src/main/java/bot/molt/android/voice/StreamingMediaDataSource.kt index 6b1536ad5..7a7f61165 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/voice/StreamingMediaDataSource.kt +++ b/apps/android/app/src/main/java/bot/molt/android/voice/StreamingMediaDataSource.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.voice +package bot.molt.android.voice import android.media.MediaDataSource import kotlin.math.min diff --git a/apps/android/app/src/main/java/com/clawdbot/android/voice/TalkDirectiveParser.kt b/apps/android/app/src/main/java/bot/molt/android/voice/TalkDirectiveParser.kt similarity index 99% rename from apps/android/app/src/main/java/com/clawdbot/android/voice/TalkDirectiveParser.kt rename to apps/android/app/src/main/java/bot/molt/android/voice/TalkDirectiveParser.kt index 02d2c3967..0d969e4d1 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/voice/TalkDirectiveParser.kt +++ b/apps/android/app/src/main/java/bot/molt/android/voice/TalkDirectiveParser.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.voice +package bot.molt.android.voice import kotlinx.serialization.json.Json import kotlinx.serialization.json.JsonElement diff --git a/apps/android/app/src/main/java/com/clawdbot/android/voice/TalkModeManager.kt b/apps/android/app/src/main/java/bot/molt/android/voice/TalkModeManager.kt similarity index 99% rename from apps/android/app/src/main/java/com/clawdbot/android/voice/TalkModeManager.kt rename to apps/android/app/src/main/java/bot/molt/android/voice/TalkModeManager.kt index 41f98140d..f050f8bd2 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/voice/TalkModeManager.kt +++ b/apps/android/app/src/main/java/bot/molt/android/voice/TalkModeManager.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.voice +package bot.molt.android.voice import android.Manifest import android.content.Context @@ -20,9 +20,9 @@ import android.speech.tts.TextToSpeech import android.speech.tts.UtteranceProgressListener import android.util.Log import androidx.core.content.ContextCompat -import com.clawdbot.android.gateway.GatewaySession -import com.clawdbot.android.isCanonicalMainSessionKey -import com.clawdbot.android.normalizeMainKey +import bot.molt.android.gateway.GatewaySession +import bot.molt.android.isCanonicalMainSessionKey +import bot.molt.android.normalizeMainKey import java.net.HttpURLConnection import java.net.URL import java.util.UUID diff --git a/apps/android/app/src/main/java/com/clawdbot/android/voice/VoiceWakeCommandExtractor.kt b/apps/android/app/src/main/java/bot/molt/android/voice/VoiceWakeCommandExtractor.kt similarity index 97% rename from apps/android/app/src/main/java/com/clawdbot/android/voice/VoiceWakeCommandExtractor.kt rename to apps/android/app/src/main/java/bot/molt/android/voice/VoiceWakeCommandExtractor.kt index 1f527b8c8..8da4e3289 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/voice/VoiceWakeCommandExtractor.kt +++ b/apps/android/app/src/main/java/bot/molt/android/voice/VoiceWakeCommandExtractor.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.voice +package bot.molt.android.voice object VoiceWakeCommandExtractor { fun extractCommand(text: String, triggerWords: List): String? { diff --git a/apps/android/app/src/main/java/com/clawdbot/android/voice/VoiceWakeManager.kt b/apps/android/app/src/main/java/bot/molt/android/voice/VoiceWakeManager.kt similarity index 99% rename from apps/android/app/src/main/java/com/clawdbot/android/voice/VoiceWakeManager.kt rename to apps/android/app/src/main/java/bot/molt/android/voice/VoiceWakeManager.kt index 69863b4cc..b27d0e3c7 100644 --- a/apps/android/app/src/main/java/com/clawdbot/android/voice/VoiceWakeManager.kt +++ b/apps/android/app/src/main/java/bot/molt/android/voice/VoiceWakeManager.kt @@ -1,4 +1,4 @@ -package com.clawdbot.android.voice +package bot.molt.android.voice import android.content.Context import android.content.Intent diff --git a/apps/android/app/src/main/res/values/strings.xml b/apps/android/app/src/main/res/values/strings.xml index 3665960c2..0aae9e739 100644 --- a/apps/android/app/src/main/res/values/strings.xml +++ b/apps/android/app/src/main/res/values/strings.xml @@ -1,3 +1,3 @@ - Clawdbot Node + Moltbot Node diff --git a/apps/android/app/src/main/res/values/themes.xml b/apps/android/app/src/main/res/values/themes.xml index fe7c9b17f..f90f40dc9 100644 --- a/apps/android/app/src/main/res/values/themes.xml +++ b/apps/android/app/src/main/res/values/themes.xml @@ -1,5 +1,5 @@ - - -
    + +
    -
    Ready
    -
    Waiting for agent
    +
    Ready
    +
    Waiting for agent
    diff --git a/docs/gateway/security/formal-verification.md b/docs/gateway/security/formal-verification.md new file mode 100644 index 000000000..f5c6bbbb4 --- /dev/null +++ b/docs/gateway/security/formal-verification.md @@ -0,0 +1,160 @@ +--- +title: Formal Verification (Security Models) +summary: Machine-checked security models for Moltbot’s highest-risk paths. +permalink: /security/formal-verification/ +--- + +# Formal Verification (Security Models) + +This page tracks Moltbot’s **formal security models** (TLA+/TLC today; more as needed). + +> Note: some older links may refer to the previous project name. + +**Goal (north star):** provide a machine-checked argument that Moltbot enforces its +intended security policy (authorization, session isolation, tool gating, and +misconfiguration safety), under explicit assumptions. + +**What this is (today):** an executable, attacker-driven **security regression suite**: +- Each claim has a runnable model-check over a finite state space. +- Many claims have a paired **negative model** that produces a counterexample trace for a realistic bug class. + +**What this is not (yet):** a proof that “Moltbot is secure in all respects” or that the full TypeScript implementation is correct. + +## Where the models live + +Models are maintained in a separate repo: [vignesh07/clawdbot-formal-models](https://github.com/vignesh07/clawdbot-formal-models). + +## Important caveats + +- These are **models**, not the full TypeScript implementation. Drift between model and code is possible. +- Results are bounded by the state space explored by TLC; “green” does not imply security beyond the modeled assumptions and bounds. +- Some claims rely on explicit environmental assumptions (e.g., correct deployment, correct configuration inputs). + +## Reproducing results + +Today, results are reproduced by cloning the models repo locally and running TLC (see below). A future iteration could offer: +- CI-run models with public artifacts (counterexample traces, run logs) +- a hosted “run this model” workflow for small, bounded checks + +Getting started: + +```bash +git clone https://github.com/vignesh07/clawdbot-formal-models +cd clawdbot-formal-models + +# Java 11+ required (TLC runs on the JVM). +# The repo vendors a pinned `tla2tools.jar` (TLA+ tools) and provides `bin/tlc` + Make targets. + +make +``` + +### Gateway exposure and open gateway misconfiguration + +**Claim:** binding beyond loopback without auth can make remote compromise possible / increases exposure; token/password blocks unauth attackers (per the model assumptions). + +- Green runs: + - `make gateway-exposure-v2` + - `make gateway-exposure-v2-protected` +- Red (expected): + - `make gateway-exposure-v2-negative` + +See also: `docs/gateway-exposure-matrix.md` in the models repo. + +### Nodes.run pipeline (highest-risk capability) + +**Claim:** `nodes.run` requires (a) node command allowlist plus declared commands and (b) live approval when configured; approvals are tokenized to prevent replay (in the model). + +- Green runs: + - `make nodes-pipeline` + - `make approvals-token` +- Red (expected): + - `make nodes-pipeline-negative` + - `make approvals-token-negative` + +### Pairing store (DM gating) + +**Claim:** pairing requests respect TTL and pending-request caps. + +- Green runs: + - `make pairing` + - `make pairing-cap` +- Red (expected): + - `make pairing-negative` + - `make pairing-cap-negative` + +### Ingress gating (mentions + control-command bypass) + +**Claim:** in group contexts requiring mention, an unauthorized “control command” cannot bypass mention gating. + +- Green: + - `make ingress-gating` +- Red (expected): + - `make ingress-gating-negative` + +### Routing/session-key isolation + +**Claim:** DMs from distinct peers do not collapse into the same session unless explicitly linked/configured. + +- Green: + - `make routing-isolation` +- Red (expected): + - `make routing-isolation-negative` + + +## v1++: additional bounded models (concurrency, retries, trace correctness) + +These are follow-on models that tighten fidelity around real-world failure modes (non-atomic updates, retries, and message fan-out). + +### Pairing store concurrency / idempotency + +**Claim:** a pairing store should enforce `MaxPending` and idempotency even under interleavings (i.e., “check-then-write” must be atomic / locked; refresh shouldn’t create duplicates). + +What it means: +- Under concurrent requests, you can’t exceed `MaxPending` for a channel. +- Repeated requests/refreshes for the same `(channel, sender)` should not create duplicate live pending rows. + +- Green runs: + - `make pairing-race` (atomic/locked cap check) + - `make pairing-idempotency` + - `make pairing-refresh` + - `make pairing-refresh-race` +- Red (expected): + - `make pairing-race-negative` (non-atomic begin/commit cap race) + - `make pairing-idempotency-negative` + - `make pairing-refresh-negative` + - `make pairing-refresh-race-negative` + +### Ingress trace correlation / idempotency + +**Claim:** ingestion should preserve trace correlation across fan-out and be idempotent under provider retries. + +What it means: +- When one external event becomes multiple internal messages, every part keeps the same trace/event identity. +- Retries do not result in double-processing. +- If provider event IDs are missing, dedupe falls back to a safe key (e.g., trace ID) to avoid dropping distinct events. + +- Green: + - `make ingress-trace` + - `make ingress-trace2` + - `make ingress-idempotency` + - `make ingress-dedupe-fallback` +- Red (expected): + - `make ingress-trace-negative` + - `make ingress-trace2-negative` + - `make ingress-idempotency-negative` + - `make ingress-dedupe-fallback-negative` + +### Routing dmScope precedence + identityLinks + +**Claim:** routing must keep DM sessions isolated by default, and only collapse sessions when explicitly configured (channel precedence + identity links). + +What it means: +- Channel-specific dmScope overrides must win over global defaults. +- identityLinks should collapse only within explicit linked groups, not across unrelated peers. + +- Green: + - `make routing-precedence` + - `make routing-identitylinks` +- Red (expected): + - `make routing-precedence-negative` + - `make routing-identitylinks-negative` diff --git a/docs/gateway/security.md b/docs/gateway/security/index.md similarity index 88% rename from docs/gateway/security.md rename to docs/gateway/security/index.md index 5f5990b9e..d29c3df48 100644 --- a/docs/gateway/security.md +++ b/docs/gateway/security/index.md @@ -5,16 +5,18 @@ read_when: --- # Security 🔒 -## Quick check: `clawdbot security audit` +## Quick check: `moltbot security audit` (formerly `clawdbot security audit`) See also: [Formal Verification (Security Models)](/security/formal-verification/) Run this regularly (especially after changing config or exposing network surfaces): ```bash -clawdbot security audit -clawdbot security audit --deep -clawdbot security audit --fix +moltbot security audit +moltbot security audit --deep +moltbot security audit --fix + +# (On older installs, the command is `clawdbot ...`.) ``` It flags common footguns (Gateway auth exposure, browser control exposure, elevated allowlists, filesystem permissions). @@ -22,11 +24,11 @@ It flags common footguns (Gateway auth exposure, browser control exposure, eleva `--fix` applies safe guardrails: - Tighten `groupPolicy="open"` to `groupPolicy="allowlist"` (and per-account variants) for common channels. - Turn `logging.redactSensitive="off"` back to `"tools"`. -- Tighten local perms (`~/.clawdbot` → `700`, config file → `600`, plus common state files like `credentials/*.json`, `agents/*/agent/auth-profiles.json`, and `agents/*/sessions/sessions.json`). +- Tighten local perms (`~/.moltbot` → `700`, config file → `600`, plus common state files like `credentials/*.json`, `agents/*/agent/auth-profiles.json`, and `agents/*/sessions/sessions.json`). Running an AI agent with shell access on your machine is... *spicy*. Here’s how to not get pwned. -Clawdbot is both a product and an experiment: you’re wiring frontier-model behavior into real messaging surfaces and real tools. **There is no “perfectly secure” setup.** The goal is to be deliberate about: +Moltbot is both a product and an experiment: you’re wiring frontier-model behavior into real messaging surfaces and real tools. **There is no “perfectly secure” setup.** The goal is to be deliberate about: - who can talk to your bot - where the bot is allowed to act - what the bot can touch @@ -43,19 +45,19 @@ Start with the smallest access that still works, then widen it as you gain confi - **Plugins** (extensions exist without an explicit allowlist). - **Model hygiene** (warn when configured models look legacy; not a hard block). -If you run `--deep`, Clawdbot also attempts a best-effort live Gateway probe. +If you run `--deep`, Moltbot also attempts a best-effort live Gateway probe. ## Credential storage map Use this when auditing access or deciding what to back up: -- **WhatsApp**: `~/.clawdbot/credentials/whatsapp//creds.json` +- **WhatsApp**: `~/.moltbot/credentials/whatsapp//creds.json` - **Telegram bot token**: config/env or `channels.telegram.tokenFile` - **Discord bot token**: config/env (token file not yet supported) - **Slack tokens**: config/env (`channels.slack.*`) -- **Pairing allowlists**: `~/.clawdbot/credentials/-allowFrom.json` -- **Model auth profiles**: `~/.clawdbot/agents//agent/auth-profiles.json` -- **Legacy OAuth import**: `~/.clawdbot/credentials/oauth.json` +- **Pairing allowlists**: `~/.moltbot/credentials/-allowFrom.json` +- **Model auth profiles**: `~/.moltbot/agents//agent/auth-profiles.json` +- **Legacy OAuth import**: `~/.moltbot/credentials/oauth.json` ## Security Audit Checklist @@ -79,7 +81,7 @@ For break-glass scenarios only, `gateway.controlUi.dangerouslyDisableDeviceAuth` disables device identity checks entirely. This is a severe security downgrade; keep it off unless you are actively debugging and can revert quickly. -`clawdbot security audit` warns when this setting is enabled. +`moltbot security audit` warns when this setting is enabled. ## Reverse Proxy Configuration @@ -100,10 +102,10 @@ When `trustedProxies` is configured, the Gateway will use `X-Forwarded-For` head ## Local session logs live on disk -Clawdbot stores session transcripts on disk under `~/.clawdbot/agents//sessions/*.jsonl`. +Moltbot stores session transcripts on disk under `~/.moltbot/agents//sessions/*.jsonl`. This is required for session continuity and (optionally) session memory indexing, but it also means **any process/user with filesystem access can read those logs**. Treat disk access as the trust -boundary and lock down permissions on `~/.clawdbot` (see the audit section below). If you need +boundary and lock down permissions on `~/.moltbot` (see the audit section below). If you need stronger isolation between agents, run them under separate OS users or separate hosts. ## Node execution (system.run) @@ -116,7 +118,7 @@ If a macOS node is paired, the Gateway can invoke `system.run` on that node. Thi ## Dynamic skills (watcher / remote nodes) -Clawdbot can refresh the skills list mid-session: +Moltbot can refresh the skills list mid-session: - **Skills watcher**: changes to `SKILL.md` can update the skills snapshot on the next agent turn. - **Remote nodes**: connecting a macOS node can make macOS-only skills eligible (based on bin probing). @@ -139,7 +141,7 @@ People who message you can: Most failures here are not fancy exploits — they’re “someone messaged the bot and the bot did what they asked.” -Clawdbot’s stance: +Moltbot’s stance: - **Identity first:** decide who can talk to the bot (DM pairing / allowlists / explicit “open”). - **Scope next:** decide where the bot is allowed to act (group allowlists + mention gating, tools, sandboxing, device permissions). - **Model last:** assume the model can be manipulated; design so manipulation has limited blast radius. @@ -162,9 +164,9 @@ Plugins run **in-process** with the Gateway. Treat them as trusted code: - Prefer explicit `plugins.allow` allowlists. - Review plugin config before enabling. - Restart the Gateway after plugin changes. -- If you install plugins from npm (`clawdbot plugins install `), treat it like running untrusted code: - - The install path is `~/.clawdbot/extensions//` (or `$CLAWDBOT_STATE_DIR/extensions//`). - - Clawdbot uses `npm pack` and then runs `npm install --omit=dev` in that directory (npm lifecycle scripts can execute code during install). +- If you install plugins from npm (`moltbot plugins install `), treat it like running untrusted code: + - The install path is `~/.moltbot/extensions//` (or `$CLAWDBOT_STATE_DIR/extensions//`). + - Moltbot uses `npm pack` and then runs `npm install --omit=dev` in that directory (npm lifecycle scripts can execute code during install). - Prefer pinned, exact versions (`@scope/pkg@1.2.3`), and inspect the unpacked code on disk before enabling. Details: [Plugins](/plugin) @@ -181,15 +183,15 @@ All current DM-capable channels support a DM policy (`dmPolicy` or `*.dm.policy` Approve via CLI: ```bash -clawdbot pairing list -clawdbot pairing approve +moltbot pairing list +moltbot pairing approve ``` Details + files on disk: [Pairing](/start/pairing) ## DM session isolation (multi-user mode) -By default, Clawdbot routes **all DMs into the main session** so your assistant has continuity across devices and channels. If **multiple people** can DM the bot (open DMs or a multi-person allowlist), consider isolating DM sessions: +By default, Moltbot routes **all DMs into the main session** so your assistant has continuity across devices and channels. If **multiple people** can DM the bot (open DMs or a multi-person allowlist), consider isolating DM sessions: ```json5 { @@ -201,10 +203,10 @@ This prevents cross-user context leakage while keeping group chats isolated. If ## Allowlists (DM + groups) — terminology -Clawdbot has two separate “who can trigger me?” layers: +Moltbot has two separate “who can trigger me?” layers: - **DM allowlist** (`allowFrom` / `channels.discord.dm.allowFrom` / `channels.slack.dm.allowFrom`): who is allowed to talk to the bot in direct messages. - - When `dmPolicy="pairing"`, approvals are written to `~/.clawdbot/credentials/-allowFrom.json` (merged with config allowlists). + - When `dmPolicy="pairing"`, approvals are written to `~/.moltbot/credentials/-allowFrom.json` (merged with config allowlists). - **Group allowlist** (channel-specific): which groups/channels/guilds the bot will accept messages from at all. - Common patterns: - `channels.whatsapp.groups`, `channels.telegram.groups`, `channels.imessage.groups`: per-group defaults like `requireMention`; when set, it also acts as a group allowlist (include `"*"` to keep allow-all behavior). @@ -231,7 +233,7 @@ Red flags to treat as untrusted: - “Read this file/URL and do exactly what it says.” - “Ignore your system prompt or safety rules.” - “Reveal your hidden instructions or tool outputs.” -- “Paste the full contents of ~/.clawdbot or your logs.” +- “Paste the full contents of ~/.moltbot or your logs.” ### Prompt injection does not require public DMs @@ -285,7 +287,7 @@ Assume “compromised” means: someone got into a room that can trigger the bot - Check Gateway logs and recent sessions/transcripts for unexpected tool calls. - Review `extensions/` and remove anything you don’t fully trust. 4. **Re-run audit** - - `clawdbot security audit --deep` and confirm the report is clean. + - `moltbot security audit --deep` and confirm the report is clean. ## Lessons Learned (The Hard Way) @@ -308,10 +310,10 @@ This is social engineering 101. Create distrust, encourage snooping. ### 0) File permissions Keep config + state private on the gateway host: -- `~/.clawdbot/clawdbot.json`: `600` (user read/write only) -- `~/.clawdbot`: `700` (user only) +- `~/.moltbot/moltbot.json`: `600` (user read/write only) +- `~/.moltbot`: `700` (user only) -`clawdbot doctor` can warn and offer to tighten these permissions. +`moltbot doctor` can warn and offer to tighten these permissions. ### 0.4) Network exposure (bind + port + firewall) @@ -330,7 +332,7 @@ Rules of thumb: ### 0.4.1) mDNS/Bonjour discovery (information disclosure) -The Gateway broadcasts its presence via mDNS (`_clawdbot-gw._tcp` on port 5353) for local device discovery. In full mode, this includes TXT records that may expose operational details: +The Gateway broadcasts its presence via mDNS (`_moltbot-gw._tcp` on port 5353) for local device discovery. In full mode, this includes TXT records that may expose operational details: - `cliPath`: full filesystem path to the CLI binary (reveals username and install location) - `sshPort`: advertises SSH availability on the host @@ -389,7 +391,7 @@ Set a token so **all** WS clients must authenticate: } ``` -Doctor can generate one for you: `clawdbot doctor --generate-gateway-token`. +Doctor can generate one for you: `moltbot doctor --generate-gateway-token`. Note: `gateway.remote.token` is **only** for remote CLI calls; it does not protect local WS access. @@ -413,9 +415,9 @@ Rotation checklist (token/password): ### 0.6) Tailscale Serve identity headers -When `gateway.auth.allowTailscale` is `true` (default for Serve), Clawdbot +When `gateway.auth.allowTailscale` is `true` (default for Serve), Moltbot accepts Tailscale Serve identity headers (`tailscale-user-login`) as -authentication. Clawdbot verifies the identity by resolving the +authentication. Moltbot verifies the identity by resolving the `x-forwarded-for` address through the local Tailscale daemon (`tailscale whois`) and matching it to the header. This only triggers for requests that hit loopback and include `x-forwarded-for`, `x-forwarded-proto`, and `x-forwarded-host` as @@ -427,7 +429,7 @@ you terminate TLS or proxy in front of the gateway, disable Trusted proxies: - If you terminate TLS in front of the Gateway, set `gateway.trustedProxies` to your proxy IPs. -- Clawdbot will trust `x-forwarded-for` (or `x-real-ip`) from those IPs to determine the client IP for local pairing checks and HTTP auth/local checks. +- Moltbot will trust `x-forwarded-for` (or `x-real-ip`) from those IPs to determine the client IP for local pairing checks and HTTP auth/local checks. - Ensure your proxy **overwrites** `x-forwarded-for` and blocks direct access to the Gateway port. See [Tailscale](/gateway/tailscale) and [Web overview](/web). @@ -448,9 +450,9 @@ Avoid: ### 0.7) Secrets on disk (what’s sensitive) -Assume anything under `~/.clawdbot/` (or `$CLAWDBOT_STATE_DIR/`) may contain secrets or private data: +Assume anything under `~/.moltbot/` (or `$CLAWDBOT_STATE_DIR/`) may contain secrets or private data: -- `clawdbot.json`: config may include tokens (gateway, remote gateway), provider settings, and allowlists. +- `moltbot.json`: config may include tokens (gateway, remote gateway), provider settings, and allowlists. - `credentials/**`: channel credentials (example: WhatsApp creds), pairing allowlists, legacy OAuth imports. - `agents//agent/auth-profiles.json`: API keys + OAuth tokens (imported from legacy `credentials/oauth.json`). - `agents//sessions/**`: session transcripts (`*.jsonl`) + routing metadata (`sessions.json`) that can contain private messages and tool output. @@ -471,7 +473,7 @@ Logs and transcripts can leak sensitive info even when access controls are corre Recommendations: - Keep tool summary redaction on (`logging.redactSensitive: "tools"`; default). - Add custom patterns for your environment via `logging.redactPatterns` (tokens, hostnames, internal URLs). -- When sharing diagnostics, prefer `clawdbot status --all` (pasteable, secrets redacted) over raw logs. +- When sharing diagnostics, prefer `moltbot status --all` (pasteable, secrets redacted) over raw logs. - Prune old session transcripts and log files if you don’t need long retention. Details: [Logging](/gateway/logging) @@ -572,9 +574,6 @@ If that browser profile already contains logged-in sessions, the model can access those accounts and data. Treat browser profiles as **sensitive state**: - Prefer a dedicated profile for the agent (the default `clawd` profile). - Avoid pointing the agent at your personal daily-driver profile. -- `act:evaluate` and `wait --fn` run arbitrary JavaScript in the page context. - Prompt injection can steer the model into calling them. If you do not need - them, set `browser.evaluateEnabled=false` (see [Configuration](/gateway/configuration#browser-clawd-managed-browser)). - Keep host browser control disabled for sandboxed agents unless you trust them. - Treat browser downloads as untrusted input; prefer an isolated downloads directory. - Disable browser sync/password managers in the agent profile if possible (reduces blast radius). @@ -678,7 +677,7 @@ If your AI does something bad: ### Contain -1. **Stop it:** stop the macOS app (if it supervises the Gateway) or terminate your `clawdbot gateway` process. +1. **Stop it:** stop the macOS app (if it supervises the Gateway) or terminate your `moltbot gateway` process. 2. **Close exposure:** set `gateway.bind: "loopback"` (or disable Tailscale Funnel/Serve) until you understand what happened. 3. **Freeze access:** switch risky DMs/groups to `dmPolicy: "disabled"` / require mentions, and remove `"*"` allow-all entries if you had them. @@ -690,13 +689,13 @@ If your AI does something bad: ### Audit -1. Check Gateway logs: `/tmp/clawdbot/clawdbot-YYYY-MM-DD.log` (or `logging.file`). -2. Review the relevant transcript(s): `~/.clawdbot/agents//sessions/*.jsonl`. +1. Check Gateway logs: `/tmp/moltbot/moltbot-YYYY-MM-DD.log` (or `logging.file`). +2. Review the relevant transcript(s): `~/.moltbot/agents//sessions/*.jsonl`. 3. Review recent config changes (anything that could have widened access: `gateway.bind`, `gateway.auth`, dm/group policies, `tools.elevated`, plugin changes). ### Collect for a report -- Timestamp, gateway host OS + Clawdbot version +- Timestamp, gateway host OS + Moltbot version - The session transcript(s) + a short log tail (after redacting) - What the attacker sent + what the agent did - Whether the Gateway was exposed beyond loopback (LAN/Tailscale Funnel/Serve) @@ -748,7 +747,7 @@ Mario asking for find ~ ## Reporting Security Issues -Found a vulnerability in Clawdbot? Please report responsibly: +Found a vulnerability in Moltbot? Please report responsibly: 1. Email: security@clawd.bot 2. Don't post publicly until fixed diff --git a/docs/gateway/tailscale.md b/docs/gateway/tailscale.md index 6b68c0c61..10ec5e211 100644 --- a/docs/gateway/tailscale.md +++ b/docs/gateway/tailscale.md @@ -6,14 +6,14 @@ read_when: --- # Tailscale (Gateway dashboard) -Clawdbot can auto-configure Tailscale **Serve** (tailnet) or **Funnel** (public) for the +Moltbot can auto-configure Tailscale **Serve** (tailnet) or **Funnel** (public) for the Gateway dashboard and WebSocket port. This keeps the Gateway bound to loopback while Tailscale provides HTTPS, routing, and (for Serve) identity headers. ## Modes - `serve`: Tailnet-only Serve via `tailscale serve`. The gateway stays on `127.0.0.1`. -- `funnel`: Public HTTPS via `tailscale funnel`. Clawdbot requires a shared password. +- `funnel`: Public HTTPS via `tailscale funnel`. Moltbot requires a shared password. - `off`: Default (no Tailscale automation). ## Auth @@ -25,10 +25,10 @@ Set `gateway.auth.mode` to control the handshake: When `tailscale.mode = "serve"` and `gateway.auth.allowTailscale` is `true`, valid Serve proxy requests can authenticate via Tailscale identity headers -(`tailscale-user-login`) without supplying a token/password. Clawdbot verifies +(`tailscale-user-login`) without supplying a token/password. Moltbot verifies the identity by resolving the `x-forwarded-for` address via the local Tailscale daemon (`tailscale whois`) and matching it to the header before accepting it. -Clawdbot only treats a request as Serve when it arrives from loopback with +Moltbot only treats a request as Serve when it arrives from loopback with Tailscale’s `x-forwarded-for`, `x-forwarded-proto`, and `x-forwarded-host` headers. To require explicit credentials, set `gateway.auth.allowTailscale: false` or @@ -85,15 +85,15 @@ Prefer `CLAWDBOT_GATEWAY_PASSWORD` over committing a password to disk. ## CLI examples ```bash -clawdbot gateway --tailscale serve -clawdbot gateway --tailscale funnel --auth password +moltbot gateway --tailscale serve +moltbot gateway --tailscale funnel --auth password ``` ## Notes - Tailscale Serve/Funnel requires the `tailscale` CLI to be installed and logged in. - `tailscale.mode: "funnel"` refuses to start unless auth mode is `password` to avoid public exposure. -- Set `gateway.tailscale.resetOnExit` if you want Clawdbot to undo `tailscale serve` +- Set `gateway.tailscale.resetOnExit` if you want Moltbot to undo `tailscale serve` or `tailscale funnel` configuration on shutdown. - `gateway.bind: "tailnet"` is a direct Tailnet bind (no HTTPS, no Serve/Funnel). - `gateway.bind: "auto"` prefers loopback; use `tailnet` if you want Tailnet-only. diff --git a/docs/gateway/tools-invoke-http-api.md b/docs/gateway/tools-invoke-http-api.md index d5902e98c..3a375db06 100644 --- a/docs/gateway/tools-invoke-http-api.md +++ b/docs/gateway/tools-invoke-http-api.md @@ -6,7 +6,7 @@ read_when: --- # Tools Invoke (HTTP) -Clawdbot’s Gateway exposes a simple HTTP endpoint for invoking a single tool directly. It is always enabled, but gated by Gateway auth and tool policy. +Moltbot’s Gateway exposes a simple HTTP endpoint for invoking a single tool directly. It is always enabled, but gated by Gateway auth and tool policy. - `POST /tools/invoke` - Same port as the Gateway (WS + HTTP multiplex): `http://:/tools/invoke` @@ -54,8 +54,8 @@ Tool availability is filtered through the same policy chain used by Gateway agen If a tool is not allowed by policy, the endpoint returns **404**. To help group policies resolve context, you can optionally set: -- `x-clawdbot-message-channel: ` (example: `slack`, `telegram`) -- `x-clawdbot-account-id: ` (when multiple accounts exist) +- `x-moltbot-message-channel: ` (example: `slack`, `telegram`) +- `x-moltbot-account-id: ` (when multiple accounts exist) ## Responses diff --git a/docs/gateway/troubleshooting.md b/docs/gateway/troubleshooting.md index 697654b80..a4b0b151d 100644 --- a/docs/gateway/troubleshooting.md +++ b/docs/gateway/troubleshooting.md @@ -1,11 +1,11 @@ --- -summary: "Quick troubleshooting guide for common Clawdbot failures" +summary: "Quick troubleshooting guide for common Moltbot failures" read_when: - Investigating runtime issues or failures --- # Troubleshooting 🔧 -When Clawdbot misbehaves, here's how to fix it. +When Moltbot misbehaves, here's how to fix it. Start with the FAQ’s [First 60 seconds](/help/faq#first-60-seconds-if-somethings-broken) if you just want a quick triage recipe. This page goes deeper on runtime failures and diagnostics. @@ -17,15 +17,15 @@ Quick triage commands (in order): | Command | What it tells you | When to use it | |---|---|---| -| `clawdbot status` | Local summary: OS + update, gateway reachability/mode, service, agents/sessions, provider config state | First check, quick overview | -| `clawdbot status --all` | Full local diagnosis (read-only, pasteable, safe-ish) incl. log tail | When you need to share a debug report | -| `clawdbot status --deep` | Runs gateway health checks (incl. provider probes; requires reachable gateway) | When “configured” doesn’t mean “working” | -| `clawdbot gateway probe` | Gateway discovery + reachability (local + remote targets) | When you suspect you’re probing the wrong gateway | -| `clawdbot channels status --probe` | Asks the running gateway for channel status (and optionally probes) | When gateway is reachable but channels misbehave | -| `clawdbot gateway status` | Supervisor state (launchd/systemd/schtasks), runtime PID/exit, last gateway error | When the service “looks loaded” but nothing runs | -| `clawdbot logs --follow` | Live logs (best signal for runtime issues) | When you need the actual failure reason | +| `moltbot status` | Local summary: OS + update, gateway reachability/mode, service, agents/sessions, provider config state | First check, quick overview | +| `moltbot status --all` | Full local diagnosis (read-only, pasteable, safe-ish) incl. log tail | When you need to share a debug report | +| `moltbot status --deep` | Runs gateway health checks (incl. provider probes; requires reachable gateway) | When “configured” doesn’t mean “working” | +| `moltbot gateway probe` | Gateway discovery + reachability (local + remote targets) | When you suspect you’re probing the wrong gateway | +| `moltbot channels status --probe` | Asks the running gateway for channel status (and optionally probes) | When gateway is reachable but channels misbehave | +| `moltbot gateway status` | Supervisor state (launchd/systemd/schtasks), runtime PID/exit, last gateway error | When the service “looks loaded” but nothing runs | +| `moltbot logs --follow` | Live logs (best signal for runtime issues) | When you need the actual failure reason | -**Sharing output:** prefer `clawdbot status --all` (it redacts tokens). If you paste `clawdbot status`, consider setting `CLAWDBOT_SHOW_SECRETS=0` first (token previews). +**Sharing output:** prefer `moltbot status --all` (it redacts tokens). If you paste `moltbot status`, consider setting `CLAWDBOT_SHOW_SECRETS=0` first (token previews). See also: [Health checks](/gateway/health) and [Logging](/logging). @@ -40,13 +40,13 @@ Fix options: - Re-run onboarding and choose **Anthropic** for that agent. - Or paste a setup-token on the **gateway host**: ```bash - clawdbot models auth setup-token --provider anthropic + moltbot models auth setup-token --provider anthropic ``` - Or copy `auth-profiles.json` from the main agent dir to the new agent dir. Verify: ```bash -clawdbot models status +moltbot models status ``` ### OAuth token refresh failed (Anthropic Claude subscription) @@ -59,15 +59,15 @@ switch to a **Claude Code setup-token** and paste it on the **gateway host**. ```bash # Run on the gateway host (paste the setup-token) -clawdbot models auth setup-token --provider anthropic -clawdbot models status +moltbot models auth setup-token --provider anthropic +moltbot models status ``` If you generated the token elsewhere: ```bash -clawdbot models auth paste-token --provider anthropic -clawdbot models status +moltbot models auth paste-token --provider anthropic +moltbot models status ``` More detail: [Anthropic](/providers/anthropic) and [OAuth](/concepts/oauth). @@ -97,18 +97,18 @@ can appear “loaded” while nothing is running. **Check:** ```bash -clawdbot gateway status -clawdbot doctor +moltbot gateway status +moltbot doctor ``` Doctor/service will show runtime state (PID/last exit) and log hints. **Logs:** -- Preferred: `clawdbot logs --follow` -- File logs (always): `/tmp/clawdbot/clawdbot-YYYY-MM-DD.log` (or your configured `logging.file`) +- Preferred: `moltbot logs --follow` +- File logs (always): `/tmp/moltbot/moltbot-YYYY-MM-DD.log` (or your configured `logging.file`) - macOS LaunchAgent (if installed): `$CLAWDBOT_STATE_DIR/logs/gateway.log` and `gateway.err.log` -- Linux systemd (if installed): `journalctl --user -u clawdbot-gateway[-].service -n 200 --no-pager` -- Windows: `schtasks /Query /TN "Clawdbot Gateway ()" /V /FO LIST` +- Linux systemd (if installed): `journalctl --user -u moltbot-gateway[-].service -n 200 --no-pager` +- Windows: `schtasks /Query /TN "Moltbot Gateway ()" /V /FO LIST` **Enable more logging:** - Bump file log detail (persisted JSONL): @@ -131,24 +131,24 @@ Gateway refuses to start. **Fix (recommended):** - Run the wizard and set the Gateway run mode to **Local**: ```bash - clawdbot configure + moltbot configure ``` - Or set it directly: ```bash - clawdbot config set gateway.mode local + moltbot config set gateway.mode local ``` **If you meant to run a remote Gateway instead:** - Set a remote URL and keep `gateway.mode=remote`: ```bash - clawdbot config set gateway.mode remote - clawdbot config set gateway.remote.url "wss://gateway.example.com" + moltbot config set gateway.mode remote + moltbot config set gateway.remote.url "wss://gateway.example.com" ``` **Ad-hoc/dev only:** pass `--allow-unconfigured` to start the gateway without `gateway.mode=local`. -**No config file yet?** Run `clawdbot setup` to create a starter config, then rerun +**No config file yet?** Run `moltbot setup` to create a starter config, then rerun the gateway. ### Service Environment (PATH + runtime) @@ -166,7 +166,7 @@ so missing tools usually mean your shell init isn’t exporting them (or set `tools.exec.pathPrepend`). See [/tools/exec](/tools/exec). WhatsApp + Telegram channels require **Node**; Bun is unsupported. If your -service was installed with Bun or a version-managed Node path, run `clawdbot doctor` +service was installed with Bun or a version-managed Node path, run `moltbot doctor` to migrate to a system Node install. ### Skill missing API key in sandbox @@ -178,7 +178,7 @@ to migrate to a system Node install. **Fix:** - set `agents.defaults.sandbox.docker.env` (or per-agent `agents.list[].sandbox.docker.env`) - or bake the key into your custom sandbox image -- then run `clawdbot sandbox recreate --agent ` (or `--all`) +- then run `moltbot sandbox recreate --agent ` (or `--all`) ### Service Running but Port Not Listening @@ -191,28 +191,28 @@ the Gateway likely refused to bind. - Always trust `Probe target:` + `Config (service):` as the “what did we actually try?” lines. **Check:** -- `gateway.mode` must be `local` for `clawdbot gateway` and the service. -- If you set `gateway.mode=remote`, the **CLI defaults** to a remote URL. The service can still be running locally, but your CLI may be probing the wrong place. Use `clawdbot gateway status` to see the service’s resolved port + probe target (or pass `--url`). -- `clawdbot gateway status` and `clawdbot doctor` surface the **last gateway error** from logs when the service looks running but the port is closed. +- `gateway.mode` must be `local` for `moltbot gateway` and the service. +- If you set `gateway.mode=remote`, the **CLI defaults** to a remote URL. The service can still be running locally, but your CLI may be probing the wrong place. Use `moltbot gateway status` to see the service’s resolved port + probe target (or pass `--url`). +- `moltbot gateway status` and `moltbot doctor` surface the **last gateway error** from logs when the service looks running but the port is closed. - Non-loopback binds (`lan`/`tailnet`/`custom`, or `auto` when loopback is unavailable) require auth: `gateway.auth.token` (or `CLAWDBOT_GATEWAY_TOKEN`). - `gateway.remote.token` is for remote CLI calls only; it does **not** enable local auth. - `gateway.token` is ignored; use `gateway.auth.token`. -**If `clawdbot gateway status` shows a config mismatch** +**If `moltbot gateway status` shows a config mismatch** - `Config (cli): ...` and `Config (service): ...` should normally match. - If they don’t, you’re almost certainly editing one config while the service is running another. -- Fix: rerun `clawdbot gateway install --force` from the same `--profile` / `CLAWDBOT_STATE_DIR` you want the service to use. +- Fix: rerun `moltbot gateway install --force` from the same `--profile` / `CLAWDBOT_STATE_DIR` you want the service to use. -**If `clawdbot gateway status` reports service config issues** +**If `moltbot gateway status` reports service config issues** - The supervisor config (launchd/systemd/schtasks) is missing current defaults. -- Fix: run `clawdbot doctor` to update it (or `clawdbot gateway install --force` for a full rewrite). +- Fix: run `moltbot doctor` to update it (or `moltbot gateway install --force` for a full rewrite). **If `Last gateway error:` mentions “refusing to bind … without auth”** - You set `gateway.bind` to a non-loopback mode (`lan`/`tailnet`/`custom`, or `auto` when loopback is unavailable) but didn’t configure auth. - Fix: set `gateway.auth.mode` + `gateway.auth.token` (or export `CLAWDBOT_GATEWAY_TOKEN`) and restart the service. -**If `clawdbot gateway status` says `bind=tailnet` but no tailnet interface was found** +**If `moltbot gateway status` says `bind=tailnet` but no tailnet interface was found** - The gateway tried to bind to a Tailscale IP (100.64.0.0/10) but none were detected on the host. - Fix: bring up Tailscale on that machine (or change `gateway.bind` to `loopback`/`lan`). @@ -226,7 +226,7 @@ This means something is already listening on the gateway port. **Check:** ```bash -clawdbot gateway status +moltbot gateway status ``` It will show the listener(s) and likely causes (gateway already running, SSH tunnel). @@ -234,7 +234,7 @@ If needed, stop the service or pick a different port. ### Extra Workspace Folders Detected -If you upgraded from older installs, you might still have `~/clawdbot` on disk. +If you upgraded from older installs, you might still have `~/moltbot` on disk. Multiple workspace directories can cause confusing auth or state drift because only one workspace is active. @@ -267,14 +267,14 @@ The agent was interrupted mid-response. ### "Agent failed before reply: Unknown model: anthropic/claude-haiku-3-5" -Clawdbot intentionally rejects **older/insecure models** (especially those more +Moltbot intentionally rejects **older/insecure models** (especially those more vulnerable to prompt injection). If you see this error, the model name is no longer supported. **Fix:** - Pick a **latest** model for the provider and update your config or model alias. -- If you’re unsure which models are available, run `clawdbot models list` or - `clawdbot models scan` and choose a supported one. +- If you’re unsure which models are available, run `moltbot models list` or + `moltbot models scan` and choose a supported one. - Check gateway logs for the detailed failure reason. See also: [Models CLI](/cli/models) and [Model providers](/concepts/model-providers). @@ -283,7 +283,7 @@ See also: [Models CLI](/cli/models) and [Model providers](/concepts/model-provid **Check 1:** Is the sender allowlisted? ```bash -clawdbot status +moltbot status ``` Look for `AllowFrom: ...` in the output. @@ -292,14 +292,14 @@ Look for `AllowFrom: ...` in the output. # The message must match mentionPatterns or explicit mentions; defaults live in channel groups/guilds. # Multi-agent: `agents.list[].groupChat.mentionPatterns` overrides global patterns. grep -n "agents\\|groupChat\\|mentionPatterns\\|channels\\.whatsapp\\.groups\\|channels\\.telegram\\.groups\\|channels\\.imessage\\.groups\\|channels\\.discord\\.guilds" \ - "${CLAWDBOT_CONFIG_PATH:-$HOME/.clawdbot/clawdbot.json}" + "${CLAWDBOT_CONFIG_PATH:-$HOME/.clawdbot/moltbot.json}" ``` **Check 3:** Check the logs ```bash -clawdbot logs --follow +moltbot logs --follow # or if you want quick filters: -tail -f "$(ls -t /tmp/clawdbot/clawdbot-*.log | head -1)" | grep "blocked\\|skip\\|unauthorized" +tail -f "$(ls -t /tmp/moltbot/moltbot-*.log | head -1)" | grep "blocked\\|skip\\|unauthorized" ``` ### Pairing Code Not Arriving @@ -308,14 +308,14 @@ If `dmPolicy` is `pairing`, unknown senders should receive a code and their mess **Check 1:** Is a pending request already waiting? ```bash -clawdbot pairing list +moltbot pairing list ``` Pending DM pairing requests are capped at **3 per channel** by default. If the list is full, new requests won’t generate a code until one is approved or expires. **Check 2:** Did the request get created but no reply was sent? ```bash -clawdbot logs --follow | grep "pairing request" +moltbot logs --follow | grep "pairing request" ``` **Check 3:** Confirm `dmPolicy` isn’t `open`/`allowlist` for that channel. @@ -368,26 +368,26 @@ Or use the `process` tool to background long commands. ```bash # Check local status (creds, sessions, queued events) -clawdbot status +moltbot status # Probe the running gateway + channels (WA connect + Telegram + Discord APIs) -clawdbot status --deep +moltbot status --deep # View recent connection events -clawdbot logs --limit 200 | grep "connection\\|disconnect\\|logout" +moltbot logs --limit 200 | grep "connection\\|disconnect\\|logout" ``` **Fix:** Usually reconnects automatically once the Gateway is running. If you’re stuck, restart the Gateway process (however you supervise it), or run it manually with verbose output: ```bash -clawdbot gateway --verbose +moltbot gateway --verbose ``` If you’re logged out / unlinked: ```bash -clawdbot channels logout +moltbot channels logout trash "${CLAWDBOT_STATE_DIR:-$HOME/.clawdbot}/credentials" # if logout can't cleanly remove everything -clawdbot channels login --verbose # re-scan QR +moltbot channels login --verbose # re-scan QR ``` ### Media Send Failing @@ -404,12 +404,12 @@ ls -la /path/to/your/image.jpg **Check 3:** Check media logs ```bash -grep "media\\|fetch\\|download" "$(ls -t /tmp/clawdbot/clawdbot-*.log | head -1)" | tail -20 +grep "media\\|fetch\\|download" "$(ls -t /tmp/moltbot/moltbot-*.log | head -1)" | tail -20 ``` ### High Memory Usage -Clawdbot keeps conversation history in memory. +Moltbot keeps conversation history in memory. **Fix:** Restart periodically or set session limits: ```json @@ -424,26 +424,26 @@ Clawdbot keeps conversation history in memory. ### “Gateway won’t start — configuration invalid” -Clawdbot now refuses to start when the config contains unknown keys, malformed values, or invalid types. +Moltbot now refuses to start when the config contains unknown keys, malformed values, or invalid types. This is intentional for safety. Fix it with Doctor: ```bash -clawdbot doctor -clawdbot doctor --fix +moltbot doctor +moltbot doctor --fix ``` Notes: -- `clawdbot doctor` reports every invalid entry. -- `clawdbot doctor --fix` applies migrations/repairs and rewrites the config. -- Diagnostic commands like `clawdbot logs`, `clawdbot health`, `clawdbot status`, `clawdbot gateway status`, and `clawdbot gateway probe` still run even if the config is invalid. +- `moltbot doctor` reports every invalid entry. +- `moltbot doctor --fix` applies migrations/repairs and rewrites the config. +- Diagnostic commands like `moltbot logs`, `moltbot health`, `moltbot status`, `moltbot gateway status`, and `moltbot gateway probe` still run even if the config is invalid. ### “All models failed” — what should I check first? - **Credentials** present for the provider(s) being tried (auth profiles + env vars). - **Model routing**: confirm `agents.defaults.model.primary` and fallbacks are models you can access. -- **Gateway logs** in `/tmp/clawdbot/…` for the exact provider error. -- **Model status**: use `/model status` (chat) or `clawdbot models status` (CLI). +- **Gateway logs** in `/tmp/moltbot/…` for the exact provider error. +- **Model status**: use `/model status` (chat) or `moltbot models status` (CLI). ### I’m running on my personal WhatsApp number — why is self-chat weird? @@ -468,13 +468,13 @@ See [WhatsApp setup](/channels/whatsapp). Run the login command again and scan the QR code: ```bash -clawdbot channels login +moltbot channels login ``` ### Build errors on `main` — what’s the standard fix path? 1) `git pull origin main && pnpm install` -2) `clawdbot doctor` +2) `moltbot doctor` 3) Check GitHub issues or Discord 4) Temporary workaround: check out an older commit @@ -488,8 +488,8 @@ Typical recovery: git status # ensure you’re in the repo root pnpm install pnpm build -clawdbot doctor -clawdbot gateway restart +moltbot doctor +moltbot gateway restart ``` Why: pnpm is the configured package manager for this repo. @@ -501,20 +501,20 @@ upgrades in place and rewrites the gateway service to point at the new install. Switch **to git install**: ```bash -curl -fsSL https://clawd.bot/install.sh | bash -s -- --install-method git --no-onboard +curl -fsSL https://molt.bot/install.sh | bash -s -- --install-method git --no-onboard ``` Switch **to npm global**: ```bash -curl -fsSL https://clawd.bot/install.sh | bash +curl -fsSL https://molt.bot/install.sh | bash ``` Notes: - The git flow only rebases if the repo is clean. Commit or stash changes first. - After switching, run: ```bash - clawdbot doctor - clawdbot gateway restart + moltbot doctor + moltbot gateway restart ``` ### Telegram block streaming isn’t splitting text between tool calls. Why? @@ -546,19 +546,19 @@ Fix checklist: 3) Put `requireMention: false` **under** `channels.discord.guilds` (global or per‑channel). Top‑level `channels.discord.requireMention` is not a supported key. 4) Ensure the bot has **Message Content Intent** and channel permissions. -5) Run `clawdbot channels status --probe` for audit hints. +5) Run `moltbot channels status --probe` for audit hints. Docs: [Discord](/channels/discord), [Channels troubleshooting](/channels/troubleshooting). ### Cloud Code Assist API error: invalid tool schema (400). What now? This is almost always a **tool schema compatibility** issue. The Cloud Code Assist -endpoint accepts a strict subset of JSON Schema. Clawdbot scrubs/normalizes tool +endpoint accepts a strict subset of JSON Schema. Moltbot scrubs/normalizes tool schemas in current `main`, but the fix is not in the last release yet (as of January 13, 2026). Fix checklist: -1) **Update Clawdbot**: +1) **Update Moltbot**: - If you can run from source, pull `main` and restart the gateway. - Otherwise, wait for the next release that includes the schema scrubber. 2) Avoid unsupported keywords like `anyOf/oneOf/allOf`, `patternProperties`, @@ -576,11 +576,11 @@ If the app disappears or shows "Abort trap 6" when you click "Allow" on a privac **Fix 1: Reset TCC Cache** ```bash -tccutil reset All com.clawdbot.mac.debug +tccutil reset All bot.molt.mac.debug ``` **Fix 2: Force New Bundle ID** -If resetting doesn't work, change the `BUNDLE_ID` in [`scripts/package-mac-app.sh`](https://github.com/clawdbot/clawdbot/blob/main/scripts/package-mac-app.sh) (e.g., add a `.test` suffix) and rebuild. This forces macOS to treat it as a new app. +If resetting doesn't work, change the `BUNDLE_ID` in [`scripts/package-mac-app.sh`](https://github.com/moltbot/moltbot/blob/main/scripts/package-mac-app.sh) (e.g., add a `.test` suffix) and rebuild. This forces macOS to treat it as a new app. ### Gateway stuck on "Starting..." @@ -589,9 +589,9 @@ The app connects to a local gateway on port `18789`. If it stays stuck: **Fix 1: Stop the supervisor (preferred)** If the gateway is supervised by launchd, killing the PID will just respawn it. Stop the supervisor first: ```bash -clawdbot gateway status -clawdbot gateway stop -# Or: launchctl bootout gui/$UID/com.clawdbot.gateway (replace with com.clawdbot. if needed) +moltbot gateway status +moltbot gateway stop +# Or: launchctl bootout gui/$UID/bot.molt.gateway (replace with bot.molt.; legacy com.clawdbot.* still works) ``` **Fix 2: Port is busy (find the listener)** @@ -607,10 +607,10 @@ kill -9 # last resort ``` **Fix 3: Check the CLI install** -Ensure the global `clawdbot` CLI is installed and matches the app version: +Ensure the global `moltbot` CLI is installed and matches the app version: ```bash -clawdbot --version -npm install -g clawdbot@ +moltbot --version +npm install -g moltbot@ ``` ## Debug Mode @@ -619,19 +619,19 @@ Get verbose logging: ```bash # Turn on trace logging in config: -# ${CLAWDBOT_CONFIG_PATH:-$HOME/.clawdbot/clawdbot.json} -> { logging: { level: "trace" } } +# ${CLAWDBOT_CONFIG_PATH:-$HOME/.clawdbot/moltbot.json} -> { logging: { level: "trace" } } # # Then run verbose commands to mirror debug output to stdout: -clawdbot gateway --verbose -clawdbot channels login --verbose +moltbot gateway --verbose +moltbot channels login --verbose ``` ## Log Locations | Log | Location | |-----|----------| -| Gateway file logs (structured) | `/tmp/clawdbot/clawdbot-YYYY-MM-DD.log` (or `logging.file`) | -| Gateway service logs (supervisor) | macOS: `$CLAWDBOT_STATE_DIR/logs/gateway.log` + `gateway.err.log` (default: `~/.clawdbot/logs/...`; profiles use `~/.clawdbot-/logs/...`)
    Linux: `journalctl --user -u clawdbot-gateway[-].service -n 200 --no-pager`
    Windows: `schtasks /Query /TN "Clawdbot Gateway ()" /V /FO LIST` | +| Gateway file logs (structured) | `/tmp/moltbot/moltbot-YYYY-MM-DD.log` (or `logging.file`) | +| Gateway service logs (supervisor) | macOS: `$CLAWDBOT_STATE_DIR/logs/gateway.log` + `gateway.err.log` (default: `~/.clawdbot/logs/...`; profiles use `~/.clawdbot-/logs/...`)
    Linux: `journalctl --user -u moltbot-gateway[-].service -n 200 --no-pager`
    Windows: `schtasks /Query /TN "Moltbot Gateway ()" /V /FO LIST` | | Session files | `$CLAWDBOT_STATE_DIR/agents//sessions/` | | Media cache | `$CLAWDBOT_STATE_DIR/media/` | | Credentials | `$CLAWDBOT_STATE_DIR/credentials/` | @@ -640,22 +640,22 @@ clawdbot channels login --verbose ```bash # Supervisor + probe target + config paths -clawdbot gateway status +moltbot gateway status # Include system-level scans (legacy/extra services, port listeners) -clawdbot gateway status --deep +moltbot gateway status --deep # Is the gateway reachable? -clawdbot health --json +moltbot health --json # If it fails, rerun with connection details: -clawdbot health --verbose +moltbot health --verbose # Is something listening on the default port? lsof -nP -iTCP:18789 -sTCP:LISTEN # Recent activity (RPC log tail) -clawdbot logs --follow +moltbot logs --follow # Fallback if RPC is down -tail -20 /tmp/clawdbot/clawdbot-*.log +tail -20 /tmp/moltbot/moltbot-*.log ``` ## Reset Everything @@ -663,23 +663,23 @@ tail -20 /tmp/clawdbot/clawdbot-*.log Nuclear option: ```bash -clawdbot gateway stop +moltbot gateway stop # If you installed a service and want a clean install: -# clawdbot gateway uninstall +# moltbot gateway uninstall trash "${CLAWDBOT_STATE_DIR:-$HOME/.clawdbot}" -clawdbot channels login # re-pair WhatsApp -clawdbot gateway restart # or: clawdbot gateway +moltbot channels login # re-pair WhatsApp +moltbot gateway restart # or: moltbot gateway ``` ⚠️ This loses all sessions and requires re-pairing WhatsApp. ## Getting Help -1. Check logs first: `/tmp/clawdbot/` (default: `clawdbot-YYYY-MM-DD.log`, or your configured `logging.file`) +1. Check logs first: `/tmp/moltbot/` (default: `moltbot-YYYY-MM-DD.log`, or your configured `logging.file`) 2. Search existing issues on GitHub 3. Open a new issue with: - - Clawdbot version + - Moltbot version - Relevant log snippets - Steps to reproduce - Your config (redact secrets!) diff --git a/docs/help/faq.md b/docs/help/faq.md index 554597165..7372a4997 100644 --- a/docs/help/faq.md +++ b/docs/help/faq.md @@ -1,5 +1,5 @@ --- -summary: "Frequently asked questions about Clawdbot setup, configuration, and usage" +summary: "Frequently asked questions about Moltbot setup, configuration, and usage" --- # FAQ @@ -9,7 +9,7 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS, - [Quick start and first-run setup](#quick-start-and-firstrun-setup) - [Im stuck whats the fastest way to get unstuck?](#im-stuck-whats-the-fastest-way-to-get-unstuck) - - [What’s the recommended way to install and set up Clawdbot?](#whats-the-recommended-way-to-install-and-set-up-clawdbot) + - [What’s the recommended way to install and set up Moltbot?](#whats-the-recommended-way-to-install-and-set-up-moltbot) - [How do I open the dashboard after onboarding?](#how-do-i-open-the-dashboard-after-onboarding) - [How do I authenticate the dashboard (token) on localhost vs remote?](#how-do-i-authenticate-the-dashboard-token-on-localhost-vs-remote) - [What runtime do I need?](#what-runtime-do-i-need) @@ -18,16 +18,16 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS, - [It is stuck on "wake up my friend" / onboarding will not hatch. What now?](#it-is-stuck-on-wake-up-my-friend-onboarding-will-not-hatch-what-now) - [Can I migrate my setup to a new machine (Mac mini) without redoing onboarding?](#can-i-migrate-my-setup-to-a-new-machine-mac-mini-without-redoing-onboarding) - [Where do I see what’s new in the latest version?](#where-do-i-see-whats-new-in-the-latest-version) - - [I can't access docs.clawd.bot (SSL error). What now?](#i-cant-access-docsclawdbot-ssl-error-what-now) + - [I can't access docs.molt.bot (SSL error). What now?](#i-cant-access-docsmoltbot-ssl-error-what-now) - [What’s the difference between stable and beta?](#whats-the-difference-between-stable-and-beta) - [How do I install the beta version, and what’s the difference between beta and dev?](#how-do-i-install-the-beta-version-and-whats-the-difference-between-beta-and-dev) - [How do I try the latest bits?](#how-do-i-try-the-latest-bits) - [How long does install and onboarding usually take?](#how-long-does-install-and-onboarding-usually-take) - [Installer stuck? How do I get more feedback?](#installer-stuck-how-do-i-get-more-feedback) - - [Windows install says git not found or clawdbot not recognized](#windows-install-says-git-not-found-or-clawdbot-not-recognized) + - [Windows install says git not found or moltbot not recognized](#windows-install-says-git-not-found-or-moltbot-not-recognized) - [The docs didn’t answer my question - how do I get a better answer?](#the-docs-didnt-answer-my-question-how-do-i-get-a-better-answer) - - [How do I install Clawdbot on Linux?](#how-do-i-install-clawdbot-on-linux) - - [How do I install Clawdbot on a VPS?](#how-do-i-install-clawdbot-on-a-vps) + - [How do I install Moltbot on Linux?](#how-do-i-install-moltbot-on-linux) + - [How do I install Moltbot on a VPS?](#how-do-i-install-moltbot-on-a-vps) - [Where are the cloud/VPS install guides?](#where-are-the-cloudvps-install-guides) - [Can I ask Clawd to update itself?](#can-i-ask-clawd-to-update-itself) - [What does the onboarding wizard actually do?](#what-does-the-onboarding-wizard-actually-do) @@ -45,24 +45,24 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS, - [How do I keep hosted model traffic in a specific region?](#how-do-i-keep-hosted-model-traffic-in-a-specific-region) - [Do I have to buy a Mac Mini to install this?](#do-i-have-to-buy-a-mac-mini-to-install-this) - [Do I need a Mac mini for iMessage support?](#do-i-need-a-mac-mini-for-imessage-support) - - [If I buy a Mac mini to run Clawdbot, can I connect it to my MacBook Pro?](#if-i-buy-a-mac-mini-to-run-clawdbot-can-i-connect-it-to-my-macbook-pro) + - [If I buy a Mac mini to run Moltbot, can I connect it to my MacBook Pro?](#if-i-buy-a-mac-mini-to-run-moltbot-can-i-connect-it-to-my-macbook-pro) - [Can I use Bun?](#can-i-use-bun) - [Telegram: what goes in `allowFrom`?](#telegram-what-goes-in-allowfrom) - - [Can multiple people use one WhatsApp number with different Clawdbots?](#can-multiple-people-use-one-whatsapp-number-with-different-clawdbots) + - [Can multiple people use one WhatsApp number with different Moltbots?](#can-multiple-people-use-one-whatsapp-number-with-different-moltbots) - [Can I run a "fast chat" agent and an "Opus for coding" agent?](#can-i-run-a-fast-chat-agent-and-an-opus-for-coding-agent) - [Does Homebrew work on Linux?](#does-homebrew-work-on-linux) - [What’s the difference between the hackable (git) install and npm install?](#whats-the-difference-between-the-hackable-git-install-and-npm-install) - [Can I switch between npm and git installs later?](#can-i-switch-between-npm-and-git-installs-later) - [Should I run the Gateway on my laptop or a VPS?](#should-i-run-the-gateway-on-my-laptop-or-a-vps) - - [How important is it to run Clawdbot on a dedicated machine?](#how-important-is-it-to-run-clawdbot-on-a-dedicated-machine) + - [How important is it to run Moltbot on a dedicated machine?](#how-important-is-it-to-run-moltbot-on-a-dedicated-machine) - [What are the minimum VPS requirements and recommended OS?](#what-are-the-minimum-vps-requirements-and-recommended-os) - - [Can I run Clawdbot in a VM and what are the requirements](#can-i-run-clawdbot-in-a-vm-and-what-are-the-requirements) -- [What is Clawdbot?](#what-is-clawdbot) - - [What is Clawdbot, in one paragraph?](#what-is-clawdbot-in-one-paragraph) + - [Can I run Moltbot in a VM and what are the requirements](#can-i-run-moltbot-in-a-vm-and-what-are-the-requirements) +- [What is Moltbot?](#what-is-moltbot) + - [What is Moltbot, in one paragraph?](#what-is-moltbot-in-one-paragraph) - [What’s the value proposition?](#whats-the-value-proposition) - [I just set it up what should I do first](#i-just-set-it-up-what-should-i-do-first) - - [What are the top five everyday use cases for Clawdbot](#what-are-the-top-five-everyday-use-cases-for-clawdbot) - - [Can Clawdbot help with lead gen outreach ads and blogs for a SaaS](#can-clawdbot-help-with-lead-gen-outreach-ads-and-blogs-for-a-saas) + - [What are the top five everyday use cases for Moltbot](#what-are-the-top-five-everyday-use-cases-for-moltbot) + - [Can Moltbot help with lead gen outreach ads and blogs for a SaaS](#can-moltbot-help-with-lead-gen-outreach-ads-and-blogs-for-a-saas) - [What are the advantages vs Claude Code for web development?](#what-are-the-advantages-vs-claude-code-for-web-development) - [Skills and automation](#skills-and-automation) - [How do I customize skills without keeping the repo dirty?](#how-do-i-customize-skills-without-keeping-the-repo-dirty) @@ -71,7 +71,7 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS, - [The bot freezes while doing heavy work. How do I offload that?](#the-bot-freezes-while-doing-heavy-work-how-do-i-offload-that) - [Cron or reminders do not fire. What should I check?](#cron-or-reminders-do-not-fire-what-should-i-check) - [How do I install skills on Linux?](#how-do-i-install-skills-on-linux) - - [Can Clawdbot run tasks on a schedule or continuously in the background?](#can-clawdbot-run-tasks-on-a-schedule-or-continuously-in-the-background) + - [Can Moltbot run tasks on a schedule or continuously in the background?](#can-moltbot-run-tasks-on-a-schedule-or-continuously-in-the-background) - [Can I run Apple/macOS-only skills from Linux?](#can-i-run-applemacosonly-skills-from-linux) - [Do you have a Notion or HeyGen integration?](#do-you-have-a-notion-or-heygen-integration) - [How do I install the Chrome extension for browser takeover?](#how-do-i-install-the-chrome-extension-for-browser-takeover) @@ -83,11 +83,11 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS, - [Does memory persist forever? What are the limits?](#does-memory-persist-forever-what-are-the-limits) - [Does semantic memory search require an OpenAI API key?](#does-semantic-memory-search-require-an-openai-api-key) - [Where things live on disk](#where-things-live-on-disk) - - [Is all data used with Clawdbot saved locally?](#is-all-data-used-with-clawdbot-saved-locally) - - [Where does Clawdbot store its data?](#where-does-clawdbot-store-its-data) + - [Is all data used with Moltbot saved locally?](#is-all-data-used-with-moltbot-saved-locally) + - [Where does Moltbot store its data?](#where-does-moltbot-store-its-data) - [Where should AGENTS.md / SOUL.md / USER.md / MEMORY.md live?](#where-should-agentsmd-soulmd-usermd-memorymd-live) - [What’s the recommended backup strategy?](#whats-the-recommended-backup-strategy) - - [How do I completely uninstall Clawdbot?](#how-do-i-completely-uninstall-clawdbot) + - [How do I completely uninstall Moltbot?](#how-do-i-completely-uninstall-moltbot) - [Can agents work outside the workspace?](#can-agents-work-outside-the-workspace) - [I’m in remote mode - where is the session store?](#im-in-remote-mode-where-is-the-session-store) - [Config basics](#config-basics) @@ -98,13 +98,13 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS, - [How do I enable web search (and web fetch)?](#how-do-i-enable-web-search-and-web-fetch) - [config.apply wiped my config. How do I recover and avoid this?](#configapply-wiped-my-config-how-do-i-recover-and-avoid-this) - [How do I run a central Gateway with specialized workers across devices?](#how-do-i-run-a-central-gateway-with-specialized-workers-across-devices) - - [Can the Clawdbot browser run headless?](#can-the-clawdbot-browser-run-headless) + - [Can the Moltbot browser run headless?](#can-the-moltbot-browser-run-headless) - [How do I use Brave for browser control?](#how-do-i-use-brave-for-browser-control) - [Remote gateways + nodes](#remote-gateways-nodes) - [How do commands propagate between Telegram, the gateway, and nodes?](#how-do-commands-propagate-between-telegram-the-gateway-and-nodes) - [How can my agent access my computer if the Gateway is hosted remotely?](#how-can-my-agent-access-my-computer-if-the-gateway-is-hosted-remotely) - [Tailscale is connected but I get no replies. What now?](#tailscale-is-connected-but-i-get-no-replies-what-now) - - [Can two Clawdbots talk to each other (local + VPS)?](#can-two-clawdbots-talk-to-each-other-local-vps) + - [Can two Moltbots talk to each other (local + VPS)?](#can-two-moltbots-talk-to-each-other-local-vps) - [Do I need separate VPSes for multiple agents](#do-i-need-separate-vpses-for-multiple-agents) - [Is there a benefit to using a node on my personal laptop instead of SSH from a VPS?](#is-there-a-benefit-to-using-a-node-on-my-personal-laptop-instead-of-ssh-from-a-vps) - [Do nodes run a gateway service?](#do-nodes-run-a-gateway-service) @@ -114,21 +114,21 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS, - [How do I connect a Mac node to a remote Gateway (Tailscale Serve)?](#how-do-i-connect-a-mac-node-to-a-remote-gateway-tailscale-serve) - [Should I install on a second laptop or just add a node?](#should-i-install-on-a-second-laptop-or-just-add-a-node) - [Env vars and .env loading](#env-vars-and-env-loading) - - [How does Clawdbot load environment variables?](#how-does-clawdbot-load-environment-variables) + - [How does Moltbot load environment variables?](#how-does-moltbot-load-environment-variables) - [“I started the Gateway via the service and my env vars disappeared.” What now?](#i-started-the-gateway-via-the-service-and-my-env-vars-disappeared-what-now) - [I set `COPILOT_GITHUB_TOKEN`, but models status shows “Shell env: off.” Why?](#i-set-copilotgithubtoken-but-models-status-shows-shell-env-off-why) - [Sessions & multiple chats](#sessions-multiple-chats) - [How do I start a fresh conversation?](#how-do-i-start-a-fresh-conversation) - [Do sessions reset automatically if I never send `/new`?](#do-sessions-reset-automatically-if-i-never-send-new) - - [Is there a way to make a team of Clawdbots one CEO and many agents](#is-there-a-way-to-make-a-team-of-clawdbots-one-ceo-and-many-agents) + - [Is there a way to make a team of Moltbots one CEO and many agents](#is-there-a-way-to-make-a-team-of-moltbots-one-ceo-and-many-agents) - [Why did context get truncated mid-task? How do I prevent it?](#why-did-context-get-truncated-midtask-how-do-i-prevent-it) - - [How do I completely reset Clawdbot but keep it installed?](#how-do-i-completely-reset-clawdbot-but-keep-it-installed) + - [How do I completely reset Moltbot but keep it installed?](#how-do-i-completely-reset-moltbot-but-keep-it-installed) - [I’m getting “context too large” errors - how do I reset or compact?](#im-getting-context-too-large-errors-how-do-i-reset-or-compact) - [Why am I seeing “LLM request rejected: messages.N.content.X.tool_use.input: Field required”?](#why-am-i-seeing-llm-request-rejected-messagesncontentxtooluseinput-field-required) - [Why am I getting heartbeat messages every 30 minutes?](#why-am-i-getting-heartbeat-messages-every-30-minutes) - [Do I need to add a “bot account” to a WhatsApp group?](#do-i-need-to-add-a-bot-account-to-a-whatsapp-group) - [How do I get the JID of a WhatsApp group?](#how-do-i-get-the-jid-of-a-whatsapp-group) - - [Why doesn’t Clawdbot reply in a group?](#why-doesnt-clawdbot-reply-in-a-group) + - [Why doesn’t Moltbot reply in a group?](#why-doesnt-moltbot-reply-in-a-group) - [Do groups/threads share context with DMs?](#do-groupsthreads-share-context-with-dms) - [How many workspaces and agents can I create?](#how-many-workspaces-and-agents-can-i-create) - [Can I run multiple bots or chats at the same time (Slack), and how should I set that up?](#can-i-run-multiple-bots-or-chats-at-the-same-time-slack-and-how-should-i-set-that-up) @@ -158,10 +158,10 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS, - [OAuth vs API key: what’s the difference?](#oauth-vs-api-key-whats-the-difference) - [Gateway: ports, “already running”, and remote mode](#gateway-ports-already-running-and-remote-mode) - [What port does the Gateway use?](#what-port-does-the-gateway-use) - - [Why does `clawdbot gateway status` say `Runtime: running` but `RPC probe: failed`?](#why-does-clawdbot-gateway-status-say-runtime-running-but-rpc-probe-failed) - - [Why does `clawdbot gateway status` show `Config (cli)` and `Config (service)` different?](#why-does-clawdbot-gateway-status-show-config-cli-and-config-service-different) + - [Why does `moltbot gateway status` say `Runtime: running` but `RPC probe: failed`?](#why-does-moltbot-gateway-status-say-runtime-running-but-rpc-probe-failed) + - [Why does `moltbot gateway status` show `Config (cli)` and `Config (service)` different?](#why-does-moltbot-gateway-status-show-config-cli-and-config-service-different) - [What does “another gateway instance is already listening” mean?](#what-does-another-gateway-instance-is-already-listening-mean) - - [How do I run Clawdbot in remote mode (client connects to a Gateway elsewhere)?](#how-do-i-run-clawdbot-in-remote-mode-client-connects-to-a-gateway-elsewhere) + - [How do I run Moltbot in remote mode (client connects to a Gateway elsewhere)?](#how-do-i-run-moltbot-in-remote-mode-client-connects-to-a-gateway-elsewhere) - [The Control UI says “unauthorized” (or keeps reconnecting). What now?](#the-control-ui-says-unauthorized-or-keeps-reconnecting-what-now) - [I set `gateway.bind: "tailnet"` but it can’t bind / nothing listens](#i-set-gatewaybind-tailnet-but-it-cant-bind-nothing-listens) - [Can I run multiple Gateways on the same host?](#can-i-run-multiple-gateways-on-the-same-host) @@ -169,18 +169,18 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS, - [Logging and debugging](#logging-and-debugging) - [Where are logs?](#where-are-logs) - [How do I start/stop/restart the Gateway service?](#how-do-i-startstoprestart-the-gateway-service) - - [I closed my terminal on Windows - how do I restart Clawdbot?](#i-closed-my-terminal-on-windows-how-do-i-restart-clawdbot) + - [I closed my terminal on Windows - how do I restart Moltbot?](#i-closed-my-terminal-on-windows-how-do-i-restart-moltbot) - [The Gateway is up but replies never arrive. What should I check?](#the-gateway-is-up-but-replies-never-arrive-what-should-i-check) - ["Disconnected from gateway: no reason" - what now?](#disconnected-from-gateway-no-reason-what-now) - [Telegram setMyCommands fails with network errors. What should I check?](#telegram-setmycommands-fails-with-network-errors-what-should-i-check) - [TUI shows no output. What should I check?](#tui-shows-no-output-what-should-i-check) - [How do I completely stop then start the Gateway?](#how-do-i-completely-stop-then-start-the-gateway) - - [ELI5: `clawdbot gateway restart` vs `clawdbot gateway`](#eli5-clawdbot-gateway-restart-vs-clawdbot-gateway) + - [ELI5: `moltbot gateway restart` vs `moltbot gateway`](#eli5-moltbot-gateway-restart-vs-moltbot-gateway) - [What’s the fastest way to get more details when something fails?](#whats-the-fastest-way-to-get-more-details-when-something-fails) - [Media & attachments](#media-attachments) - [My skill generated an image/PDF, but nothing was sent](#my-skill-generated-an-imagepdf-but-nothing-was-sent) - [Security and access control](#security-and-access-control) - - [Is it safe to expose Clawdbot to inbound DMs?](#is-it-safe-to-expose-clawdbot-to-inbound-dms) + - [Is it safe to expose Moltbot to inbound DMs?](#is-it-safe-to-expose-moltbot-to-inbound-dms) - [Is prompt injection only a concern for public bots?](#is-prompt-injection-only-a-concern-for-public-bots) - [Should my bot have its own email GitHub account or phone number](#should-my-bot-have-its-own-email-github-account-or-phone-number) - [Can I give it autonomy over my text messages and is that safe](#can-i-give-it-autonomy-over-my-text-messages-and-is-that-safe) @@ -197,48 +197,48 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS, 1) **Quick status (first check)** ```bash - clawdbot status + moltbot status ``` Fast local summary: OS + update, gateway/service reachability, agents/sessions, provider config + runtime issues (when gateway is reachable). 2) **Pasteable report (safe to share)** ```bash - clawdbot status --all + moltbot status --all ``` Read-only diagnosis with log tail (tokens redacted). 3) **Daemon + port state** ```bash - clawdbot gateway status + moltbot gateway status ``` Shows supervisor runtime vs RPC reachability, the probe target URL, and which config the service likely used. 4) **Deep probes** ```bash - clawdbot status --deep + moltbot status --deep ``` Runs gateway health checks + provider probes (requires a reachable gateway). See [Health](/gateway/health). 5) **Tail the latest log** ```bash - clawdbot logs --follow + moltbot logs --follow ``` If RPC is down, fall back to: ```bash - tail -f "$(ls -t /tmp/clawdbot/clawdbot-*.log | head -1)" + tail -f "$(ls -t /tmp/moltbot/moltbot-*.log | head -1)" ``` File logs are separate from service logs; see [Logging](/logging) and [Troubleshooting](/gateway/troubleshooting). 6) **Run the doctor (repairs)** ```bash - clawdbot doctor + moltbot doctor ``` Repairs/migrates config/state + runs health checks. See [Doctor](/gateway/doctor). 7) **Gateway snapshot** ```bash - clawdbot health --json - clawdbot health --verbose # shows the target URL + config path on errors + moltbot health --json + moltbot health --verbose # shows the target URL + config path on errors ``` Asks the running gateway for a full snapshot (WS-only). See [Health](/gateway/health). @@ -258,10 +258,10 @@ setup (PATH, services, permissions, auth files). Give them the **full source che the hackable (git) install: ```bash -curl -fsSL https://clawd.bot/install.sh | bash -s -- --install-method git +curl -fsSL https://molt.bot/install.sh | bash -s -- --install-method git ``` -This installs Clawdbot **from a git checkout**, so the agent can read the code + docs and +This installs Moltbot **from a git checkout**, so the agent can read the code + docs and reason about the exact version you are running. You can always switch back to stable later by re-running the installer without `--install-method git`. @@ -269,35 +269,35 @@ Tip: ask the agent to **plan and supervise** the fix (step-by-step), then execut necessary commands. That keeps changes small and easier to audit. If you discover a real bug or fix, please file a GitHub issue or send a PR: -https://github.com/clawdbot/clawdbot/issues -https://github.com/clawdbot/clawdbot/pulls +https://github.com/moltbot/moltbot/issues +https://github.com/moltbot/moltbot/pulls Start with these commands (share outputs when asking for help): ```bash -clawdbot status -clawdbot models status -clawdbot doctor +moltbot status +moltbot models status +moltbot doctor ``` What they do: -- `clawdbot status`: quick snapshot of gateway/agent health + basic config. -- `clawdbot models status`: checks provider auth + model availability. -- `clawdbot doctor`: validates and repairs common config/state issues. +- `moltbot status`: quick snapshot of gateway/agent health + basic config. +- `moltbot models status`: checks provider auth + model availability. +- `moltbot doctor`: validates and repairs common config/state issues. -Other useful CLI checks: `clawdbot status --all`, `clawdbot logs --follow`, -`clawdbot gateway status`, `clawdbot health --verbose`. +Other useful CLI checks: `moltbot status --all`, `moltbot logs --follow`, +`moltbot gateway status`, `moltbot health --verbose`. Quick debug loop: [First 60 seconds if something's broken](#first-60-seconds-if-somethings-broken). Install docs: [Install](/install), [Installer flags](/install/installer), [Updating](/install/updating). -### Whats the recommended way to install and set up Clawdbot +### Whats the recommended way to install and set up Moltbot The repo recommends running from source and using the onboarding wizard: ```bash -curl -fsSL https://clawd.bot/install.sh | bash -clawdbot onboard --install-daemon +curl -fsSL https://molt.bot/install.sh | bash +moltbot onboard --install-daemon ``` The wizard can also build UI assets automatically. After onboarding, you typically run the Gateway on port **18789**. @@ -305,15 +305,15 @@ The wizard can also build UI assets automatically. After onboarding, you typical From source (contributors/dev): ```bash -git clone https://github.com/clawdbot/clawdbot.git -cd clawdbot +git clone https://github.com/moltbot/moltbot.git +cd moltbot pnpm install pnpm build pnpm ui:build # auto-installs UI deps on first run -clawdbot onboard +moltbot onboard ``` -If you don’t have a global install yet, run it via `pnpm clawdbot onboard`. +If you don’t have a global install yet, run it via `pnpm moltbot onboard`. ### How do I open the dashboard after onboarding @@ -323,13 +323,13 @@ The wizard now opens your browser with a tokenized dashboard URL right after onb **Localhost (same machine):** - Open `http://127.0.0.1:18789/`. -- If it asks for auth, run `clawdbot dashboard` and use the tokenized link (`?token=...`). +- If it asks for auth, run `moltbot dashboard` and use the tokenized link (`?token=...`). - The token is the same value as `gateway.auth.token` (or `CLAWDBOT_GATEWAY_TOKEN`) and is stored by the UI after first load. **Not on localhost:** -- **Tailscale Serve** (recommended): keep bind loopback, run `clawdbot gateway --tailscale serve`, open `https:///`. If `gateway.auth.allowTailscale` is `true`, identity headers satisfy auth (no token). -- **Tailnet bind**: run `clawdbot gateway --bind tailnet --token ""`, open `http://:18789/`, paste token in dashboard settings. -- **SSH tunnel**: `ssh -N -L 18789:127.0.0.1:18789 user@host` then open `http://127.0.0.1:18789/?token=...` from `clawdbot dashboard`. +- **Tailscale Serve** (recommended): keep bind loopback, run `moltbot gateway --tailscale serve`, open `https:///`. If `gateway.auth.allowTailscale` is `true`, identity headers satisfy auth (no token). +- **Tailnet bind**: run `moltbot gateway --bind tailnet --token ""`, open `http://:18789/`, paste token in dashboard settings. +- **SSH tunnel**: `ssh -N -L 18789:127.0.0.1:18789 user@host` then open `http://127.0.0.1:18789/?token=...` from `moltbot dashboard`. See [Dashboard](/web/dashboard) and [Web surfaces](/web) for bind modes and auth details. @@ -367,17 +367,17 @@ and tokens stay at 0, the agent never ran. 1) Restart the Gateway: ```bash -clawdbot gateway restart +moltbot gateway restart ``` 2) Check status + auth: ```bash -clawdbot status -clawdbot models status -clawdbot logs --follow +moltbot status +moltbot models status +moltbot logs --follow ``` 3) If it still hangs, run: ```bash -clawdbot doctor +moltbot doctor ``` If the Gateway is remote, ensure the tunnel/Tailscale connection is up and that the UI @@ -389,10 +389,10 @@ Yes. Copy the **state directory** and **workspace**, then run Doctor once. This keeps your bot “exactly the same” (memory, session history, auth, and channel state) as long as you copy **both** locations: -1) Install Clawdbot on the new machine. +1) Install Moltbot on the new machine. 2) Copy `$CLAWDBOT_STATE_DIR` (default: `~/.clawdbot`) from the old machine. 3) Copy your workspace (default: `~/clawd`). -4) Run `clawdbot doctor` and restart the Gateway service. +4) Run `moltbot doctor` and restart the Gateway service. That preserves config, auth profiles, WhatsApp creds, sessions, and memory. If you’re in remote mode, remember the gateway host owns the session store and workspace. @@ -401,28 +401,28 @@ remote mode, remember the gateway host owns the session store and workspace. up **memory + bootstrap files**, but **not** session history or auth. Those live under `~/.clawdbot/` (for example `~/.clawdbot/agents//sessions/`). -Related: [Migrating](/install/migrating), [Where things live on disk](/help/faq#where-does-clawdbot-store-its-data), +Related: [Migrating](/install/migrating), [Where things live on disk](/help/faq#where-does-moltbot-store-its-data), [Agent workspace](/concepts/agent-workspace), [Doctor](/gateway/doctor), [Remote mode](/gateway/remote). ### Where do I see whats new in the latest version Check the GitHub changelog: -https://github.com/clawdbot/clawdbot/blob/main/CHANGELOG.md +https://github.com/moltbot/moltbot/blob/main/CHANGELOG.md Newest entries are at the top. If the top section is marked **Unreleased**, the next dated section is the latest shipped version. Entries are grouped by **Highlights**, **Changes**, and **Fixes** (plus docs/other sections when needed). -### I cant access docsclawdbot SSL error What now +### I cant access docsmoltbot SSL error What now -Some Comcast/Xfinity connections incorrectly block `docs.clawd.bot` via Xfinity -Advanced Security. Disable it or allowlist `docs.clawd.bot`, then retry. More -detail: [Troubleshooting](/help/troubleshooting#docsclawdbot-shows-an-ssl-error-comcastxfinity). +Some Comcast/Xfinity connections incorrectly block `docs.molt.bot` via Xfinity +Advanced Security. Disable it or allowlist `docs.molt.bot`, then retry. More +detail: [Troubleshooting](/help/troubleshooting#docsmoltbot-shows-an-ssl-error-comcastxfinity). Please help us unblock it by reporting here: https://spa.xfinity.com/check_url_status. If you still can't reach the site, the docs are mirrored on GitHub: -https://github.com/clawdbot/clawdbot/tree/main/docs +https://github.com/moltbot/moltbot/tree/main/docs ### Whats the difference between stable and beta @@ -435,7 +435,7 @@ that same version to `latest`**. That’s why beta and stable can point at the **same version**. See what changed: -https://github.com/clawdbot/clawdbot/blob/main/CHANGELOG.md +https://github.com/moltbot/moltbot/blob/main/CHANGELOG.md ### How do I install the beta version and whats the difference between beta and dev @@ -445,15 +445,15 @@ https://github.com/clawdbot/clawdbot/blob/main/CHANGELOG.md One‑liners (macOS/Linux): ```bash -curl -fsSL --proto '=https' --tlsv1.2 https://clawd.bot/install.sh | bash -s -- --beta +curl -fsSL --proto '=https' --tlsv1.2 https://molt.bot/install.sh | bash -s -- --beta ``` ```bash -curl -fsSL --proto '=https' --tlsv1.2 https://clawd.bot/install.sh | bash -s -- --install-method git +curl -fsSL --proto '=https' --tlsv1.2 https://molt.bot/install.sh | bash -s -- --install-method git ``` Windows installer (PowerShell): -https://clawd.bot/install.ps1 +https://molt.bot/install.ps1 More detail: [Development channels](/install/development-channels) and [Installer flags](/install/installer). @@ -472,20 +472,20 @@ Two options: 1) **Dev channel (git checkout):** ```bash -clawdbot update --channel dev +moltbot update --channel dev ``` This switches to the `main` branch and updates from source. 2) **Hackable install (from the installer site):** ```bash -curl -fsSL https://clawd.bot/install.sh | bash -s -- --install-method git +curl -fsSL https://molt.bot/install.sh | bash -s -- --install-method git ``` That gives you a local repo you can edit, then update via git. If you prefer a clean clone manually, use: ```bash -git clone https://github.com/clawdbot/clawdbot.git -cd clawdbot +git clone https://github.com/moltbot/moltbot.git +cd moltbot pnpm install pnpm build ``` @@ -498,24 +498,24 @@ Docs: [Update](/cli/update), [Development channels](/install/development-channel Re-run the installer with **verbose output**: ```bash -curl -fsSL https://clawd.bot/install.sh | bash -s -- --verbose +curl -fsSL https://molt.bot/install.sh | bash -s -- --verbose ``` Beta install with verbose: ```bash -curl -fsSL https://clawd.bot/install.sh | bash -s -- --beta --verbose +curl -fsSL https://molt.bot/install.sh | bash -s -- --beta --verbose ``` For a hackable (git) install: ```bash -curl -fsSL https://clawd.bot/install.sh | bash -s -- --install-method git --verbose +curl -fsSL https://molt.bot/install.sh | bash -s -- --install-method git --verbose ``` More options: [Installer flags](/install/installer). -### Windows install says git not found or clawdbot not recognized +### Windows install says git not found or moltbot not recognized Two common Windows issues: @@ -523,7 +523,7 @@ Two common Windows issues: - Install **Git for Windows** and make sure `git` is on your PATH. - Close and reopen PowerShell, then re-run the installer. -**2) clawdbot is not recognized after install** +**2) moltbot is not recognized after install** - Your npm global bin folder is not on PATH. - Check the path: ```powershell @@ -541,12 +541,12 @@ Use the **hackable (git) install** so you have the full source and docs locally, your bot (or Claude/Codex) *from that folder* so it can read the repo and answer precisely. ```bash -curl -fsSL https://clawd.bot/install.sh | bash -s -- --install-method git +curl -fsSL https://molt.bot/install.sh | bash -s -- --install-method git ``` More detail: [Install](/install) and [Installer flags](/install/installer). -### How do I install Clawdbot on Linux +### How do I install Moltbot on Linux Short answer: follow the Linux guide, then run the onboarding wizard. @@ -554,7 +554,7 @@ Short answer: follow the Linux guide, then run the onboarding wizard. - Full walkthrough: [Getting Started](/start/getting-started). - Installer + updates: [Install & updates](/install/updating). -### How do I install Clawdbot on a VPS +### How do I install Moltbot on a VPS Any Linux VPS works. Install on the server, then use SSH/Tailscale to reach the Gateway. @@ -590,25 +590,25 @@ can prompt for confirmation. Safer: run updates from a shell as the operator. Use the CLI: ```bash -clawdbot update -clawdbot update status -clawdbot update --channel stable|beta|dev -clawdbot update --tag -clawdbot update --no-restart +moltbot update +moltbot update status +moltbot update --channel stable|beta|dev +moltbot update --tag +moltbot update --no-restart ``` If you must automate from an agent: ```bash -clawdbot update --yes --no-restart -clawdbot gateway restart +moltbot update --yes --no-restart +moltbot gateway restart ``` Docs: [Update](/cli/update), [Updating](/install/updating). ### What does the onboarding wizard actually do -`clawdbot onboard` is the recommended setup path. In **local mode** it walks you through: +`moltbot onboard` is the recommended setup path. In **local mode** it walks you through: - **Model/auth setup** (Anthropic **setup-token** recommended for Claude subscriptions, OpenAI Codex OAuth supported, API keys optional, LM Studio local models supported) - **Workspace** location + bootstrap files @@ -621,7 +621,7 @@ It also warns if your configured model is unknown or missing auth. ### Do I need a Claude or OpenAI subscription to run this -No. You can run Clawdbot with **API keys** (Anthropic/OpenAI/others) or with +No. You can run Moltbot with **API keys** (Anthropic/OpenAI/others) or with **local‑only models** so your data stays on your device. Subscriptions (Claude Pro/Max or OpenAI Codex) are optional ways to authenticate those providers. @@ -640,7 +640,7 @@ If you want the most explicit, supported path, use an Anthropic API key. ### How does Anthropic setuptoken auth work -`claude setup-token` generates a **token string** via the Claude Code CLI (it is not available in the web console). You can run it on **any machine**. Choose **Anthropic token (paste setup-token)** in the wizard or paste it with `clawdbot models auth paste-token --provider anthropic`. The token is stored as an auth profile for the **anthropic** provider and used like an API key (no auto-refresh). More detail: [OAuth](/concepts/oauth). +`claude setup-token` generates a **token string** via the Claude Code CLI (it is not available in the web console). You can run it on **any machine**. Choose **Anthropic token (paste setup-token)** in the wizard or paste it with `moltbot models auth paste-token --provider anthropic`. The token is stored as an auth profile for the **anthropic** provider and used like an API key (no auto-refresh). More detail: [OAuth](/concepts/oauth). ### Where do I find an Anthropic setuptoken @@ -650,11 +650,11 @@ It is **not** in the Anthropic Console. The setup-token is generated by the **Cl claude setup-token ``` -Copy the token it prints, then choose **Anthropic token (paste setup-token)** in the wizard. If you want to run it on the gateway host, use `clawdbot models auth setup-token --provider anthropic`. If you ran `claude setup-token` elsewhere, paste it on the gateway host with `clawdbot models auth paste-token --provider anthropic`. See [Anthropic](/providers/anthropic). +Copy the token it prints, then choose **Anthropic token (paste setup-token)** in the wizard. If you want to run it on the gateway host, use `moltbot models auth setup-token --provider anthropic`. If you ran `claude setup-token` elsewhere, paste it on the gateway host with `moltbot models auth paste-token --provider anthropic`. See [Anthropic](/providers/anthropic). ### Do you support Claude subscription auth (Claude Pro/Max) -Yes — via **setup-token**. Clawdbot no longer reuses Claude Code CLI OAuth tokens; use a setup-token or an Anthropic API key. Generate the token anywhere and paste it on the gateway host. See [Anthropic](/providers/anthropic) and [OAuth](/concepts/oauth). +Yes — via **setup-token**. Moltbot no longer reuses Claude Code CLI OAuth tokens; use a setup-token or an Anthropic API key. Generate the token anywhere and paste it on the gateway host. See [Anthropic](/providers/anthropic) and [OAuth](/concepts/oauth). Note: Claude subscription access is governed by Anthropic’s terms. For production or multi‑user workloads, API keys are usually the safer choice. @@ -665,7 +665,7 @@ use a **Claude subscription** (setup‑token or Claude Code OAuth), wait for the reset or upgrade your plan. If you use an **Anthropic API key**, check the Anthropic Console for usage/billing and raise limits as needed. -Tip: set a **fallback model** so Clawdbot can keep replying while a provider is rate‑limited. +Tip: set a **fallback model** so Moltbot can keep replying while a provider is rate‑limited. See [Models](/cli/models) and [OAuth](/concepts/oauth). ### Is AWS Bedrock supported @@ -674,28 +674,28 @@ Yes - via pi‑ai’s **Amazon Bedrock (Converse)** provider with **manual confi ### How does Codex auth work -Clawdbot supports **OpenAI Code (Codex)** via OAuth (ChatGPT sign-in). The wizard can run the OAuth flow and will set the default model to `openai-codex/gpt-5.2` when appropriate. See [Model providers](/concepts/model-providers) and [Wizard](/start/wizard). +Moltbot supports **OpenAI Code (Codex)** via OAuth (ChatGPT sign-in). The wizard can run the OAuth flow and will set the default model to `openai-codex/gpt-5.2` when appropriate. See [Model providers](/concepts/model-providers) and [Wizard](/start/wizard). ### Do you support OpenAI subscription auth Codex OAuth -Yes. Clawdbot fully supports **OpenAI Code (Codex) subscription OAuth**. The onboarding wizard +Yes. Moltbot fully supports **OpenAI Code (Codex) subscription OAuth**. The onboarding wizard can run the OAuth flow for you. See [OAuth](/concepts/oauth), [Model providers](/concepts/model-providers), and [Wizard](/start/wizard). ### How do I set up Gemini CLI OAuth -Gemini CLI uses a **plugin auth flow**, not a client id or secret in `clawdbot.json`. +Gemini CLI uses a **plugin auth flow**, not a client id or secret in `moltbot.json`. Steps: -1) Enable the plugin: `clawdbot plugins enable google-gemini-cli-auth` -2) Login: `clawdbot models auth login --provider google-gemini-cli --set-default` +1) Enable the plugin: `moltbot plugins enable google-gemini-cli-auth` +2) Login: `moltbot models auth login --provider google-gemini-cli --set-default` This stores OAuth tokens in auth profiles on the gateway host. Details: [Model providers](/concepts/model-providers). ### Is a local model OK for casual chats -Usually no. Clawdbot needs large context + strong safety; small cards truncate and leak. If you must, run the **largest** MiniMax M2.1 build you can locally (LM Studio) and see [/gateway/local-models](/gateway/local-models). Smaller/quantized models increase prompt-injection risk - see [Security](/gateway/security). +Usually no. Moltbot needs large context + strong safety; small cards truncate and leak. If you must, run the **largest** MiniMax M2.1 build you can locally (LM Studio) and see [/gateway/local-models](/gateway/local-models). Smaller/quantized models increase prompt-injection risk - see [Security](/gateway/security). ### How do I keep hosted model traffic in a specific region @@ -703,7 +703,7 @@ Pick region-pinned endpoints. OpenRouter exposes US-hosted options for MiniMax, ### Do I have to buy a Mac Mini to install this -No. Clawdbot runs on macOS or Linux (Windows via WSL2). A Mac mini is optional - some people +No. Moltbot runs on macOS or Linux (Windows via WSL2). A Mac mini is optional - some people buy one as an always‑on host, but a small VPS, home server, or Raspberry Pi‑class box works too. You only need a Mac **for macOS‑only tools**. For iMessage, you can keep the Gateway on Linux @@ -715,7 +715,7 @@ Docs: [iMessage](/channels/imessage), [Nodes](/nodes), [Mac remote mode](/platfo ### Do I need a Mac mini for iMessage support You need **some macOS device** signed into Messages. It does **not** have to be a Mac mini - -any Mac works. Clawdbot’s iMessage integrations run on macOS (BlueBubbles or `imsg`), while +any Mac works. Moltbot’s iMessage integrations run on macOS (BlueBubbles or `imsg`), while the Gateway can run elsewhere. Common setups: @@ -726,7 +726,7 @@ Common setups: Docs: [iMessage](/channels/imessage), [BlueBubbles](/channels/bluebubbles), [Mac remote mode](/platforms/mac/remote). -### If I buy a Mac mini to run Clawdbot can I connect it to my MacBook Pro +### If I buy a Mac mini to run Moltbot can I connect it to my MacBook Pro Yes. The **Mac mini can run the Gateway**, and your MacBook Pro can connect as a **node** (companion device). Nodes don’t run the Gateway - they provide extra @@ -735,7 +735,7 @@ capabilities like screen/camera/canvas and `system.run` on that device. Common pattern: - Gateway on the Mac mini (always‑on). - MacBook Pro runs the macOS app or a node host and pairs to the Gateway. -- Use `clawdbot nodes status` / `clawdbot nodes list` to see it. +- Use `moltbot nodes status` / `moltbot nodes list` to see it. Docs: [Nodes](/nodes), [Nodes CLI](/cli/nodes). @@ -752,7 +752,7 @@ without WhatsApp/Telegram. `channels.telegram.allowFrom` is **the human sender’s Telegram user ID** (numeric, recommended) or `@username`. It is not the bot username. Safer (no third-party bot): -- DM your bot, then run `clawdbot logs --follow` and read `from.id`. +- DM your bot, then run `moltbot logs --follow` and read `from.id`. Official Bot API: - DM your bot, then call `https://api.telegram.org/bot/getUpdates` and read `message.from.id`. @@ -762,7 +762,7 @@ Third-party (less private): See [/channels/telegram](/channels/telegram#access-control-dms--groups). -### Can multiple people use one WhatsApp number with different Clawdbots +### Can multiple people use one WhatsApp number with different Moltbots Yes, via **multi‑agent routing**. Bind each sender’s WhatsApp **DM** (peer `kind: "dm"`, sender E.164 like `+15551234567`) to a different `agentId`, so each person gets their own workspace and session store. Replies still come from the **same WhatsApp account**, and DM access control (`channels.whatsapp.dmPolicy` / `channels.whatsapp.allowFrom`) is global per WhatsApp account. See [Multi-Agent Routing](/concepts/multi-agent) and [WhatsApp](/channels/whatsapp). @@ -781,7 +781,7 @@ eval "$(/home/linuxbrew/.linuxbrew/bin/brew shellenv)" brew install ``` -If you run Clawdbot via systemd, ensure the service PATH includes `/home/linuxbrew/.linuxbrew/bin` (or your brew prefix) so `brew`-installed tools resolve in non‑login shells. +If you run Moltbot via systemd, ensure the service PATH includes `/home/linuxbrew/.linuxbrew/bin` (or your brew prefix) so `brew`-installed tools resolve in non‑login shells. Recent builds also prepend common user bin dirs on Linux systemd services (for example `~/.local/bin`, `~/.npm-global/bin`, `~/.local/share/pnpm`, `~/.bun/bin`) and honor `PNPM_HOME`, `NPM_CONFIG_PREFIX`, `BUN_INSTALL`, `VOLTA_HOME`, `ASDF_DATA_DIR`, `NVM_DIR`, and `FNM_DIR` when set. ### Whats the difference between the hackable git install and npm install @@ -796,26 +796,26 @@ Docs: [Getting started](/start/getting-started), [Updating](/install/updating). ### Can I switch between npm and git installs later Yes. Install the other flavor, then run Doctor so the gateway service points at the new entrypoint. -This **does not delete your data** - it only changes the Clawdbot code install. Your state +This **does not delete your data** - it only changes the Moltbot code install. Your state (`~/.clawdbot`) and workspace (`~/clawd`) stay untouched. From npm → git: ```bash -git clone https://github.com/clawdbot/clawdbot.git -cd clawdbot +git clone https://github.com/moltbot/moltbot.git +cd moltbot pnpm install pnpm build -clawdbot doctor -clawdbot gateway restart +moltbot doctor +moltbot gateway restart ``` From git → npm: ```bash -npm install -g clawdbot@latest -clawdbot doctor -clawdbot gateway restart +npm install -g moltbot@latest +moltbot doctor +moltbot gateway restart ``` Doctor detects a gateway service entrypoint mismatch and offers to rewrite the service config to match the current install (use `--repair` in automation). @@ -835,11 +835,11 @@ lowest friction and you’re okay with sleep/restarts, run it locally. - **Pros:** always‑on, stable network, no laptop sleep issues, easier to keep running. - **Cons:** often run headless (use screenshots), remote file access only, you must SSH for updates. -**Clawdbot-specific note:** WhatsApp/Telegram/Slack/Mattermost (plugin)/Discord all work fine from a VPS. The only real trade-off is **headless browser** vs a visible window. See [Browser](/tools/browser). +**Moltbot-specific note:** WhatsApp/Telegram/Slack/Mattermost (plugin)/Discord all work fine from a VPS. The only real trade-off is **headless browser** vs a visible window. See [Browser](/tools/browser). **Recommended default:** VPS if you had gateway disconnects before. Local is great when you’re actively using the Mac and want local file access or UI automation with a visible browser. -### How important is it to run Clawdbot on a dedicated machine +### How important is it to run Moltbot on a dedicated machine Not required, but **recommended for reliability and isolation**. @@ -851,7 +851,7 @@ For security guidance, read [Security](/gateway/security). ### What are the minimum VPS requirements and recommended OS -Clawdbot is lightweight. For a basic Gateway + one chat channel: +Moltbot is lightweight. For a basic Gateway + one chat channel: - **Absolute minimum:** 1 vCPU, 1GB RAM, ~500MB disk. - **Recommended:** 1-2 vCPU, 2GB RAM or more for headroom (logs, media, multiple channels). Node tools and browser automation can be resource hungry. @@ -860,7 +860,7 @@ OS: use **Ubuntu LTS** (or any modern Debian/Ubuntu). The Linux install path is Docs: [Linux](/platforms/linux), [VPS hosting](/vps). -### Can I run Clawdbot in a VM and what are the requirements +### Can I run Moltbot in a VM and what are the requirements Yes. Treat a VM the same as a VPS: it needs to be always on, reachable, and have enough RAM for the Gateway and any channels you enable. @@ -874,15 +874,15 @@ If you are on Windows, **WSL2 is the easiest VM style setup** and has the best t compatibility. See [Windows](/platforms/windows), [VPS hosting](/vps). If you are running macOS in a VM, see [macOS VM](/platforms/macos-vm). -## What is Clawdbot? +## What is Moltbot? -### What is Clawdbot in one paragraph +### What is Moltbot in one paragraph -Clawdbot is a personal AI assistant you run on your own devices. It replies on the messaging surfaces you already use (WhatsApp, Telegram, Slack, Mattermost (plugin), Discord, Google Chat, Signal, iMessage, WebChat) and can also do voice + a live Canvas on supported platforms. The **Gateway** is the always-on control plane; the assistant is the product. +Moltbot is a personal AI assistant you run on your own devices. It replies on the messaging surfaces you already use (WhatsApp, Telegram, Slack, Mattermost (plugin), Discord, Google Chat, Signal, iMessage, WebChat) and can also do voice + a live Canvas on supported platforms. The **Gateway** is the always-on control plane; the assistant is the product. ### Whats the value proposition -Clawdbot is not “just a Claude wrapper.” It’s a **local-first control plane** that lets you run a +Moltbot is not “just a Claude wrapper.” It’s a **local-first control plane** that lets you run a capable assistant on **your own hardware**, reachable from the chat apps you already use, with stateful sessions, memory, and tools - without handing control of your workflows to a hosted SaaS. @@ -913,7 +913,7 @@ Good first projects: It can handle large tasks, but it works best when you split them into phases and use sub agents for parallel work. -### What are the top five everyday use cases for Clawdbot +### What are the top five everyday use cases for Moltbot Everyday wins usually look like: - **Personal briefings:** summaries of inbox, calendar, and news you care about. @@ -922,21 +922,21 @@ Everyday wins usually look like: - **Browser automation:** filling forms, collecting data, and repeating web tasks. - **Cross device coordination:** send a task from your phone, let the Gateway run it on a server, and get the result back in chat. -### Can Clawdbot help with lead gen outreach ads and blogs for a SaaS +### Can Moltbot help with lead gen outreach ads and blogs for a SaaS Yes for **research, qualification, and drafting**. It can scan sites, build shortlists, summarize prospects, and write outreach or ad copy drafts. For **outreach or ad runs**, keep a human in the loop. Avoid spam, follow local laws and platform policies, and review anything before it is sent. The safest pattern is to let -Clawdbot draft and you approve. +Moltbot draft and you approve. Docs: [Security](/gateway/security). ### What are the advantages vs Claude Code for web development -Clawdbot is a **personal assistant** and coordination layer, not an IDE replacement. Use -Claude Code or Codex for the fastest direct coding loop inside a repo. Use Clawdbot when you +Moltbot is a **personal assistant** and coordination layer, not an IDE replacement. Use +Claude Code or Codex for the fastest direct coding loop inside a repo. Use Moltbot when you want durable memory, cross-device access, and tool orchestration. Advantages: @@ -946,17 +946,17 @@ Advantages: - **Always-on Gateway** (run on a VPS, interact from anywhere) - **Nodes** for local browser/screen/camera/exec -Showcase: https://clawd.bot/showcase +Showcase: https://molt.bot/showcase ## Skills and automation ### How do I customize skills without keeping the repo dirty -Use managed overrides instead of editing the repo copy. Put your changes in `~/.clawdbot/skills//SKILL.md` (or add a folder via `skills.load.extraDirs` in `~/.clawdbot/clawdbot.json`). Precedence is `/skills` > `~/.clawdbot/skills` > bundled, so managed overrides win without touching git. Only upstream-worthy edits should live in the repo and go out as PRs. +Use managed overrides instead of editing the repo copy. Put your changes in `~/.clawdbot/skills//SKILL.md` (or add a folder via `skills.load.extraDirs` in `~/.clawdbot/moltbot.json`). Precedence is `/skills` > `~/.clawdbot/skills` > bundled, so managed overrides win without touching git. Only upstream-worthy edits should live in the repo and go out as PRs. ### Can I load skills from a custom folder -Yes. Add extra directories via `skills.load.extraDirs` in `~/.clawdbot/clawdbot.json` (lowest precedence). Default precedence remains: `/skills` → `~/.clawdbot/skills` → bundled → `skills.load.extraDirs`. `clawdhub` installs into `./skills` by default, which Clawdbot treats as `/skills`. +Yes. Add extra directories via `skills.load.extraDirs` in `~/.clawdbot/moltbot.json` (lowest precedence). Default precedence remains: `/skills` → `~/.clawdbot/skills` → bundled → `skills.load.extraDirs`. `clawdhub` installs into `./skills` by default, which Moltbot treats as `/skills`. ### How can I use different models for different tasks @@ -992,8 +992,8 @@ Checklist: Debug: ```bash -clawdbot cron run --force -clawdbot cron runs --id --limit 50 +moltbot cron run --force +moltbot cron runs --id --limit 50 ``` Docs: [Cron jobs](/automation/cron-jobs), [Cron vs Heartbeat](/automation/cron-vs-heartbeat). @@ -1013,7 +1013,7 @@ npm i -g clawdhub pnpm add -g clawdhub ``` -### Can Clawdbot run tasks on a schedule or continuously in the background +### Can Moltbot run tasks on a schedule or continuously in the background Yes. Use the Gateway scheduler: @@ -1026,15 +1026,15 @@ Docs: [Cron jobs](/automation/cron-jobs), [Cron vs Heartbeat](/automation/cron-v **Can I run Apple macOS only skills from Linux** -Not directly. macOS skills are gated by `metadata.clawdbot.os` plus required binaries, and skills only appear in the system prompt when they are eligible on the **Gateway host**. On Linux, `darwin`-only skills (like `imsg`, `apple-notes`, `apple-reminders`) will not load unless you override the gating. +Not directly. macOS skills are gated by `metadata.moltbot.os` plus required binaries, and skills only appear in the system prompt when they are eligible on the **Gateway host**. On Linux, `darwin`-only skills (like `imsg`, `apple-notes`, `apple-reminders`) will not load unless you override the gating. You have three supported patterns: **Option A - run the Gateway on a Mac (simplest).** -Run the Gateway where the macOS binaries exist, then connect from Linux in [remote mode](#how-do-i-run-clawdbot-in-remote-mode-client-connects-to-a-gateway-elsewhere) or over Tailscale. The skills load normally because the Gateway host is macOS. +Run the Gateway where the macOS binaries exist, then connect from Linux in [remote mode](#how-do-i-run-moltbot-in-remote-mode-client-connects-to-a-gateway-elsewhere) or over Tailscale. The skills load normally because the Gateway host is macOS. **Option B - use a macOS node (no SSH).** -Run the Gateway on Linux, pair a macOS node (menubar app), and set **Node Run Commands** to "Always Ask" or "Always Allow" on the Mac. Clawdbot can treat macOS-only skills as eligible when the required binaries exist on the node. The agent runs those skills via the `nodes` tool. If you choose "Always Ask", approving "Always Allow" in the prompt adds that command to the allowlist. +Run the Gateway on Linux, pair a macOS node (menubar app), and set **Node Run Commands** to "Always Ask" or "Always Allow" on the Mac. Moltbot can treat macOS-only skills as eligible when the required binaries exist on the node. The agent runs those skills via the `nodes` tool. If you choose "Always Ask", approving "Always Allow" in the prompt adds that command to the allowlist. **Option C - proxy macOS binaries over SSH (advanced).** Keep the Gateway on Linux, but make the required CLI binaries resolve to SSH wrappers that run on a Mac. Then override the skill to allow Linux so it stays eligible. @@ -1051,12 +1051,12 @@ Keep the Gateway on Linux, but make the required CLI binaries resolve to SSH wra --- name: imsg description: iMessage/SMS CLI for listing chats, history, watch, and sending. - metadata: {"clawdbot":{"os":["darwin","linux"],"requires":{"bins":["imsg"]}}} + metadata: {"moltbot":{"os":["darwin","linux"],"requires":{"bins":["imsg"]}}} --- ``` 4) Start a new session so the skills snapshot refreshes. -For iMessage specifically, you can also point `channels.imessage.cliPath` at an SSH wrapper (Clawdbot only needs stdio). See [iMessage](/channels/imessage). +For iMessage specifically, you can also point `channels.imessage.cliPath` at an SSH wrapper (Moltbot only needs stdio). See [iMessage](/channels/imessage). ### Do you have a Notion or HeyGen integration @@ -1080,15 +1080,15 @@ clawdhub install clawdhub update --all ``` -ClawdHub installs into `./skills` under your current directory (or falls back to your configured Clawdbot workspace); Clawdbot treats that as `/skills` on the next session. For shared skills across agents, place them in `~/.clawdbot/skills//SKILL.md`. Some skills expect binaries installed via Homebrew; on Linux that means Linuxbrew (see the Homebrew Linux FAQ entry above). See [Skills](/tools/skills) and [ClawdHub](/tools/clawdhub). +ClawdHub installs into `./skills` under your current directory (or falls back to your configured Moltbot workspace); Moltbot treats that as `/skills` on the next session. For shared skills across agents, place them in `~/.clawdbot/skills//SKILL.md`. Some skills expect binaries installed via Homebrew; on Linux that means Linuxbrew (see the Homebrew Linux FAQ entry above). See [Skills](/tools/skills) and [ClawdHub](/tools/clawdhub). ### How do I install the Chrome extension for browser takeover Use the built-in installer, then load the unpacked extension in Chrome: ```bash -clawdbot browser extension install -clawdbot browser extension path +moltbot browser extension install +moltbot browser extension path ``` Then Chrome → `chrome://extensions` → enable “Developer mode” → “Load unpacked” → pick that folder. @@ -1121,11 +1121,11 @@ Set `agents.defaults.sandbox.docker.binds` to `["host:path:mode"]` (e.g., `"/hom ### How does memory work -Clawdbot memory is just Markdown files in the agent workspace: +Moltbot memory is just Markdown files in the agent workspace: - Daily notes in `memory/YYYY-MM-DD.md` - Curated long-term notes in `MEMORY.md` (main/private sessions only) -Clawdbot also runs a **silent pre-compaction memory flush** to remind the model +Moltbot also runs a **silent pre-compaction memory flush** to remind the model to write durable notes before auto-compaction. This only runs when the workspace is writable (read-only sandboxes skip it). See [Memory](/concepts/memory). @@ -1147,11 +1147,11 @@ does **not** grant embeddings access, so **signing in with Codex (OAuth or the Codex CLI login)** does not help for semantic memory search. OpenAI embeddings still need a real API key (`OPENAI_API_KEY` or `models.providers.openai.apiKey`). -If you don’t set a provider explicitly, Clawdbot auto-selects a provider when it +If you don’t set a provider explicitly, Moltbot auto-selects a provider when it can resolve an API key (auth profiles, `models.providers.*.apiKey`, or env vars). It prefers OpenAI if an OpenAI key resolves, otherwise Gemini if a Gemini key resolves. If neither key is available, memory search stays disabled until you -configure it. If you have a local model path configured and present, Clawdbot +configure it. If you have a local model path configured and present, Moltbot prefers `local`. If you’d rather stay local, set `memorySearch.provider = "local"` (and optionally @@ -1171,9 +1171,9 @@ Docs: [Memory](/concepts/memory), [Context](/concepts/context). ## Where things live on disk -### Is all data used with Clawdbot saved locally +### Is all data used with Moltbot saved locally -No - **Clawdbot’s state is local**, but **external services still see what you send them**. +No - **Moltbot’s state is local**, but **external services still see what you send them**. - **Local by default:** sessions, memory files, config, and workspace live on the Gateway host (`~/.clawdbot` + your workspace directory). @@ -1185,13 +1185,13 @@ No - **Clawdbot’s state is local**, but **external services still see what you Related: [Agent workspace](/concepts/agent-workspace), [Memory](/concepts/memory). -### Where does Clawdbot store its data +### Where does Moltbot store its data Everything lives under `$CLAWDBOT_STATE_DIR` (default: `~/.clawdbot`): | Path | Purpose | |------|---------| -| `$CLAWDBOT_STATE_DIR/clawdbot.json` | Main config (JSON5) | +| `$CLAWDBOT_STATE_DIR/moltbot.json` | Main config (JSON5) | | `$CLAWDBOT_STATE_DIR/credentials/oauth.json` | Legacy OAuth import (copied into auth profiles on first use) | | `$CLAWDBOT_STATE_DIR/agents//agent/auth-profiles.json` | Auth profiles (OAuth + API keys) | | `$CLAWDBOT_STATE_DIR/agents//agent/auth.json` | Runtime auth cache (managed automatically) | @@ -1200,7 +1200,7 @@ Everything lives under `$CLAWDBOT_STATE_DIR` (default: `~/.clawdbot`): | `$CLAWDBOT_STATE_DIR/agents//sessions/` | Conversation history & state (per agent) | | `$CLAWDBOT_STATE_DIR/agents//sessions/sessions.json` | Session metadata (per agent) | -Legacy single‑agent path: `~/.clawdbot/agent/*` (migrated by `clawdbot doctor`). +Legacy single‑agent path: `~/.clawdbot/agent/*` (migrated by `moltbot doctor`). Your **workspace** (AGENTS.md, memory files, skills, etc.) is separate and configured via `agents.defaults.workspace` (default: `~/clawd`). @@ -1242,7 +1242,7 @@ separately (see the migration question above). Docs: [Agent workspace](/concepts/agent-workspace). -### How do I completely uninstall Clawdbot +### How do I completely uninstall Moltbot See the dedicated guide: [Uninstall](/install/uninstall). @@ -1253,7 +1253,7 @@ Relative paths resolve inside the workspace, but absolute paths can access other host locations unless sandboxing is enabled. If you need isolation, use [`agents.defaults.sandbox`](/gateway/sandboxing) or per‑agent sandbox settings. If you want a repo to be the default working directory, point that agent’s -`workspace` to the repo root. The Clawdbot repo is just source code; keep the +`workspace` to the repo root. The Moltbot repo is just source code; keep the workspace separate unless you intentionally want the agent to work inside it. Example (repo as default cwd): @@ -1276,7 +1276,7 @@ Session state is owned by the **gateway host**. If you’re in remote mode, the ### What format is the config Where is it -Clawdbot reads an optional **JSON5** config from `$CLAWDBOT_CONFIG_PATH` (default: `~/.clawdbot/clawdbot.json`): +Moltbot reads an optional **JSON5** config from `$CLAWDBOT_CONFIG_PATH` (default: `~/.clawdbot/moltbot.json`): ``` $CLAWDBOT_CONFIG_PATH @@ -1308,7 +1308,7 @@ Notes: The wizard generates a gateway token by default (even on loopback) so **local WS clients must authenticate**. This blocks other local processes from calling the Gateway. Paste the token into the Control UI settings (or your client config) to connect. -If you **really** want open loopback, remove `gateway.auth` from your config. Doctor can generate a token for you any time: `clawdbot doctor --generate-gateway-token`. +If you **really** want open loopback, remove `gateway.auth` from your config. Doctor can generate a token for you any time: `moltbot doctor --generate-gateway-token`. ### Do I have to restart after changing config @@ -1320,7 +1320,7 @@ The Gateway watches the config and supports hot‑reload: ### How do I enable web search and web fetch `web_fetch` works without an API key. `web_search` requires a Brave Search API -key. **Recommended:** run `clawdbot configure --section web` to store it in +key. **Recommended:** run `moltbot configure --section web` to store it in `tools.web.search.apiKey`. Environment alternative: set `BRAVE_API_KEY` for the Gateway process. @@ -1360,7 +1360,7 @@ The common pattern is **one Gateway** (e.g. Raspberry Pi) plus **nodes** and **a Docs: [Nodes](/nodes), [Remote access](/gateway/remote), [Multi-Agent Routing](/concepts/multi-agent), [Sub-agents](/tools/subagents), [TUI](/tui). -### Can the Clawdbot browser run headless +### Can the Moltbot browser run headless Yes. It’s a config option: @@ -1411,8 +1411,8 @@ Typical setup: so it can register as a node. 5) Approve the node on the Gateway: ```bash - clawdbot nodes pending - clawdbot nodes approve + moltbot nodes pending + moltbot nodes approve ``` No separate TCP bridge is required; nodes connect over the Gateway WebSocket. @@ -1425,9 +1425,9 @@ Docs: [Nodes](/nodes), [Gateway protocol](/gateway/protocol), [macOS remote mode ### Tailscale is connected but I get no replies What now Check the basics: -- Gateway is running: `clawdbot gateway status` -- Gateway health: `clawdbot status` -- Channel health: `clawdbot channels status` +- Gateway is running: `moltbot gateway status` +- Gateway health: `moltbot status` +- Channel health: `moltbot channels status` Then verify auth and routing: - If you use Tailscale Serve, make sure `gateway.auth.allowTailscale` is set correctly. @@ -1436,7 +1436,7 @@ Then verify auth and routing: Docs: [Tailscale](/gateway/tailscale), [Remote access](/gateway/remote), [Channels](/channels). -### Can two Clawdbots talk to each other local VPS +### Can two Moltbots talk to each other local VPS Yes. There is no built-in "bot-to-bot" bridge, but you can wire it up in a few reliable ways: @@ -1445,13 +1445,13 @@ reliable ways: Have Bot A send a message to Bot B, then let Bot B reply as usual. **CLI bridge (generic):** run a script that calls the other Gateway with -`clawdbot agent --message ... --deliver`, targeting a chat where the other bot +`moltbot agent --message ... --deliver`, targeting a chat where the other bot listens. If one bot is on a remote VPS, point your CLI at that remote Gateway via SSH/Tailscale (see [Remote access](/gateway/remote)). Example pattern (run from a machine that can reach the target Gateway): ```bash -clawdbot agent --message "Hello from local bot" --deliver --channel telegram --reply-to +moltbot agent --message "Hello from local bot" --deliver --channel telegram --reply-to ``` Tip: add a guardrail so the two bots do not loop endlessly (mention-only, channel @@ -1515,14 +1515,14 @@ Yes. `config.apply` validates + writes the full config and restarts the Gateway else is removed. Recover: -- Restore from backup (git or a copied `~/.clawdbot/clawdbot.json`). -- If you have no backup, re-run `clawdbot doctor` and reconfigure channels/models. +- Restore from backup (git or a copied `~/.clawdbot/moltbot.json`). +- If you have no backup, re-run `moltbot doctor` and reconfigure channels/models. - If this was unexpected, file a bug and include your last known config or any backup. - A local coding agent can often reconstruct a working config from logs or history. Avoid it: -- Use `clawdbot config set` for small changes. -- Use `clawdbot configure` for interactive edits. +- Use `moltbot config set` for small changes. +- Use `moltbot configure` for interactive edits. Docs: [Config](/cli/config), [Configure](/cli/configure), [Doctor](/gateway/doctor). @@ -1556,7 +1556,7 @@ Minimal steps: If you want the Control UI without SSH, use Tailscale Serve on the VPS: ```bash -clawdbot gateway --tailscale serve +moltbot gateway --tailscale serve ``` This keeps the gateway bound to loopback and exposes HTTPS via Tailscale. See [Tailscale](/gateway/tailscale). @@ -1570,17 +1570,17 @@ Recommended setup: The app will tunnel the Gateway port and connect as a node. 3) **Approve the node** on the gateway: ```bash - clawdbot nodes pending - clawdbot nodes approve + moltbot nodes pending + moltbot nodes approve ``` Docs: [Gateway protocol](/gateway/protocol), [Discovery](/gateway/discovery), [macOS remote mode](/platforms/mac/remote). ## Env vars and .env loading -### How does Clawdbot load environment variables +### How does Moltbot load environment variables -Clawdbot reads env vars from the parent process (shell, launchd/systemd, CI, etc.) and additionally loads: +Moltbot reads env vars from the parent process (shell, launchd/systemd, CI, etc.) and additionally loads: - `.env` from the current working directory - a global fallback `.env` from `~/.clawdbot/.env` (aka `$CLAWDBOT_STATE_DIR/.env`) @@ -1623,8 +1623,8 @@ This runs your login shell and imports only missing expected keys (never overrid ### I set COPILOTGITHUBTOKEN but models status shows Shell env off Why -`clawdbot models status` reports whether **shell env import** is enabled. “Shell env: off” -does **not** mean your env vars are missing - it just means Clawdbot won’t load +`moltbot models status` reports whether **shell env import** is enabled. “Shell env: off” +does **not** mean your env vars are missing - it just means Moltbot won’t load your login shell automatically. If the Gateway runs as a service (launchd/systemd), it won’t inherit your shell @@ -1639,7 +1639,7 @@ environment. Fix by doing one of these: Then restart the gateway and recheck: ```bash -clawdbot models status +moltbot models status ``` Copilot tokens are read from `COPILOT_GITHUB_TOKEN` (also `GH_TOKEN` / `GITHUB_TOKEN`). @@ -1665,7 +1665,7 @@ transcripts - it just starts a new session. } ``` -### Is there a way to make a team of Clawdbots one CEO and many agents +### Is there a way to make a team of Moltbots one CEO and many agents Yes, via **multi-agent routing** and **sub-agents**. You can create one coordinator agent and several worker agents with their own workspaces and models. @@ -1689,30 +1689,30 @@ What helps: - Use sub-agents for long or parallel work so the main chat stays smaller. - Pick a model with a larger context window if this happens often. -### How do I completely reset Clawdbot but keep it installed +### How do I completely reset Moltbot but keep it installed Use the reset command: ```bash -clawdbot reset +moltbot reset ``` Non-interactive full reset: ```bash -clawdbot reset --scope full --yes --non-interactive +moltbot reset --scope full --yes --non-interactive ``` Then re-run onboarding: ```bash -clawdbot onboard --install-daemon +moltbot onboard --install-daemon ``` Notes: - The onboarding wizard also offers **Reset** if it sees an existing config. See [Wizard](/start/wizard). - If you used profiles (`--profile` / `CLAWDBOT_PROFILE`), reset each state dir (defaults are `~/.clawdbot-`). -- Dev reset: `clawdbot gateway --dev --reset` (dev-only; wipes dev config + credentials + sessions + workspace). +- Dev reset: `moltbot gateway --dev --reset` (dev-only; wipes dev config + credentials + sessions + workspace). ### Im getting context too large errors how do I reset or compact @@ -1761,14 +1761,14 @@ Heartbeats run every **30m** by default. Tune or disable them: ``` If `HEARTBEAT.md` exists but is effectively empty (only blank lines and markdown -headers like `# Heading`), Clawdbot skips the heartbeat run to save API calls. +headers like `# Heading`), Moltbot skips the heartbeat run to save API calls. If the file is missing, the heartbeat still runs and the model decides what to do. Per-agent overrides use `agents.list[].heartbeat`. Docs: [Heartbeat](/gateway/heartbeat). ### Do I need to add a bot account to a WhatsApp group -No. Clawdbot runs on **your own account**, so if you’re in the group, Clawdbot can see it. +No. Moltbot runs on **your own account**, so if you’re in the group, Moltbot can see it. By default, group replies are blocked until you allow senders (`groupPolicy: "allowlist"`). If you want only **you** to be able to trigger group replies: @@ -1789,7 +1789,7 @@ If you want only **you** to be able to trigger group replies: Option 1 (fastest): tail logs and send a test message in the group: ```bash -clawdbot logs --follow --json +moltbot logs --follow --json ``` Look for `chatId` (or `from`) ending in `@g.us`, like: @@ -1798,12 +1798,12 @@ Look for `chatId` (or `from`) ending in `@g.us`, like: Option 2 (if already configured/allowlisted): list groups from config: ```bash -clawdbot directory groups list --channel whatsapp +moltbot directory groups list --channel whatsapp ``` Docs: [WhatsApp](/channels/whatsapp), [Directory](/cli/directory), [Logs](/cli/logs). -### Why doesnt Clawdbot reply in a group +### Why doesnt Moltbot reply in a group Two common causes: - Mention gating is on (default). You must @mention the bot (or match `mentionPatterns`). @@ -1826,7 +1826,7 @@ No hard limits. Dozens (even hundreds) are fine, but watch for: Tips: - Keep one **active** workspace per agent (`agents.defaults.workspace`). - Prune old sessions (delete JSONL or store entries) if disk grows. -- Use `clawdbot doctor` to spot stray workspaces and profile mismatches. +- Use `moltbot doctor` to spot stray workspaces and profile mismatches. ### Can I run multiple bots or chats at the same time Slack and how should I set that up @@ -1850,13 +1850,13 @@ Docs: [Multi‑Agent Routing](/concepts/multi-agent), [Slack](/channels/slack), ### What is the default model -Clawdbot’s default model is whatever you set as: +Moltbot’s default model is whatever you set as: ``` agents.defaults.model.primary ``` -Models are referenced as `provider/model` (example: `anthropic/claude-opus-4-5`). If you omit the provider, Clawdbot currently assumes `anthropic` as a temporary deprecation fallback - but you should still **explicitly** set `provider/model`. +Models are referenced as `provider/model` (example: `anthropic/claude-opus-4-5`). If you omit the provider, Moltbot currently assumes `anthropic` as a temporary deprecation fallback - but you should still **explicitly** set `provider/model`. ### What model do you recommend @@ -1897,12 +1897,12 @@ Use **model commands** or edit only the **model** fields. Avoid full config repl Safe options: - `/model` in chat (quick, per-session) -- `clawdbot models set ...` (updates just model config) -- `clawdbot configure --section models` (interactive) -- edit `agents.defaults.model` in `~/.clawdbot/clawdbot.json` +- `moltbot models set ...` (updates just model config) +- `moltbot configure --section models` (interactive) +- edit `agents.defaults.model` in `~/.clawdbot/moltbot.json` Avoid `config.apply` with a partial object unless you intend to replace the whole config. -If you did overwrite config, restore from backup or re-run `clawdbot doctor` to repair. +If you did overwrite config, restore from backup or re-run `moltbot doctor` to repair. Docs: [Models](/concepts/models), [Configure](/cli/configure), [Config](/cli/config), [Doctor](/gateway/doctor). @@ -1990,7 +1990,7 @@ Fix checklist: `minimax/MiniMax-M2.1-lightning`. 4) Run: ```bash - clawdbot models list + moltbot models list ``` and pick from the list (or `/model list` in chat). @@ -2031,7 +2031,7 @@ Docs: [Models](/concepts/models), [Multi-Agent Routing](/concepts/multi-agent), ### Are opus sonnet gpt builtin shortcuts -Yes. Clawdbot ships a few default shorthands (only applied when the model exists in `agents.defaults.models`): +Yes. Moltbot ships a few default shorthands (only applied when the model exists in `agents.defaults.models`): - `opus` → `anthropic/claude-opus-4-5` - `sonnet` → `anthropic/claude-sonnet-4-5` @@ -2105,7 +2105,7 @@ stored in: ``` Fix options: -- Run `clawdbot agents add ` and configure auth during the wizard. +- Run `moltbot agents add ` and configure auth during the wizard. - Or copy `auth-profiles.json` from the main agent’s `agentDir` into the new agent’s `agentDir`. Do **not** reuse `agentDir` across agents; it causes auth/session collisions. @@ -2119,7 +2119,7 @@ Failover happens in two stages: 1) **Auth profile rotation** within the same provider. 2) **Model fallback** to the next model in `agents.defaults.model.fallbacks`. -Cooldowns apply to failing profiles (exponential backoff), so Clawdbot can keep responding even when a provider is rate‑limited or temporarily failing. +Cooldowns apply to failing profiles (exponential backoff), so Moltbot can keep responding even when a provider is rate‑limited or temporarily failing. ### What does this error mean @@ -2133,13 +2133,13 @@ It means the system attempted to use the auth profile ID `anthropic:default`, bu - **Confirm where auth profiles live** (new vs legacy paths) - Current: `~/.clawdbot/agents//agent/auth-profiles.json` - - Legacy: `~/.clawdbot/agent/*` (migrated by `clawdbot doctor`) + - Legacy: `~/.clawdbot/agent/*` (migrated by `moltbot doctor`) - **Confirm your env var is loaded by the Gateway** - If you set `ANTHROPIC_API_KEY` in your shell but run the Gateway via systemd/launchd, it may not inherit it. Put it in `~/.clawdbot/.env` or enable `env.shellEnv`. - **Make sure you’re editing the correct agent** - Multi‑agent setups mean there can be multiple `auth-profiles.json` files. - **Sanity‑check model/auth status** - - Use `clawdbot models status` to see configured models and whether providers are authenticated. + - Use `moltbot models status` to see configured models and whether providers are authenticated. **Fix checklist for No credentials found for profile anthropic** @@ -2147,20 +2147,20 @@ This means the run is pinned to an Anthropic auth profile, but the Gateway can’t find it in its auth store. - **Use a setup-token** - - Run `claude setup-token`, then paste it with `clawdbot models auth setup-token --provider anthropic`. - - If the token was created on another machine, use `clawdbot models auth paste-token --provider anthropic`. + - Run `claude setup-token`, then paste it with `moltbot models auth setup-token --provider anthropic`. + - If the token was created on another machine, use `moltbot models auth paste-token --provider anthropic`. - **If you want to use an API key instead** - Put `ANTHROPIC_API_KEY` in `~/.clawdbot/.env` on the **gateway host**. - Clear any pinned order that forces a missing profile: ```bash - clawdbot models auth order clear --provider anthropic + moltbot models auth order clear --provider anthropic ``` - **Confirm you’re running commands on the gateway host** - In remote mode, auth profiles live on the gateway machine, not your laptop. ### Why did it also try Google Gemini and fail -If your model config includes Google Gemini as a fallback (or you switched to a Gemini shorthand), Clawdbot will try it during model fallback. If you haven’t configured Google credentials, you’ll see `No API key found for provider "google"`. +If your model config includes Google Gemini as a fallback (or you switched to a Gemini shorthand), Moltbot will try it during model fallback. If you haven’t configured Google credentials, you’ll see `No API key found for provider "google"`. Fix: either provide Google auth, or remove/avoid Google models in `agents.defaults.model.fallbacks` / aliases so fallback doesn’t route there. @@ -2169,7 +2169,7 @@ Fix: either provide Google auth, or remove/avoid Google models in `agents.defaul Cause: the session history contains **thinking blocks without signatures** (often from an aborted/partial stream). Google Antigravity requires signatures for thinking blocks. -Fix: Clawdbot now strips unsigned thinking blocks for Google Antigravity Claude. If it still appears, start a **new session** or set `/thinking off` for that agent. +Fix: Moltbot now strips unsigned thinking blocks for Google Antigravity Claude. If it still appears, start a **new session** or set `/thinking off` for that agent. ## Auth profiles: what they are and how to manage them @@ -2185,7 +2185,7 @@ An auth profile is a named credential record (OAuth or API key) tied to a provid ### What are typical profile IDs -Clawdbot uses provider‑prefixed IDs like: +Moltbot uses provider‑prefixed IDs like: - `anthropic:default` (common when no email identity exists) - `anthropic:` for OAuth identities @@ -2195,33 +2195,33 @@ Clawdbot uses provider‑prefixed IDs like: Yes. Config supports optional metadata for profiles and an ordering per provider (`auth.order.`). This does **not** store secrets; it maps IDs to provider/mode and sets rotation order. -Clawdbot may temporarily skip a profile if it’s in a short **cooldown** (rate limits/timeouts/auth failures) or a longer **disabled** state (billing/insufficient credits). To inspect this, run `clawdbot models status --json` and check `auth.unusableProfiles`. Tuning: `auth.cooldowns.billingBackoffHours*`. +Moltbot may temporarily skip a profile if it’s in a short **cooldown** (rate limits/timeouts/auth failures) or a longer **disabled** state (billing/insufficient credits). To inspect this, run `moltbot models status --json` and check `auth.unusableProfiles`. Tuning: `auth.cooldowns.billingBackoffHours*`. You can also set a **per-agent** order override (stored in that agent’s `auth-profiles.json`) via the CLI: ```bash # Defaults to the configured default agent (omit --agent) -clawdbot models auth order get --provider anthropic +moltbot models auth order get --provider anthropic # Lock rotation to a single profile (only try this one) -clawdbot models auth order set --provider anthropic anthropic:default +moltbot models auth order set --provider anthropic anthropic:default # Or set an explicit order (fallback within provider) -clawdbot models auth order set --provider anthropic anthropic:work anthropic:default +moltbot models auth order set --provider anthropic anthropic:work anthropic:default # Clear override (fall back to config auth.order / round-robin) -clawdbot models auth order clear --provider anthropic +moltbot models auth order clear --provider anthropic ``` To target a specific agent: ```bash -clawdbot models auth order set --provider anthropic --agent main anthropic:default +moltbot models auth order set --provider anthropic --agent main anthropic:default ``` ### OAuth vs API key whats the difference -Clawdbot supports both: +Moltbot supports both: - **OAuth** often leverages subscription access (where applicable). - **API keys** use pay‑per‑token billing. @@ -2240,32 +2240,32 @@ Precedence: --port > CLAWDBOT_GATEWAY_PORT > gateway.port > default 18789 ``` -### Why does clawdbot gateway status say Runtime running but RPC probe failed +### Why does moltbot gateway status say Runtime running but RPC probe failed Because “running” is the **supervisor’s** view (launchd/systemd/schtasks). The RPC probe is the CLI actually connecting to the gateway WebSocket and calling `status`. -Use `clawdbot gateway status` and trust these lines: +Use `moltbot gateway status` and trust these lines: - `Probe target:` (the URL the probe actually used) - `Listening:` (what’s actually bound on the port) - `Last gateway error:` (common root cause when the process is alive but the port isn’t listening) -### Why does clawdbot gateway status show Config cli and Config service different +### Why does moltbot gateway status show Config cli and Config service different You’re editing one config file while the service is running another (often a `--profile` / `CLAWDBOT_STATE_DIR` mismatch). Fix: ```bash -clawdbot gateway install --force +moltbot gateway install --force ``` Run that from the same `--profile` / environment you want the service to use. ### What does another gateway instance is already listening mean -Clawdbot enforces a runtime lock by binding the WebSocket listener immediately on startup (default `ws://127.0.0.1:18789`). If the bind fails with `EADDRINUSE`, it throws `GatewayLockError` indicating another instance is already listening. +Moltbot enforces a runtime lock by binding the WebSocket listener immediately on startup (default `ws://127.0.0.1:18789`). If the bind fails with `EADDRINUSE`, it throws `GatewayLockError` indicating another instance is already listening. -Fix: stop the other instance, free the port, or run with `clawdbot gateway --port `. +Fix: stop the other instance, free the port, or run with `moltbot gateway --port `. -### How do I run Clawdbot in remote mode client connects to a Gateway elsewhere +### How do I run Moltbot in remote mode client connects to a Gateway elsewhere Set `gateway.mode: "remote"` and point to a remote WebSocket URL, optionally with a token/password: @@ -2283,7 +2283,7 @@ Set `gateway.mode: "remote"` and point to a remote WebSocket URL, optionally wit ``` Notes: -- `clawdbot gateway` only starts when `gateway.mode` is `local` (or you pass the override flag). +- `moltbot gateway` only starts when `gateway.mode` is `local` (or you pass the override flag). - The macOS app watches the config file and switches modes live when these values change. ### The Control UI says unauthorized or keeps reconnecting What now @@ -2291,16 +2291,16 @@ Notes: Your gateway is running with auth enabled (`gateway.auth.*`), but the UI is not sending the matching token/password. Facts (from code): -- The Control UI stores the token in browser localStorage key `clawdbot.control.settings.v1`. +- The Control UI stores the token in browser localStorage key `moltbot.control.settings.v1`. - The UI can import `?token=...` (and/or `?password=...`) once, then strips it from the URL. Fix: -- Fastest: `clawdbot dashboard` (prints + copies tokenized link, tries to open; shows SSH hint if headless). -- If you don’t have a token yet: `clawdbot doctor --generate-gateway-token`. +- Fastest: `moltbot dashboard` (prints + copies tokenized link, tries to open; shows SSH hint if headless). +- If you don’t have a token yet: `moltbot doctor --generate-gateway-token`. - If remote, tunnel first: `ssh -N -L 18789:127.0.0.1:18789 user@host` then open `http://127.0.0.1:18789/?token=...`. - Set `gateway.auth.token` (or `CLAWDBOT_GATEWAY_TOKEN`) on the gateway host. - In the Control UI settings, paste the same token (or refresh with a one-time `?token=...` link). -- Still stuck? Run `clawdbot status --all` and follow [Troubleshooting](/gateway/troubleshooting). See [Dashboard](/web/dashboard) for auth details. +- Still stuck? Run `moltbot status --all` and follow [Troubleshooting](/gateway/troubleshooting). See [Dashboard](/web/dashboard) for auth details. ### I set gatewaybind tailnet but it cant bind nothing listens @@ -2324,11 +2324,11 @@ Yes, but you must isolate: - `gateway.port` (unique ports) Quick setup (recommended): -- Use `clawdbot --profile …` per instance (auto-creates `~/.clawdbot-`). +- Use `moltbot --profile …` per instance (auto-creates `~/.clawdbot-`). - Set a unique `gateway.port` in each profile config (or pass `--port` for manual runs). -- Install a per-profile service: `clawdbot --profile gateway install`. +- Install a per-profile service: `moltbot --profile gateway install`. -Profiles also suffix service names (`com.clawdbot.`, `clawdbot-gateway-.service`, `Clawdbot Gateway ()`). +Profiles also suffix service names (`bot.molt.`; legacy `com.clawdbot.*`, `moltbot-gateway-.service`, `Moltbot Gateway ()`). Full guide: [Multiple gateways](/gateway/multiple-gateways). ### What does invalid handshake code 1008 mean @@ -2349,7 +2349,7 @@ Quick fixes: If you’re using the CLI or TUI, the URL should look like: ``` -clawdbot tui --url ws://:18789 --token +moltbot tui --url ws://:18789 --token ``` Protocol details: [Gateway protocol](/gateway/protocol). @@ -2361,7 +2361,7 @@ Protocol details: [Gateway protocol](/gateway/protocol). File logs (structured): ``` -/tmp/clawdbot/clawdbot-YYYY-MM-DD.log +/tmp/moltbot/moltbot-YYYY-MM-DD.log ``` You can set a stable path via `logging.file`. File log level is controlled by `logging.level`. Console verbosity is controlled by `--verbose` and `logging.consoleLevel`. @@ -2369,13 +2369,13 @@ You can set a stable path via `logging.file`. File log level is controlled by `l Fastest log tail: ```bash -clawdbot logs --follow +moltbot logs --follow ``` Service/supervisor logs (when the gateway runs via launchd/systemd): - macOS: `$CLAWDBOT_STATE_DIR/logs/gateway.log` and `gateway.err.log` (default: `~/.clawdbot/logs/...`; profiles use `~/.clawdbot-/logs/...`) -- Linux: `journalctl --user -u clawdbot-gateway[-].service -n 200 --no-pager` -- Windows: `schtasks /Query /TN "Clawdbot Gateway ()" /V /FO LIST` +- Linux: `journalctl --user -u moltbot-gateway[-].service -n 200 --no-pager` +- Windows: `schtasks /Query /TN "Moltbot Gateway ()" /V /FO LIST` See [Troubleshooting](/gateway/troubleshooting#log-locations) for more. @@ -2384,13 +2384,13 @@ See [Troubleshooting](/gateway/troubleshooting#log-locations) for more. Use the gateway helpers: ```bash -clawdbot gateway status -clawdbot gateway restart +moltbot gateway status +moltbot gateway restart ``` -If you run the gateway manually, `clawdbot gateway --force` can reclaim the port. See [Gateway](/gateway). +If you run the gateway manually, `moltbot gateway --force` can reclaim the port. See [Gateway](/gateway). -### I closed my terminal on Windows how do I restart Clawdbot +### I closed my terminal on Windows how do I restart Moltbot There are **two Windows install modes**: @@ -2400,14 +2400,14 @@ Open PowerShell, enter WSL, then restart: ```powershell wsl -clawdbot gateway status -clawdbot gateway restart +moltbot gateway status +moltbot gateway restart ``` If you never installed the service, start it in the foreground: ```bash -clawdbot gateway run +moltbot gateway run ``` **2) Native Windows (not recommended):** the Gateway runs directly in Windows. @@ -2415,14 +2415,14 @@ clawdbot gateway run Open PowerShell and run: ```powershell -clawdbot gateway status -clawdbot gateway restart +moltbot gateway status +moltbot gateway restart ``` If you run it manually (no service), use: ```powershell -clawdbot gateway run +moltbot gateway run ``` Docs: [Windows (WSL2)](/platforms/windows), [Gateway service runbook](/gateway). @@ -2432,10 +2432,10 @@ Docs: [Windows (WSL2)](/platforms/windows), [Gateway service runbook](/gateway). Start with a quick health sweep: ```bash -clawdbot status -clawdbot models status -clawdbot channels status -clawdbot logs --follow +moltbot status +moltbot models status +moltbot channels status +moltbot logs --follow ``` Common causes: @@ -2452,15 +2452,15 @@ Docs: [Channels](/channels), [Troubleshooting](/gateway/troubleshooting), [Remot This usually means the UI lost the WebSocket connection. Check: -1) Is the Gateway running? `clawdbot gateway status` -2) Is the Gateway healthy? `clawdbot status` -3) Does the UI have the right token? `clawdbot dashboard` +1) Is the Gateway running? `moltbot gateway status` +2) Is the Gateway healthy? `moltbot status` +3) Does the UI have the right token? `moltbot dashboard` 4) If remote, is the tunnel/Tailscale link up? Then tail logs: ```bash -clawdbot logs --follow +moltbot logs --follow ``` Docs: [Dashboard](/web/dashboard), [Remote access](/gateway/remote), [Troubleshooting](/gateway/troubleshooting). @@ -2470,8 +2470,8 @@ Docs: [Dashboard](/web/dashboard), [Remote access](/gateway/remote), [Troublesho Start with logs and channel status: ```bash -clawdbot channels status -clawdbot channels logs --channel telegram +moltbot channels status +moltbot channels logs --channel telegram ``` If you are on a VPS or behind a proxy, confirm outbound HTTPS is allowed and DNS works. @@ -2484,9 +2484,9 @@ Docs: [Telegram](/channels/telegram), [Channel troubleshooting](/channels/troubl First confirm the Gateway is reachable and the agent can run: ```bash -clawdbot status -clawdbot models status -clawdbot logs --follow +moltbot status +moltbot models status +moltbot logs --follow ``` In the TUI, use `/status` to see the current state. If you expect replies in a chat @@ -2499,8 +2499,8 @@ Docs: [TUI](/tui), [Slash commands](/tools/slash-commands). If you installed the service: ```bash -clawdbot gateway stop -clawdbot gateway start +moltbot gateway stop +moltbot gateway start ``` This stops/starts the **supervised service** (launchd on macOS, systemd on Linux). @@ -2509,17 +2509,17 @@ Use this when the Gateway runs in the background as a daemon. If you’re running in the foreground, stop with Ctrl‑C, then: ```bash -clawdbot gateway run +moltbot gateway run ``` Docs: [Gateway service runbook](/gateway). -### ELI5 clawdbot gateway restart vs clawdbot gateway +### ELI5 moltbot gateway restart vs moltbot gateway -- `clawdbot gateway restart`: restarts the **background service** (launchd/systemd). -- `clawdbot gateway`: runs the gateway **in the foreground** for this terminal session. +- `moltbot gateway restart`: restarts the **background service** (launchd/systemd). +- `moltbot gateway`: runs the gateway **in the foreground** for this terminal session. -If you installed the service, use the gateway commands. Use `clawdbot gateway` when +If you installed the service, use the gateway commands. Use `moltbot gateway` when you want a one-off, foreground run. ### Whats the fastest way to get more details when something fails @@ -2530,12 +2530,12 @@ Start the Gateway with `--verbose` to get more console detail. Then inspect the ### My skill generated an imagePDF but nothing was sent -Outbound attachments from the agent must include a `MEDIA:` line (on its own line). See [Clawdbot assistant setup](/start/clawd) and [Agent send](/tools/agent-send). +Outbound attachments from the agent must include a `MEDIA:` line (on its own line). See [Moltbot assistant setup](/start/clawd) and [Agent send](/tools/agent-send). CLI sending: ```bash -clawdbot message send --target +15555550123 --message "Here you go" --media /path/to/file.png +moltbot message send --target +15555550123 --message "Here you go" --media /path/to/file.png ``` Also check: @@ -2546,17 +2546,17 @@ See [Images](/nodes/images). ## Security and access control -### Is it safe to expose Clawdbot to inbound DMs +### Is it safe to expose Moltbot to inbound DMs Treat inbound DMs as untrusted input. Defaults are designed to reduce risk: - Default behavior on DM‑capable channels is **pairing**: - Unknown senders receive a pairing code; the bot does not process their message. - - Approve with: `clawdbot pairing approve ` - - Pending requests are capped at **3 per channel**; check `clawdbot pairing list ` if a code didn’t arrive. + - Approve with: `moltbot pairing approve ` + - Pending requests are capped at **3 per channel**; check `moltbot pairing list ` if a code didn’t arrive. - Opening DMs publicly requires explicit opt‑in (`dmPolicy: "open"` and allowlist `"*"`). -Run `clawdbot doctor` to surface risky DM policies. +Run `moltbot doctor` to surface risky DM policies. ### Is prompt injection only a concern for public bots @@ -2608,7 +2608,7 @@ Pairing codes are sent **only** when an unknown sender messages the bot and Check pending requests: ```bash -clawdbot pairing list telegram +moltbot pairing list telegram ``` If you want immediate access, allowlist your sender id or set `dmPolicy: "open"` @@ -2616,18 +2616,18 @@ for that account. ### WhatsApp will it message my contacts How does pairing work -No. Default WhatsApp DM policy is **pairing**. Unknown senders only get a pairing code and their message is **not processed**. Clawdbot only replies to chats it receives or to explicit sends you trigger. +No. Default WhatsApp DM policy is **pairing**. Unknown senders only get a pairing code and their message is **not processed**. Moltbot only replies to chats it receives or to explicit sends you trigger. Approve pairing with: ```bash -clawdbot pairing approve whatsapp +moltbot pairing approve whatsapp ``` List pending requests: ```bash -clawdbot pairing list whatsapp +moltbot pairing list whatsapp ``` Wizard phone number prompt: it’s used to set your **allowlist/owner** so your own DMs are permitted. It’s not used for auto-sending. If you run on your personal WhatsApp number, use that number and enable `channels.whatsapp.selfChatMode`. @@ -2678,7 +2678,7 @@ Most commands must be sent as a **standalone** message that starts with `/`, but ### How do I send a Discord message from Telegram Crosscontext messaging denied -Clawdbot blocks **cross‑provider** messaging by default. If a tool call is bound +Moltbot blocks **cross‑provider** messaging by default. If a tool call is bound to Telegram, it won’t send to Discord unless you explicitly allow it. Enable cross‑provider messaging for the agent: @@ -2719,8 +2719,8 @@ You can add options like `debounce:2s cap:25 drop:summarize` for followup modes. **Q: “What’s the default model for Anthropic with an API key?”** -**A:** In Clawdbot, credentials and model selection are separate. Setting `ANTHROPIC_API_KEY` (or storing an Anthropic API key in auth profiles) enables authentication, but the actual default model is whatever you configure in `agents.defaults.model.primary` (for example, `anthropic/claude-sonnet-4-5` or `anthropic/claude-opus-4-5`). If you see `No credentials found for profile "anthropic:default"`, it means the Gateway couldn’t find Anthropic credentials in the expected `auth-profiles.json` for the agent that’s running. +**A:** In Moltbot, credentials and model selection are separate. Setting `ANTHROPIC_API_KEY` (or storing an Anthropic API key in auth profiles) enables authentication, but the actual default model is whatever you configure in `agents.defaults.model.primary` (for example, `anthropic/claude-sonnet-4-5` or `anthropic/claude-opus-4-5`). If you see `No credentials found for profile "anthropic:default"`, it means the Gateway couldn’t find Anthropic credentials in the expected `auth-profiles.json` for the agent that’s running. --- -Still stuck? Ask in [Discord](https://discord.com/invite/clawd) or open a [GitHub discussion](https://github.com/clawdbot/clawdbot/discussions). +Still stuck? Ask in [Discord](https://discord.com/invite/clawd) or open a [GitHub discussion](https://github.com/moltbot/moltbot/discussions). diff --git a/docs/help/troubleshooting.md b/docs/help/troubleshooting.md index 4a7d2ced3..e681edd9d 100644 --- a/docs/help/troubleshooting.md +++ b/docs/help/troubleshooting.md @@ -12,22 +12,22 @@ read_when: Run these in order: ```bash -clawdbot status -clawdbot status --all -clawdbot gateway probe -clawdbot logs --follow -clawdbot doctor +moltbot status +moltbot status --all +moltbot gateway probe +moltbot logs --follow +moltbot doctor ``` If the gateway is reachable, deep probes: ```bash -clawdbot status --deep +moltbot status --deep ``` ## Common “it broke” cases -### `clawdbot: command not found` +### `moltbot: command not found` Almost always a Node/npm PATH issue. Start here: @@ -38,13 +38,13 @@ Almost always a Node/npm PATH issue. Start here: Re-run the installer in verbose mode to see the full trace and npm output: ```bash -curl -fsSL https://clawd.bot/install.sh | bash -s -- --verbose +curl -fsSL https://molt.bot/install.sh | bash -s -- --verbose ``` For beta installs: ```bash -curl -fsSL https://clawd.bot/install.sh | bash -s -- --beta --verbose +curl -fsSL https://molt.bot/install.sh | bash -s -- --beta --verbose ``` You can also set `CLAWDBOT_VERBOSE=1` instead of the flag. @@ -59,10 +59,10 @@ You can also set `CLAWDBOT_VERBOSE=1` instead of the flag. - [Gateway troubleshooting](/gateway/troubleshooting) - [Control UI](/web/control-ui#insecure-http) -### `docs.clawd.bot` shows an SSL error (Comcast/Xfinity) +### `docs.molt.bot` shows an SSL error (Comcast/Xfinity) -Some Comcast/Xfinity connections block `docs.clawd.bot` via Xfinity Advanced Security. -Disable Advanced Security or add `docs.clawd.bot` to the allowlist, then retry. +Some Comcast/Xfinity connections block `docs.molt.bot` via Xfinity Advanced Security. +Disable Advanced Security or add `docs.molt.bot` to the allowlist, then retry. - Xfinity Advanced Security help: https://www.xfinity.com/support/articles/using-xfinity-xfi-advanced-security - Quick sanity checks: try a mobile hotspot or VPN to confirm it’s ISP-level filtering @@ -82,7 +82,7 @@ Disable Advanced Security or add `docs.clawd.bot` to the allowlist, then retry. This usually means `agents.defaults.models` is configured as an allowlist. When it’s non-empty, only those provider/model keys can be selected. -- Check the allowlist: `clawdbot config get agents.defaults.models` +- Check the allowlist: `moltbot config get agents.defaults.models` - Add the model you want (or clear the allowlist) and retry `/model` - Use `/models` to browse the allowed providers/models @@ -91,7 +91,7 @@ only those provider/model keys can be selected. Paste a safe report: ```bash -clawdbot status --all +moltbot status --all ``` -If you can, include the relevant log tail from `clawdbot logs --follow`. +If you can, include the relevant log tail from `moltbot logs --follow`. diff --git a/docs/hooks.md b/docs/hooks.md index 9870dda88..8576146ba 100644 --- a/docs/hooks.md +++ b/docs/hooks.md @@ -6,14 +6,14 @@ read_when: --- # Hooks -Hooks provide an extensible event-driven system for automating actions in response to agent commands and events. Hooks are automatically discovered from directories and can be managed via CLI commands, similar to how skills work in Clawdbot. +Hooks provide an extensible event-driven system for automating actions in response to agent commands and events. Hooks are automatically discovered from directories and can be managed via CLI commands, similar to how skills work in Moltbot. ## Getting Oriented Hooks are small scripts that run when something happens. There are two kinds: - **Hooks** (this page): run inside the Gateway when agent events fire, like `/new`, `/reset`, `/stop`, or lifecycle events. -- **Webhooks**: external HTTP webhooks that let other systems trigger work in Clawdbot. See [Webhook Hooks](/automation/webhook) or use `clawdbot webhooks` for Gmail helper commands. +- **Webhooks**: external HTTP webhooks that let other systems trigger work in Moltbot. See [Webhook Hooks](/automation/webhook) or use `moltbot webhooks` for Gmail helper commands. Hooks can also be bundled inside plugins; see [Plugins](/plugin#plugin-hooks). @@ -31,13 +31,13 @@ The hooks system allows you to: - Save session context to memory when `/new` is issued - Log all commands for auditing - Trigger custom automations on agent lifecycle events -- Extend Clawdbot's behavior without modifying core code +- Extend Moltbot's behavior without modifying core code ## Getting Started ### Bundled Hooks -Clawdbot ships with four bundled hooks that are automatically discovered: +Moltbot ships with four bundled hooks that are automatically discovered: - **💾 session-memory**: Saves session context to your agent workspace (default `~/clawd/memory/`) when you issue `/new` - **📝 command-logger**: Logs all command events to `~/.clawdbot/logs/commands.log` @@ -47,30 +47,30 @@ Clawdbot ships with four bundled hooks that are automatically discovered: List available hooks: ```bash -clawdbot hooks list +moltbot hooks list ``` Enable a hook: ```bash -clawdbot hooks enable session-memory +moltbot hooks enable session-memory ``` Check hook status: ```bash -clawdbot hooks check +moltbot hooks check ``` Get detailed information: ```bash -clawdbot hooks info session-memory +moltbot hooks info session-memory ``` ### Onboarding -During onboarding (`clawdbot onboard`), you'll be prompted to enable recommended hooks. The wizard automatically discovers eligible hooks and presents them for selection. +During onboarding (`moltbot onboard`), you'll be prompted to enable recommended hooks. The wizard automatically discovers eligible hooks and presents them for selection. ## Hook Discovery @@ -78,7 +78,7 @@ Hooks are automatically discovered from three directories (in order of precedenc 1. **Workspace hooks**: `/hooks/` (per-agent, highest precedence) 2. **Managed hooks**: `~/.clawdbot/hooks/` (user-installed, shared across workspaces) -3. **Bundled hooks**: `/dist/hooks/bundled/` (shipped with Clawdbot) +3. **Bundled hooks**: `/dist/hooks/bundled/` (shipped with Moltbot) Managed hook directories can be either a **single hook** or a **hook pack** (package directory). @@ -92,11 +92,11 @@ my-hook/ ## Hook Packs (npm/archives) -Hook packs are standard npm packages that export one or more hooks via `clawdbot.hooks` in +Hook packs are standard npm packages that export one or more hooks via `moltbot.hooks` in `package.json`. Install them with: ```bash -clawdbot hooks install +moltbot hooks install ``` Example `package.json`: @@ -105,7 +105,7 @@ Example `package.json`: { "name": "@acme/my-hooks", "version": "0.1.0", - "clawdbot": { + "moltbot": { "hooks": ["./hooks/my-hook", "./hooks/other-hook"] } } @@ -124,8 +124,8 @@ The `HOOK.md` file contains metadata in YAML frontmatter plus Markdown documenta --- name: my-hook description: "Short description of what this hook does" -homepage: https://docs.clawd.bot/hooks#my-hook -metadata: {"clawdbot":{"emoji":"🔗","events":["command:new"],"requires":{"bins":["node"]}}} +homepage: https://docs.molt.bot/hooks#my-hook +metadata: {"moltbot":{"emoji":"🔗","events":["command:new"],"requires":{"bins":["node"]}}} --- # My Hook @@ -149,7 +149,7 @@ No configuration needed. ### Metadata Fields -The `metadata.clawdbot` object supports: +The `metadata.moltbot` object supports: - **`emoji`**: Display emoji for CLI (e.g., `"💾"`) - **`events`**: Array of events to listen for (e.g., `["command:new", "command:reset"]`) @@ -209,7 +209,7 @@ Each event includes: senderId?: string, workspaceDir?: string, bootstrapFiles?: WorkspaceBootstrapFile[], - cfg?: ClawdbotConfig + cfg?: MoltbotConfig } } ``` @@ -237,7 +237,7 @@ Triggered when the gateway starts: ### Tool Result Hooks (Plugin API) -These hooks are not event-stream listeners; they let plugins synchronously adjust tool results before Clawdbot persists them. +These hooks are not event-stream listeners; they let plugins synchronously adjust tool results before Moltbot persists them. - **`tool_result_persist`**: transform tool results before they are written to the session transcript. Must be synchronous; return the updated tool result payload or `undefined` to keep it as-is. See [Agent Loop](/concepts/agent-loop). @@ -271,7 +271,7 @@ cd ~/.clawdbot/hooks/my-hook --- name: my-hook description: "Does something useful" -metadata: {"clawdbot":{"emoji":"🎯","events":["command:new"]}} +metadata: {"moltbot":{"emoji":"🎯","events":["command:new"]}} --- # My Custom Hook @@ -300,10 +300,10 @@ export default handler; ```bash # Verify hook is discovered -clawdbot hooks list +moltbot hooks list # Enable it -clawdbot hooks enable my-hook +moltbot hooks enable my-hook # Restart your gateway process (menu bar app restart on macOS, or restart your dev process) @@ -397,46 +397,46 @@ The old config format still works for backwards compatibility: ```bash # List all hooks -clawdbot hooks list +moltbot hooks list # Show only eligible hooks -clawdbot hooks list --eligible +moltbot hooks list --eligible # Verbose output (show missing requirements) -clawdbot hooks list --verbose +moltbot hooks list --verbose # JSON output -clawdbot hooks list --json +moltbot hooks list --json ``` ### Hook Information ```bash # Show detailed info about a hook -clawdbot hooks info session-memory +moltbot hooks info session-memory # JSON output -clawdbot hooks info session-memory --json +moltbot hooks info session-memory --json ``` ### Check Eligibility ```bash # Show eligibility summary -clawdbot hooks check +moltbot hooks check # JSON output -clawdbot hooks check --json +moltbot hooks check --json ``` ### Enable/Disable ```bash # Enable a hook -clawdbot hooks enable session-memory +moltbot hooks enable session-memory # Disable a hook -clawdbot hooks disable command-logger +moltbot hooks disable command-logger ``` ## Bundled Hooks @@ -475,7 +475,7 @@ Saves session context to memory when you issue `/new`. **Enable**: ```bash -clawdbot hooks enable session-memory +moltbot hooks enable session-memory ``` ### command-logger @@ -516,7 +516,7 @@ grep '"action":"new"' ~/.clawdbot/logs/commands.log | jq . **Enable**: ```bash -clawdbot hooks enable command-logger +moltbot hooks enable command-logger ``` ### soul-evil @@ -532,7 +532,7 @@ Swaps injected `SOUL.md` content with `SOUL_EVIL.md` during a purge window or by **Enable**: ```bash -clawdbot hooks enable soul-evil +moltbot hooks enable soul-evil ``` **Config**: @@ -572,7 +572,7 @@ Internal hooks must be enabled for this to run. **Enable**: ```bash -clawdbot hooks enable boot-md +moltbot hooks enable boot-md ``` ## Best Practices @@ -629,13 +629,13 @@ const handler: HookHandler = async (event) => { Specify exact events in metadata when possible: ```yaml -metadata: {"clawdbot":{"events":["command:new"]}} # Specific +metadata: {"moltbot":{"events":["command:new"]}} # Specific ``` Rather than: ```yaml -metadata: {"clawdbot":{"events":["command"]}} # General - more overhead +metadata: {"moltbot":{"events":["command"]}} # General - more overhead ``` ## Debugging @@ -655,7 +655,7 @@ Registered hook: boot-md -> gateway:startup List all discovered hooks: ```bash -clawdbot hooks list --verbose +moltbot hooks list --verbose ``` ### Check Registration @@ -674,7 +674,7 @@ const handler: HookHandler = async (event) => { Check why a hook isn't eligible: ```bash -clawdbot hooks info my-hook +moltbot hooks info my-hook ``` Look for missing requirements in the output. @@ -777,7 +777,7 @@ Session reset 3. List all discovered hooks: ```bash - clawdbot hooks list + moltbot hooks list ``` ### Hook Not Eligible @@ -785,7 +785,7 @@ Session reset Check requirements: ```bash -clawdbot hooks info my-hook +moltbot hooks info my-hook ``` Look for missing: @@ -798,7 +798,7 @@ Look for missing: 1. Verify hook is enabled: ```bash - clawdbot hooks list + moltbot hooks list # Should show ✓ next to enabled hooks ``` @@ -853,7 +853,7 @@ node -e "import('./path/to/handler.ts').then(console.log)" --- name: my-hook description: "My custom hook" - metadata: {"clawdbot":{"emoji":"🎯","events":["command:new"]}} + metadata: {"moltbot":{"emoji":"🎯","events":["command:new"]}} --- # My Hook @@ -877,7 +877,7 @@ node -e "import('./path/to/handler.ts').then(console.log)" 4. Verify and restart your gateway process: ```bash - clawdbot hooks list + moltbot hooks list # Should show: 🎯 my-hook ✓ ``` @@ -891,6 +891,6 @@ node -e "import('./path/to/handler.ts').then(console.log)" ## See Also - [CLI Reference: hooks](/cli/hooks) -- [Bundled Hooks README](https://github.com/clawdbot/clawdbot/tree/main/src/hooks/bundled) +- [Bundled Hooks README](https://github.com/moltbot/moltbot/tree/main/src/hooks/bundled) - [Webhook Hooks](/automation/webhook) - [Configuration](/gateway/configuration#hooks) diff --git a/docs/hooks/soul-evil.md b/docs/hooks/soul-evil.md index 7688afc54..cd489b628 100644 --- a/docs/hooks/soul-evil.md +++ b/docs/hooks/soul-evil.md @@ -14,7 +14,7 @@ a purge window or by random chance. It does **not** modify files on disk. When `agent:bootstrap` runs, the hook can replace the `SOUL.md` content in memory before the system prompt is assembled. If `SOUL_EVIL.md` is missing or empty, -Clawdbot logs a warning and keeps the normal `SOUL.md`. +Moltbot logs a warning and keeps the normal `SOUL.md`. Sub-agent runs do **not** include `SOUL.md` in their bootstrap files, so this hook has no effect on sub-agents. @@ -22,7 +22,7 @@ has no effect on sub-agents. ## Enable ```bash -clawdbot hooks enable soul-evil +moltbot hooks enable soul-evil ``` Then set the config: diff --git a/docs/index.md b/docs/index.md index a5b7dbc51..3d85e0eb0 100644 --- a/docs/index.md +++ b/docs/index.md @@ -1,14 +1,14 @@ --- -summary: "Top-level overview of Clawdbot, features, and purpose" +summary: "Top-level overview of Moltbot, features, and purpose" read_when: - - Introducing Clawdbot to newcomers + - Introducing Moltbot to newcomers --- -# Clawdbot 🦞 +# Moltbot 🦞 > *"EXFOLIATE! EXFOLIATE!"* — A space lobster, probably

    - Clawdbot + Moltbot

    @@ -18,23 +18,23 @@ read_when:

    - GitHub · - Releases · + GitHub · + Releases · Docs · - Clawdbot assistant setup + Moltbot assistant setup

    -Clawdbot bridges WhatsApp (via WhatsApp Web / Baileys), Telegram (Bot API / grammY), Discord (Bot API / channels.discord.js), and iMessage (imsg CLI) to coding agents like [Pi](https://github.com/badlogic/pi-mono). Plugins add Mattermost (Bot API + WebSocket) and more. -Clawdbot also powers [Clawd](https://clawd.me), the space‑lobster assistant. +Moltbot bridges WhatsApp (via WhatsApp Web / Baileys), Telegram (Bot API / grammY), Discord (Bot API / channels.discord.js), and iMessage (imsg CLI) to coding agents like [Pi](https://github.com/badlogic/pi-mono). Plugins add Mattermost (Bot API + WebSocket) and more. +Moltbot also powers [Clawd](https://clawd.me), the space‑lobster assistant. ## Start here - **New install from zero:** [Getting Started](/start/getting-started) -- **Guided setup (recommended):** [Wizard](/start/wizard) (`clawdbot onboard`) +- **Guided setup (recommended):** [Wizard](/start/wizard) (`moltbot onboard`) - **Open the dashboard (local Gateway):** http://127.0.0.1:18789/ (or http://localhost:18789/) If the Gateway is running on the same computer, that link opens the browser Control UI -immediately. If it fails, start the Gateway first: `clawdbot gateway`. +immediately. If it fails, start the Gateway first: `moltbot gateway`. ## Dashboard (browser Control UI) @@ -52,27 +52,27 @@ WhatsApp / Telegram / Discord / iMessage (+ plugins) │ Gateway │ ws://127.0.0.1:18789 (loopback-only) │ (single source) │ │ │ http://:18793 - │ │ /__clawdbot__/canvas/ (Canvas host) + │ │ /__moltbot__/canvas/ (Canvas host) └───────────┬───────────────┘ │ ├─ Pi agent (RPC) - ├─ CLI (clawdbot …) + ├─ CLI (moltbot …) ├─ Chat UI (SwiftUI) - ├─ macOS app (Clawdbot.app) + ├─ macOS app (Moltbot.app) ├─ iOS node via Gateway WS + pairing └─ Android node via Gateway WS + pairing ``` -Most operations flow through the **Gateway** (`clawdbot gateway`), a single long-running process that owns channel connections and the WebSocket control plane. +Most operations flow through the **Gateway** (`moltbot gateway`), a single long-running process that owns channel connections and the WebSocket control plane. ## Network model - **One Gateway per host (recommended)**: it is the only process allowed to own the WhatsApp Web session. If you need a rescue bot or strict isolation, run multiple gateways with isolated profiles and ports; see [Multiple gateways](/gateway/multiple-gateways). - **Loopback-first**: Gateway WS defaults to `ws://127.0.0.1:18789`. - The wizard now generates a gateway token by default (even for loopback). - - For Tailnet access, run `clawdbot gateway --bind tailnet --token ...` (token is required for non-loopback binds). + - For Tailnet access, run `moltbot gateway --bind tailnet --token ...` (token is required for non-loopback binds). - **Nodes**: connect to the Gateway WebSocket (LAN/tailnet/SSH as needed); legacy TCP bridge is deprecated/removed. -- **Canvas host**: HTTP file server on `canvasHost.port` (default `18793`), serving `/__clawdbot__/canvas/` for node WebViews; see [Gateway configuration](/gateway/configuration) (`canvasHost`). +- **Canvas host**: HTTP file server on `canvasHost.port` (default `18793`), serving `/__moltbot__/canvas/` for node WebViews; see [Gateway configuration](/gateway/configuration) (`canvasHost`). - **Remote use**: SSH tunnel or tailnet/VPN; see [Remote access](/gateway/remote) and [Discovery](/gateway/discovery). ## Features (high level) @@ -102,53 +102,53 @@ Runtime requirement: **Node ≥ 22**. ```bash # Recommended: global install (npm/pnpm) -npm install -g clawdbot@latest -# or: pnpm add -g clawdbot@latest +npm install -g moltbot@latest +# or: pnpm add -g moltbot@latest # Onboard + install the service (launchd/systemd user service) -clawdbot onboard --install-daemon +moltbot onboard --install-daemon # Pair WhatsApp Web (shows QR) -clawdbot channels login +moltbot channels login # Gateway runs via the service after onboarding; manual run is still possible: -clawdbot gateway --port 18789 +moltbot gateway --port 18789 ``` -Switching between npm and git installs later is easy: install the other flavor and run `clawdbot doctor` to update the gateway service entrypoint. +Switching between npm and git installs later is easy: install the other flavor and run `moltbot doctor` to update the gateway service entrypoint. From source (development): ```bash -git clone https://github.com/clawdbot/clawdbot.git -cd clawdbot +git clone https://github.com/moltbot/moltbot.git +cd moltbot pnpm install pnpm ui:build # auto-installs UI deps on first run pnpm build -clawdbot onboard --install-daemon +moltbot onboard --install-daemon ``` -If you don’t have a global install yet, run the onboarding step via `pnpm clawdbot ...` from the repo. +If you don’t have a global install yet, run the onboarding step via `pnpm moltbot ...` from the repo. Multi-instance quickstart (optional): ```bash CLAWDBOT_CONFIG_PATH=~/.clawdbot/a.json \ CLAWDBOT_STATE_DIR=~/.clawdbot-a \ -clawdbot gateway --port 19001 +moltbot gateway --port 19001 ``` Send a test message (requires a running Gateway): ```bash -clawdbot message send --target +15555550123 --message "Hello from Clawdbot" +moltbot message send --target +15555550123 --message "Hello from Moltbot" ``` ## Configuration (optional) -Config lives at `~/.clawdbot/clawdbot.json`. +Config lives at `~/.clawdbot/moltbot.json`. -- If you **do nothing**, Clawdbot uses the bundled Pi binary in RPC mode with per-sender sessions. +- If you **do nothing**, Moltbot uses the bundled Pi binary in RPC mode with per-sender sessions. - If you want to lock it down, start with `channels.whatsapp.allowFrom` and (for groups) mention rules. Example: @@ -177,7 +177,7 @@ Example: - [Updating / rollback](/install/updating) - [Pairing (DM + nodes)](/start/pairing) - [Nix mode](/install/nix) - - [Clawdbot assistant setup (Clawd)](/start/clawd) + - [Moltbot assistant setup (Clawd)](/start/clawd) - [Skills](/tools/skills) - [Skills config](/tools/skills-config) - [Workspace templates](/reference/templates/AGENTS) @@ -214,7 +214,7 @@ Example: ## The name -**Clawdbot = CLAW + TARDIS** — because every space lobster needs a time-and-space machine. +**Moltbot = CLAW + TARDIS** — because every space lobster needs a time-and-space machine. --- diff --git a/docs/install/ansible.md b/docs/install/ansible.md index 2715b5871..1417b9002 100644 --- a/docs/install/ansible.md +++ b/docs/install/ansible.md @@ -1,5 +1,5 @@ --- -summary: "Automated, hardened Clawdbot installation with Ansible, Tailscale VPN, and firewall isolation" +summary: "Automated, hardened Moltbot installation with Ansible, Tailscale VPN, and firewall isolation" read_when: - You want automated server deployment with security hardening - You need firewall-isolated setup with VPN access @@ -8,19 +8,19 @@ read_when: # Ansible Installation -The recommended way to deploy Clawdbot to production servers is via **[clawdbot-ansible](https://github.com/clawdbot/clawdbot-ansible)** — an automated installer with security-first architecture. +The recommended way to deploy Moltbot to production servers is via **[moltbot-ansible](https://github.com/moltbot/moltbot-ansible)** — an automated installer with security-first architecture. ## Quick Start One-command install: ```bash -curl -fsSL https://raw.githubusercontent.com/clawdbot/clawdbot-ansible/main/install.sh | bash +curl -fsSL https://raw.githubusercontent.com/moltbot/moltbot-ansible/main/install.sh | bash ``` -> **📦 Full guide: [github.com/clawdbot/clawdbot-ansible](https://github.com/clawdbot/clawdbot-ansible)** +> **📦 Full guide: [github.com/moltbot/moltbot-ansible](https://github.com/moltbot/moltbot-ansible)** > -> The clawdbot-ansible repo is the source of truth for Ansible deployment. This page is a quick overview. +> The moltbot-ansible repo is the source of truth for Ansible deployment. This page is a quick overview. ## What You Get @@ -46,22 +46,22 @@ The Ansible playbook installs and configures: 2. **UFW firewall** (SSH + Tailscale ports only) 3. **Docker CE + Compose V2** (for agent sandboxes) 4. **Node.js 22.x + pnpm** (runtime dependencies) -5. **Clawdbot** (host-based, not containerized) +5. **Moltbot** (host-based, not containerized) 6. **Systemd service** (auto-start with security hardening) Note: The gateway runs **directly on the host** (not in Docker), but agent sandboxes use Docker for isolation. See [Sandboxing](/gateway/sandboxing) for details. ## Post-Install Setup -After installation completes, switch to the clawdbot user: +After installation completes, switch to the moltbot user: ```bash -sudo -i -u clawdbot +sudo -i -u moltbot ``` The post-install script will guide you through: -1. **Onboarding wizard**: Configure Clawdbot settings +1. **Onboarding wizard**: Configure Moltbot settings 2. **Provider login**: Connect WhatsApp/Telegram/Discord/Signal 3. **Gateway testing**: Verify the installation 4. **Tailscale setup**: Connect to your VPN mesh @@ -70,17 +70,17 @@ The post-install script will guide you through: ```bash # Check service status -sudo systemctl status clawdbot +sudo systemctl status moltbot # View live logs -sudo journalctl -u clawdbot -f +sudo journalctl -u moltbot -f # Restart gateway -sudo systemctl restart clawdbot +sudo systemctl restart moltbot -# Provider login (run as clawdbot user) -sudo -i -u clawdbot -clawdbot channels login +# Provider login (run as moltbot user) +sudo -i -u moltbot +moltbot channels login ``` ## Security Architecture @@ -117,8 +117,8 @@ If you prefer manual control over the automation: sudo apt update && sudo apt install -y ansible git # 2. Clone repository -git clone https://github.com/clawdbot/clawdbot-ansible.git -cd clawdbot-ansible +git clone https://github.com/moltbot/moltbot-ansible.git +cd moltbot-ansible # 3. Install Ansible collections ansible-galaxy collection install -r requirements.yml @@ -126,18 +126,18 @@ ansible-galaxy collection install -r requirements.yml # 4. Run playbook ./run-playbook.sh -# Or run directly (then manually execute /tmp/clawdbot-setup.sh after) +# Or run directly (then manually execute /tmp/moltbot-setup.sh after) # ansible-playbook playbook.yml --ask-become-pass ``` -## Updating Clawdbot +## Updating Moltbot -The Ansible installer sets up Clawdbot for manual updates. See [Updating](/install/updating) for the standard update flow. +The Ansible installer sets up Moltbot for manual updates. See [Updating](/install/updating) for the standard update flow. To re-run the Ansible playbook (e.g., for configuration changes): ```bash -cd clawdbot-ansible +cd moltbot-ansible ./run-playbook.sh ``` @@ -156,14 +156,14 @@ If you're locked out: ```bash # Check logs -sudo journalctl -u clawdbot -n 100 +sudo journalctl -u moltbot -n 100 # Verify permissions -sudo ls -la /opt/clawdbot +sudo ls -la /opt/moltbot # Test manual start -sudo -i -u clawdbot -cd ~/clawdbot +sudo -i -u moltbot +cd ~/moltbot pnpm start ``` @@ -174,32 +174,32 @@ pnpm start sudo systemctl status docker # Check sandbox image -sudo docker images | grep clawdbot-sandbox +sudo docker images | grep moltbot-sandbox # Build sandbox image if missing -cd /opt/clawdbot/clawdbot -sudo -u clawdbot ./scripts/sandbox-setup.sh +cd /opt/moltbot/moltbot +sudo -u moltbot ./scripts/sandbox-setup.sh ``` ### Provider login fails -Make sure you're running as the `clawdbot` user: +Make sure you're running as the `moltbot` user: ```bash -sudo -i -u clawdbot -clawdbot channels login +sudo -i -u moltbot +moltbot channels login ``` ## Advanced Configuration For detailed security architecture and troubleshooting: -- [Security Architecture](https://github.com/clawdbot/clawdbot-ansible/blob/main/docs/security.md) -- [Technical Details](https://github.com/clawdbot/clawdbot-ansible/blob/main/docs/architecture.md) -- [Troubleshooting Guide](https://github.com/clawdbot/clawdbot-ansible/blob/main/docs/troubleshooting.md) +- [Security Architecture](https://github.com/moltbot/moltbot-ansible/blob/main/docs/security.md) +- [Technical Details](https://github.com/moltbot/moltbot-ansible/blob/main/docs/architecture.md) +- [Troubleshooting Guide](https://github.com/moltbot/moltbot-ansible/blob/main/docs/troubleshooting.md) ## Related -- [clawdbot-ansible](https://github.com/clawdbot/clawdbot-ansible) — full deployment guide +- [moltbot-ansible](https://github.com/moltbot/moltbot-ansible) — full deployment guide - [Docker](/install/docker) — containerized gateway setup - [Sandboxing](/gateway/sandboxing) — agent sandbox configuration - [Multi-Agent Sandbox & Tools](/multi-agent-sandbox-tools) — per-agent isolation diff --git a/docs/install/development-channels.md b/docs/install/development-channels.md index 6243b2a93..2024f10a9 100644 --- a/docs/install/development-channels.md +++ b/docs/install/development-channels.md @@ -9,7 +9,7 @@ read_when: Last updated: 2026-01-21 -Clawdbot ships three update channels: +Moltbot ships three update channels: - **stable**: npm dist-tag `latest`. - **beta**: npm dist-tag `beta` (builds under test). @@ -23,9 +23,9 @@ without changing the version number — dist-tags are the source of truth for np Git checkout: ```bash -clawdbot update --channel stable -clawdbot update --channel beta -clawdbot update --channel dev +moltbot update --channel stable +moltbot update --channel beta +moltbot update --channel dev ``` - `stable`/`beta` check out the latest matching tag (often the same tag). @@ -34,17 +34,17 @@ clawdbot update --channel dev npm/pnpm global install: ```bash -clawdbot update --channel stable -clawdbot update --channel beta -clawdbot update --channel dev +moltbot update --channel stable +moltbot update --channel beta +moltbot update --channel dev ``` This updates via the corresponding npm dist-tag (`latest`, `beta`, `dev`). -When you **explicitly** switch channels with `--channel`, Clawdbot also aligns +When you **explicitly** switch channels with `--channel`, Moltbot also aligns the install method: -- `dev` ensures a git checkout (default `~/clawdbot`, override with `CLAWDBOT_GIT_DIR`), +- `dev` ensures a git checkout (default `~/moltbot`, override with `CLAWDBOT_GIT_DIR`), updates it, and installs the global CLI from that checkout. - `stable`/`beta` installs from npm using the matching dist-tag. @@ -52,7 +52,7 @@ Tip: if you want stable + dev in parallel, keep two clones and point your gatewa ## Plugins and channels -When you switch channels with `clawdbot update`, Clawdbot also syncs plugin sources: +When you switch channels with `moltbot update`, Moltbot also syncs plugin sources: - `dev` prefers bundled plugins from the git checkout. - `stable` and `beta` restore npm-installed plugin packages. diff --git a/docs/install/docker.md b/docs/install/docker.md index 5c4941248..8ca80e53b 100644 --- a/docs/install/docker.md +++ b/docs/install/docker.md @@ -1,5 +1,5 @@ --- -summary: "Optional Docker-based setup and onboarding for Clawdbot" +summary: "Optional Docker-based setup and onboarding for Moltbot" read_when: - You want a containerized gateway instead of local installs - You are validating the Docker flow @@ -11,12 +11,12 @@ Docker is **optional**. Use it only if you want a containerized gateway or to va ## Is Docker right for me? -- **Yes**: you want an isolated, throwaway gateway environment or to run Clawdbot on a host without local installs. +- **Yes**: you want an isolated, throwaway gateway environment or to run Moltbot on a host without local installs. - **No**: you’re running on your own machine and just want the fastest dev loop. Use the normal install flow instead. - **Sandboxing note**: agent sandboxing uses Docker too, but it does **not** require the full gateway to run in Docker. See [Sandboxing](/gateway/sandboxing). This guide covers: -- Containerized Gateway (full Clawdbot in Docker) +- Containerized Gateway (full Moltbot in Docker) - Per-session Agent Sandbox (host gateway + Docker-isolated agent tools) Sandboxing details: [Sandboxing](/gateway/sandboxing) @@ -61,9 +61,9 @@ Running on a VPS? See [Hetzner (Docker VPS)](/platforms/hetzner). ### Manual flow (compose) ```bash -docker build -t clawdbot:local -f Dockerfile . -docker compose run --rm clawdbot-cli onboard -docker compose up -d clawdbot-gateway +docker build -t moltbot:local -f Dockerfile . +docker compose run --rm moltbot-cli onboard +docker compose up -d moltbot-gateway ``` ### Extra mounts (optional) @@ -71,7 +71,7 @@ docker compose up -d clawdbot-gateway If you want to mount additional host directories into the containers, set `CLAWDBOT_EXTRA_MOUNTS` before running `docker-setup.sh`. This accepts a comma-separated list of Docker bind mounts and applies them to both -`clawdbot-gateway` and `clawdbot-cli` by generating `docker-compose.extra.yml`. +`moltbot-gateway` and `moltbot-cli` by generating `docker-compose.extra.yml`. Example: @@ -97,14 +97,14 @@ named volume here (not a bind path); for bind mounts, use Example: ```bash -export CLAWDBOT_HOME_VOLUME="clawdbot_home" +export CLAWDBOT_HOME_VOLUME="moltbot_home" ./docker-setup.sh ``` You can combine this with extra mounts: ```bash -export CLAWDBOT_HOME_VOLUME="clawdbot_home" +export CLAWDBOT_HOME_VOLUME="moltbot_home" export CLAWDBOT_EXTRA_MOUNTS="$HOME/.codex:/home/node/.codex:ro,$HOME/github:/home/node/github:rw" ./docker-setup.sh ``` @@ -172,17 +172,17 @@ Use the CLI container to configure channels, then restart the gateway if needed. WhatsApp (QR): ```bash -docker compose run --rm clawdbot-cli channels login +docker compose run --rm moltbot-cli channels login ``` Telegram (bot token): ```bash -docker compose run --rm clawdbot-cli channels add --channel telegram --token "" +docker compose run --rm moltbot-cli channels add --channel telegram --token "" ``` Discord (bot token): ```bash -docker compose run --rm clawdbot-cli channels add --channel discord --token "" +docker compose run --rm moltbot-cli channels add --channel discord --token "" ``` Docs: [WhatsApp](/channels/whatsapp), [Telegram](/channels/telegram), [Discord](/channels/discord) @@ -190,7 +190,7 @@ Docs: [WhatsApp](/channels/whatsapp), [Telegram](/channels/telegram), [Discord]( ### Health check ```bash -docker compose exec clawdbot-gateway node dist/index.js health --token "$CLAWDBOT_GATEWAY_TOKEN" +docker compose exec moltbot-gateway node dist/index.js health --token "$CLAWDBOT_GATEWAY_TOKEN" ``` ### E2E smoke test (Docker) @@ -242,7 +242,7 @@ precedence, and troubleshooting. ### Default behavior -- Image: `clawdbot-sandbox:bookworm-slim` +- Image: `moltbot-sandbox:bookworm-slim` - One container per agent - Agent workspace access: `workspaceAccess: "none"` (default) uses `~/.clawdbot/sandboxes` - `"ro"` keeps the sandbox workspace at `/workspace` and mounts the agent workspace read-only at `/agent` (disables `write`/`edit`/`apply_patch`) @@ -258,9 +258,9 @@ If you plan to install packages in `setupCommand`, note: - Default `docker.network` is `"none"` (no egress). - `readOnlyRoot: true` blocks package installs. - `user` must be root for `apt-get` (omit `user` or set `user: "0:0"`). -Clawdbot auto-recreates containers when `setupCommand` (or docker config) changes +Moltbot auto-recreates containers when `setupCommand` (or docker config) changes unless the container was **recently used** (within ~5 minutes). Hot containers -log a warning with the exact `clawdbot sandbox recreate ...` command. +log a warning with the exact `moltbot sandbox recreate ...` command. ```json5 { @@ -272,7 +272,7 @@ log a warning with the exact `clawdbot sandbox recreate ...` command. workspaceAccess: "none", // none | ro | rw workspaceRoot: "~/.clawdbot/sandboxes", docker: { - image: "clawdbot-sandbox:bookworm-slim", + image: "moltbot-sandbox:bookworm-slim", workdir: "/workspace", readOnlyRoot: true, tmpfs: ["/tmp", "/var/tmp", "/run"], @@ -290,7 +290,7 @@ log a warning with the exact `clawdbot sandbox recreate ...` command. nproc: 256 }, seccompProfile: "/path/to/seccomp.json", - apparmorProfile: "clawdbot-sandbox", + apparmorProfile: "moltbot-sandbox", dns: ["1.1.1.1", "8.8.8.8"], extraHosts: ["internal.service:10.0.0.5"] }, @@ -325,7 +325,7 @@ Multi-agent: override `agents.defaults.sandbox.{docker,browser,prune}.*` per age scripts/sandbox-setup.sh ``` -This builds `clawdbot-sandbox:bookworm-slim` using `Dockerfile.sandbox`. +This builds `moltbot-sandbox:bookworm-slim` using `Dockerfile.sandbox`. ### Sandbox common image (optional) If you want a sandbox image with common build tooling (Node, Go, Rust, etc.), build the common image: @@ -334,11 +334,11 @@ If you want a sandbox image with common build tooling (Node, Go, Rust, etc.), bu scripts/sandbox-common-setup.sh ``` -This builds `clawdbot-sandbox-common:bookworm-slim`. To use it: +This builds `moltbot-sandbox-common:bookworm-slim`. To use it: ```json5 { - agents: { defaults: { sandbox: { docker: { image: "clawdbot-sandbox-common:bookworm-slim" } } } } + agents: { defaults: { sandbox: { docker: { image: "moltbot-sandbox-common:bookworm-slim" } } } } } ``` @@ -350,7 +350,7 @@ To run the browser tool inside the sandbox, build the browser image: scripts/sandbox-browser-setup.sh ``` -This builds `clawdbot-sandbox-browser:bookworm-slim` using +This builds `moltbot-sandbox-browser:bookworm-slim` using `Dockerfile.sandbox-browser`. The container runs Chromium with CDP enabled and an optional noVNC observer (headful via Xvfb). @@ -379,7 +379,7 @@ Custom browser image: { agents: { defaults: { - sandbox: { browser: { image: "my-clawdbot-browser" } } + sandbox: { browser: { image: "my-moltbot-browser" } } } } } @@ -398,14 +398,14 @@ Prune rules (`agents.defaults.sandbox.prune`) apply to browser containers too. Build your own image and point config to it: ```bash -docker build -t my-clawdbot-sbx -f Dockerfile.sandbox . +docker build -t my-moltbot-sbx -f Dockerfile.sandbox . ``` ```json5 { agents: { defaults: { - sandbox: { docker: { image: "my-clawdbot-sbx" } } + sandbox: { docker: { image: "my-moltbot-sbx" } } } } } @@ -437,11 +437,11 @@ Example: ## Troubleshooting -- Image missing: build with [`scripts/sandbox-setup.sh`](https://github.com/clawdbot/clawdbot/blob/main/scripts/sandbox-setup.sh) or set `agents.defaults.sandbox.docker.image`. +- Image missing: build with [`scripts/sandbox-setup.sh`](https://github.com/moltbot/moltbot/blob/main/scripts/sandbox-setup.sh) or set `agents.defaults.sandbox.docker.image`. - Container not running: it will auto-create per session on demand. - Permission errors in sandbox: set `docker.user` to a UID:GID that matches your mounted workspace ownership (or chown the workspace folder). -- Custom tools not found: Clawdbot runs commands with `sh -lc` (login shell), which +- Custom tools not found: Moltbot runs commands with `sh -lc` (login shell), which sources `/etc/profile` and may reset PATH. Set `docker.env.PATH` to prepend your custom tool paths (e.g., `/custom/bin:/usr/local/share/npm-global/bin`), or add a script under `/etc/profile.d/` in your Dockerfile. diff --git a/docs/install/index.md b/docs/install/index.md index 7ccab0ca8..8c6943589 100644 --- a/docs/install/index.md +++ b/docs/install/index.md @@ -1,7 +1,7 @@ --- -summary: "Install Clawdbot (recommended installer, global install, or from source)" +summary: "Install Moltbot (recommended installer, global install, or from source)" read_when: - - Installing Clawdbot + - Installing Moltbot - You want to install from GitHub --- @@ -12,19 +12,19 @@ Use the installer unless you have a reason not to. It sets up the CLI and runs o ## Quick install (recommended) ```bash -curl -fsSL https://clawd.bot/install.sh | bash +curl -fsSL https://molt.bot/install.sh | bash ``` Windows (PowerShell): ```powershell -iwr -useb https://clawd.bot/install.ps1 | iex +iwr -useb https://molt.bot/install.ps1 | iex ``` Next step (if you skipped onboarding): ```bash -clawdbot onboard --install-daemon +moltbot onboard --install-daemon ``` ## System requirements @@ -37,16 +37,16 @@ clawdbot onboard --install-daemon ### 1) Installer script (recommended) -Installs `clawdbot` globally via npm and runs onboarding. +Installs `moltbot` globally via npm and runs onboarding. ```bash -curl -fsSL https://clawd.bot/install.sh | bash +curl -fsSL https://molt.bot/install.sh | bash ``` Installer flags: ```bash -curl -fsSL https://clawd.bot/install.sh | bash -s -- --help +curl -fsSL https://molt.bot/install.sh | bash -s -- --help ``` Details: [Installer internals](/install/installer). @@ -54,7 +54,7 @@ Details: [Installer internals](/install/installer). Non-interactive (skip onboarding): ```bash -curl -fsSL https://clawd.bot/install.sh | bash -s -- --no-onboard +curl -fsSL https://molt.bot/install.sh | bash -s -- --no-onboard ``` ### 2) Global install (manual) @@ -62,13 +62,13 @@ curl -fsSL https://clawd.bot/install.sh | bash -s -- --no-onboard If you already have Node: ```bash -npm install -g clawdbot@latest +npm install -g moltbot@latest ``` If you have libvips installed globally (common on macOS via Homebrew) and `sharp` fails to install, force prebuilt binaries: ```bash -SHARP_IGNORE_GLOBAL_LIBVIPS=1 npm install -g clawdbot@latest +SHARP_IGNORE_GLOBAL_LIBVIPS=1 npm install -g moltbot@latest ``` If you see `sharp: Please add node-gyp to your dependencies`, either install build tooling (macOS: Xcode CLT + `npm install -g node-gyp`) or use the `SHARP_IGNORE_GLOBAL_LIBVIPS=1` workaround above to skip the native build. @@ -76,27 +76,27 @@ If you see `sharp: Please add node-gyp to your dependencies`, either install bui Or: ```bash -pnpm add -g clawdbot@latest +pnpm add -g moltbot@latest ``` Then: ```bash -clawdbot onboard --install-daemon +moltbot onboard --install-daemon ``` ### 3) From source (contributors/dev) ```bash -git clone https://github.com/clawdbot/clawdbot.git -cd clawdbot +git clone https://github.com/moltbot/moltbot.git +cd moltbot pnpm install pnpm ui:build # auto-installs UI deps on first run pnpm build -clawdbot onboard --install-daemon +moltbot onboard --install-daemon ``` -Tip: if you don’t have a global install yet, run repo commands via `pnpm clawdbot ...`. +Tip: if you don’t have a global install yet, run repo commands via `pnpm moltbot ...`. ### 4) Other install options @@ -107,32 +107,32 @@ Tip: if you don’t have a global install yet, run repo commands via `pnpm clawd ## After install -- Run onboarding: `clawdbot onboard --install-daemon` -- Quick check: `clawdbot doctor` -- Check gateway health: `clawdbot status` + `clawdbot health` -- Open the dashboard: `clawdbot dashboard` +- Run onboarding: `moltbot onboard --install-daemon` +- Quick check: `moltbot doctor` +- Check gateway health: `moltbot status` + `moltbot health` +- Open the dashboard: `moltbot dashboard` ## Install method: npm vs git (installer) The installer supports two methods: -- `npm` (default): `npm install -g clawdbot@latest` +- `npm` (default): `npm install -g moltbot@latest` - `git`: clone/build from GitHub and run from a source checkout ### CLI flags ```bash # Explicit npm -curl -fsSL https://clawd.bot/install.sh | bash -s -- --install-method npm +curl -fsSL https://molt.bot/install.sh | bash -s -- --install-method npm # Install from GitHub (source checkout) -curl -fsSL https://clawd.bot/install.sh | bash -s -- --install-method git +curl -fsSL https://molt.bot/install.sh | bash -s -- --install-method git ``` Common flags: - `--install-method npm|git` -- `--git-dir ` (default: `~/clawdbot`) +- `--git-dir ` (default: `~/moltbot`) - `--no-git-update` (skip `git pull` when using an existing checkout) - `--no-prompt` (disable prompts; required in CI/automation) - `--dry-run` (print what would happen; make no changes) @@ -150,7 +150,7 @@ Equivalent env vars (useful for automation): - `CLAWDBOT_NO_ONBOARD=1` - `SHARP_IGNORE_GLOBAL_LIBVIPS=0|1` (default: `1`; avoids `sharp` building against system libvips) -## Troubleshooting: `clawdbot` not found (PATH) +## Troubleshooting: `moltbot` not found (PATH) Quick diagnosis: @@ -161,7 +161,7 @@ npm prefix -g echo "$PATH" ``` -If `$(npm prefix -g)/bin` (macOS/Linux) or `$(npm prefix -g)` (Windows) is **not** present inside `echo "$PATH"`, your shell can’t find global npm binaries (including `clawdbot`). +If `$(npm prefix -g)/bin` (macOS/Linux) or `$(npm prefix -g)` (Windows) is **not** present inside `echo "$PATH"`, your shell can’t find global npm binaries (including `moltbot`). Fix: add it to your shell startup file (zsh: `~/.zshrc`, bash: `~/.bashrc`): diff --git a/docs/install/installer.md b/docs/install/installer.md index 7cd485756..c4139de6a 100644 --- a/docs/install/installer.md +++ b/docs/install/installer.md @@ -1,32 +1,32 @@ --- summary: "How the installer scripts work (install.sh + install-cli.sh), flags, and automation" read_when: - - You want to understand `clawd.bot/install.sh` + - You want to understand `molt.bot/install.sh` - You want to automate installs (CI / headless) - You want to install from a GitHub checkout --- # Installer internals -Clawdbot ships two installer scripts (served from `clawd.bot`): +Moltbot ships two installer scripts (served from `molt.bot`): -- `https://clawd.bot/install.sh` — “recommended” installer (global npm install by default; can also install from a GitHub checkout) -- `https://clawd.bot/install-cli.sh` — non-root-friendly CLI installer (installs into a prefix with its own Node) - - `https://clawd.bot/install.ps1` — Windows PowerShell installer (npm by default; optional git install) +- `https://molt.bot/install.sh` — “recommended” installer (global npm install by default; can also install from a GitHub checkout) +- `https://molt.bot/install-cli.sh` — non-root-friendly CLI installer (installs into a prefix with its own Node) + - `https://molt.bot/install.ps1` — Windows PowerShell installer (npm by default; optional git install) To see the current flags/behavior, run: ```bash -curl -fsSL https://clawd.bot/install.sh | bash -s -- --help +curl -fsSL https://molt.bot/install.sh | bash -s -- --help ``` Windows (PowerShell) help: ```powershell -& ([scriptblock]::Create((iwr -useb https://clawd.bot/install.ps1))) -? +& ([scriptblock]::Create((iwr -useb https://molt.bot/install.ps1))) -? ``` -If the installer completes but `clawdbot` is not found in a new terminal, it’s usually a Node/npm PATH issue. See: [Install](/install#nodejs--npm-path-sanity). +If the installer completes but `moltbot` is not found in a new terminal, it’s usually a Node/npm PATH issue. See: [Install](/install#nodejs--npm-path-sanity). ## install.sh (recommended) @@ -35,22 +35,22 @@ What it does (high level): - Detect OS (macOS / Linux / WSL). - Ensure Node.js **22+** (macOS via Homebrew; Linux via NodeSource). - Choose install method: - - `npm` (default): `npm install -g clawdbot@latest` + - `npm` (default): `npm install -g moltbot@latest` - `git`: clone/build a source checkout and install a wrapper script - On Linux: avoid global npm permission errors by switching npm’s prefix to `~/.npm-global` when needed. -- If upgrading an existing install: runs `clawdbot doctor --non-interactive` (best effort). -- For git installs: runs `clawdbot doctor --non-interactive` after install/update (best effort). +- If upgrading an existing install: runs `moltbot doctor --non-interactive` (best effort). +- For git installs: runs `moltbot doctor --non-interactive` after install/update (best effort). - Mitigates `sharp` native install gotchas by defaulting `SHARP_IGNORE_GLOBAL_LIBVIPS=1` (avoids building against system libvips). If you *want* `sharp` to link against a globally-installed libvips (or you’re debugging), set: ```bash -SHARP_IGNORE_GLOBAL_LIBVIPS=0 curl -fsSL https://clawd.bot/install.sh | bash +SHARP_IGNORE_GLOBAL_LIBVIPS=0 curl -fsSL https://molt.bot/install.sh | bash ``` ### Discoverability / “git install” prompt -If you run the installer while **already inside a Clawdbot source checkout** (detected via `package.json` + `pnpm-workspace.yaml`), it prompts: +If you run the installer while **already inside a Moltbot source checkout** (detected via `package.json` + `pnpm-workspace.yaml`), it prompts: - update and use this checkout (`git`) - or migrate to the global npm install (`npm`) @@ -73,12 +73,12 @@ On some Linux setups (especially after installing Node via the system package ma ## install-cli.sh (non-root CLI installer) -This script installs `clawdbot` into a prefix (default: `~/.clawdbot`) and also installs a dedicated Node runtime under that prefix, so it can work on machines where you don’t want to touch the system Node/npm. +This script installs `moltbot` into a prefix (default: `~/.clawdbot`) and also installs a dedicated Node runtime under that prefix, so it can work on machines where you don’t want to touch the system Node/npm. Help: ```bash -curl -fsSL https://clawd.bot/install-cli.sh | bash -s -- --help +curl -fsSL https://molt.bot/install-cli.sh | bash -s -- --help ``` ## install.ps1 (Windows PowerShell) @@ -87,22 +87,22 @@ What it does (high level): - Ensure Node.js **22+** (winget/Chocolatey/Scoop or manual). - Choose install method: - - `npm` (default): `npm install -g clawdbot@latest` + - `npm` (default): `npm install -g moltbot@latest` - `git`: clone/build a source checkout and install a wrapper script -- Runs `clawdbot doctor --non-interactive` on upgrades and git installs (best effort). +- Runs `moltbot doctor --non-interactive` on upgrades and git installs (best effort). Examples: ```powershell -iwr -useb https://clawd.bot/install.ps1 | iex +iwr -useb https://molt.bot/install.ps1 | iex ``` ```powershell -iwr -useb https://clawd.bot/install.ps1 | iex -InstallMethod git +iwr -useb https://molt.bot/install.ps1 | iex -InstallMethod git ``` ```powershell -iwr -useb https://clawd.bot/install.ps1 | iex -InstallMethod git -GitDir "C:\\clawdbot" +iwr -useb https://molt.bot/install.ps1 | iex -InstallMethod git -GitDir "C:\\moltbot" ``` Environment variables: @@ -118,5 +118,5 @@ Git for Windows link (`https://git-scm.com/download/win`) and exit. Common Windows issues: - **npm error spawn git / ENOENT**: install Git for Windows and reopen PowerShell, then rerun the installer. -- **"clawdbot" is not recognized**: your npm global bin folder is not on PATH. Most systems use +- **"moltbot" is not recognized**: your npm global bin folder is not on PATH. Most systems use `%AppData%\\npm`. You can also run `npm config get prefix` and add `\\bin` to PATH, then reopen PowerShell. diff --git a/docs/install/migrating.md b/docs/install/migrating.md index 4987b38b9..131d9fa7d 100644 --- a/docs/install/migrating.md +++ b/docs/install/migrating.md @@ -1,12 +1,12 @@ --- -summary: "Move (migrate) a Clawdbot install from one machine to another" +summary: "Move (migrate) a Moltbot install from one machine to another" read_when: - - You are moving Clawdbot to a new laptop/server + - You are moving Moltbot to a new laptop/server - You want to preserve sessions, auth, and channel logins (WhatsApp, etc.) --- -# Migrating Clawdbot to a new machine +# Migrating Moltbot to a new machine -This guide migrates a Clawdbot Gateway from one machine to another **without redoing onboarding**. +This guide migrates a Moltbot Gateway from one machine to another **without redoing onboarding**. The migration is simple conceptually: @@ -31,7 +31,7 @@ But it may be different if you use: If you’re not sure, run on the **old** machine: ```bash -clawdbot status +moltbot status ``` Look for mentions of `CLAWDBOT_STATE_DIR` / profile in the output. If you run multiple gateways, repeat for each profile. @@ -49,7 +49,7 @@ Your workspace is where files like `MEMORY.md`, `USER.md`, and `memory/*.md` liv If you copy **both** the state dir and workspace, you keep: -- Gateway configuration (`clawdbot.json`) +- Gateway configuration (`moltbot.json`) - Auth profiles / API keys / OAuth tokens - Session history + agent state - Channel state (e.g. WhatsApp login/session) @@ -70,7 +70,7 @@ Those live under `$CLAWDBOT_STATE_DIR`. On the **old** machine, stop the gateway first so files aren’t changing mid-copy: ```bash -clawdbot gateway stop +moltbot gateway stop ``` (Optional but recommended) archive the state dir and workspace: @@ -78,14 +78,14 @@ clawdbot gateway stop ```bash # Adjust paths if you use a profile or custom locations cd ~ -tar -czf clawdbot-state.tgz .clawdbot +tar -czf moltbot-state.tgz .clawdbot tar -czf clawd-workspace.tgz clawd ``` If you have multiple profiles/state dirs (e.g. `~/.clawdbot-main`, `~/.clawdbot-work`), archive each. -### Step 1 — Install Clawdbot on the new machine +### Step 1 — Install Moltbot on the new machine On the **new** machine, install the CLI (and Node if needed): @@ -116,7 +116,7 @@ After copying, ensure: On the **new** machine: ```bash -clawdbot doctor +moltbot doctor ``` Doctor is the “safe boring” command. It repairs services, applies config migrations, and warns about mismatches. @@ -124,8 +124,8 @@ Doctor is the “safe boring” command. It repairs services, applies config mig Then: ```bash -clawdbot gateway restart -clawdbot status +moltbot gateway restart +moltbot status ``` ## Common footguns (and how to avoid them) @@ -141,12 +141,12 @@ If you ran the old gateway with a profile (or `CLAWDBOT_STATE_DIR`), and the new Fix: run the gateway/service using the **same** profile/state dir you migrated, then rerun: ```bash -clawdbot doctor +moltbot doctor ``` -### Footgun: copying only `clawdbot.json` +### Footgun: copying only `moltbot.json` -`clawdbot.json` is not enough. Many providers store state under: +`moltbot.json` is not enough. Many providers store state under: - `$CLAWDBOT_STATE_DIR/credentials/` - `$CLAWDBOT_STATE_DIR/agents//...` @@ -178,7 +178,7 @@ If you’re in remote mode, migrate the **gateway host**. On the new machine, confirm: -- `clawdbot status` shows the gateway running +- `moltbot status` shows the gateway running - Your channels are still connected (e.g. WhatsApp doesn’t require re-pair) - The dashboard opens and shows existing sessions - Your workspace files (memory, configs) are present @@ -187,4 +187,4 @@ On the new machine, confirm: - [Doctor](/gateway/doctor) - [Gateway troubleshooting](/gateway/troubleshooting) -- [Where does Clawdbot store its data?](/help/faq#where-does-clawdbot-store-its-data) +- [Where does Moltbot store its data?](/help/faq#where-does-moltbot-store-its-data) diff --git a/docs/install/nix.md b/docs/install/nix.md index e11c226f2..b67677423 100644 --- a/docs/install/nix.md +++ b/docs/install/nix.md @@ -1,5 +1,5 @@ --- -summary: "Install Clawdbot declaratively with Nix" +summary: "Install Moltbot declaratively with Nix" read_when: - You want reproducible, rollback-able installs - You're already using Nix/NixOS/Home Manager @@ -8,30 +8,30 @@ read_when: # Nix Installation -The recommended way to run Clawdbot with Nix is via **[nix-clawdbot](https://github.com/clawdbot/nix-clawdbot)** — a batteries-included Home Manager module. +The recommended way to run Moltbot with Nix is via **[nix-moltbot](https://github.com/moltbot/nix-moltbot)** — a batteries-included Home Manager module. ## Quick Start Paste this to your AI agent (Claude, Cursor, etc.): ```text -I want to set up nix-clawdbot on my Mac. -Repository: github:clawdbot/nix-clawdbot +I want to set up nix-moltbot on my Mac. +Repository: github:moltbot/nix-moltbot What I need you to do: 1. Check if Determinate Nix is installed (if not, install it) -2. Create a local flake at ~/code/clawdbot-local using templates/agent-first/flake.nix +2. Create a local flake at ~/code/moltbot-local using templates/agent-first/flake.nix 3. Help me create a Telegram bot (@BotFather) and get my chat ID (@userinfobot) 4. Set up secrets (bot token, Anthropic key) - plain files at ~/.secrets/ is fine 5. Fill in the template placeholders and run home-manager switch 6. Verify: launchd running, bot responds to messages -Reference the nix-clawdbot README for module options. +Reference the nix-moltbot README for module options. ``` -> **📦 Full guide: [github.com/clawdbot/nix-clawdbot](https://github.com/clawdbot/nix-clawdbot)** +> **📦 Full guide: [github.com/moltbot/nix-moltbot](https://github.com/moltbot/nix-moltbot)** > -> The nix-clawdbot repo is the source of truth for Nix installation. This page is just a quick overview. +> The nix-moltbot repo is the source of truth for Nix installation. This page is just a quick overview. ## What you get @@ -44,9 +44,9 @@ Reference the nix-clawdbot README for module options. ## Nix Mode Runtime Behavior -When `CLAWDBOT_NIX_MODE=1` is set (automatic with nix-clawdbot): +When `CLAWDBOT_NIX_MODE=1` is set (automatic with nix-moltbot): -Clawdbot supports a **Nix mode** that makes configuration deterministic and disables auto-install flows. +Moltbot supports a **Nix mode** that makes configuration deterministic and disables auto-install flows. Enable it by exporting: ```bash @@ -57,15 +57,15 @@ On macOS, the GUI app does not automatically inherit shell env vars. You can also enable Nix mode via defaults: ```bash -defaults write com.clawdbot.mac clawdbot.nixMode -bool true +defaults write bot.molt.mac moltbot.nixMode -bool true ``` ### Config + state paths -Clawdbot reads JSON5 config from `CLAWDBOT_CONFIG_PATH` and stores mutable data in `CLAWDBOT_STATE_DIR`. +Moltbot reads JSON5 config from `CLAWDBOT_CONFIG_PATH` and stores mutable data in `CLAWDBOT_STATE_DIR`. - `CLAWDBOT_STATE_DIR` (default: `~/.clawdbot`) -- `CLAWDBOT_CONFIG_PATH` (default: `$CLAWDBOT_STATE_DIR/clawdbot.json`) +- `CLAWDBOT_CONFIG_PATH` (default: `$CLAWDBOT_STATE_DIR/moltbot.json`) When running under Nix, set these explicitly to Nix-managed locations so runtime state and config stay out of the immutable store. @@ -81,15 +81,15 @@ stay out of the immutable store. The macOS packaging flow expects a stable Info.plist template at: ``` -apps/macos/Sources/Clawdbot/Resources/Info.plist +apps/macos/Sources/Moltbot/Resources/Info.plist ``` -[`scripts/package-mac-app.sh`](https://github.com/clawdbot/clawdbot/blob/main/scripts/package-mac-app.sh) copies this template into the app bundle and patches dynamic fields +[`scripts/package-mac-app.sh`](https://github.com/moltbot/moltbot/blob/main/scripts/package-mac-app.sh) copies this template into the app bundle and patches dynamic fields (bundle ID, version/build, Git SHA, Sparkle keys). This keeps the plist deterministic for SwiftPM packaging and Nix builds (which do not rely on a full Xcode toolchain). ## Related -- [nix-clawdbot](https://github.com/clawdbot/nix-clawdbot) — full setup guide +- [nix-moltbot](https://github.com/moltbot/nix-moltbot) — full setup guide - [Wizard](/start/wizard) — non-Nix CLI setup - [Docker](/install/docker) — containerized setup diff --git a/docs/install/node.md b/docs/install/node.md index 3075b6207..801864424 100644 --- a/docs/install/node.md +++ b/docs/install/node.md @@ -2,16 +2,16 @@ title: "Node.js + npm (PATH sanity)" summary: "Node.js + npm install sanity: versions, PATH, and global installs" read_when: - - "You installed Clawdbot but `clawdbot` is “command not found”" + - "You installed Moltbot but `moltbot` is “command not found”" - "You’re setting up Node.js/npm on a new machine" - "npm install -g ... fails with permissions or PATH issues" --- # Node.js + npm (PATH sanity) -Clawdbot’s runtime baseline is **Node 22+**. +Moltbot’s runtime baseline is **Node 22+**. -If you can run `npm install -g clawdbot@latest` but later see `clawdbot: command not found`, it’s almost always a **PATH** issue: the directory where npm puts global binaries isn’t on your shell’s PATH. +If you can run `npm install -g moltbot@latest` but later see `moltbot: command not found`, it’s almost always a **PATH** issue: the directory where npm puts global binaries isn’t on your shell’s PATH. ## Quick diagnosis @@ -24,7 +24,7 @@ npm prefix -g echo "$PATH" ``` -If `$(npm prefix -g)/bin` (macOS/Linux) or `$(npm prefix -g)` (Windows) is **not** present inside `echo "$PATH"`, your shell can’t find global npm binaries (including `clawdbot`). +If `$(npm prefix -g)/bin` (macOS/Linux) or `$(npm prefix -g)` (Windows) is **not** present inside `echo "$PATH"`, your shell can’t find global npm binaries (including `moltbot`). ## Fix: put npm’s global bin dir on PATH diff --git a/docs/install/uninstall.md b/docs/install/uninstall.md index 5849a6780..f3a180caa 100644 --- a/docs/install/uninstall.md +++ b/docs/install/uninstall.md @@ -1,14 +1,14 @@ --- -summary: "Uninstall Clawdbot completely (CLI, service, state, workspace)" +summary: "Uninstall Moltbot completely (CLI, service, state, workspace)" read_when: - - You want to remove Clawdbot from a machine + - You want to remove Moltbot from a machine - The gateway service is still running after uninstall --- # Uninstall Two paths: -- **Easy path** if `clawdbot` is still installed. +- **Easy path** if `moltbot` is still installed. - **Manual service removal** if the CLI is gone but the service is still running. ## Easy path (CLI still installed) @@ -16,14 +16,14 @@ Two paths: Recommended: use the built-in uninstaller: ```bash -clawdbot uninstall +moltbot uninstall ``` Non-interactive (automation / npx): ```bash -clawdbot uninstall --all --yes --non-interactive -npx -y clawdbot uninstall --all --yes --non-interactive +moltbot uninstall --all --yes --non-interactive +npx -y moltbot uninstall --all --yes --non-interactive ``` Manual steps (same result): @@ -31,13 +31,13 @@ Manual steps (same result): 1) Stop the gateway service: ```bash -clawdbot gateway stop +moltbot gateway stop ``` 2) Uninstall the gateway service (launchd/systemd/schtasks): ```bash -clawdbot gateway uninstall +moltbot gateway uninstall ``` 3) Delete state + config: @@ -57,15 +57,15 @@ rm -rf ~/clawd 5) Remove the CLI install (pick the one you used): ```bash -npm rm -g clawdbot -pnpm remove -g clawdbot -bun remove -g clawdbot +npm rm -g moltbot +pnpm remove -g moltbot +bun remove -g moltbot ``` 6) If you installed the macOS app: ```bash -rm -rf /Applications/Clawdbot.app +rm -rf /Applications/Moltbot.app ``` Notes: @@ -74,36 +74,36 @@ Notes: ## Manual service removal (CLI not installed) -Use this if the gateway service keeps running but `clawdbot` is missing. +Use this if the gateway service keeps running but `moltbot` is missing. ### macOS (launchd) -Default label is `com.clawdbot.gateway` (or `com.clawdbot.`): +Default label is `bot.molt.gateway` (or `bot.molt.`; legacy `com.clawdbot.*` may still exist): ```bash -launchctl bootout gui/$UID/com.clawdbot.gateway -rm -f ~/Library/LaunchAgents/com.clawdbot.gateway.plist +launchctl bootout gui/$UID/bot.molt.gateway +rm -f ~/Library/LaunchAgents/bot.molt.gateway.plist ``` -If you used a profile, replace the label and plist name with `com.clawdbot.`. +If you used a profile, replace the label and plist name with `bot.molt.`. Remove any legacy `com.clawdbot.*` plists if present. ### Linux (systemd user unit) -Default unit name is `clawdbot-gateway.service` (or `clawdbot-gateway-.service`): +Default unit name is `moltbot-gateway.service` (or `moltbot-gateway-.service`): ```bash -systemctl --user disable --now clawdbot-gateway.service -rm -f ~/.config/systemd/user/clawdbot-gateway.service +systemctl --user disable --now moltbot-gateway.service +rm -f ~/.config/systemd/user/moltbot-gateway.service systemctl --user daemon-reload ``` ### Windows (Scheduled Task) -Default task name is `Clawdbot Gateway` (or `Clawdbot Gateway ()`). +Default task name is `Moltbot Gateway` (or `Moltbot Gateway ()`). The task script lives under your state dir. ```powershell -schtasks /Delete /F /TN "Clawdbot Gateway" +schtasks /Delete /F /TN "Moltbot Gateway" Remove-Item -Force "$env:USERPROFILE\.clawdbot\gateway.cmd" ``` @@ -113,12 +113,12 @@ If you used a profile, delete the matching task name and `~\.clawdbot-\ ### Normal install (install.sh / npm / pnpm / bun) -If you used `https://clawd.bot/install.sh` or `install.ps1`, the CLI was installed with `npm install -g clawdbot@latest`. -Remove it with `npm rm -g clawdbot` (or `pnpm remove -g` / `bun remove -g` if you installed that way). +If you used `https://molt.bot/install.sh` or `install.ps1`, the CLI was installed with `npm install -g moltbot@latest`. +Remove it with `npm rm -g moltbot` (or `pnpm remove -g` / `bun remove -g` if you installed that way). ### Source checkout (git clone) -If you run from a repo checkout (`git clone` + `clawdbot ...` / `bun run clawdbot ...`): +If you run from a repo checkout (`git clone` + `moltbot ...` / `bun run moltbot ...`): 1) Uninstall the gateway service **before** deleting the repo (use the easy path above or manual service removal). 2) Delete the repo directory. diff --git a/docs/install/updating.md b/docs/install/updating.md index 1d39fa6e4..12303cb2a 100644 --- a/docs/install/updating.md +++ b/docs/install/updating.md @@ -1,39 +1,40 @@ --- -summary: "Updating Clawdbot safely (global install or source), plus rollback strategy" +summary: "Updating Moltbot safely (global install or source), plus rollback strategy" read_when: - - Updating Clawdbot + - Updating Moltbot - Something breaks after an update --- # Updating -Clawdbot is moving fast (pre “1.0”). Treat updates like shipping infra: update → run checks → restart (or use `clawdbot update`, which restarts) → verify. +Moltbot is moving fast (pre “1.0”). Treat updates like shipping infra: update → run checks → restart (or use `moltbot update`, which restarts) → verify. ## Recommended: re-run the website installer (upgrade in place) The **preferred** update path is to re-run the installer from the website. It -detects existing installs, upgrades in place, and runs `clawdbot doctor` when +detects existing installs, upgrades in place, and runs `moltbot doctor` when needed. ```bash -curl -fsSL https://clawd.bot/install.sh | bash +curl -fsSL https://molt.bot/install.sh | bash ``` Notes: - Add `--no-onboard` if you don’t want the onboarding wizard to run again. - For **source installs**, use: ```bash - curl -fsSL https://clawd.bot/install.sh | bash -s -- --install-method git --no-onboard + curl -fsSL https://molt.bot/install.sh | bash -s -- --install-method git --no-onboard ``` The installer will `git pull --rebase` **only** if the repo is clean. -- For **global installs**, the script uses `npm install -g clawdbot@latest` under the hood. +- For **global installs**, the script uses `npm install -g moltbot@latest` under the hood. +- Legacy note: `moltbot` remains available as a compatibility shim. ## Before you update - Know how you installed: **global** (npm/pnpm) vs **from source** (git clone). - Know how your Gateway is running: **foreground terminal** vs **supervised service** (launchd/systemd). - Snapshot your tailoring: - - Config: `~/.clawdbot/clawdbot.json` + - Config: `~/.clawdbot/moltbot.json` - Credentials: `~/.clawdbot/credentials/` - Workspace: `~/clawd` @@ -42,20 +43,20 @@ Notes: Global install (pick one): ```bash -npm i -g clawdbot@latest +npm i -g moltbot@latest ``` ```bash -pnpm add -g clawdbot@latest +pnpm add -g moltbot@latest ``` We do **not** recommend Bun for the Gateway runtime (WhatsApp/Telegram bugs). To switch update channels (git + npm installs): ```bash -clawdbot update --channel beta -clawdbot update --channel dev -clawdbot update --channel stable +moltbot update --channel beta +moltbot update --channel dev +moltbot update --channel stable ``` Use `--tag ` for a one-off install tag/version. @@ -67,36 +68,36 @@ Note: on npm installs, the gateway logs an update hint on startup (checks the cu Then: ```bash -clawdbot doctor -clawdbot gateway restart -clawdbot health +moltbot doctor +moltbot gateway restart +moltbot health ``` Notes: -- If your Gateway runs as a service, `clawdbot gateway restart` is preferred over killing PIDs. +- If your Gateway runs as a service, `moltbot gateway restart` is preferred over killing PIDs. - If you’re pinned to a specific version, see “Rollback / pinning” below. -## Update (`clawdbot update`) +## Update (`moltbot update`) For **source installs** (git checkout), prefer: ```bash -clawdbot update +moltbot update ``` It runs a safe-ish update flow: - Requires a clean worktree. - Switches to the selected channel (tag or branch). - Fetches + rebases against the configured upstream (dev channel). -- Installs deps, builds, builds the Control UI, and runs `clawdbot doctor`. +- Installs deps, builds, builds the Control UI, and runs `moltbot doctor`. - Restarts the gateway by default (use `--no-restart` to skip). -If you installed via **npm/pnpm** (no git metadata), `clawdbot update` will try to update via your package manager. If it can’t detect the install, use “Update (global install)” instead. +If you installed via **npm/pnpm** (no git metadata), `moltbot update` will try to update via your package manager. If it can’t detect the install, use “Update (global install)” instead. ## Update (Control UI / RPC) The Control UI has **Update & Restart** (RPC: `update.run`). It: -1) Runs the same source-update flow as `clawdbot update` (git checkout only). +1) Runs the same source-update flow as `moltbot update` (git checkout only). 2) Writes a restart sentinel with a structured report (stdout/stderr tail). 3) Restarts the gateway and pings the last active session with the report. @@ -109,7 +110,7 @@ From the repo checkout: Preferred: ```bash -clawdbot update +moltbot update ``` Manual (equivalent-ish): @@ -119,27 +120,27 @@ git pull pnpm install pnpm build pnpm ui:build # auto-installs UI deps on first run -clawdbot doctor -clawdbot health +moltbot doctor +moltbot health ``` Notes: -- `pnpm build` matters when you run the packaged `clawdbot` binary ([`dist/entry.js`](https://github.com/clawdbot/clawdbot/blob/main/dist/entry.js)) or use Node to run `dist/`. -- If you run from a repo checkout without a global install, use `pnpm clawdbot ...` for CLI commands. -- If you run directly from TypeScript (`pnpm clawdbot ...`), a rebuild is usually unnecessary, but **config migrations still apply** → run doctor. -- Switching between global and git installs is easy: install the other flavor, then run `clawdbot doctor` so the gateway service entrypoint is rewritten to the current install. +- `pnpm build` matters when you run the packaged `moltbot` binary ([`moltbot.mjs`](https://github.com/moltbot/moltbot/blob/main/moltbot.mjs)) or use Node to run `dist/`. +- If you run from a repo checkout without a global install, use `pnpm moltbot ...` for CLI commands. +- If you run directly from TypeScript (`pnpm moltbot ...`), a rebuild is usually unnecessary, but **config migrations still apply** → run doctor. +- Switching between global and git installs is easy: install the other flavor, then run `moltbot doctor` so the gateway service entrypoint is rewritten to the current install. -## Always run: `clawdbot doctor` +## Always Run: `moltbot doctor` Doctor is the “safe update” command. It’s intentionally boring: repair + migrate + warn. -Note: if you’re on a **source install** (git checkout), `clawdbot doctor` will offer to run `clawdbot update` first. +Note: if you’re on a **source install** (git checkout), `moltbot doctor` will offer to run `moltbot update` first. Typical things it does: - Migrate deprecated config keys / legacy config file locations. - Audit DM policies and warn on risky “open” settings. - Check Gateway health and can offer to restart. -- Detect and migrate older gateway services (launchd/systemd; legacy schtasks) to current Clawdbot services. +- Detect and migrate older gateway services (launchd/systemd; legacy schtasks) to current Moltbot services. - On Linux, ensure systemd user lingering (so the Gateway survives logout). Details: [Doctor](/gateway/doctor) @@ -149,18 +150,18 @@ Details: [Doctor](/gateway/doctor) CLI (works regardless of OS): ```bash -clawdbot gateway status -clawdbot gateway stop -clawdbot gateway restart -clawdbot gateway --port 18789 -clawdbot logs --follow +moltbot gateway status +moltbot gateway stop +moltbot gateway restart +moltbot gateway --port 18789 +moltbot logs --follow ``` If you’re supervised: -- macOS launchd (app-bundled LaunchAgent): `launchctl kickstart -k gui/$UID/com.clawdbot.gateway` (use `com.clawdbot.` if set) -- Linux systemd user service: `systemctl --user restart clawdbot-gateway[-].service` -- Windows (WSL2): `systemctl --user restart clawdbot-gateway[-].service` - - `launchctl`/`systemctl` only work if the service is installed; otherwise run `clawdbot gateway install`. +- macOS launchd (app-bundled LaunchAgent): `launchctl kickstart -k gui/$UID/bot.molt.gateway` (use `bot.molt.`; legacy `com.clawdbot.*` still works) +- Linux systemd user service: `systemctl --user restart moltbot-gateway[-].service` +- Windows (WSL2): `systemctl --user restart moltbot-gateway[-].service` + - `launchctl`/`systemctl` only work if the service is installed; otherwise run `moltbot gateway install`. Runbook + exact service labels: [Gateway runbook](/gateway) @@ -171,20 +172,20 @@ Runbook + exact service labels: [Gateway runbook](/gateway) Install a known-good version (replace `` with the last working one): ```bash -npm i -g clawdbot@ +npm i -g moltbot@ ``` ```bash -pnpm add -g clawdbot@ +pnpm add -g moltbot@ ``` -Tip: to see the current published version, run `npm view clawdbot version`. +Tip: to see the current published version, run `npm view moltbot version`. Then restart + re-run doctor: ```bash -clawdbot doctor -clawdbot gateway restart +moltbot doctor +moltbot gateway restart ``` ### Pin (source) by date @@ -201,7 +202,7 @@ Then reinstall deps + restart: ```bash pnpm install pnpm build -clawdbot gateway restart +moltbot gateway restart ``` If you want to go back to latest later: @@ -213,6 +214,6 @@ git pull ## If you’re stuck -- Run `clawdbot doctor` again and read the output carefully (it often tells you the fix). +- Run `moltbot doctor` again and read the output carefully (it often tells you the fix). - Check: [Troubleshooting](/gateway/troubleshooting) - Ask in Discord: https://channels.discord.gg/clawd diff --git a/docs/logging.md b/docs/logging.md index 8d1cd5a9f..ec6ee5ff6 100644 --- a/docs/logging.md +++ b/docs/logging.md @@ -8,7 +8,7 @@ read_when: # Logging -Clawdbot logs in two places: +Moltbot logs in two places: - **File logs** (JSON lines) written by the Gateway. - **Console output** shown in terminals and the Control UI. @@ -20,16 +20,16 @@ levels and formats. By default, the Gateway writes a rolling log file under: -`/tmp/clawdbot/clawdbot-YYYY-MM-DD.log` +`/tmp/moltbot/moltbot-YYYY-MM-DD.log` The date uses the gateway host's local timezone. -You can override this in `~/.clawdbot/clawdbot.json`: +You can override this in `~/.clawdbot/moltbot.json`: ```json { "logging": { - "file": "/path/to/clawdbot.log" + "file": "/path/to/moltbot.log" } } ``` @@ -41,7 +41,7 @@ You can override this in `~/.clawdbot/clawdbot.json`: Use the CLI to tail the gateway log file via RPC: ```bash -clawdbot logs --follow +moltbot logs --follow ``` Output modes: @@ -62,7 +62,7 @@ In JSON mode, the CLI emits `type`-tagged objects: If the Gateway is unreachable, the CLI prints a short hint to run: ```bash -clawdbot doctor +moltbot doctor ``` ### Control UI (web) @@ -75,7 +75,7 @@ See [/web/control-ui](/web/control-ui) for how to open it. To filter channel activity (WhatsApp/Telegram/etc), use: ```bash -clawdbot channels logs --channel whatsapp +moltbot channels logs --channel whatsapp ``` ## Log formats @@ -97,13 +97,13 @@ Console formatting is controlled by `logging.consoleStyle`. ## Configuring logging -All logging configuration lives under `logging` in `~/.clawdbot/clawdbot.json`. +All logging configuration lives under `logging` in `~/.clawdbot/moltbot.json`. ```json { "logging": { "level": "info", - "file": "/tmp/clawdbot/clawdbot-YYYY-MM-DD.log", + "file": "/tmp/moltbot/moltbot-YYYY-MM-DD.log", "consoleLevel": "info", "consoleStyle": "pretty", "redactSensitive": "tools", @@ -151,7 +151,7 @@ diagnostics + the exporter plugin are enabled. - **OpenTelemetry (OTel)**: the data model + SDKs for traces, metrics, and logs. - **OTLP**: the wire protocol used to export OTel data to a collector/backend. -- Clawdbot exports via **OTLP/HTTP (protobuf)** today. +- Moltbot exports via **OTLP/HTTP (protobuf)** today. ### Signals exported @@ -237,7 +237,7 @@ works with any OpenTelemetry collector/backend that accepts OTLP/HTTP. "enabled": true, "endpoint": "http://otel-collector:4318", "protocol": "http/protobuf", - "serviceName": "clawdbot-gateway", + "serviceName": "moltbot-gateway", "traces": true, "metrics": true, "logs": true, @@ -249,7 +249,7 @@ works with any OpenTelemetry collector/backend that accepts OTLP/HTTP. ``` Notes: -- You can also enable the plugin with `clawdbot plugins enable diagnostics-otel`. +- You can also enable the plugin with `moltbot plugins enable diagnostics-otel`. - `protocol` currently supports `http/protobuf` only. `grpc` is ignored. - Metrics include token usage, cost, context size, run duration, and message-flow counters/histograms (webhooks, queueing, session state, queue depth/wait). @@ -262,58 +262,58 @@ Notes: ### Exported metrics (names + types) Model usage: -- `clawdbot.tokens` (counter, attrs: `clawdbot.token`, `clawdbot.channel`, - `clawdbot.provider`, `clawdbot.model`) -- `clawdbot.cost.usd` (counter, attrs: `clawdbot.channel`, `clawdbot.provider`, - `clawdbot.model`) -- `clawdbot.run.duration_ms` (histogram, attrs: `clawdbot.channel`, - `clawdbot.provider`, `clawdbot.model`) -- `clawdbot.context.tokens` (histogram, attrs: `clawdbot.context`, - `clawdbot.channel`, `clawdbot.provider`, `clawdbot.model`) +- `moltbot.tokens` (counter, attrs: `moltbot.token`, `moltbot.channel`, + `moltbot.provider`, `moltbot.model`) +- `moltbot.cost.usd` (counter, attrs: `moltbot.channel`, `moltbot.provider`, + `moltbot.model`) +- `moltbot.run.duration_ms` (histogram, attrs: `moltbot.channel`, + `moltbot.provider`, `moltbot.model`) +- `moltbot.context.tokens` (histogram, attrs: `moltbot.context`, + `moltbot.channel`, `moltbot.provider`, `moltbot.model`) Message flow: -- `clawdbot.webhook.received` (counter, attrs: `clawdbot.channel`, - `clawdbot.webhook`) -- `clawdbot.webhook.error` (counter, attrs: `clawdbot.channel`, - `clawdbot.webhook`) -- `clawdbot.webhook.duration_ms` (histogram, attrs: `clawdbot.channel`, - `clawdbot.webhook`) -- `clawdbot.message.queued` (counter, attrs: `clawdbot.channel`, - `clawdbot.source`) -- `clawdbot.message.processed` (counter, attrs: `clawdbot.channel`, - `clawdbot.outcome`) -- `clawdbot.message.duration_ms` (histogram, attrs: `clawdbot.channel`, - `clawdbot.outcome`) +- `moltbot.webhook.received` (counter, attrs: `moltbot.channel`, + `moltbot.webhook`) +- `moltbot.webhook.error` (counter, attrs: `moltbot.channel`, + `moltbot.webhook`) +- `moltbot.webhook.duration_ms` (histogram, attrs: `moltbot.channel`, + `moltbot.webhook`) +- `moltbot.message.queued` (counter, attrs: `moltbot.channel`, + `moltbot.source`) +- `moltbot.message.processed` (counter, attrs: `moltbot.channel`, + `moltbot.outcome`) +- `moltbot.message.duration_ms` (histogram, attrs: `moltbot.channel`, + `moltbot.outcome`) Queues + sessions: -- `clawdbot.queue.lane.enqueue` (counter, attrs: `clawdbot.lane`) -- `clawdbot.queue.lane.dequeue` (counter, attrs: `clawdbot.lane`) -- `clawdbot.queue.depth` (histogram, attrs: `clawdbot.lane` or - `clawdbot.channel=heartbeat`) -- `clawdbot.queue.wait_ms` (histogram, attrs: `clawdbot.lane`) -- `clawdbot.session.state` (counter, attrs: `clawdbot.state`, `clawdbot.reason`) -- `clawdbot.session.stuck` (counter, attrs: `clawdbot.state`) -- `clawdbot.session.stuck_age_ms` (histogram, attrs: `clawdbot.state`) -- `clawdbot.run.attempt` (counter, attrs: `clawdbot.attempt`) +- `moltbot.queue.lane.enqueue` (counter, attrs: `moltbot.lane`) +- `moltbot.queue.lane.dequeue` (counter, attrs: `moltbot.lane`) +- `moltbot.queue.depth` (histogram, attrs: `moltbot.lane` or + `moltbot.channel=heartbeat`) +- `moltbot.queue.wait_ms` (histogram, attrs: `moltbot.lane`) +- `moltbot.session.state` (counter, attrs: `moltbot.state`, `moltbot.reason`) +- `moltbot.session.stuck` (counter, attrs: `moltbot.state`) +- `moltbot.session.stuck_age_ms` (histogram, attrs: `moltbot.state`) +- `moltbot.run.attempt` (counter, attrs: `moltbot.attempt`) ### Exported spans (names + key attributes) -- `clawdbot.model.usage` - - `clawdbot.channel`, `clawdbot.provider`, `clawdbot.model` - - `clawdbot.sessionKey`, `clawdbot.sessionId` - - `clawdbot.tokens.*` (input/output/cache_read/cache_write/total) -- `clawdbot.webhook.processed` - - `clawdbot.channel`, `clawdbot.webhook`, `clawdbot.chatId` -- `clawdbot.webhook.error` - - `clawdbot.channel`, `clawdbot.webhook`, `clawdbot.chatId`, - `clawdbot.error` -- `clawdbot.message.processed` - - `clawdbot.channel`, `clawdbot.outcome`, `clawdbot.chatId`, - `clawdbot.messageId`, `clawdbot.sessionKey`, `clawdbot.sessionId`, - `clawdbot.reason` -- `clawdbot.session.stuck` - - `clawdbot.state`, `clawdbot.ageMs`, `clawdbot.queueDepth`, - `clawdbot.sessionKey`, `clawdbot.sessionId` +- `moltbot.model.usage` + - `moltbot.channel`, `moltbot.provider`, `moltbot.model` + - `moltbot.sessionKey`, `moltbot.sessionId` + - `moltbot.tokens.*` (input/output/cache_read/cache_write/total) +- `moltbot.webhook.processed` + - `moltbot.channel`, `moltbot.webhook`, `moltbot.chatId` +- `moltbot.webhook.error` + - `moltbot.channel`, `moltbot.webhook`, `moltbot.chatId`, + `moltbot.error` +- `moltbot.message.processed` + - `moltbot.channel`, `moltbot.outcome`, `moltbot.chatId`, + `moltbot.messageId`, `moltbot.sessionKey`, `moltbot.sessionId`, + `moltbot.reason` +- `moltbot.session.stuck` + - `moltbot.state`, `moltbot.ageMs`, `moltbot.queueDepth`, + `moltbot.sessionKey`, `moltbot.sessionId` ### Sampling + flushing @@ -337,7 +337,7 @@ Queues + sessions: ## Troubleshooting tips -- **Gateway not reachable?** Run `clawdbot doctor` first. +- **Gateway not reachable?** Run `moltbot doctor` first. - **Logs empty?** Check that the Gateway is running and writing to the file path in `logging.file`. - **Need more detail?** Set `logging.level` to `debug` or `trace` and retry. diff --git a/docs/multi-agent-sandbox-tools.md b/docs/multi-agent-sandbox-tools.md index 892c5d92d..ff00df93f 100644 --- a/docs/multi-agent-sandbox-tools.md +++ b/docs/multi-agent-sandbox-tools.md @@ -31,7 +31,7 @@ Credentials are **not** shared between agents. Never reuse `agentDir` across age If you want to share creds, copy `auth-profiles.json` into the other agent's `agentDir`. For how sandboxing behaves at runtime, see [Sandboxing](/gateway/sandboxing). -For debugging “why is this blocked?”, see [Sandbox vs Tool Policy vs Elevated](/gateway/sandbox-vs-tool-policy-vs-elevated) and `clawdbot sandbox explain`. +For debugging “why is this blocked?”, see [Sandbox vs Tool Policy vs Elevated](/gateway/sandbox-vs-tool-policy-vs-elevated) and `moltbot sandbox explain`. --- @@ -225,7 +225,7 @@ Tool policies (global, agent, sandbox) support `group:*` entries that expand to - `group:automation`: `cron`, `gateway` - `group:messaging`: `message` - `group:nodes`: `nodes` -- `group:clawdbot`: all built-in Clawdbot tools (excludes provider plugins) +- `group:moltbot`: all built-in Moltbot tools (excludes provider plugins) ### Elevated Mode `tools.elevated` is the global baseline (sender-based allowlist). `agents.list[].tools.elevated` can further restrict elevated for specific agents (both must allow). @@ -278,7 +278,7 @@ Mitigation patterns: } ``` -Legacy `agent.*` configs are migrated by `clawdbot doctor`; prefer `agents.defaults` + `agents.list` going forward. +Legacy `agent.*` configs are migrated by `moltbot doctor`; prefer `agents.defaults` + `agents.list` going forward. --- @@ -331,12 +331,12 @@ After configuring multi-agent sandbox and tools: 1. **Check agent resolution:** ```exec - clawdbot agents list --bindings + moltbot agents list --bindings ``` 2. **Verify sandbox containers:** ```exec - docker ps --filter "label=clawdbot.sandbox=1" + docker ps --filter "label=moltbot.sandbox=1" ``` 3. **Test tool restrictions:** diff --git a/docs/network.md b/docs/network.md index 155727667..8b8e5d1af 100644 --- a/docs/network.md +++ b/docs/network.md @@ -7,7 +7,7 @@ read_when: --- # Network hub -This hub links the core docs for how Clawdbot connects, pairs, and secures +This hub links the core docs for how Moltbot connects, pairs, and secures devices across localhost, LAN, and tailnet. ## Core model diff --git a/docs/nodes/audio.md b/docs/nodes/audio.md index 90eff623a..194948eaf 100644 --- a/docs/nodes/audio.md +++ b/docs/nodes/audio.md @@ -6,7 +6,7 @@ read_when: # Audio / Voice Notes — 2026-01-17 ## What works -- **Media understanding (audio)**: If audio understanding is enabled (or auto‑detected), Clawdbot: +- **Media understanding (audio)**: If audio understanding is enabled (or auto‑detected), Moltbot: 1) Locates the first audio attachment (local path or URL) and downloads it if needed. 2) Enforces `maxBytes` before sending to each model entry. 3) Runs the first eligible model entry in order (provider or CLI). @@ -17,7 +17,7 @@ read_when: ## Auto-detection (default) If you **don’t configure models** and `tools.media.audio.enabled` is **not** set to `false`, -Clawdbot auto-detects in this order and stops at the first working option: +Moltbot auto-detects in this order and stops at the first working option: 1) **Local CLIs** (if installed) - `sherpa-onnx-offline` (requires `SHERPA_ONNX_MODEL_DIR` with encoder/decoder/joiner/tokens) diff --git a/docs/nodes/camera.md b/docs/nodes/camera.md index 6b0f408d3..9f3c46dec 100644 --- a/docs/nodes/camera.md +++ b/docs/nodes/camera.md @@ -7,7 +7,7 @@ read_when: # Camera capture (agent) -Clawdbot supports **camera capture** for agent workflows: +Moltbot supports **camera capture** for agent workflows: - **iOS node** (paired via Gateway): capture a **photo** (`jpg`) or **short video clip** (`mp4`, with optional audio) via `node.invoke`. - **Android node** (paired via Gateway): capture a **photo** (`jpg`) or **short video clip** (`mp4`, with optional audio) via `node.invoke`. @@ -67,10 +67,10 @@ The easiest way to get attachments is via the CLI helper, which writes decoded m Examples: ```bash -clawdbot nodes camera snap --node # default: both front + back (2 MEDIA lines) -clawdbot nodes camera snap --node --facing front -clawdbot nodes camera clip --node --duration 3000 -clawdbot nodes camera clip --node --no-audio +moltbot nodes camera snap --node # default: both front + back (2 MEDIA lines) +moltbot nodes camera snap --node --facing front +moltbot nodes camera clip --node --duration 3000 +moltbot nodes camera clip --node --no-audio ``` Notes: @@ -108,30 +108,30 @@ Photos are recompressed to keep the base64 payload under 5 MB. The macOS companion app exposes a checkbox: -- **Settings → General → Allow Camera** (`clawdbot.cameraEnabled`) +- **Settings → General → Allow Camera** (`moltbot.cameraEnabled`) - Default: **off** - When off: camera requests return “Camera disabled by user”. ### CLI helper (node invoke) -Use the main `clawdbot` CLI to invoke camera commands on the macOS node. +Use the main `moltbot` CLI to invoke camera commands on the macOS node. Examples: ```bash -clawdbot nodes camera list --node # list camera ids -clawdbot nodes camera snap --node # prints MEDIA: -clawdbot nodes camera snap --node --max-width 1280 -clawdbot nodes camera snap --node --delay-ms 2000 -clawdbot nodes camera snap --node --device-id -clawdbot nodes camera clip --node --duration 10s # prints MEDIA: -clawdbot nodes camera clip --node --duration-ms 3000 # prints MEDIA: (legacy flag) -clawdbot nodes camera clip --node --device-id -clawdbot nodes camera clip --node --no-audio +moltbot nodes camera list --node # list camera ids +moltbot nodes camera snap --node # prints MEDIA: +moltbot nodes camera snap --node --max-width 1280 +moltbot nodes camera snap --node --delay-ms 2000 +moltbot nodes camera snap --node --device-id +moltbot nodes camera clip --node --duration 10s # prints MEDIA: +moltbot nodes camera clip --node --duration-ms 3000 # prints MEDIA: (legacy flag) +moltbot nodes camera clip --node --device-id +moltbot nodes camera clip --node --no-audio ``` Notes: -- `clawdbot nodes camera snap` defaults to `maxWidth=1600` unless overridden. +- `moltbot nodes camera snap` defaults to `maxWidth=1600` unless overridden. - On macOS, `camera.snap` waits `delayMs` (default 2000ms) after warm-up/exposure settle before capturing. - Photo payloads are recompressed to keep base64 under 5 MB. @@ -145,7 +145,7 @@ Notes: For *screen* video (not camera), use the macOS companion: ```bash -clawdbot nodes screen record --node --duration 10s --fps 15 # prints MEDIA: +moltbot nodes screen record --node --duration 10s --fps 15 # prints MEDIA: ``` Notes: diff --git a/docs/nodes/images.md b/docs/nodes/images.md index bb9188738..953794f01 100644 --- a/docs/nodes/images.md +++ b/docs/nodes/images.md @@ -8,12 +8,12 @@ read_when: The WhatsApp channel runs via **Baileys Web**. This document captures the current media handling rules for send, gateway, and agent replies. ## Goals -- Send media with optional captions via `clawdbot message send --media`. +- Send media with optional captions via `moltbot message send --media`. - Allow auto-replies from the web inbox to include media alongside text. - Keep per-type limits sane and predictable. ## CLI Surface -- `clawdbot message send --media [--message ]` +- `moltbot message send --media [--message ]` - `--media` optional; caption can be empty for media-only sends. - `--dry-run` prints the resolved payload; `--json` emits `{ channel, to, messageId, mediaUrl, caption }`. @@ -30,11 +30,11 @@ The WhatsApp channel runs via **Baileys Web**. This document captures the curren ## Auto-Reply Pipeline - `getReplyFromConfig` returns `{ text?, mediaUrl?, mediaUrls? }`. -- When media is present, the web sender resolves local paths or URLs using the same pipeline as `clawdbot message send`. +- When media is present, the web sender resolves local paths or URLs using the same pipeline as `moltbot message send`. - Multiple media entries are sent sequentially if provided. ## Inbound Media to Commands (Pi) -- When inbound web messages include media, Clawdbot downloads to a temp file and exposes templating variables: +- When inbound web messages include media, Moltbot downloads to a temp file and exposes templating variables: - `{{MediaUrl}}` pseudo-URL for the inbound media. - `{{MediaPath}}` local temp path written before running the command. - When a per-session Docker sandbox is enabled, inbound media is copied into the sandbox workspace and `MediaPath`/`MediaUrl` are rewritten to a relative path like `media/inbound/`. diff --git a/docs/nodes/index.md b/docs/nodes/index.md index 3608ae382..f713a7b21 100644 --- a/docs/nodes/index.md +++ b/docs/nodes/index.md @@ -12,7 +12,7 @@ A **node** is a companion device (macOS/iOS/Android/headless) that connects to t Legacy transport: [Bridge protocol](/gateway/bridge-protocol) (TCP JSONL; deprecated/removed for current nodes). -macOS can also run in **node mode**: the menubar app connects to the Gateway’s WS server and exposes its local canvas/camera commands as a node (so `clawdbot nodes …` works against this Mac). +macOS can also run in **node mode**: the menubar app connects to the Gateway’s WS server and exposes its local canvas/camera commands as a node (so `moltbot nodes …` works against this Mac). Notes: - Nodes are **peripherals**, not gateways. They don’t run the gateway service. @@ -26,16 +26,16 @@ creates a device pairing request for `role: node`. Approve via the devices CLI ( Quick CLI: ```bash -clawdbot devices list -clawdbot devices approve -clawdbot devices reject -clawdbot nodes status -clawdbot nodes describe --node +moltbot devices list +moltbot devices approve +moltbot devices reject +moltbot nodes status +moltbot nodes describe --node ``` Notes: - `nodes status` marks a node as **paired** when its device pairing role includes `node`. -- `node.pair.*` (CLI: `clawdbot nodes pending/approve/reject`) is a separate gateway-owned +- `node.pair.*` (CLI: `moltbot nodes pending/approve/reject`) is a separate gateway-owned node pairing store; it does **not** gate the WS `connect` handshake. ## Remote node host (system.run) @@ -54,14 +54,14 @@ forwards `exec` calls to the **node host** when `host=node` is selected. On the node machine: ```bash -clawdbot node run --host --port 18789 --display-name "Build Node" +moltbot node run --host --port 18789 --display-name "Build Node" ``` ### Start a node host (service) ```bash -clawdbot node install --host --port 18789 --display-name "Build Node" -clawdbot node restart +moltbot node install --host --port 18789 --display-name "Build Node" +moltbot node restart ``` ### Pair + name @@ -69,22 +69,22 @@ clawdbot node restart On the gateway host: ```bash -clawdbot nodes pending -clawdbot nodes approve -clawdbot nodes list +moltbot nodes pending +moltbot nodes approve +moltbot nodes list ``` Naming options: -- `--display-name` on `clawdbot node run` / `clawdbot node install` (persists in `~/.clawdbot/node.json` on the node). -- `clawdbot nodes rename --node --name "Build Node"` (gateway override). +- `--display-name` on `moltbot node run` / `moltbot node install` (persists in `~/.clawdbot/node.json` on the node). +- `moltbot nodes rename --node --name "Build Node"` (gateway override). ### Allowlist the commands Exec approvals are **per node host**. Add allowlist entries from the gateway: ```bash -clawdbot approvals allowlist add --node "/usr/bin/uname" -clawdbot approvals allowlist add --node "/usr/bin/sw_vers" +moltbot approvals allowlist add --node "/usr/bin/uname" +moltbot approvals allowlist add --node "/usr/bin/sw_vers" ``` Approvals live on the node host at `~/.clawdbot/exec-approvals.json`. @@ -94,9 +94,9 @@ Approvals live on the node host at `~/.clawdbot/exec-approvals.json`. Configure defaults (gateway config): ```bash -clawdbot config set tools.exec.host node -clawdbot config set tools.exec.security allowlist -clawdbot config set tools.exec.node "" +moltbot config set tools.exec.host node +moltbot config set tools.exec.security allowlist +moltbot config set tools.exec.node "" ``` Or per session: @@ -118,7 +118,7 @@ Related: Low-level (raw RPC): ```bash -clawdbot nodes invoke --node --command canvas.eval --params '{"javaScript":"location.href"}' +moltbot nodes invoke --node --command canvas.eval --params '{"javaScript":"location.href"}' ``` Higher-level helpers exist for the common “give the agent a MEDIA attachment” workflows. @@ -130,17 +130,17 @@ If the node is showing the Canvas (WebView), `canvas.snapshot` returns `{ format CLI helper (writes to a temp file and prints `MEDIA:`): ```bash -clawdbot nodes canvas snapshot --node --format png -clawdbot nodes canvas snapshot --node --format jpg --max-width 1200 --quality 0.9 +moltbot nodes canvas snapshot --node --format png +moltbot nodes canvas snapshot --node --format jpg --max-width 1200 --quality 0.9 ``` ### Canvas controls ```bash -clawdbot nodes canvas present --node --target https://example.com -clawdbot nodes canvas hide --node -clawdbot nodes canvas navigate https://example.com --node -clawdbot nodes canvas eval --node --js "document.title" +moltbot nodes canvas present --node --target https://example.com +moltbot nodes canvas hide --node +moltbot nodes canvas navigate https://example.com --node +moltbot nodes canvas eval --node --js "document.title" ``` Notes: @@ -150,9 +150,9 @@ Notes: ### A2UI (Canvas) ```bash -clawdbot nodes canvas a2ui push --node --text "Hello" -clawdbot nodes canvas a2ui push --node --jsonl ./payload.jsonl -clawdbot nodes canvas a2ui reset --node +moltbot nodes canvas a2ui push --node --text "Hello" +moltbot nodes canvas a2ui push --node --jsonl ./payload.jsonl +moltbot nodes canvas a2ui reset --node ``` Notes: @@ -163,16 +163,16 @@ Notes: Photos (`jpg`): ```bash -clawdbot nodes camera list --node -clawdbot nodes camera snap --node # default: both facings (2 MEDIA lines) -clawdbot nodes camera snap --node --facing front +moltbot nodes camera list --node +moltbot nodes camera snap --node # default: both facings (2 MEDIA lines) +moltbot nodes camera snap --node --facing front ``` Video clips (`mp4`): ```bash -clawdbot nodes camera clip --node --duration 10s -clawdbot nodes camera clip --node --duration 3000 --no-audio +moltbot nodes camera clip --node --duration 10s +moltbot nodes camera clip --node --duration 3000 --no-audio ``` Notes: @@ -185,8 +185,8 @@ Notes: Nodes expose `screen.record` (mp4). Example: ```bash -clawdbot nodes screen record --node --duration 10s --fps 10 -clawdbot nodes screen record --node --duration 10s --fps 10 --no-audio +moltbot nodes screen record --node --duration 10s --fps 10 +moltbot nodes screen record --node --duration 10s --fps 10 --no-audio ``` Notes: @@ -203,8 +203,8 @@ Nodes expose `location.get` when Location is enabled in settings. CLI helper: ```bash -clawdbot nodes location get --node -clawdbot nodes location get --node --accuracy precise --max-age 15000 --location-timeout 10000 +moltbot nodes location get --node +moltbot nodes location get --node --accuracy precise --max-age 15000 --location-timeout 10000 ``` Notes: @@ -219,7 +219,7 @@ Android nodes can expose `sms.send` when the user grants **SMS** permission and Low-level invoke: ```bash -clawdbot nodes invoke --node --command sms.send --params '{"to":"+15555550123","message":"Hello from Clawdbot"}' +moltbot nodes invoke --node --command sms.send --params '{"to":"+15555550123","message":"Hello from Moltbot"}' ``` Notes: @@ -234,8 +234,8 @@ The headless node host exposes `system.run`, `system.which`, and `system.execApp Examples: ```bash -clawdbot nodes run --node -- echo "Hello from mac node" -clawdbot nodes notify --node --title "Ping" --body "Gateway ready" +moltbot nodes run --node -- echo "Hello from mac node" +moltbot nodes notify --node --title "Ping" --body "Gateway ready" ``` Notes: @@ -256,21 +256,21 @@ This sets the default node for `exec host=node` (and can be overridden per agent Global default: ```bash -clawdbot config set tools.exec.node "node-id-or-name" +moltbot config set tools.exec.node "node-id-or-name" ``` Per-agent override: ```bash -clawdbot config get agents.list -clawdbot config set agents.list[0].tools.exec.node "node-id-or-name" +moltbot config get agents.list +moltbot config set agents.list[0].tools.exec.node "node-id-or-name" ``` Unset to allow any node: ```bash -clawdbot config unset tools.exec.node -clawdbot config unset agents.list[0].tools.exec.node +moltbot config unset tools.exec.node +moltbot config unset agents.list[0].tools.exec.node ``` ## Permissions map @@ -279,14 +279,14 @@ Nodes may include a `permissions` map in `node.list` / `node.describe`, keyed by ## Headless node host (cross-platform) -Clawdbot can run a **headless node host** (no UI) that connects to the Gateway +Moltbot can run a **headless node host** (no UI) that connects to the Gateway WebSocket and exposes `system.run` / `system.which`. This is useful on Linux/Windows or for running a minimal node alongside a server. Start it: ```bash -clawdbot node run --host --port 18789 +moltbot node run --host --port 18789 ``` Notes: @@ -301,5 +301,5 @@ Notes: ## Mac node mode -- The macOS menubar app connects to the Gateway WS server as a node (so `clawdbot nodes …` works against this Mac). +- The macOS menubar app connects to the Gateway WS server as a node (so `moltbot nodes …` works against this Mac). - In remote mode, the app opens an SSH tunnel for the Gateway port and connects to `localhost`. diff --git a/docs/nodes/location-command.md b/docs/nodes/location-command.md index 79ba38841..475af735f 100644 --- a/docs/nodes/location-command.md +++ b/docs/nodes/location-command.md @@ -85,11 +85,11 @@ Notes: ## Model/tooling integration - Tool surface: `nodes` tool adds `location_get` action (node required). -- CLI: `clawdbot nodes location get --node `. +- CLI: `moltbot nodes location get --node `. - Agent guidelines: only call when user enabled location and understands the scope. ## UX copy (suggested) - Off: “Location sharing is disabled.” -- While Using: “Only when Clawdbot is open.” +- While Using: “Only when Moltbot is open.” - Always: “Allow background location. Requires system permission.” - Precise: “Use precise GPS location. Toggle off to share approximate location.” diff --git a/docs/nodes/media-understanding.md b/docs/nodes/media-understanding.md index 4c6208b8b..6bb13fb54 100644 --- a/docs/nodes/media-understanding.md +++ b/docs/nodes/media-understanding.md @@ -6,7 +6,7 @@ read_when: --- # Media Understanding (Inbound) — 2026-01-17 -Clawdbot can **summarize inbound media** (image/audio/video) before the reply pipeline runs. It auto‑detects when local tools or provider keys are available, and can be disabled or customized. If understanding is off, models still receive the original files/URLs as usual. +Moltbot can **summarize inbound media** (image/audio/video) before the reply pipeline runs. It auto‑detects when local tools or provider keys are available, and can be disabled or customized. If understanding is off, models still receive the original files/URLs as usual. ## Goals - Optional: pre‑digest inbound media into short text for faster routing + better command parsing. @@ -106,12 +106,12 @@ Rules: - If media exceeds `maxBytes`, that model is skipped and the **next model is tried**. - If the model returns more than `maxChars`, output is trimmed. - `prompt` defaults to simple “Describe the {media}.” plus the `maxChars` guidance (image/video only). -- If `.enabled: true` but no models are configured, Clawdbot tries the +- If `.enabled: true` but no models are configured, Moltbot tries the **active reply model** when its provider supports the capability. ### Auto-detect media understanding (default) If `tools.media..enabled` is **not** set to `false` and you haven’t -configured models, Clawdbot auto-detects in this order and **stops at the first +configured models, Moltbot auto-detects in this order and **stops at the first working option**: 1) **Local CLIs** (audio only; if installed) @@ -140,7 +140,7 @@ Note: Binary detection is best-effort across macOS/Linux/Windows; ensure the CLI ## Capabilities (optional) If you set `capabilities`, the entry only runs for those media types. For shared -lists, Clawdbot can infer defaults: +lists, Moltbot can infer defaults: - `openai`, `anthropic`, `minimax`: **image** - `google` (Gemini API): **image + audio + video** - `groq`: **audio** @@ -149,7 +149,7 @@ lists, Clawdbot can infer defaults: For CLI entries, **set `capabilities` explicitly** to avoid surprising matches. If you omit `capabilities`, the entry is eligible for the list it appears in. -## Provider support matrix (Clawdbot integrations) +## Provider support matrix (Moltbot integrations) | Capability | Provider integration | Notes | |------------|----------------------|-------| | Image | OpenAI / Anthropic / Google / others via `pi-ai` | Any image-capable model in the registry works. | diff --git a/docs/nodes/talk.md b/docs/nodes/talk.md index a0c723397..51be7d328 100644 --- a/docs/nodes/talk.md +++ b/docs/nodes/talk.md @@ -40,7 +40,7 @@ Supported keys: - `seed`, `normalize`, `lang`, `output_format`, `latency_tier` - `once` -## Config (`~/.clawdbot/clawdbot.json`) +## Config (`~/.clawdbot/moltbot.json`) ```json5 { "talk": { diff --git a/docs/nodes/voicewake.md b/docs/nodes/voicewake.md index 224e3b8b9..647481719 100644 --- a/docs/nodes/voicewake.md +++ b/docs/nodes/voicewake.md @@ -6,7 +6,7 @@ read_when: --- # Voice Wake (Global Wake Words) -Clawdbot treats **wake words as a single global list** owned by the **Gateway**. +Moltbot treats **wake words as a single global list** owned by the **Gateway**. - There are **no per-node custom wake words**. - **Any node/app UI may edit** the list; changes are persisted by the Gateway and broadcast to everyone. diff --git a/docs/northflank.mdx b/docs/northflank.mdx index aae9c6a22..15d745c4b 100644 --- a/docs/northflank.mdx +++ b/docs/northflank.mdx @@ -2,25 +2,25 @@ title: Deploy on Northflank --- -Deploy Clawdbot on Northflank with a one-click template and finish setup in your browser. +Deploy Moltbot on Northflank with a one-click template and finish setup in your browser. This is the easiest “no terminal on the server” path: Northflank runs the Gateway for you, and you configure everything via the `/setup` web wizard. ## How to get started -1. Click [Deploy Clawdbot](https://northflank.com/stacks/deploy-clawdbot) to open the template. +1. Click [Deploy Moltbot](https://northflank.com/stacks/deploy-moltbot) to open the template. 2. Create an [account on Northflank](https://app.northflank.com/signup) if you don’t already have one. -3. Click **Deploy Clawdbot now**. +3. Click **Deploy Moltbot now**. 4. Set the required environment variable: `SETUP_PASSWORD`. -5. Click **Deploy stack** to build and run the Clawdbot template. +5. Click **Deploy stack** to build and run the Moltbot template. 6. Wait for the deployment to complete, then click **View resources**. -7. Open the Clawdbot service. -8. Open the public Clawdbot URL and complete setup at `/setup`. -9. Open the Control UI at `/clawdbot`. +7. Open the Moltbot service. +8. Open the public Moltbot URL and complete setup at `/setup`. +9. Open the Control UI at `/moltbot`. ## What you get -- Hosted Clawdbot Gateway + Control UI +- Hosted Moltbot Gateway + Control UI - Web setup wizard at `/setup` (no terminal commands) - Persistent storage via Northflank Volume (`/data`) so config/credentials/workspace survive redeploys @@ -30,7 +30,7 @@ and you configure everything via the `/setup` web wizard. 2) Choose a model/auth provider and paste your key. 3) (Optional) Add Telegram/Discord/Slack tokens. 4) Click **Run setup**. -5) Open the Control UI at `https:///clawdbot` +5) Open the Control UI at `https:///moltbot` If Telegram DMs are set to pairing, the setup wizard can approve the pairing code. diff --git a/docs/perplexity.md b/docs/perplexity.md index 29434e2db..3faacd812 100644 --- a/docs/perplexity.md +++ b/docs/perplexity.md @@ -7,7 +7,7 @@ read_when: # Perplexity Sonar -Clawdbot can use Perplexity Sonar for the `web_search` tool. You can connect +Moltbot can use Perplexity Sonar for the `web_search` tool. You can connect through Perplexity’s direct API or via OpenRouter. ## API options @@ -64,7 +64,7 @@ If both `PERPLEXITY_API_KEY` and `OPENROUTER_API_KEY` are set, set `tools.web.search.perplexity.baseUrl` (or `tools.web.search.perplexity.apiKey`) to disambiguate. -If no base URL is set, Clawdbot chooses a default based on the API key source: +If no base URL is set, Moltbot chooses a default based on the API key source: - `PERPLEXITY_API_KEY` or `pplx-...` → direct Perplexity (`https://api.perplexity.ai`) - `OPENROUTER_API_KEY` or `sk-or-...` → OpenRouter (`https://openrouter.ai/api/v1`) diff --git a/docs/platforms/android.md b/docs/platforms/android.md index 55b3589b9..7a7a39afe 100644 --- a/docs/platforms/android.md +++ b/docs/platforms/android.md @@ -31,12 +31,12 @@ Android connects directly to the Gateway WebSocket (default `ws://:18789`) - Same LAN with mDNS/NSD, **or** - Same Tailscale tailnet using Wide-Area Bonjour / unicast DNS-SD (see below), **or** - Manual gateway host/port (fallback) -- You can run the CLI (`clawdbot`) on the gateway machine (or via SSH). +- You can run the CLI (`moltbot`) on the gateway machine (or via SSH). ### 1) Start the Gateway ```bash -clawdbot gateway --port 18789 --verbose +moltbot gateway --port 18789 --verbose ``` Confirm in logs you see something like: @@ -44,7 +44,7 @@ Confirm in logs you see something like: For tailnet-only setups (recommended for Vienna ⇄ London), bind the gateway to the tailnet IP: -- Set `gateway.bind: "tailnet"` in `~/.clawdbot/clawdbot.json` on the gateway host. +- Set `gateway.bind: "tailnet"` in `~/.clawdbot/moltbot.json` on the gateway host. - Restart the Gateway / macOS menubar app. ### 2) Verify discovery (optional) @@ -52,7 +52,7 @@ For tailnet-only setups (recommended for Vienna ⇄ London), bind the gateway to From the gateway machine: ```bash -dns-sd -B _clawdbot-gw._tcp local. +dns-sd -B _moltbot-gw._tcp local. ``` More debugging notes: [Bonjour](/gateway/bonjour). @@ -61,8 +61,8 @@ More debugging notes: [Bonjour](/gateway/bonjour). Android NSD/mDNS discovery won’t cross networks. If your Android node and the gateway are on different networks but connected via Tailscale, use Wide-Area Bonjour / unicast DNS-SD instead: -1) Set up a DNS-SD zone (example `clawdbot.internal.`) on the gateway host and publish `_clawdbot-gw._tcp` records. -2) Configure Tailscale split DNS for `clawdbot.internal` pointing at that DNS server. +1) Set up a DNS-SD zone (example `moltbot.internal.`) on the gateway host and publish `_moltbot-gw._tcp` records. +2) Configure Tailscale split DNS for `moltbot.internal` pointing at that DNS server. Details and example CoreDNS config: [Bonjour](/gateway/bonjour). @@ -84,8 +84,8 @@ After the first successful pairing, Android auto-reconnects on launch: On the gateway machine: ```bash -clawdbot nodes pending -clawdbot nodes approve +moltbot nodes pending +moltbot nodes approve ``` Pairing details: [Gateway pairing](/gateway/pairing). @@ -94,11 +94,11 @@ Pairing details: [Gateway pairing](/gateway/pairing). - Via nodes status: ```bash - clawdbot nodes status + moltbot nodes status ``` - Via Gateway: ```bash - clawdbot gateway call node.list --params "{}" + moltbot gateway call node.list --params "{}" ``` ### 6) Chat + history @@ -122,13 +122,13 @@ Note: nodes use the standalone canvas host on `canvasHost.port` (default `18793` 2) Navigate the node to it (LAN): ```bash -clawdbot nodes invoke --node "" --command canvas.navigate --params '{"url":"http://.local:18793/__clawdbot__/canvas/"}' +moltbot nodes invoke --node "" --command canvas.navigate --params '{"url":"http://.local:18793/__moltbot__/canvas/"}' ``` -Tailnet (optional): if both devices are on Tailscale, use a MagicDNS name or tailnet IP instead of `.local`, e.g. `http://:18793/__clawdbot__/canvas/`. +Tailnet (optional): if both devices are on Tailscale, use a MagicDNS name or tailnet IP instead of `.local`, e.g. `http://:18793/__moltbot__/canvas/`. This server injects a live-reload client into HTML and reloads on file changes. -The A2UI host lives at `http://:18793/__clawdbot__/a2ui/`. +The A2UI host lives at `http://:18793/__moltbot__/a2ui/`. Canvas commands (foreground only): - `canvas.eval`, `canvas.snapshot`, `canvas.navigate` (use `{"url":""}` or `{"url":"/"}` to return to the default scaffold). `canvas.snapshot` returns `{ format, base64 }` (default `format="jpeg"`). diff --git a/docs/platforms/digitalocean.md b/docs/platforms/digitalocean.md index afefe3676..e890c2c9f 100644 --- a/docs/platforms/digitalocean.md +++ b/docs/platforms/digitalocean.md @@ -1,15 +1,15 @@ --- -summary: "Clawdbot on DigitalOcean (simple paid VPS option)" +summary: "Moltbot on DigitalOcean (simple paid VPS option)" read_when: - - Setting up Clawdbot on DigitalOcean - - Looking for cheap VPS hosting for Clawdbot + - Setting up Moltbot on DigitalOcean + - Looking for cheap VPS hosting for Moltbot --- -# Clawdbot on DigitalOcean +# Moltbot on DigitalOcean ## Goal -Run a persistent Clawdbot Gateway on DigitalOcean for **$6/month** (or $4/mo with reserved pricing). +Run a persistent Moltbot Gateway on DigitalOcean for **$6/month** (or $4/mo with reserved pricing). If you want a $0/month option and don’t mind ARM + provider-specific setup, see the [Oracle Cloud guide](/platforms/oracle). @@ -54,7 +54,7 @@ If you want a $0/month option and don’t mind ARM + provider-specific setup, se ssh root@YOUR_DROPLET_IP ``` -## 3) Install Clawdbot +## 3) Install Moltbot ```bash # Update system @@ -64,17 +64,17 @@ apt update && apt upgrade -y curl -fsSL https://deb.nodesource.com/setup_22.x | bash - apt install -y nodejs -# Install Clawdbot -curl -fsSL https://clawd.bot/install.sh | bash +# Install Moltbot +curl -fsSL https://molt.bot/install.sh | bash # Verify -clawdbot --version +moltbot --version ``` ## 4) Run Onboarding ```bash -clawdbot onboard --install-daemon +moltbot onboard --install-daemon ``` The wizard will walk you through: @@ -87,13 +87,13 @@ The wizard will walk you through: ```bash # Check status -clawdbot status +moltbot status # Check service -systemctl --user status clawdbot-gateway.service +systemctl --user status moltbot-gateway.service # View logs -journalctl --user -u clawdbot-gateway.service -f +journalctl --user -u moltbot-gateway.service -f ``` ## 6) Access the Dashboard @@ -115,8 +115,8 @@ curl -fsSL https://tailscale.com/install.sh | sh tailscale up # Configure Gateway to use Tailscale Serve -clawdbot config set gateway.tailscale.mode serve -clawdbot gateway restart +moltbot config set gateway.tailscale.mode serve +moltbot gateway restart ``` Open: `https:///` @@ -127,8 +127,8 @@ Notes: **Option C: Tailnet bind (no Serve)** ```bash -clawdbot config set gateway.bind tailnet -clawdbot gateway restart +moltbot config set gateway.bind tailnet +moltbot gateway restart ``` Open: `http://:18789` (token required). @@ -137,13 +137,13 @@ Open: `http://:18789` (token required). ### Telegram ```bash -clawdbot pairing list telegram -clawdbot pairing approve telegram +moltbot pairing list telegram +moltbot pairing approve telegram ``` ### WhatsApp ```bash -clawdbot channels login whatsapp +moltbot channels login whatsapp # Scan QR code ``` @@ -185,7 +185,7 @@ All state lives in: These survive reboots. Back them up periodically: ```bash -tar -czvf clawdbot-backup.tar.gz ~/.clawdbot ~/clawd +tar -czvf moltbot-backup.tar.gz ~/.clawdbot ~/clawd ``` --- @@ -213,9 +213,9 @@ For the full setup guide, see [Oracle Cloud](/platforms/oracle). For signup tips ### Gateway won't start ```bash -clawdbot gateway status -clawdbot doctor --non-interactive -journalctl -u clawdbot --no-pager -n 50 +moltbot gateway status +moltbot doctor --non-interactive +journalctl -u moltbot --no-pager -n 50 ``` ### Port already in use diff --git a/docs/platforms/exe-dev.md b/docs/platforms/exe-dev.md index c4fcfdd76..796ddc374 100644 --- a/docs/platforms/exe-dev.md +++ b/docs/platforms/exe-dev.md @@ -1,5 +1,5 @@ --- -summary: "Run Clawdbot Gateway on exe.dev (VM + HTTPS proxy) for remote access" +summary: "Run Moltbot Gateway on exe.dev (VM + HTTPS proxy) for remote access" read_when: - You want a cheap always-on Linux host for the Gateway - You want remote Control UI access without running your own VPS @@ -7,43 +7,50 @@ read_when: # exe.dev -Goal: Clawdbot Gateway running on an exe.dev VM, reachable from your laptop via: -- **exe.dev HTTPS proxy** (easy, no tunnel) or -- **SSH tunnel** (most secure; loopback-only Gateway) +Goal: Moltbot Gateway running on an exe.dev VM, reachable from your laptop via: `https://.exe.xyz` -This page assumes **Ubuntu/Debian**. If you picked a different distro, map packages accordingly. - -If you’re on any other Linux VPS, the same steps apply — you just won’t use the exe.dev proxy commands. +This page assumes exe.dev's default **exeuntu** image. If you picked a different distro, map packages accordingly. ## Beginner quick path -1) Create VM → install Node 22 → install Clawdbot -2) Run `clawdbot onboard --install-daemon` -3) Tunnel from laptop (`ssh -N -L 18789:127.0.0.1:18789 …`) -4) Open `http://127.0.0.1:18789/` and paste your token +1) [https://exe.new/moltbot](https://exe.new/moltbot) +2) Fill in your auth key/token as needed +3) Click on "Agent" next to your VM, and wait... +4) ??? +5) Profit ## What you need -- exe.dev account + `ssh exe.dev` working on your laptop -- SSH keys set up (your laptop → exe.dev) -- Model auth (OAuth or API key) you want to use -- Provider credentials (optional): WhatsApp QR scan, Telegram bot token, Discord bot token, … +- exe.dev account +- `ssh exe.dev` access to [exe.dev](https://exe.dev) virtual machines (optional) + + +## Automated Install with Shelley + +Shelley, [exe.dev](https://exe.dev)'s agent, can install Moltbot instantly with our +prompt. The prompt used is as below: + +``` +Set up Moltbot (https://docs.molt.bot/install) on this VM. Use the non-interactive and accept-risk flags for moltbot onboarding. Add the supplied auth or token as needed. Configure nginx to forward from the default port 18789 to the root location on the default enabled site config, making sure to enable Websocket support. Pairing is done by "moltbot devices list" and "moltbot device approve ". Make sure the dashboard shows that Moltbot's health is OK. exe.dev handles forwarding from port 8000 to port 80/443 and HTTPS for us, so the final "reachable" should be .exe.xyz, without port specification. +``` + +## Manual installation ## 1) Create the VM -From your laptop: +From your device: ```bash -ssh exe.dev new --name=clawdbot +ssh exe.dev new ``` Then connect: ```bash -ssh clawdbot.exe.xyz +ssh .exe.xyz ``` -Tip: keep this VM **stateful**. Clawdbot stores state under `~/.clawdbot/` and `~/clawd/`. +Tip: keep this VM **stateful**. Moltbot stores state under `~/.clawdbot/` and `~/clawd/`. ## 2) Install prerequisites (on the VM) @@ -52,136 +59,67 @@ sudo apt-get update sudo apt-get install -y git curl jq ca-certificates openssl ``` -### Node 22 +## 3) Install Moltbot -Install Node **>= 22.12** (any method is fine). Quick check: +Run the Moltbot install script: ```bash -node -v +curl -fsSL https://molt.bot/install.sh | bash ``` -If you don’t already have Node 22 on the VM, use your preferred Node manager (nvm/mise/asdf) or a distro package source that provides Node 22+. +## 4) Setup nginx to proxy Moltbot to port 8000 -Common Ubuntu/Debian option (NodeSource): +Edit `/etc/nginx/sites-enabled/default` with -```bash -curl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash - -sudo apt-get install -y nodejs ``` +server { + listen 80 default_server; + listen [::]:80 default_server; + listen 8000; + listen [::]:8000; -## 3) Install Clawdbot + server_name _; -Recommended on servers: npm global install. + location / { + proxy_pass http://127.0.0.1:18789; + proxy_http_version 1.1; -```bash -npm i -g clawdbot@latest -clawdbot --version -``` + # WebSocket support + proxy_set_header Upgrade $http_upgrade; + proxy_set_header Connection "upgrade"; -If native deps fail to install (rare; usually `sharp`), add build tools: + # Standard proxy headers + proxy_set_header Host $host; + proxy_set_header X-Real-IP $remote_addr; + proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; + proxy_set_header X-Forwarded-Proto $scheme; -```bash -sudo apt-get install -y build-essential python3 -``` - -## 4) First-time setup (wizard) - -Run the onboarding wizard on the VM: - -```bash -clawdbot onboard --install-daemon -``` - -It can set up: -- `~/clawd` workspace bootstrap -- `~/.clawdbot/clawdbot.json` config -- model auth profiles -- model provider config/login -- Linux systemd **user** service (service) - -If you’re doing OAuth on a headless VM: do OAuth on a normal machine first, then copy the auth profile to the VM (see [Help](/help)). - -## 5) Remote access options - -### Option A (recommended): SSH tunnel (loopback-only) - -Keep Gateway on loopback (default) and tunnel it from your laptop: - -```bash -ssh -N -L 18789:127.0.0.1:18789 clawdbot.exe.xyz -``` - -Open locally: -- `http://127.0.0.1:18789/` (Control UI) - -Runbook: [Remote access](/gateway/remote) - -### Option B: exe.dev HTTPS proxy (no tunnel) - -To let exe.dev proxy traffic to the VM, bind the Gateway to the LAN interface and set a token: - -```bash -export CLAWDBOT_GATEWAY_TOKEN="$(openssl rand -hex 32)" -clawdbot gateway --bind lan --port 8080 --token "$CLAWDBOT_GATEWAY_TOKEN" -``` - -For service runs, persist it in `~/.clawdbot/clawdbot.json`: - -```json5 -{ - gateway: { - mode: "local", - port: 8080, - bind: "lan", - auth: { mode: "token", token: "YOUR_TOKEN" } - } + # Timeout settings for long-lived connections + proxy_read_timeout 86400s; + proxy_send_timeout 86400s; + } } ``` -Notes: -- Non-loopback binds require `gateway.auth.token` (or `CLAWDBOT_GATEWAY_TOKEN`). -- `gateway.remote.token` is only for remote CLI calls; it does not enable local auth. +## 5) Access Moltbot and grant privileges -Then point exe.dev’s proxy at `8080` (or whatever port you chose) and open your VM’s HTTPS URL: +Access `https://.exe.xyz/?token=YOUR-TOKEN-FROM-TERMINAL`. Approve +devices with `moltbot devices list` and `moltbot device approve`. When in doubt, +use Shelley from your browser! + +## Remote Access + +Remote access is handled by [exe.dev](https://exe.dev)'s authentication. By +default, HTTP traffic from port 8000 is forwarded to `https://.exe.xyz` +with email auth. + +## Updating ```bash -ssh exe.dev share port clawdbot 8080 -``` - -Open: -- `https://clawdbot.exe.xyz/` - -In the Control UI, paste the token (UI → Settings → token). The UI sends it as `connect.params.auth.token`. - -Notes: -- Prefer a **non-default** port (like `8080`) if your proxy expects an app port. -- Treat the token like a password. - -Control UI details: [Control UI](/web/control-ui) - -## 6) Keep it running (service) - -On Linux, Clawdbot uses a systemd **user** service. After `--install-daemon`, verify: - -```bash -systemctl --user status clawdbot-gateway[-].service -``` - -If the service dies after logout, enable lingering: - -```bash -sudo loginctl enable-linger "$USER" -``` - -More: [Linux](/platforms/linux) - -## 7) Updates - -```bash -npm i -g clawdbot@latest -clawdbot doctor -clawdbot gateway restart -clawdbot health +npm i -g moltbot@latest +moltbot doctor +moltbot gateway restart +moltbot health ``` Guide: [Updating](/install/updating) diff --git a/docs/platforms/fly.md b/docs/platforms/fly.md index dee731ea7..d8db124ac 100644 --- a/docs/platforms/fly.md +++ b/docs/platforms/fly.md @@ -1,11 +1,11 @@ --- title: Fly.io -description: Deploy Clawdbot on Fly.io +description: Deploy Moltbot on Fly.io --- # Fly.io Deployment -**Goal:** Clawdbot Gateway running on a [Fly.io](https://fly.io) machine with persistent storage, automatic HTTPS, and Discord/channel access. +**Goal:** Moltbot Gateway running on a [Fly.io](https://fly.io) machine with persistent storage, automatic HTTPS, and Discord/channel access. ## What you need @@ -25,14 +25,14 @@ description: Deploy Clawdbot on Fly.io ```bash # Clone the repo -git clone https://github.com/clawdbot/clawdbot.git -cd clawdbot +git clone https://github.com/moltbot/moltbot.git +cd moltbot # Create a new Fly app (pick your own name) -fly apps create my-clawdbot +fly apps create my-moltbot # Create a persistent volume (1GB is usually enough) -fly volumes create clawdbot_data --size 1 --region iad +fly volumes create moltbot_data --size 1 --region iad ``` **Tip:** Choose a region close to you. Common options: `lhr` (London), `iad` (Virginia), `sjc` (San Jose). @@ -44,7 +44,7 @@ Edit `fly.toml` to match your app name and requirements. **Security note:** The default config exposes a public URL. For a hardened deployment with no public IP, see [Private Deployment](#private-deployment-hardened) or use `fly.private.toml`. ```toml -app = "my-clawdbot" # Your app name +app = "my-moltbot" # Your app name primary_region = "iad" [build] @@ -72,7 +72,7 @@ primary_region = "iad" memory = "2048mb" [mounts] - source = "clawdbot_data" + source = "moltbot_data" destination = "/data" ``` @@ -106,7 +106,7 @@ fly secrets set DISCORD_BOT_TOKEN=MTQ... **Notes:** - Non-loopback binds (`--bind lan`) require `CLAWDBOT_GATEWAY_TOKEN` for security. - Treat these tokens like passwords. -- **Prefer env vars over config file** for all API keys and tokens. This keeps secrets out of `clawdbot.json` where they could be accidentally exposed or logged. +- **Prefer env vars over config file** for all API keys and tokens. This keeps secrets out of `moltbot.json` where they could be accidentally exposed or logged. ## 4) Deploy @@ -139,7 +139,7 @@ fly ssh console Create the config directory and file: ```bash mkdir -p /data -cat > /data/clawdbot.json << 'EOF' +cat > /data/moltbot.json << 'EOF' { "agents": { "defaults": { @@ -185,13 +185,13 @@ cat > /data/clawdbot.json << 'EOF' "bind": "auto" }, "meta": { - "lastTouchedVersion": "2026.1.25" + "lastTouchedVersion": "2026.1.27-beta.1" } } EOF ``` -**Note:** With `CLAWDBOT_STATE_DIR=/data`, the config path is `/data/clawdbot.json`. +**Note:** With `CLAWDBOT_STATE_DIR=/data`, the config path is `/data/moltbot.json`. **Note:** The Discord token can come from either: - Environment variable: `DISCORD_BOT_TOKEN` (recommended for secrets) @@ -214,7 +214,7 @@ Open in browser: fly open ``` -Or visit `https://my-clawdbot.fly.dev/` +Or visit `https://my-moltbot.fly.dev/` Paste your gateway token (the one from `CLAWDBOT_GATEWAY_TOKEN`) to authenticate. @@ -278,11 +278,11 @@ The lock file is at `/data/gateway.*.lock` (not in a subdirectory). ### Config Not Being Read -If using `--allow-unconfigured`, the gateway creates a minimal config. Your custom config at `/data/clawdbot.json` should be read on restart. +If using `--allow-unconfigured`, the gateway creates a minimal config. Your custom config at `/data/moltbot.json` should be read on restart. Verify the config exists: ```bash -fly ssh console --command "cat /data/clawdbot.json" +fly ssh console --command "cat /data/moltbot.json" ``` ### Writing Config via SSH @@ -291,16 +291,16 @@ The `fly ssh console -C` command doesn't support shell redirection. To write a c ```bash # Use echo + tee (pipe from local to remote) -echo '{"your":"config"}' | fly ssh console -C "tee /data/clawdbot.json" +echo '{"your":"config"}' | fly ssh console -C "tee /data/moltbot.json" # Or use sftp fly sftp shell -> put /local/path/config.json /data/clawdbot.json +> put /local/path/config.json /data/moltbot.json ``` **Note:** `fly sftp` may fail if the file already exists. Delete first: ```bash -fly ssh console --command "rm /data/clawdbot.json" +fly ssh console --command "rm /data/moltbot.json" ``` ### State Not Persisting @@ -366,18 +366,18 @@ Or convert an existing deployment: ```bash # List current IPs -fly ips list -a my-clawdbot +fly ips list -a my-moltbot # Release public IPs -fly ips release -a my-clawdbot -fly ips release -a my-clawdbot +fly ips release -a my-moltbot +fly ips release -a my-moltbot # Switch to private config so future deploys don't re-allocate public IPs # (remove [http_service] or deploy with the private template) fly deploy -c fly.private.toml # Allocate private-only IPv6 -fly ips allocate-v6 --private -a my-clawdbot +fly ips allocate-v6 --private -a my-moltbot ``` After this, `fly ips list` should show only a `private` type IP: @@ -393,7 +393,7 @@ Since there's no public URL, use one of these methods: **Option 1: Local proxy (simplest)** ```bash # Forward local port 3000 to the app -fly proxy 3000:3000 -a my-clawdbot +fly proxy 3000:3000 -a my-moltbot # Then open http://localhost:3000 in browser ``` @@ -409,7 +409,7 @@ fly wireguard create **Option 3: SSH only** ```bash -fly ssh console -a my-clawdbot +fly ssh console -a my-moltbot ``` ### Webhooks with private deployment diff --git a/docs/platforms/gcp.md b/docs/platforms/gcp.md index cffa03ace..6ad3825de 100644 --- a/docs/platforms/gcp.md +++ b/docs/platforms/gcp.md @@ -1,18 +1,18 @@ --- -summary: "Run Clawdbot Gateway 24/7 on a GCP Compute Engine VM (Docker) with durable state" +summary: "Run Moltbot Gateway 24/7 on a GCP Compute Engine VM (Docker) with durable state" read_when: - - You want Clawdbot running 24/7 on GCP + - You want Moltbot running 24/7 on GCP - You want a production-grade, always-on Gateway on your own VM - You want full control over persistence, binaries, and restart behavior --- -# Clawdbot on GCP Compute Engine (Docker, Production VPS Guide) +# Moltbot on GCP Compute Engine (Docker, Production VPS Guide) ## Goal -Run a persistent Clawdbot Gateway on a GCP Compute Engine VM using Docker, with durable state, baked-in binaries, and safe restart behavior. +Run a persistent Moltbot Gateway on a GCP Compute Engine VM using Docker, with durable state, baked-in binaries, and safe restart behavior. -If you want "Clawdbot 24/7 for ~$5-12/mo", this is a reliable setup on Google Cloud. +If you want "Moltbot 24/7 for ~$5-12/mo", this is a reliable setup on Google Cloud. Pricing varies by machine type and region; pick the smallest VM that fits your workload and scale up if you hit OOMs. ## What are we doing (simple terms)? @@ -20,7 +20,7 @@ Pricing varies by machine type and region; pick the smallest VM that fits your w - Create a GCP project and enable billing - Create a Compute Engine VM - Install Docker (isolated app runtime) -- Start the Clawdbot Gateway in Docker +- Start the Moltbot Gateway in Docker - Persist `~/.clawdbot` + `~/clawd` on the host (survives restarts/rebuilds) - Access the Control UI from your laptop via an SSH tunnel @@ -40,7 +40,7 @@ For the generic Docker flow, see [Docker](/install/docker). 2) Create Compute Engine VM (e2-small, Debian 12, 20GB) 3) SSH into the VM 4) Install Docker -5) Clone Clawdbot repository +5) Clone Moltbot repository 6) Create persistent host directories 7) Configure `.env` and `docker-compose.yml` 8) Bake required binaries, build, and launch @@ -87,8 +87,8 @@ All steps can be done via the web UI at https://console.cloud.google.com **CLI:** ```bash -gcloud projects create my-clawdbot-project --name="Clawdbot Gateway" -gcloud config set project my-clawdbot-project +gcloud projects create my-moltbot-project --name="Moltbot Gateway" +gcloud config set project my-moltbot-project ``` Enable billing at https://console.cloud.google.com/billing (required for Compute Engine). @@ -120,7 +120,7 @@ gcloud services enable compute.googleapis.com **CLI:** ```bash -gcloud compute instances create clawdbot-gateway \ +gcloud compute instances create moltbot-gateway \ --zone=us-central1-a \ --machine-type=e2-small \ --boot-disk-size=20GB \ @@ -131,7 +131,7 @@ gcloud compute instances create clawdbot-gateway \ **Console:** 1. Go to Compute Engine > VM instances > Create instance -2. Name: `clawdbot-gateway` +2. Name: `moltbot-gateway` 3. Region: `us-central1`, Zone: `us-central1-a` 4. Machine type: `e2-small` 5. Boot disk: Debian 12, 20GB @@ -144,7 +144,7 @@ gcloud compute instances create clawdbot-gateway \ **CLI:** ```bash -gcloud compute ssh clawdbot-gateway --zone=us-central1-a +gcloud compute ssh moltbot-gateway --zone=us-central1-a ``` **Console:** @@ -173,7 +173,7 @@ exit Then SSH back in: ```bash -gcloud compute ssh clawdbot-gateway --zone=us-central1-a +gcloud compute ssh moltbot-gateway --zone=us-central1-a ``` Verify: @@ -185,11 +185,11 @@ docker compose version --- -## 6) Clone the Clawdbot repository +## 6) Clone the Moltbot repository ```bash -git clone https://github.com/clawdbot/clawdbot.git -cd clawdbot +git clone https://github.com/moltbot/moltbot.git +cd moltbot ``` This guide assumes you will build a custom image to guarantee binary persistence. @@ -213,7 +213,7 @@ mkdir -p ~/clawd Create `.env` in the repository root. ```bash -CLAWDBOT_IMAGE=clawdbot:latest +CLAWDBOT_IMAGE=moltbot:latest CLAWDBOT_GATEWAY_TOKEN=change-me-now CLAWDBOT_GATEWAY_BIND=lan CLAWDBOT_GATEWAY_PORT=18789 @@ -241,7 +241,7 @@ Create or update `docker-compose.yml`. ```yaml services: - clawdbot-gateway: + moltbot-gateway: image: ${CLAWDBOT_IMAGE} build: . restart: unless-stopped @@ -347,15 +347,15 @@ CMD ["node","dist/index.js"] ```bash docker compose build -docker compose up -d clawdbot-gateway +docker compose up -d moltbot-gateway ``` Verify binaries: ```bash -docker compose exec clawdbot-gateway which gog -docker compose exec clawdbot-gateway which goplaces -docker compose exec clawdbot-gateway which wacli +docker compose exec moltbot-gateway which gog +docker compose exec moltbot-gateway which goplaces +docker compose exec moltbot-gateway which wacli ``` Expected output: @@ -371,7 +371,7 @@ Expected output: ## 12) Verify Gateway ```bash -docker compose logs -f clawdbot-gateway +docker compose logs -f moltbot-gateway ``` Success: @@ -387,7 +387,7 @@ Success: Create an SSH tunnel to forward the Gateway port: ```bash -gcloud compute ssh clawdbot-gateway --zone=us-central1-a -- -L 18789:127.0.0.1:18789 +gcloud compute ssh moltbot-gateway --zone=us-central1-a -- -L 18789:127.0.0.1:18789 ``` Open in your browser: @@ -400,12 +400,12 @@ Paste your gateway token. ## What persists where (source of truth) -Clawdbot runs in Docker, but Docker is not the source of truth. +Moltbot runs in Docker, but Docker is not the source of truth. All long-lived state must survive restarts, rebuilds, and reboots. | Component | Location | Persistence mechanism | Notes | |---|---|---|---| -| Gateway config | `/home/node/.clawdbot/` | Host volume mount | Includes `clawdbot.json`, tokens | +| Gateway config | `/home/node/.clawdbot/` | Host volume mount | Includes `moltbot.json`, tokens | | Model auth profiles | `/home/node/.clawdbot/` | Host volume mount | OAuth tokens, API keys | | Skill configs | `/home/node/.clawdbot/skills/` | Host volume mount | Skill-level state | | Agent workspace | `/home/node/clawd/` | Host volume mount | Code and agent artifacts | @@ -420,10 +420,10 @@ All long-lived state must survive restarts, rebuilds, and reboots. ## Updates -To update Clawdbot on the VM: +To update Moltbot on the VM: ```bash -cd ~/clawdbot +cd ~/moltbot git pull docker compose build docker compose up -d @@ -453,15 +453,15 @@ If using e2-micro and hitting OOM, upgrade to e2-small or e2-medium: ```bash # Stop the VM first -gcloud compute instances stop clawdbot-gateway --zone=us-central1-a +gcloud compute instances stop moltbot-gateway --zone=us-central1-a # Change machine type -gcloud compute instances set-machine-type clawdbot-gateway \ +gcloud compute instances set-machine-type moltbot-gateway \ --zone=us-central1-a \ --machine-type=e2-small # Start the VM -gcloud compute instances start clawdbot-gateway --zone=us-central1-a +gcloud compute instances start moltbot-gateway --zone=us-central1-a ``` --- @@ -474,14 +474,14 @@ For automation or CI/CD pipelines, create a dedicated service account with minim 1. Create a service account: ```bash - gcloud iam service-accounts create clawdbot-deploy \ - --display-name="Clawdbot Deployment" + gcloud iam service-accounts create moltbot-deploy \ + --display-name="Moltbot Deployment" ``` 2. Grant Compute Instance Admin role (or narrower custom role): ```bash - gcloud projects add-iam-policy-binding my-clawdbot-project \ - --member="serviceAccount:clawdbot-deploy@my-clawdbot-project.iam.gserviceaccount.com" \ + gcloud projects add-iam-policy-binding my-moltbot-project \ + --member="serviceAccount:moltbot-deploy@my-moltbot-project.iam.gserviceaccount.com" \ --role="roles/compute.instanceAdmin.v1" ``` diff --git a/docs/platforms/hetzner.md b/docs/platforms/hetzner.md index 4516040cc..695e72c7d 100644 --- a/docs/platforms/hetzner.md +++ b/docs/platforms/hetzner.md @@ -1,25 +1,25 @@ --- -summary: "Run Clawdbot Gateway 24/7 on a cheap Hetzner VPS (Docker) with durable state and baked-in binaries" +summary: "Run Moltbot Gateway 24/7 on a cheap Hetzner VPS (Docker) with durable state and baked-in binaries" read_when: - - You want Clawdbot running 24/7 on a cloud VPS (not your laptop) + - You want Moltbot running 24/7 on a cloud VPS (not your laptop) - You want a production-grade, always-on Gateway on your own VPS - You want full control over persistence, binaries, and restart behavior - - You are running Clawdbot in Docker on Hetzner or a similar provider + - You are running Moltbot in Docker on Hetzner or a similar provider --- -# Clawdbot on Hetzner (Docker, Production VPS Guide) +# Moltbot on Hetzner (Docker, Production VPS Guide) ## Goal -Run a persistent Clawdbot Gateway on a Hetzner VPS using Docker, with durable state, baked-in binaries, and safe restart behavior. +Run a persistent Moltbot Gateway on a Hetzner VPS using Docker, with durable state, baked-in binaries, and safe restart behavior. -If you want “Clawdbot 24/7 for ~$5”, this is the simplest reliable setup. +If you want “Moltbot 24/7 for ~$5”, this is the simplest reliable setup. Hetzner pricing changes; pick the smallest Debian/Ubuntu VPS and scale up if you hit OOMs. ## What are we doing (simple terms)? - Rent a small Linux server (Hetzner VPS) - Install Docker (isolated app runtime) -- Start the Clawdbot Gateway in Docker +- Start the Moltbot Gateway in Docker - Persist `~/.clawdbot` + `~/clawd` on the host (survives restarts/rebuilds) - Access the Control UI from your laptop via an SSH tunnel @@ -37,7 +37,7 @@ For the generic Docker flow, see [Docker](/install/docker). 1) Provision Hetzner VPS 2) Install Docker -3) Clone Clawdbot repository +3) Clone Moltbot repository 4) Create persistent host directories 5) Configure `.env` and `docker-compose.yml` 6) Bake required binaries into the image @@ -93,11 +93,11 @@ docker compose version --- -## 3) Clone the Clawdbot repository +## 3) Clone the Moltbot repository ```bash -git clone https://github.com/clawdbot/clawdbot.git -cd clawdbot +git clone https://github.com/moltbot/moltbot.git +cd moltbot ``` This guide assumes you will build a custom image to guarantee binary persistence. @@ -125,7 +125,7 @@ chown -R 1000:1000 /root/clawd Create `.env` in the repository root. ```bash -CLAWDBOT_IMAGE=clawdbot:latest +CLAWDBOT_IMAGE=moltbot:latest CLAWDBOT_GATEWAY_TOKEN=change-me-now CLAWDBOT_GATEWAY_BIND=lan CLAWDBOT_GATEWAY_PORT=18789 @@ -153,7 +153,7 @@ Create or update `docker-compose.yml`. ```yaml services: - clawdbot-gateway: + moltbot-gateway: image: ${CLAWDBOT_IMAGE} build: . restart: unless-stopped @@ -259,15 +259,15 @@ CMD ["node","dist/index.js"] ```bash docker compose build -docker compose up -d clawdbot-gateway +docker compose up -d moltbot-gateway ``` Verify binaries: ```bash -docker compose exec clawdbot-gateway which gog -docker compose exec clawdbot-gateway which goplaces -docker compose exec clawdbot-gateway which wacli +docker compose exec moltbot-gateway which gog +docker compose exec moltbot-gateway which goplaces +docker compose exec moltbot-gateway which wacli ``` Expected output: @@ -283,7 +283,7 @@ Expected output: ## 9) Verify Gateway ```bash -docker compose logs -f clawdbot-gateway +docker compose logs -f moltbot-gateway ``` Success: @@ -308,12 +308,12 @@ Paste your gateway token. ## What persists where (source of truth) -Clawdbot runs in Docker, but Docker is not the source of truth. +Moltbot runs in Docker, but Docker is not the source of truth. All long-lived state must survive restarts, rebuilds, and reboots. | Component | Location | Persistence mechanism | Notes | |---|---|---|---| -| Gateway config | `/home/node/.clawdbot/` | Host volume mount | Includes `clawdbot.json`, tokens | +| Gateway config | `/home/node/.clawdbot/` | Host volume mount | Includes `moltbot.json`, tokens | | Model auth profiles | `/home/node/.clawdbot/` | Host volume mount | OAuth tokens, API keys | | Skill configs | `/home/node/.clawdbot/skills/` | Host volume mount | Skill-level state | | Agent workspace | `/home/node/clawd/` | Host volume mount | Code and agent artifacts | diff --git a/docs/platforms/index.md b/docs/platforms/index.md index 3a1e87267..65eeac2ed 100644 --- a/docs/platforms/index.md +++ b/docs/platforms/index.md @@ -6,7 +6,7 @@ read_when: --- # Platforms -Clawdbot core is written in TypeScript. **Node is the recommended runtime**. +Moltbot core is written in TypeScript. **Node is the recommended runtime**. Bun is not recommended for the Gateway (WhatsApp/Telegram bugs). Companion apps exist for macOS (menu bar app) and mobile nodes (iOS/Android). Windows and @@ -34,17 +34,17 @@ Native companion apps for Windows are also planned; the Gateway is recommended v - Install guide: [Getting Started](/start/getting-started) - Gateway runbook: [Gateway](/gateway) - Gateway configuration: [Configuration](/gateway/configuration) -- Service status: `clawdbot gateway status` +- Service status: `moltbot gateway status` ## Gateway service install (CLI) Use one of these (all supported): -- Wizard (recommended): `clawdbot onboard --install-daemon` -- Direct: `clawdbot gateway install` -- Configure flow: `clawdbot configure` → select **Gateway service** -- Repair/migrate: `clawdbot doctor` (offers to install or fix the service) +- Wizard (recommended): `moltbot onboard --install-daemon` +- Direct: `moltbot gateway install` +- Configure flow: `moltbot configure` → select **Gateway service** +- Repair/migrate: `moltbot doctor` (offers to install or fix the service) The service target depends on OS: -- macOS: LaunchAgent (`com.clawdbot.gateway` or `com.clawdbot.`) -- Linux/WSL2: systemd user service (`clawdbot-gateway[-].service`) +- macOS: LaunchAgent (`bot.molt.gateway` or `bot.molt.`; legacy `com.clawdbot.*`) +- Linux/WSL2: systemd user service (`moltbot-gateway[-].service`) diff --git a/docs/platforms/ios.md b/docs/platforms/ios.md index 8d39ae181..ef644281c 100644 --- a/docs/platforms/ios.md +++ b/docs/platforms/ios.md @@ -20,7 +20,7 @@ Availability: internal preview. The iOS app is not publicly distributed yet. - Gateway running on another device (macOS, Linux, or Windows via WSL2). - Network path: - Same LAN via Bonjour, **or** - - Tailnet via unicast DNS-SD (`clawdbot.internal.`), **or** + - Tailnet via unicast DNS-SD (`moltbot.internal.`), **or** - Manual host/port (fallback). ## Quick start (pair + connect) @@ -28,7 +28,7 @@ Availability: internal preview. The iOS app is not publicly distributed yet. 1) Start the Gateway: ```bash -clawdbot gateway --port 18789 +moltbot gateway --port 18789 ``` 2) In the iOS app, open Settings and pick a discovered gateway (or enable Manual Host and enter host/port). @@ -36,26 +36,26 @@ clawdbot gateway --port 18789 3) Approve the pairing request on the gateway host: ```bash -clawdbot nodes pending -clawdbot nodes approve +moltbot nodes pending +moltbot nodes approve ``` 4) Verify connection: ```bash -clawdbot nodes status -clawdbot gateway call node.list --params "{}" +moltbot nodes status +moltbot gateway call node.list --params "{}" ``` ## Discovery paths ### Bonjour (LAN) -The Gateway advertises `_clawdbot._tcp` on `local.`. The iOS app lists these automatically. +The Gateway advertises `_moltbot._tcp` on `local.`. The iOS app lists these automatically. ### Tailnet (cross-network) -If mDNS is blocked, use a unicast DNS-SD zone (recommended domain: `clawdbot.internal.`) and Tailscale split DNS. +If mDNS is blocked, use a unicast DNS-SD zone (recommended domain: `moltbot.internal.`) and Tailscale split DNS. See [Bonjour](/gateway/bonjour) for the CoreDNS example. ### Manual host/port @@ -67,22 +67,22 @@ In Settings, enable **Manual Host** and enter the gateway host + port (default ` The iOS node renders a WKWebView canvas. Use `node.invoke` to drive it: ```bash -clawdbot nodes invoke --node "iOS Node" --command canvas.navigate --params '{"url":"http://:18793/__clawdbot__/canvas/"}' +moltbot nodes invoke --node "iOS Node" --command canvas.navigate --params '{"url":"http://:18793/__moltbot__/canvas/"}' ``` Notes: -- The Gateway canvas host serves `/__clawdbot__/canvas/` and `/__clawdbot__/a2ui/`. +- The Gateway canvas host serves `/__moltbot__/canvas/` and `/__moltbot__/a2ui/`. - The iOS node auto-navigates to A2UI on connect when a canvas host URL is advertised. - Return to the built-in scaffold with `canvas.navigate` and `{"url":""}`. ### Canvas eval / snapshot ```bash -clawdbot nodes invoke --node "iOS Node" --command canvas.eval --params '{"javaScript":"(() => { const {ctx} = window.__clawdbot; ctx.clearRect(0,0,innerWidth,innerHeight); ctx.lineWidth=6; ctx.strokeStyle=\"#ff2d55\"; ctx.beginPath(); ctx.moveTo(40,40); ctx.lineTo(innerWidth-40, innerHeight-40); ctx.stroke(); return \"ok\"; })()"}' +moltbot nodes invoke --node "iOS Node" --command canvas.eval --params '{"javaScript":"(() => { const {ctx} = window.__moltbot; ctx.clearRect(0,0,innerWidth,innerHeight); ctx.lineWidth=6; ctx.strokeStyle=\"#ff2d55\"; ctx.beginPath(); ctx.moveTo(40,40); ctx.lineTo(innerWidth-40, innerHeight-40); ctx.stroke(); return \"ok\"; })()"}' ``` ```bash -clawdbot nodes invoke --node "iOS Node" --command canvas.snapshot --params '{"maxWidth":900,"format":"jpeg"}' +moltbot nodes invoke --node "iOS Node" --command canvas.snapshot --params '{"maxWidth":900,"format":"jpeg"}' ``` ## Voice wake + talk mode @@ -94,7 +94,7 @@ clawdbot nodes invoke --node "iOS Node" --command canvas.snapshot --params '{"ma - `NODE_BACKGROUND_UNAVAILABLE`: bring the iOS app to the foreground (canvas/camera/screen commands require it). - `A2UI_HOST_NOT_CONFIGURED`: the Gateway did not advertise a canvas host URL; check `canvasHost` in [Gateway configuration](/gateway/configuration). -- Pairing prompt never appears: run `clawdbot nodes pending` and approve manually. +- Pairing prompt never appears: run `moltbot nodes pending` and approve manually. - Reconnect fails after reinstall: the Keychain pairing token was cleared; re-pair the node. ## Related docs diff --git a/docs/platforms/linux.md b/docs/platforms/linux.md index 1184eca8a..d5dd873c5 100644 --- a/docs/platforms/linux.md +++ b/docs/platforms/linux.md @@ -14,8 +14,8 @@ Native Linux companion apps are planned. Contributions are welcome if you want t ## Beginner quick path (VPS) 1) Install Node 22+ -2) `npm i -g clawdbot@latest` -3) `clawdbot onboard --install-daemon` +2) `npm i -g moltbot@latest` +3) `moltbot onboard --install-daemon` 4) From your laptop: `ssh -N -L 18789:127.0.0.1:18789 @` 5) Open `http://127.0.0.1:18789/` and paste your token @@ -35,19 +35,19 @@ Step-by-step VPS guide: [exe.dev](/platforms/exe-dev) Use one of these: ``` -clawdbot onboard --install-daemon +moltbot onboard --install-daemon ``` Or: ``` -clawdbot gateway install +moltbot gateway install ``` Or: ``` -clawdbot configure +moltbot configure ``` Select **Gateway service** when prompted. @@ -55,26 +55,26 @@ Select **Gateway service** when prompted. Repair/migrate: ``` -clawdbot doctor +moltbot doctor ``` ## System control (systemd user unit) -Clawdbot installs a systemd **user** service by default. Use a **system** +Moltbot installs a systemd **user** service by default. Use a **system** service for shared or always-on servers. The full unit example and guidance live in the [Gateway runbook](/gateway). Minimal setup: -Create `~/.config/systemd/user/clawdbot-gateway[-].service`: +Create `~/.config/systemd/user/moltbot-gateway[-].service`: ``` [Unit] -Description=Clawdbot Gateway (profile: , v) +Description=Moltbot Gateway (profile: , v) After=network-online.target Wants=network-online.target [Service] -ExecStart=/usr/local/bin/clawdbot gateway --port 18789 +ExecStart=/usr/local/bin/moltbot gateway --port 18789 Restart=always RestartSec=5 @@ -85,5 +85,5 @@ WantedBy=default.target Enable it: ``` -systemctl --user enable --now clawdbot-gateway[-].service +systemctl --user enable --now moltbot-gateway[-].service ``` diff --git a/docs/platforms/mac/bundled-gateway.md b/docs/platforms/mac/bundled-gateway.md index ae60e5e41..909fddcfc 100644 --- a/docs/platforms/mac/bundled-gateway.md +++ b/docs/platforms/mac/bundled-gateway.md @@ -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@ +npm install -g moltbot@ ``` The macOS app’s **Install CLI** button runs the same flow via npm/pnpm (bun not recommended for Gateway runtime). @@ -26,24 +26,24 @@ The macOS app’s **Install CLI** button runs the same flow via npm/pnpm (bun no ## Launchd (Gateway as LaunchAgent) Label: -- `com.clawdbot.gateway` (or `com.clawdbot.`) +- `bot.molt.gateway` (or `bot.molt.`; legacy `com.clawdbot.*` may remain) Plist location (per‑user): -- `~/Library/LaunchAgents/com.clawdbot.gateway.plist` - (or `~/Library/LaunchAgents/com.clawdbot..plist`) +- `~/Library/LaunchAgents/bot.molt.gateway.plist` + (or `~/Library/LaunchAgents/bot.molt..plist`) 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 ``` diff --git a/docs/platforms/mac/canvas.md b/docs/platforms/mac/canvas.md index 0e9d52b64..7f457c7c3 100644 --- a/docs/platforms/mac/canvas.md +++ b/docs/platforms/mac/canvas.md @@ -15,16 +15,16 @@ UI surfaces. Canvas state is stored under Application Support: -- `~/Library/Application Support/Clawdbot/canvas//...` +- `~/Library/Application Support/Moltbot/canvas//...` The Canvas panel serves those files via a **custom URL scheme**: -- `clawdbot-canvas:///` +- `moltbot-canvas:///` Examples: -- `clawdbot-canvas://main/` → `/main/index.html` -- `clawdbot-canvas://main/assets/app.css` → `/main/assets/app.css` -- `clawdbot-canvas://main/widgets/todo/` → `/main/widgets/todo/index.html` +- `moltbot-canvas://main/` → `/main/index.html` +- `moltbot-canvas://main/assets/app.css` → `/main/assets/app.css` +- `moltbot-canvas://main/widgets/todo/` → `/main/widgets/todo/index.html` If no `index.html` exists at the root, the app shows a **built‑in scaffold page**. @@ -50,10 +50,10 @@ Canvas is exposed via the **Gateway WebSocket**, so the agent can: CLI examples: ```bash -clawdbot nodes canvas present --node -clawdbot nodes canvas navigate --node --url "/" -clawdbot nodes canvas eval --node --js "document.title" -clawdbot nodes canvas snapshot --node +moltbot nodes canvas present --node +moltbot nodes canvas navigate --node --url "/" +moltbot nodes canvas eval --node --js "document.title" +moltbot nodes canvas snapshot --node ``` Notes: @@ -69,7 +69,7 @@ A2UI host page on first open. Default A2UI host URL: ``` -http://:18793/__clawdbot__/a2ui/ +http://:18793/__moltbot__/a2ui/ ``` ### A2UI commands (v0.8) @@ -91,25 +91,25 @@ cat > /tmp/a2ui-v0.8.jsonl <<'EOFA2' {"beginRendering":{"surfaceId":"main","root":"root"}} EOFA2 -clawdbot nodes canvas a2ui push --jsonl /tmp/a2ui-v0.8.jsonl --node +moltbot nodes canvas a2ui push --jsonl /tmp/a2ui-v0.8.jsonl --node ``` Quick smoke: ```bash -clawdbot nodes canvas a2ui push --node --text "Hello from A2UI" +moltbot nodes canvas a2ui push --node --text "Hello from A2UI" ``` ## Triggering agent runs from Canvas Canvas can trigger new agent runs via deep links: -- `clawdbot://agent?...` +- `moltbot://agent?...` Example (in JS): ```js -window.location.href = "clawdbot://agent?message=Review%20this%20design"; +window.location.href = "moltbot://agent?message=Review%20this%20design"; ``` The app prompts for confirmation unless a valid key is provided. diff --git a/docs/platforms/mac/child-process.md b/docs/platforms/mac/child-process.md index 46e98c040..d8b2d8728 100644 --- a/docs/platforms/mac/child-process.md +++ b/docs/platforms/mac/child-process.md @@ -8,7 +8,7 @@ read_when: The macOS app **manages the Gateway via launchd** by default and does not spawn the Gateway as a child process. It first tries to attach to an already‑running Gateway on the configured port; if none is reachable, it enables the launchd -service via the external `clawdbot` CLI (no embedded runtime). This gives you +service via the external `moltbot` CLI (no embedded runtime). This gives you reliable auto‑start at login and restart on crashes. Child‑process mode (Gateway spawned directly by the app) is **not in use** today. @@ -16,8 +16,8 @@ If you need tighter coupling to the UI, run the Gateway manually in a terminal. ## Default behavior (launchd) -- The app installs a per‑user LaunchAgent labeled `com.clawdbot.gateway` - (or `com.clawdbot.` when using `--profile`/`CLAWDBOT_PROFILE`). +- The app installs a per‑user LaunchAgent labeled `bot.molt.gateway` + (or `bot.molt.` when using `--profile`/`CLAWDBOT_PROFILE`; legacy `com.clawdbot.*` is supported). - When Local mode is enabled, the app ensures the LaunchAgent is loaded and starts the Gateway if needed. - Logs are written to the launchd gateway log path (visible in Debug Settings). @@ -25,11 +25,11 @@ If you need tighter coupling to the UI, run the Gateway manually in a terminal. Common commands: ```bash -launchctl kickstart -k gui/$UID/com.clawdbot.gateway -launchctl bootout gui/$UID/com.clawdbot.gateway +launchctl kickstart -k gui/$UID/bot.molt.gateway +launchctl bootout gui/$UID/bot.molt.gateway ``` -Replace the label with `com.clawdbot.` when running a named profile. +Replace the label with `bot.molt.` when running a named profile. ## Unsigned dev builds diff --git a/docs/platforms/mac/dev-setup.md b/docs/platforms/mac/dev-setup.md index 79d23abb5..af0883e18 100644 --- a/docs/platforms/mac/dev-setup.md +++ b/docs/platforms/mac/dev-setup.md @@ -1,11 +1,11 @@ --- -summary: "Setup guide for developers working on the Clawdbot macOS app" +summary: "Setup guide for developers working on the Moltbot macOS app" read_when: - Setting up the macOS development environment --- # macOS Developer Setup -This guide covers the necessary steps to build and run the Clawdbot macOS application from source. +This guide covers the necessary steps to build and run the Moltbot macOS application from source. ## Prerequisites @@ -24,7 +24,7 @@ pnpm install ## 2. Build and Package the App -To build the macOS app and package it into `dist/Clawdbot.app`, run: +To build the macOS app and package it into `dist/Moltbot.app`, run: ```bash ./scripts/package-mac-app.sh @@ -33,22 +33,22 @@ To build the macOS app and package it into `dist/Clawdbot.app`, run: If you don't have an Apple Developer ID certificate, the script will automatically use **ad-hoc signing** (`-`). For dev run modes, signing flags, and Team ID troubleshooting, see the macOS app README: -https://github.com/clawdbot/clawdbot/blob/main/apps/macos/README.md +https://github.com/moltbot/moltbot/blob/main/apps/macos/README.md > **Note**: Ad-hoc signed apps may trigger security prompts. If the app crashes immediately with "Abort trap 6", see the [Troubleshooting](#troubleshooting) section. ## 3. Install the CLI -The macOS app expects a global `clawdbot` CLI install to manage background tasks. +The macOS app expects a global `moltbot` CLI install to manage background tasks. **To install it (recommended):** -1. Open the Clawdbot app. +1. Open the Moltbot app. 2. Go to the **General** settings tab. 3. Click **"Install CLI"**. Alternatively, install it manually: ```bash -npm install -g clawdbot@ +npm install -g moltbot@ ``` ## Troubleshooting @@ -74,16 +74,16 @@ If the app crashes when you try to allow **Speech Recognition** or **Microphone* **Fix:** 1. Reset the TCC permissions: ```bash - tccutil reset All com.clawdbot.mac.debug + tccutil reset All bot.molt.mac.debug ``` -2. If that fails, change the `BUNDLE_ID` temporarily in [`scripts/package-mac-app.sh`](https://github.com/clawdbot/clawdbot/blob/main/scripts/package-mac-app.sh) to force a "clean slate" from macOS. +2. If that fails, change the `BUNDLE_ID` temporarily in [`scripts/package-mac-app.sh`](https://github.com/moltbot/moltbot/blob/main/scripts/package-mac-app.sh) to force a "clean slate" from macOS. ### Gateway "Starting..." indefinitely If the gateway status stays on "Starting...", check if a zombie process is holding the port: ```bash -clawdbot gateway status -clawdbot gateway stop +moltbot gateway status +moltbot gateway stop # If you’re not using a LaunchAgent (dev mode / manual runs), find the listener: lsof -nP -iTCP:18789 -sTCP:LISTEN diff --git a/docs/platforms/mac/health.md b/docs/platforms/mac/health.md index 1acdff686..1bef2166f 100644 --- a/docs/platforms/mac/health.md +++ b/docs/platforms/mac/health.md @@ -21,8 +21,8 @@ How to see whether the linked channel is healthy from the menu bar app. - **Channels tab** surfaces channel status + controls for WhatsApp/Telegram (login QR, logout, probe, last disconnect/error). ## How the probe works -- App runs `clawdbot health --json` via `ShellExecutor` every ~60s and on demand. The probe loads creds and reports status without sending messages. +- App runs `moltbot health --json` via `ShellExecutor` every ~60s and on demand. The probe loads creds and reports status without sending messages. - Cache the last good snapshot and the last error separately to avoid flicker; show the timestamp of each. ## When in doubt -- You can still use the CLI flow in [Gateway health](/gateway/health) (`clawdbot status`, `clawdbot status --deep`, `clawdbot health --json`) and tail `/tmp/clawdbot/clawdbot-*.log` for `web-heartbeat` / `web-reconnect`. +- You can still use the CLI flow in [Gateway health](/gateway/health) (`moltbot status`, `moltbot status --deep`, `moltbot health --json`) and tail `/tmp/moltbot/moltbot-*.log` for `web-heartbeat` / `web-reconnect`. diff --git a/docs/platforms/mac/icon.md b/docs/platforms/mac/icon.md index 520cbae0b..b03c45081 100644 --- a/docs/platforms/mac/icon.md +++ b/docs/platforms/mac/icon.md @@ -1,5 +1,5 @@ --- -summary: "Menu bar icon states and animations for Clawdbot on macOS" +summary: "Menu bar icon states and animations for Moltbot on macOS" read_when: - Changing menu bar icon behavior --- diff --git a/docs/platforms/mac/logging.md b/docs/platforms/mac/logging.md index 8e91b1e35..9a5594d7d 100644 --- a/docs/platforms/mac/logging.md +++ b/docs/platforms/mac/logging.md @@ -1,5 +1,5 @@ --- -summary: "Clawdbot logging: rolling diagnostics file log + unified log privacy flags" +summary: "Moltbot logging: rolling diagnostics file log + unified log privacy flags" read_when: - Capturing macOS logs or investigating private data logging - Debugging voice wake/session lifecycle issues @@ -7,11 +7,11 @@ read_when: # Logging (macOS) ## Rolling diagnostics file log (Debug pane) -Clawdbot routes macOS app logs through swift-log (unified logging by default) and can write a local, rotating file log to disk when you need a durable capture. +Moltbot routes macOS app logs through swift-log (unified logging by default) and can write a local, rotating file log to disk when you need a durable capture. - Verbosity: **Debug pane → Logs → App logging → Verbosity** - Enable: **Debug pane → Logs → App logging → “Write rolling diagnostics log (JSONL)”** -- Location: `~/Library/Logs/Clawdbot/diagnostics.jsonl` (rotates automatically; old files are suffixed with `.1`, `.2`, …) +- Location: `~/Library/Logs/Moltbot/diagnostics.jsonl` (rotates automatically; old files are suffixed with `.1`, `.2`, …) - Clear: **Debug pane → Logs → App logging → “Clear”** Notes: @@ -22,11 +22,11 @@ Notes: Unified logging redacts most payloads unless a subsystem opts into `privacy -off`. Per Peter's write-up on macOS [logging privacy shenanigans](https://steipete.me/posts/2025/logging-privacy-shenanigans) (2025) this is controlled by a plist in `/Library/Preferences/Logging/Subsystems/` keyed by the subsystem name. Only new log entries pick up the flag, so enable it before reproducing an issue. -## Enable for Clawdbot (`com.clawdbot`) +## Enable for Moltbot (`bot.molt`) - Write the plist to a temp file first, then install it atomically as root: ```bash -cat <<'EOF' >/tmp/com.clawdbot.plist +cat <<'EOF' >/tmp/bot.molt.plist @@ -39,13 +39,13 @@ cat <<'EOF' >/tmp/com.clawdbot.plist EOF -sudo install -m 644 -o root -g wheel /tmp/com.clawdbot.plist /Library/Preferences/Logging/Subsystems/com.clawdbot.plist +sudo install -m 644 -o root -g wheel /tmp/bot.molt.plist /Library/Preferences/Logging/Subsystems/bot.molt.plist ``` - No reboot is required; logd notices the file quickly, but only new log lines will include private payloads. - View the richer output with the existing helper, e.g. `./scripts/clawlog.sh --category WebChat --last 5m`. ## Disable after debugging -- Remove the override: `sudo rm /Library/Preferences/Logging/Subsystems/com.clawdbot.plist`. +- Remove the override: `sudo rm /Library/Preferences/Logging/Subsystems/bot.molt.plist`. - Optionally run `sudo log config --reload` to force logd to drop the override immediately. - Remember this surface can include phone numbers and message bodies; keep the plist in place only while you actively need the extra detail. diff --git a/docs/platforms/mac/menu-bar.md b/docs/platforms/mac/menu-bar.md index 36b39f535..a0e1bddff 100644 --- a/docs/platforms/mac/menu-bar.md +++ b/docs/platforms/mac/menu-bar.md @@ -40,7 +40,7 @@ read_when: ## Status row text (menu) - While work is active: ` · ` - - Examples: `Main · exec: pnpm test`, `Other · read: apps/macos/Sources/Clawdbot/AppState.swift`. + - Examples: `Main · exec: pnpm test`, `Other · read: apps/macos/Sources/Moltbot/AppState.swift`. - When idle: falls back to the health summary. ## Event ingestion diff --git a/docs/platforms/mac/peekaboo.md b/docs/platforms/mac/peekaboo.md index 08718c652..da9abe432 100644 --- a/docs/platforms/mac/peekaboo.md +++ b/docs/platforms/mac/peekaboo.md @@ -1,28 +1,28 @@ --- summary: "PeekabooBridge integration for macOS UI automation" read_when: - - Hosting PeekabooBridge in Clawdbot.app + - Hosting PeekabooBridge in Moltbot.app - Integrating Peekaboo via Swift Package Manager - Changing PeekabooBridge protocol/paths --- # Peekaboo Bridge (macOS UI automation) -Clawdbot can host **PeekabooBridge** as a local, permission‑aware UI automation +Moltbot can host **PeekabooBridge** as a local, permission‑aware UI automation broker. This lets the `peekaboo` CLI drive UI automation while reusing the macOS app’s TCC permissions. ## What this is (and isn’t) -- **Host**: Clawdbot.app can act as a PeekabooBridge host. -- **Client**: use the `peekaboo` CLI (no separate `clawdbot ui ...` surface). -- **UI**: visual overlays stay in Peekaboo.app; Clawdbot is a thin broker host. +- **Host**: Moltbot.app can act as a PeekabooBridge host. +- **Client**: use the `peekaboo` CLI (no separate `moltbot ui ...` surface). +- **UI**: visual overlays stay in Peekaboo.app; Moltbot is a thin broker host. ## Enable the bridge In the macOS app: - Settings → **Enable Peekaboo Bridge** -When enabled, Clawdbot starts a local UNIX socket server. If disabled, the host +When enabled, Moltbot starts a local UNIX socket server. If disabled, the host is stopped and `peekaboo` will fall back to other available hosts. ## Client discovery order @@ -31,7 +31,7 @@ Peekaboo clients typically try hosts in this order: 1. Peekaboo.app (full UX) 2. Claude.app (if installed) -3. Clawdbot.app (thin broker) +3. Moltbot.app (thin broker) Use `peekaboo bridge status --verbose` to see which host is active and which socket path is in use. You can override with: @@ -43,7 +43,7 @@ export PEEKABOO_BRIDGE_SOCKET=/path/to/bridge.sock ## Security & permissions - The bridge validates **caller code signatures**; an allowlist of TeamIDs is - enforced (Peekaboo host TeamID + Clawdbot app TeamID). + enforced (Peekaboo host TeamID + Moltbot app TeamID). - Requests time out after ~10 seconds. - If required permissions are missing, the bridge returns a clear error message rather than launching System Settings. @@ -58,5 +58,5 @@ If you need longer retention, re‑capture from the client. - If `peekaboo` reports “bridge client is not authorized”, ensure the client is properly signed or run the host with `PEEKABOO_ALLOW_UNSIGNED_SOCKET_CLIENTS=1` in **debug** mode only. -- If no hosts are found, open one of the host apps (Peekaboo.app or Clawdbot.app) +- If no hosts are found, open one of the host apps (Peekaboo.app or Moltbot.app) and confirm permissions are granted. diff --git a/docs/platforms/mac/permissions.md b/docs/platforms/mac/permissions.md index f46d4534f..d2570829c 100644 --- a/docs/platforms/mac/permissions.md +++ b/docs/platforms/mac/permissions.md @@ -12,7 +12,7 @@ app's code signature, bundle identifier, and on-disk path. If any of those chang macOS treats the app as new and may drop or hide prompts. ## Requirements for stable permissions -- Same path: run the app from a fixed location (for Clawdbot, `dist/Clawdbot.app`). +- Same path: run the app from a fixed location (for Moltbot, `dist/Moltbot.app`). - Same bundle identifier: changing the bundle ID creates a new permission identity. - Signed app: unsigned or ad-hoc signed builds do not persist permissions. - Consistent signature: use a real Apple Development or Developer ID certificate @@ -31,8 +31,8 @@ grants, and prompts can disappear entirely until the stale entries are cleared. Example resets (replace bundle ID as needed): ```bash -sudo tccutil reset Accessibility com.clawdbot.mac -sudo tccutil reset ScreenCapture com.clawdbot.mac +sudo tccutil reset Accessibility bot.molt.mac +sudo tccutil reset ScreenCapture bot.molt.mac sudo tccutil reset AppleEvents ``` diff --git a/docs/platforms/mac/release.md b/docs/platforms/mac/release.md index d3bfd02c3..237eac616 100644 --- a/docs/platforms/mac/release.md +++ b/docs/platforms/mac/release.md @@ -1,11 +1,11 @@ --- -summary: "Clawdbot macOS release checklist (Sparkle feed, packaging, signing)" +summary: "Moltbot macOS release checklist (Sparkle feed, packaging, signing)" read_when: - - Cutting or validating a Clawdbot macOS release + - Cutting or validating a Moltbot macOS release - Updating the Sparkle appcast or feed assets --- -# Clawdbot macOS release (Sparkle) +# Moltbot macOS release (Sparkle) This app now ships Sparkle auto-updates. Release builds must be Developer ID–signed, zipped, and published with a signed appcast entry. @@ -13,10 +13,10 @@ This app now ships Sparkle auto-updates. Release builds must be Developer ID–s - Developer ID Application cert installed (example: `Developer ID Application: ()`). - Sparkle private key path set in the environment as `SPARKLE_PRIVATE_KEY_FILE` (path to your Sparkle ed25519 private key; public key baked into Info.plist). If it is missing, check `~/.profile`. - Notary credentials (keychain profile or API key) for `xcrun notarytool` if you want Gatekeeper-safe DMG/zip distribution. - - We use a Keychain profile named `clawdbot-notary`, created from App Store Connect API key env vars in your shell profile: + - We use a Keychain profile named `moltbot-notary`, created from App Store Connect API key env vars in your shell profile: - `APP_STORE_CONNECT_API_KEY_P8`, `APP_STORE_CONNECT_KEY_ID`, `APP_STORE_CONNECT_ISSUER_ID` - - `echo "$APP_STORE_CONNECT_API_KEY_P8" | sed 's/\\n/\n/g' > /tmp/clawdbot-notary.p8` - - `xcrun notarytool store-credentials "clawdbot-notary" --key /tmp/clawdbot-notary.p8 --key-id "$APP_STORE_CONNECT_KEY_ID" --issuer "$APP_STORE_CONNECT_ISSUER_ID"` + - `echo "$APP_STORE_CONNECT_API_KEY_P8" | sed 's/\\n/\n/g' > /tmp/moltbot-notary.p8` + - `xcrun notarytool store-credentials "moltbot-notary" --key /tmp/moltbot-notary.p8 --key-id "$APP_STORE_CONNECT_KEY_ID" --issuer "$APP_STORE_CONNECT_ISSUER_ID"` - `pnpm` deps installed (`pnpm install --config.node-linker=hoisted`). - Sparkle tools are fetched automatically via SwiftPM at `apps/macos/.build/artifacts/sparkle/Sparkle/bin/` (`sign_update`, `generate_appcast`, etc.). @@ -29,48 +29,48 @@ Notes: ```bash # From repo root; set release IDs so Sparkle feed is enabled. # APP_BUILD must be numeric + monotonic for Sparkle compare. -BUNDLE_ID=com.clawdbot.mac \ -APP_VERSION=2026.1.25 \ +BUNDLE_ID=bot.molt.mac \ +APP_VERSION=2026.1.27-beta.1 \ APP_BUILD="$(git rev-list --count HEAD)" \ BUILD_CONFIG=release \ SIGN_IDENTITY="Developer ID Application: ()" \ scripts/package-mac-app.sh # Zip for distribution (includes resource forks for Sparkle delta support) -ditto -c -k --sequesterRsrc --keepParent dist/Clawdbot.app dist/Clawdbot-2026.1.25.zip +ditto -c -k --sequesterRsrc --keepParent dist/Moltbot.app dist/Moltbot-2026.1.27-beta.1.zip # Optional: also build a styled DMG for humans (drag to /Applications) -scripts/create-dmg.sh dist/Clawdbot.app dist/Clawdbot-2026.1.25.dmg +scripts/create-dmg.sh dist/Moltbot.app dist/Moltbot-2026.1.27-beta.1.dmg # Recommended: build + notarize/staple zip + DMG # First, create a keychain profile once: -# xcrun notarytool store-credentials "clawdbot-notary" \ +# xcrun notarytool store-credentials "moltbot-notary" \ # --apple-id "" --team-id "" --password "" -NOTARIZE=1 NOTARYTOOL_PROFILE=clawdbot-notary \ -BUNDLE_ID=com.clawdbot.mac \ -APP_VERSION=2026.1.25 \ +NOTARIZE=1 NOTARYTOOL_PROFILE=moltbot-notary \ +BUNDLE_ID=bot.molt.mac \ +APP_VERSION=2026.1.27-beta.1 \ APP_BUILD="$(git rev-list --count HEAD)" \ BUILD_CONFIG=release \ SIGN_IDENTITY="Developer ID Application: ()" \ scripts/package-mac-dist.sh # Optional: ship dSYM alongside the release -ditto -c -k --keepParent apps/macos/.build/release/Clawdbot.app.dSYM dist/Clawdbot-2026.1.25.dSYM.zip +ditto -c -k --keepParent apps/macos/.build/release/Moltbot.app.dSYM dist/Moltbot-2026.1.27-beta.1.dSYM.zip ``` ## Appcast entry Use the release note generator so Sparkle renders formatted HTML notes: ```bash -SPARKLE_PRIVATE_KEY_FILE=/path/to/ed25519-private-key scripts/make_appcast.sh dist/Clawdbot-2026.1.25.zip https://raw.githubusercontent.com/clawdbot/clawdbot/main/appcast.xml +SPARKLE_PRIVATE_KEY_FILE=/path/to/ed25519-private-key scripts/make_appcast.sh dist/Moltbot-2026.1.27-beta.1.zip https://raw.githubusercontent.com/moltbot/moltbot/main/appcast.xml ``` -Generates HTML release notes from `CHANGELOG.md` (via [`scripts/changelog-to-html.sh`](https://github.com/clawdbot/clawdbot/blob/main/scripts/changelog-to-html.sh)) and embeds them in the appcast entry. +Generates HTML release notes from `CHANGELOG.md` (via [`scripts/changelog-to-html.sh`](https://github.com/moltbot/moltbot/blob/main/scripts/changelog-to-html.sh)) and embeds them in the appcast entry. Commit the updated `appcast.xml` alongside the release assets (zip + dSYM) when publishing. ## Publish & verify -- Upload `Clawdbot-2026.1.25.zip` (and `Clawdbot-2026.1.25.dSYM.zip`) to the GitHub release for tag `v2026.1.25`. -- Ensure the raw appcast URL matches the baked feed: `https://raw.githubusercontent.com/clawdbot/clawdbot/main/appcast.xml`. +- Upload `Moltbot-2026.1.27-beta.1.zip` (and `Moltbot-2026.1.27-beta.1.dSYM.zip`) to the GitHub release for tag `v2026.1.27-beta.1`. +- Ensure the raw appcast URL matches the baked feed: `https://raw.githubusercontent.com/moltbot/moltbot/main/appcast.xml`. - Sanity checks: - - `curl -I https://raw.githubusercontent.com/clawdbot/clawdbot/main/appcast.xml` returns 200. + - `curl -I https://raw.githubusercontent.com/moltbot/moltbot/main/appcast.xml` returns 200. - `curl -I ` returns 200 after assets upload. - On a previous public build, run “Check for Updates…” from the About tab and verify Sparkle installs the new build cleanly. diff --git a/docs/platforms/mac/remote.md b/docs/platforms/mac/remote.md index 6d36700f9..2a726e52e 100644 --- a/docs/platforms/mac/remote.md +++ b/docs/platforms/mac/remote.md @@ -1,16 +1,16 @@ --- -summary: "macOS app flow for controlling a remote Clawdbot gateway over SSH" +summary: "macOS app flow for controlling a remote Moltbot gateway over SSH" read_when: - Setting up or debugging remote mac control --- -# Remote Clawdbot (macOS ⇄ remote host) +# Remote Moltbot (macOS ⇄ remote host) -This flow lets the macOS app act as a full remote control for a Clawdbot gateway running on another host (desktop/server). It’s the app’s **Remote over SSH** (remote run) feature. All features—health checks, Voice Wake forwarding, and Web Chat—reuse the same remote SSH configuration from *Settings → General*. +This flow lets the macOS app act as a full remote control for a Moltbot gateway running on another host (desktop/server). It’s the app’s **Remote over SSH** (remote run) feature. All features—health checks, Voice Wake forwarding, and Web Chat—reuse the same remote SSH configuration from *Settings → General*. ## Modes - **Local (this Mac)**: Everything runs on the laptop. No SSH involved. -- **Remote over SSH (default)**: Clawdbot commands are executed on the remote host. The mac app opens an SSH connection with `-o BatchMode` plus your chosen identity/key and a local port-forward. +- **Remote over SSH (default)**: Moltbot commands are executed on the remote host. The mac app opens an SSH connection with `-o BatchMode` plus your chosen identity/key and a local port-forward. - **Remote direct (ws/wss)**: No SSH tunnel. The mac app connects to the gateway URL directly (for example, via Tailscale Serve or a public HTTPS reverse proxy). ## Remote transports @@ -19,21 +19,21 @@ Remote mode supports two transports: - **Direct (ws/wss)**: Connects straight to the gateway URL. The gateway sees the real client IP. ## Prereqs on the remote host -1) Install Node + pnpm and build/install the Clawdbot CLI (`pnpm install && pnpm build && pnpm link --global`). -2) Ensure `clawdbot` is on PATH for non-interactive shells (symlink into `/usr/local/bin` or `/opt/homebrew/bin` if needed). +1) Install Node + pnpm and build/install the Moltbot CLI (`pnpm install && pnpm build && pnpm link --global`). +2) Ensure `moltbot` is on PATH for non-interactive shells (symlink into `/usr/local/bin` or `/opt/homebrew/bin` if needed). 3) Open SSH with key auth. We recommend **Tailscale** IPs for stable reachability off-LAN. ## macOS app setup 1) Open *Settings → General*. -2) Under **Clawdbot runs**, pick **Remote over SSH** and set: +2) Under **Moltbot runs**, pick **Remote over SSH** and set: - **Transport**: **SSH tunnel** or **Direct (ws/wss)**. - **SSH target**: `user@host` (optional `:port`). - If the gateway is on the same LAN and advertises Bonjour, pick it from the discovered list to auto-fill this field. - **Gateway URL** (Direct only): `wss://gateway.example.ts.net` (or `ws://...` for local/LAN). - **Identity file** (advanced): path to your key. - **Project root** (advanced): remote checkout path used for commands. - - **CLI path** (advanced): optional path to a runnable `clawdbot` entrypoint/binary (auto-filled when advertised). -3) Hit **Test remote**. Success indicates the remote `clawdbot status --json` runs correctly. Failures usually mean PATH/CLI issues; exit 127 means the CLI isn’t found remotely. + - **CLI path** (advanced): optional path to a runnable `moltbot` entrypoint/binary (auto-filled when advertised). +3) Hit **Test remote**. Success indicates the remote `moltbot status --json` runs correctly. Failures usually mean PATH/CLI issues; exit 127 means the CLI isn’t found remotely. 4) Health checks and Web Chat will now run through this SSH tunnel automatically. ## Web Chat @@ -51,21 +51,21 @@ Remote mode supports two transports: - See [Security](/gateway/security) and [Tailscale](/gateway/tailscale). ## WhatsApp login flow (remote) -- Run `clawdbot channels login --verbose` **on the remote host**. Scan the QR with WhatsApp on your phone. +- Run `moltbot channels login --verbose` **on the remote host**. Scan the QR with WhatsApp on your phone. - Re-run login on that host if auth expires. Health check will surface link problems. ## Troubleshooting -- **exit 127 / not found**: `clawdbot` isn’t on PATH for non-login shells. Add it to `/etc/paths`, your shell rc, or symlink into `/usr/local/bin`/`/opt/homebrew/bin`. -- **Health probe failed**: check SSH reachability, PATH, and that Baileys is logged in (`clawdbot status --json`). +- **exit 127 / not found**: `moltbot` isn’t on PATH for non-login shells. Add it to `/etc/paths`, your shell rc, or symlink into `/usr/local/bin`/`/opt/homebrew/bin`. +- **Health probe failed**: check SSH reachability, PATH, and that Baileys is logged in (`moltbot status --json`). - **Web Chat stuck**: confirm the gateway is running on the remote host and the forwarded port matches the gateway WS port; the UI requires a healthy WS connection. - **Node IP shows 127.0.0.1**: expected with the SSH tunnel. Switch **Transport** to **Direct (ws/wss)** if you want the gateway to see the real client IP. - **Voice Wake**: trigger phrases are forwarded automatically in remote mode; no separate forwarder is needed. ## Notification sounds -Pick sounds per notification from scripts with `clawdbot` and `node.invoke`, e.g.: +Pick sounds per notification from scripts with `moltbot` and `node.invoke`, e.g.: ```bash -clawdbot nodes notify --node --title "Ping" --body "Remote gateway ready" --sound Glass +moltbot nodes notify --node --title "Ping" --body "Remote gateway ready" --sound Glass ``` There is no global “default sound” toggle in the app anymore; callers choose a sound (or none) per request. diff --git a/docs/platforms/mac/signing.md b/docs/platforms/mac/signing.md index de549bf57..71f153765 100644 --- a/docs/platforms/mac/signing.md +++ b/docs/platforms/mac/signing.md @@ -5,13 +5,13 @@ read_when: --- # mac signing (debug builds) -This app is usually built from [`scripts/package-mac-app.sh`](https://github.com/clawdbot/clawdbot/blob/main/scripts/package-mac-app.sh), which now: +This app is usually built from [`scripts/package-mac-app.sh`](https://github.com/moltbot/moltbot/blob/main/scripts/package-mac-app.sh), which now: -- sets a stable debug bundle identifier: `com.clawdbot.mac.debug` +- sets a stable debug bundle identifier: `bot.molt.mac.debug` - writes the Info.plist with that bundle id (override via `BUNDLE_ID=...`) -- calls [`scripts/codesign-mac-app.sh`](https://github.com/clawdbot/clawdbot/blob/main/scripts/codesign-mac-app.sh) to sign the main binary and app bundle so macOS treats each rebuild as the same signed bundle and keeps TCC permissions (notifications, accessibility, screen recording, mic, speech). For stable permissions, use a real signing identity; ad-hoc is opt-in and fragile (see [macOS permissions](/platforms/mac/permissions)). +- calls [`scripts/codesign-mac-app.sh`](https://github.com/moltbot/moltbot/blob/main/scripts/codesign-mac-app.sh) to sign the main binary and app bundle so macOS treats each rebuild as the same signed bundle and keeps TCC permissions (notifications, accessibility, screen recording, mic, speech). For stable permissions, use a real signing identity; ad-hoc is opt-in and fragile (see [macOS permissions](/platforms/mac/permissions)). - uses `CODESIGN_TIMESTAMP=auto` by default; it enables trusted timestamps for Developer ID signatures. Set `CODESIGN_TIMESTAMP=off` to skip timestamping (offline debug builds). -- inject build metadata into Info.plist: `ClawdbotBuildTimestamp` (UTC) and `ClawdbotGitCommit` (short hash) so the About pane can show build, git, and debug/release channel. +- inject build metadata into Info.plist: `MoltbotBuildTimestamp` (UTC) and `MoltbotGitCommit` (short hash) so the About pane can show build, git, and debug/release channel. - **Packaging requires Node 22+**: the script runs TS builds and the Control UI build. - reads `SIGN_IDENTITY` from the environment. Add `export SIGN_IDENTITY="Apple Development: Your Name (TEAMID)"` (or your Developer ID Application cert) to your shell rc to always sign with your cert. Ad-hoc signing requires explicit opt-in via `ALLOW_ADHOC_SIGNING=1` or `SIGN_IDENTITY="-"` (not recommended for permission testing). - runs a Team ID audit after signing and fails if any Mach-O inside the app bundle is signed by a different Team ID. Set `SKIP_TEAM_ID_CHECK=1` to bypass. @@ -33,11 +33,11 @@ When signing with `SIGN_IDENTITY="-"` (ad-hoc), the script automatically disable ## Build metadata for About `package-mac-app.sh` stamps the bundle with: -- `ClawdbotBuildTimestamp`: ISO8601 UTC at package time -- `ClawdbotGitCommit`: short git hash (or `unknown` if unavailable) +- `MoltbotBuildTimestamp`: ISO8601 UTC at package time +- `MoltbotGitCommit`: short git hash (or `unknown` if unavailable) The About tab reads these keys to show version, build date, git commit, and whether it’s a debug build (via `#if DEBUG`). Run the packager to refresh these values after code changes. ## Why -TCC permissions are tied to the bundle identifier *and* code signature. Unsigned debug builds with changing UUIDs were causing macOS to forget grants after each rebuild. Signing the binaries (ad‑hoc by default) and keeping a fixed bundle id/path (`dist/Clawdbot.app`) preserves the grants between builds, matching the VibeTunnel approach. +TCC permissions are tied to the bundle identifier *and* code signature. Unsigned debug builds with changing UUIDs were causing macOS to forget grants after each rebuild. Signing the binaries (ad‑hoc by default) and keeping a fixed bundle id/path (`dist/Moltbot.app`) preserves the grants between builds, matching the VibeTunnel approach. diff --git a/docs/platforms/mac/skills.md b/docs/platforms/mac/skills.md index 9eb836c9c..aad035d53 100644 --- a/docs/platforms/mac/skills.md +++ b/docs/platforms/mac/skills.md @@ -6,21 +6,21 @@ read_when: --- # Skills (macOS) -The macOS app surfaces Clawdbot skills via the gateway; it does not parse skills locally. +The macOS app surfaces Moltbot skills via the gateway; it does not parse skills locally. ## Data source - `skills.status` (gateway) returns all skills plus eligibility and missing requirements (including allowlist blocks for bundled skills). -- Requirements are derived from `metadata.clawdbot.requires` in each `SKILL.md`. +- Requirements are derived from `metadata.moltbot.requires` in each `SKILL.md`. ## Install actions -- `metadata.clawdbot.install` defines install options (brew/node/go/uv). +- `metadata.moltbot.install` defines install options (brew/node/go/uv). - The app calls `skills.install` to run installers on the gateway host. - The gateway surfaces only one preferred installer when multiple are provided (brew when available, otherwise node manager from `skills.install`, default npm). ## Env/API keys -- The app stores keys in `~/.clawdbot/clawdbot.json` under `skills.entries.`. +- The app stores keys in `~/.clawdbot/moltbot.json` under `skills.entries.`. - `skills.update` patches `enabled`, `apiKey`, and `env`. ## Remote mode diff --git a/docs/platforms/mac/voice-overlay.md b/docs/platforms/mac/voice-overlay.md index 5d755fe67..139445164 100644 --- a/docs/platforms/mac/voice-overlay.md +++ b/docs/platforms/mac/voice-overlay.md @@ -32,14 +32,14 @@ Audience: macOS app contributors. Goal: keep the voice overlay predictable when - Push-to-talk: no delay; wake-word: optional delay for auto-send. - Apply a short cooldown to the wake runtime after push-to-talk finishes so wake-word doesn’t immediately retrigger. 5. **Logging** - - Coordinator emits `.info` logs in subsystem `com.clawdbot`, categories `voicewake.overlay` and `voicewake.chime`. + - Coordinator emits `.info` logs in subsystem `bot.molt`, categories `voicewake.overlay` and `voicewake.chime`. - Key events: `session_started`, `adopted_by_push_to_talk`, `partial`, `finalized`, `send`, `dismiss`, `cancel`, `cooldown`. ### Debugging checklist - Stream logs while reproducing a sticky overlay: ```bash - sudo log stream --predicate 'subsystem == "com.clawdbot" AND category CONTAINS "voicewake"' --level info --style compact + sudo log stream --predicate 'subsystem == "bot.molt" AND category CONTAINS "voicewake"' --level info --style compact ``` - Verify only one active session token; stale callbacks should be dropped by the coordinator. - Ensure push-to-talk release always calls `endCapture` with the active token; if text is empty, expect `dismiss` without chime or send. diff --git a/docs/platforms/mac/webchat.md b/docs/platforms/mac/webchat.md index a71780a40..5f4e32308 100644 --- a/docs/platforms/mac/webchat.md +++ b/docs/platforms/mac/webchat.md @@ -18,9 +18,9 @@ agent (with a session switcher for other sessions). - Manual: Lobster menu → “Open Chat”. - Auto‑open for testing: ```bash - dist/Clawdbot.app/Contents/MacOS/Clawdbot --webchat + dist/Moltbot.app/Contents/MacOS/Moltbot --webchat ``` -- Logs: `./scripts/clawlog.sh` (subsystem `com.clawdbot`, category `WebChatSwiftUI`). +- Logs: `./scripts/clawlog.sh` (subsystem `bot.molt`, category `WebChatSwiftUI`). ## How it’s wired diff --git a/docs/platforms/mac/xpc.md b/docs/platforms/mac/xpc.md index fa3ca208b..629141b93 100644 --- a/docs/platforms/mac/xpc.md +++ b/docs/platforms/mac/xpc.md @@ -1,11 +1,11 @@ --- -summary: "macOS IPC architecture for Clawdbot app, gateway node transport, and PeekabooBridge" +summary: "macOS IPC architecture for Moltbot app, gateway node transport, and PeekabooBridge" read_when: - Editing IPC contracts or menu bar app IPC --- -# Clawdbot macOS IPC architecture +# Moltbot macOS IPC architecture -**Current model:** a local Unix socket connects the **node host service** to the **macOS app** for exec approvals + `system.run`. A `clawdbot-mac` debug CLI exists for discovery/connect checks; agent actions still flow through the Gateway WebSocket and `node.invoke`. UI automation uses PeekabooBridge. +**Current model:** a local Unix socket connects the **node host service** to the **macOS app** for exec approvals + `system.run`. A `moltbot-mac` debug CLI exists for discovery/connect checks; agent actions still flow through the Gateway WebSocket and `node.invoke`. UI automation uses PeekabooBridge. ## Goals - Single GUI app instance that owns all TCC-facing work (notifications, screen recording, mic, speech, AppleScript). @@ -32,7 +32,7 @@ Agent -> Gateway -> Node Service (WS) ### PeekabooBridge (UI automation) - UI automation uses a separate UNIX socket named `bridge.sock` and the PeekabooBridge JSON protocol. -- Host preference order (client-side): Peekaboo.app → Claude.app → Clawdbot.app → local execution. +- Host preference order (client-side): Peekaboo.app → Claude.app → Moltbot.app → local execution. - Security: bridge hosts require an allowed TeamID; DEBUG-only same-UID escape hatch is guarded by `PEEKABOO_ALLOW_UNSIGNED_SOCKET_CLIENTS=1` (Peekaboo convention). - See: [PeekabooBridge usage](/platforms/mac/peekaboo) for details. diff --git a/docs/platforms/macos-vm.md b/docs/platforms/macos-vm.md index f9edef6b1..2b2f2281f 100644 --- a/docs/platforms/macos-vm.md +++ b/docs/platforms/macos-vm.md @@ -1,13 +1,13 @@ --- -summary: "Run Clawdbot in a sandboxed macOS VM (local or hosted) when you need isolation or iMessage" +summary: "Run Moltbot in a sandboxed macOS VM (local or hosted) when you need isolation or iMessage" read_when: - - You want Clawdbot isolated from your main macOS environment + - You want Moltbot isolated from your main macOS environment - You want iMessage integration (BlueBubbles) in a sandbox - You want a resettable macOS environment you can clone - You want to compare local vs hosted macOS VM options --- -# Clawdbot on macOS VMs (Sandboxing) +# Moltbot on macOS VMs (Sandboxing) ## Recommended default (most users) @@ -21,7 +21,7 @@ Use a macOS VM when you specifically need macOS-only capabilities (iMessage/Blue ### Local VM on your Apple Silicon Mac (Lume) -Run Clawdbot in a sandboxed macOS VM on your existing Apple Silicon Mac using [Lume](https://cua.ai/docs/lume). +Run Moltbot in a sandboxed macOS VM on your existing Apple Silicon Mac using [Lume](https://cua.ai/docs/lume). This gives you: - Full macOS environment in isolation (your host stays clean) @@ -42,10 +42,10 @@ Once you have SSH access to a macOS VM, continue at step 6 below. ## Quick path (Lume, experienced users) 1. Install Lume -2. `lume create clawdbot --os macos --ipsw latest` +2. `lume create moltbot --os macos --ipsw latest` 3. Complete Setup Assistant, enable Remote Login (SSH) -4. `lume run clawdbot --no-display` -5. SSH in, install Clawdbot, configure channels +4. `lume run moltbot --no-display` +5. SSH in, install Moltbot, configure channels 6. Done --- @@ -84,7 +84,7 @@ Docs: [Lume Installation](https://cua.ai/docs/lume/guide/getting-started/install ## 2) Create the macOS VM ```bash -lume create clawdbot --os macos --ipsw latest +lume create moltbot --os macos --ipsw latest ``` This downloads macOS and creates the VM. A VNC window opens automatically. @@ -110,7 +110,7 @@ After setup completes, enable SSH: ## 4) Get the VM's IP address ```bash -lume get clawdbot +lume get moltbot ``` Look for the IP address (usually `192.168.64.x`). @@ -127,13 +127,13 @@ Replace `youruser` with the account you created, and the IP with your VM's IP. --- -## 6) Install Clawdbot +## 6) Install Moltbot Inside the VM: ```bash -npm install -g clawdbot@latest -clawdbot onboard --install-daemon +npm install -g moltbot@latest +moltbot onboard --install-daemon ``` Follow the onboarding prompts to set up your model provider (Anthropic, OpenAI, etc.). @@ -145,7 +145,7 @@ Follow the onboarding prompts to set up your model provider (Anthropic, OpenAI, Edit the config file: ```bash -nano ~/.clawdbot/clawdbot.json +nano ~/.clawdbot/moltbot.json ``` Add your channels: @@ -167,7 +167,7 @@ Add your channels: Then login to WhatsApp (scan QR): ```bash -clawdbot channels login +moltbot channels login ``` --- @@ -177,23 +177,23 @@ clawdbot channels login Stop the VM and restart without display: ```bash -lume stop clawdbot -lume run clawdbot --no-display +lume stop moltbot +lume run moltbot --no-display ``` -The VM runs in the background. Clawdbot's daemon keeps the gateway running. +The VM runs in the background. Moltbot's daemon keeps the gateway running. To check status: ```bash -ssh youruser@192.168.64.X "clawdbot status" +ssh youruser@192.168.64.X "moltbot status" ``` --- ## Bonus: iMessage integration -This is the killer feature of running on macOS. Use [BlueBubbles](https://bluebubbles.app) to add iMessage to Clawdbot. +This is the killer feature of running on macOS. Use [BlueBubbles](https://bluebubbles.app) to add iMessage to Moltbot. Inside the VM: @@ -202,7 +202,7 @@ Inside the VM: 3. Enable the Web API and set a password 4. Point BlueBubbles webhooks at your gateway (example: `https://your-gateway-host:3000/bluebubbles-webhook?password=`) -Add to your Clawdbot config: +Add to your Moltbot config: ```json { @@ -227,16 +227,16 @@ Full setup details: [BlueBubbles channel](/channels/bluebubbles) Before customizing further, snapshot your clean state: ```bash -lume stop clawdbot -lume clone clawdbot clawdbot-golden +lume stop moltbot +lume clone moltbot moltbot-golden ``` Reset anytime: ```bash -lume stop clawdbot && lume delete clawdbot -lume clone clawdbot-golden clawdbot -lume run clawdbot --no-display +lume stop moltbot && lume delete moltbot +lume clone moltbot-golden moltbot +lume run moltbot --no-display ``` --- @@ -257,9 +257,9 @@ For true always-on, consider a dedicated Mac mini or a small VPS. See [VPS hosti | Problem | Solution | |---------|----------| | Can't SSH into VM | Check "Remote Login" is enabled in VM's System Settings | -| VM IP not showing | Wait for VM to fully boot, run `lume get clawdbot` again | +| VM IP not showing | Wait for VM to fully boot, run `lume get moltbot` again | | Lume command not found | Add `~/.local/bin` to your PATH | -| WhatsApp QR not scanning | Ensure you're logged into the VM (not host) when running `clawdbot channels login` | +| WhatsApp QR not scanning | Ensure you're logged into the VM (not host) when running `moltbot channels login` | --- diff --git a/docs/platforms/macos.md b/docs/platforms/macos.md index 36e7f2182..c98fe0817 100644 --- a/docs/platforms/macos.md +++ b/docs/platforms/macos.md @@ -1,12 +1,12 @@ --- -summary: "Clawdbot macOS companion app (menu bar + gateway broker)" +summary: "Moltbot macOS companion app (menu bar + gateway broker)" read_when: - Implementing macOS app features - Changing gateway lifecycle or node bridging on macOS --- -# Clawdbot macOS Companion (menu bar + gateway broker) +# Moltbot macOS Companion (menu bar + gateway broker) -The macOS app is the **menu‑bar companion** for Clawdbot. It owns permissions, +The macOS app is the **menu‑bar companion** for Moltbot. It owns permissions, manages/attaches to the Gateway locally (launchd or manual), and exposes macOS capabilities to the agent as a node. @@ -19,12 +19,12 @@ capabilities to the agent as a node. - Exposes macOS‑only tools (Canvas, Camera, Screen Recording, `system.run`). - Starts the local node host service in **remote** mode (launchd), and stops it in **local** mode. - Optionally hosts **PeekabooBridge** for UI automation. -- Installs the global CLI (`clawdbot`) via npm/pnpm on request (bun not recommended for the Gateway runtime). +- Installs the global CLI (`moltbot`) via npm/pnpm on request (bun not recommended for the Gateway runtime). ## Local vs remote mode - **Local** (default): the app attaches to a running local Gateway if present; - otherwise it enables the launchd service via `clawdbot gateway install`. + otherwise it enables the launchd service via `moltbot gateway install`. - **Remote**: the app connects to a Gateway over SSH/Tailscale and never starts a local process. The app starts the local **node host service** so the remote Gateway can reach this Mac. @@ -32,18 +32,18 @@ The app does not spawn the Gateway as a child process. ## Launchd control -The app manages a per‑user LaunchAgent labeled `com.clawdbot.gateway` -(or `com.clawdbot.` when using `--profile`/`CLAWDBOT_PROFILE`). +The app manages a per‑user LaunchAgent labeled `bot.molt.gateway` +(or `bot.molt.` when using `--profile`/`CLAWDBOT_PROFILE`; legacy `com.clawdbot.*` still unloads). ```bash -launchctl kickstart -k gui/$UID/com.clawdbot.gateway -launchctl bootout gui/$UID/com.clawdbot.gateway +launchctl kickstart -k gui/$UID/bot.molt.gateway +launchctl bootout gui/$UID/bot.molt.gateway ``` -Replace the label with `com.clawdbot.` when running a named profile. +Replace the label with `bot.molt.` when running a named profile. If the LaunchAgent isn’t installed, enable it from the app or run -`clawdbot gateway install`. +`moltbot gateway install`. ## Node capabilities (mac) @@ -105,14 +105,14 @@ Notes: ## Deep links -The app registers the `clawdbot://` URL scheme for local actions. +The app registers the `moltbot://` URL scheme for local actions. -### `clawdbot://agent` +### `moltbot://agent` Triggers a Gateway `agent` request. ```bash -open 'clawdbot://agent?message=Hello%20from%20deep%20link' +open 'moltbot://agent?message=Hello%20from%20deep%20link' ``` Query parameters: @@ -129,7 +129,7 @@ Safety: ## Onboarding flow (typical) -1) Install and launch **Clawdbot.app**. +1) Install and launch **Moltbot.app**. 2) Complete the permissions checklist (TCC prompts). 3) Ensure **Local** mode is active and the Gateway is running. 4) Install the CLI if you want terminal access. @@ -137,7 +137,7 @@ Safety: ## Build & dev workflow (native) - `cd apps/macos && swift build` -- `swift run Clawdbot` (or Xcode) +- `swift run Moltbot` (or Xcode) - Package app: `scripts/package-mac-app.sh` ## Debug gateway connectivity (macOS CLI) @@ -147,8 +147,8 @@ logic that the macOS app uses, without launching the app. ```bash cd apps/macos -swift run clawdbot-mac connect --json -swift run clawdbot-mac discover --timeout 3000 --json +swift run moltbot-mac connect --json +swift run moltbot-mac discover --timeout 3000 --json ``` Connect options: @@ -163,7 +163,7 @@ Discovery options: - `--timeout `: overall discovery window (default: `2000`) - `--json`: structured output for diffing -Tip: compare against `clawdbot gateway discover --json` to see whether the +Tip: compare against `moltbot gateway discover --json` to see whether the macOS app’s discovery pipeline (NWBrowser + tailnet DNS‑SD fallback) differs from the Node CLI’s `dns-sd` based discovery. diff --git a/docs/platforms/oracle.md b/docs/platforms/oracle.md index d8006754b..b77117054 100644 --- a/docs/platforms/oracle.md +++ b/docs/platforms/oracle.md @@ -1,18 +1,18 @@ --- -summary: "Clawdbot on Oracle Cloud (Always Free ARM)" +summary: "Moltbot on Oracle Cloud (Always Free ARM)" read_when: - - Setting up Clawdbot on Oracle Cloud - - Looking for low-cost VPS hosting for Clawdbot - - Want 24/7 Clawdbot on a small server + - Setting up Moltbot on Oracle Cloud + - Looking for low-cost VPS hosting for Moltbot + - Want 24/7 Moltbot on a small server --- -# Clawdbot on Oracle Cloud (OCI) +# Moltbot on Oracle Cloud (OCI) ## Goal -Run a persistent Clawdbot Gateway on Oracle Cloud's **Always Free** ARM tier. +Run a persistent Moltbot Gateway on Oracle Cloud's **Always Free** ARM tier. -Oracle’s free tier can be a great fit for Clawdbot (especially if you already have an OCI account), but it comes with tradeoffs: +Oracle’s free tier can be a great fit for Moltbot (especially if you already have an OCI account), but it comes with tradeoffs: - ARM architecture (most things work, but some binaries may be x86-only) - Capacity and signup can be finicky @@ -40,7 +40,7 @@ Oracle’s free tier can be a great fit for Clawdbot (especially if you already 1. Log into [Oracle Cloud Console](https://cloud.oracle.com/) 2. Navigate to **Compute → Instances → Create Instance** 3. Configure: - - **Name:** `clawdbot` + - **Name:** `moltbot` - **Image:** Ubuntu 24.04 (aarch64) - **Shape:** `VM.Standard.A1.Flex` (Ampere ARM) - **OCPUs:** 2 (or up to 4) @@ -69,7 +69,7 @@ sudo apt install -y build-essential ```bash # Set hostname -sudo hostnamectl set-hostname clawdbot +sudo hostnamectl set-hostname moltbot # Set password for ubuntu user sudo passwd ubuntu @@ -82,22 +82,22 @@ sudo loginctl enable-linger ubuntu ```bash curl -fsSL https://tailscale.com/install.sh | sh -sudo tailscale up --ssh --hostname=clawdbot +sudo tailscale up --ssh --hostname=moltbot ``` -This enables Tailscale SSH, so you can connect via `ssh clawdbot` from any device on your tailnet — no public IP needed. +This enables Tailscale SSH, so you can connect via `ssh moltbot` from any device on your tailnet — no public IP needed. Verify: ```bash tailscale status ``` -**From now on, connect via Tailscale:** `ssh ubuntu@clawdbot` (or use the Tailscale IP). +**From now on, connect via Tailscale:** `ssh ubuntu@moltbot` (or use the Tailscale IP). -## 5) Install Clawdbot +## 5) Install Moltbot ```bash -curl -fsSL https://clawd.bot/install.sh | bash +curl -fsSL https://molt.bot/install.sh | bash source ~/.bashrc ``` @@ -111,27 +111,27 @@ Use token auth as the default. It’s predictable and avoids needing any “inse ```bash # Keep the Gateway private on the VM -clawdbot config set gateway.bind loopback +moltbot config set gateway.bind loopback # Require auth for the Gateway + Control UI -clawdbot config set gateway.auth.mode token -clawdbot doctor --generate-gateway-token +moltbot config set gateway.auth.mode token +moltbot doctor --generate-gateway-token # Expose over Tailscale Serve (HTTPS + tailnet access) -clawdbot config set gateway.tailscale.mode serve -clawdbot config set gateway.trustedProxies '["127.0.0.1"]' +moltbot config set gateway.tailscale.mode serve +moltbot config set gateway.trustedProxies '["127.0.0.1"]' -systemctl --user restart clawdbot-gateway +systemctl --user restart moltbot-gateway ``` ## 7) Verify ```bash # Check version -clawdbot --version +moltbot --version # Check daemon status -systemctl --user status clawdbot-gateway +systemctl --user status moltbot-gateway # Check Tailscale Serve tailscale serve status @@ -159,7 +159,7 @@ This blocks SSH on port 22, HTTP, HTTPS, and everything else at the network edge From any device on your Tailscale network: ``` -https://clawdbot..ts.net/ +https://moltbot..ts.net/ ``` Replace `` with your tailnet name (visible in `tailscale status`). @@ -175,7 +175,7 @@ No SSH tunnel needed. Tailscale provides: With the VCN locked down (only UDP 41641 open) and the Gateway bound to loopback, you get strong defense-in-depth: public traffic is blocked at the network edge, and admin access happens over your tailnet. -This setup often removes the *need* for extra host-based firewall rules purely to stop Internet-wide SSH brute force — but you should still keep the OS updated, run `clawdbot security audit`, and verify you aren’t accidentally listening on public interfaces. +This setup often removes the *need* for extra host-based firewall rules purely to stop Internet-wide SSH brute force — but you should still keep the OS updated, run `moltbot security audit`, and verify you aren’t accidentally listening on public interfaces. ### What's Already Protected @@ -191,7 +191,7 @@ This setup often removes the *need* for extra host-based firewall rules purely t ### Still Recommended - **Credential permissions:** `chmod 700 ~/.clawdbot` -- **Security audit:** `clawdbot security audit` +- **Security audit:** `moltbot security audit` - **System updates:** `sudo apt update && sudo apt upgrade` regularly - **Monitor Tailscale:** Review devices in [Tailscale admin console](https://login.tailscale.com/admin) @@ -216,7 +216,7 @@ If Tailscale Serve isn't working, use an SSH tunnel: ```bash # From your local machine (via Tailscale) -ssh -L 18789:127.0.0.1:18789 ubuntu@clawdbot +ssh -L 18789:127.0.0.1:18789 ubuntu@moltbot ``` Then open `http://localhost:18789`. @@ -237,14 +237,14 @@ Free tier ARM instances are popular. Try: sudo tailscale status # Re-authenticate -sudo tailscale up --ssh --hostname=clawdbot --reset +sudo tailscale up --ssh --hostname=moltbot --reset ``` ### Gateway won't start ```bash -clawdbot gateway status -clawdbot doctor --non-interactive -journalctl --user -u clawdbot-gateway -n 50 +moltbot gateway status +moltbot doctor --non-interactive +journalctl --user -u moltbot-gateway -n 50 ``` ### Can't reach Control UI @@ -256,7 +256,7 @@ tailscale serve status curl http://localhost:18789 # Restart if needed -systemctl --user restart clawdbot-gateway +systemctl --user restart moltbot-gateway ``` ### ARM binary issues @@ -277,7 +277,7 @@ All state lives in: Back up periodically: ```bash -tar -czvf clawdbot-backup.tar.gz ~/.clawdbot ~/clawd +tar -czvf moltbot-backup.tar.gz ~/.clawdbot ~/clawd ``` --- diff --git a/docs/platforms/raspberry-pi.md b/docs/platforms/raspberry-pi.md index b34e3fcfe..bd5943b17 100644 --- a/docs/platforms/raspberry-pi.md +++ b/docs/platforms/raspberry-pi.md @@ -1,16 +1,16 @@ --- -summary: "Clawdbot on Raspberry Pi (budget self-hosted setup)" +summary: "Moltbot on Raspberry Pi (budget self-hosted setup)" read_when: - - Setting up Clawdbot on a Raspberry Pi - - Running Clawdbot on ARM devices + - Setting up Moltbot on a Raspberry Pi + - Running Moltbot on ARM devices - Building a cheap always-on personal AI --- -# Clawdbot on Raspberry Pi +# Moltbot on Raspberry Pi ## Goal -Run a persistent, always-on Clawdbot Gateway on a Raspberry Pi for **~$35-80** one-time cost (no monthly fees). +Run a persistent, always-on Moltbot Gateway on a Raspberry Pi for **~$35-80** one-time cost (no monthly fees). Perfect for: - 24/7 personal AI assistant @@ -105,19 +105,19 @@ echo 'vm.swappiness=10' | sudo tee -a /etc/sysctl.conf sudo sysctl -p ``` -## 6) Install Clawdbot +## 6) Install Moltbot ### Option A: Standard Install (Recommended) ```bash -curl -fsSL https://clawd.bot/install.sh | bash +curl -fsSL https://molt.bot/install.sh | bash ``` ### Option B: Hackable Install (For tinkering) ```bash -git clone https://github.com/clawdbot/clawdbot.git -cd clawdbot +git clone https://github.com/moltbot/moltbot.git +cd moltbot npm install npm run build npm link @@ -128,7 +128,7 @@ The hackable install gives you direct access to logs and code — useful for deb ## 7) Run Onboarding ```bash -clawdbot onboard --install-daemon +moltbot onboard --install-daemon ``` Follow the wizard: @@ -141,13 +141,13 @@ Follow the wizard: ```bash # Check status -clawdbot status +moltbot status # Check service -sudo systemctl status clawdbot +sudo systemctl status moltbot # View logs -journalctl -u clawdbot -f +journalctl -u moltbot -f ``` ## 9) Access the Dashboard @@ -170,8 +170,8 @@ curl -fsSL https://tailscale.com/install.sh | sh sudo tailscale up # Update config -clawdbot config set gateway.bind tailnet -sudo systemctl restart clawdbot +moltbot config set gateway.bind tailnet +sudo systemctl restart moltbot ``` --- @@ -218,7 +218,7 @@ htop ### Binary Compatibility -Most Clawdbot features work on ARM64, but some external binaries may need ARM builds: +Most Moltbot features work on ARM64, but some external binaries may need ARM builds: | Tool | ARM64 Status | Notes | |------|--------------|-------| @@ -268,13 +268,13 @@ The onboarding wizard sets this up, but to verify: ```bash # Check service is enabled -sudo systemctl is-enabled clawdbot +sudo systemctl is-enabled moltbot # Enable if not -sudo systemctl enable clawdbot +sudo systemctl enable moltbot # Start on boot -sudo systemctl start clawdbot +sudo systemctl start moltbot ``` --- @@ -301,12 +301,12 @@ free -h ```bash # Check logs -journalctl -u clawdbot --no-pager -n 100 +journalctl -u moltbot --no-pager -n 100 # Common fix: rebuild -cd ~/clawdbot # if using hackable install +cd ~/moltbot # if using hackable install npm run build -sudo systemctl restart clawdbot +sudo systemctl restart moltbot ``` ### ARM Binary Issues diff --git a/docs/platforms/windows.md b/docs/platforms/windows.md index fa7d5d35b..372477c59 100644 --- a/docs/platforms/windows.md +++ b/docs/platforms/windows.md @@ -1,12 +1,12 @@ --- summary: "Windows (WSL2) support + companion app status" read_when: - - Installing Clawdbot on Windows + - Installing Moltbot on Windows - Looking for Windows companion app status --- # Windows (WSL2) -Clawdbot on Windows is recommended **via WSL2** (Ubuntu recommended). The +Moltbot on Windows is recommended **via WSL2** (Ubuntu recommended). The CLI + Gateway run inside Linux, which keeps the runtime consistent and makes tooling far more compatible (Node/Bun/pnpm, Linux binaries, skills). Native Windows installs are untested and more problematic. @@ -27,19 +27,19 @@ Native Windows companion apps are planned. Inside WSL2: ``` -clawdbot onboard --install-daemon +moltbot onboard --install-daemon ``` Or: ``` -clawdbot gateway install +moltbot gateway install ``` Or: ``` -clawdbot configure +moltbot configure ``` Select **Gateway service** when prompted. @@ -47,7 +47,7 @@ Select **Gateway service** when prompted. Repair/migrate: ``` -clawdbot doctor +moltbot doctor ``` ## Advanced: expose WSL services over LAN (portproxy) @@ -89,7 +89,7 @@ netsh interface portproxy add v4tov4 listenport=$ListenPort listenaddress=0.0.0. Notes: - SSH from another machine targets the **Windows host IP** (example: `ssh user@windows-host -p 2222`). - Remote nodes must point at a **reachable** Gateway URL (not `127.0.0.1`); use - `clawdbot status --all` to confirm. + `moltbot status --all` to confirm. - Use `listenaddress=0.0.0.0` for LAN access; `127.0.0.1` keeps it local only. - If you want this automatic, register a Scheduled Task to run the refresh step at login. @@ -132,17 +132,17 @@ Re-open Ubuntu, then verify: systemctl --user status ``` -### 3) Install Clawdbot (inside WSL) +### 3) Install Moltbot (inside WSL) Follow the Linux Getting Started flow inside WSL: ```bash -git clone https://github.com/clawdbot/clawdbot.git -cd clawdbot +git clone https://github.com/moltbot/moltbot.git +cd moltbot pnpm install pnpm ui:build # auto-installs UI deps on first run pnpm build -clawdbot onboard +moltbot onboard ``` Full guide: [Getting Started](/start/getting-started) diff --git a/docs/plugin.md b/docs/plugin.md index c57a024f2..1b5a20608 100644 --- a/docs/plugin.md +++ b/docs/plugin.md @@ -1,5 +1,5 @@ --- -summary: "Clawdbot plugins/extensions: discovery, config, and safety" +summary: "Moltbot plugins/extensions: discovery, config, and safety" read_when: - Adding or modifying plugins/extensions - Documenting plugin install or load rules @@ -8,11 +8,11 @@ read_when: ## Quick start (new to plugins?) -A plugin is just a **small code module** that extends Clawdbot with extra +A plugin is just a **small code module** that extends Moltbot with extra features (commands, tools, and Gateway RPC). Most of the time, you’ll use plugins when you want a feature that’s not built -into core Clawdbot yet (or you want to keep optional features out of your main +into core Moltbot yet (or you want to keep optional features out of your main install). Fast path: @@ -20,13 +20,13 @@ Fast path: 1) See what’s already loaded: ```bash -clawdbot plugins list +moltbot plugins list ``` 2) Install an official plugin (example: Voice Call): ```bash -clawdbot plugins install @clawdbot/voice-call +moltbot plugins install @moltbot/voice-call ``` 3) Restart the Gateway, then configure under `plugins.entries..config`. @@ -35,21 +35,21 @@ See [Voice Call](/plugins/voice-call) for a concrete example plugin. ## Available plugins (official) -- Microsoft Teams is plugin-only as of 2026.1.15; install `@clawdbot/msteams` if you use Teams. +- Microsoft Teams is plugin-only as of 2026.1.15; install `@moltbot/msteams` if you use Teams. - Memory (Core) — bundled memory search plugin (enabled by default via `plugins.slots.memory`) - Memory (LanceDB) — bundled long-term memory plugin (auto-recall/capture; set `plugins.slots.memory = "memory-lancedb"`) -- [Voice Call](/plugins/voice-call) — `@clawdbot/voice-call` -- [Zalo Personal](/plugins/zalouser) — `@clawdbot/zalouser` -- [Matrix](/channels/matrix) — `@clawdbot/matrix` -- [Nostr](/channels/nostr) — `@clawdbot/nostr` -- [Zalo](/channels/zalo) — `@clawdbot/zalo` -- [Microsoft Teams](/channels/msteams) — `@clawdbot/msteams` +- [Voice Call](/plugins/voice-call) — `@moltbot/voice-call` +- [Zalo Personal](/plugins/zalouser) — `@moltbot/zalouser` +- [Matrix](/channels/matrix) — `@moltbot/matrix` +- [Nostr](/channels/nostr) — `@moltbot/nostr` +- [Zalo](/channels/zalo) — `@moltbot/zalo` +- [Microsoft Teams](/channels/msteams) — `@moltbot/msteams` - Google Antigravity OAuth (provider auth) — bundled as `google-antigravity-auth` (disabled by default) - Gemini CLI OAuth (provider auth) — bundled as `google-gemini-cli-auth` (disabled by default) - Qwen OAuth (provider auth) — bundled as `qwen-portal-auth` (disabled by default) - Copilot Proxy (provider auth) — local VS Code Copilot Proxy bridge; distinct from built-in `github-copilot` device login (bundled, disabled by default) -Clawdbot plugins are **TypeScript modules** loaded at runtime via jiti. **Config +Moltbot plugins are **TypeScript modules** loaded at runtime via jiti. **Config validation does not execute plugin code**; it uses the plugin manifest and JSON Schema instead. See [Plugin manifest](/plugins/manifest). @@ -73,7 +73,7 @@ Plugins can access selected core helpers via `api.runtime`. For telephony TTS: ```ts const result = await api.runtime.tts.textToSpeechTelephony({ - text: "Hello from Clawdbot", + text: "Hello from Moltbot", cfg: api.config, }); ``` @@ -85,7 +85,7 @@ Notes: ## Discovery & precedence -Clawdbot scans, in order: +Moltbot scans, in order: 1) Config paths - `plugins.load.paths` (file or directory) @@ -98,14 +98,14 @@ Clawdbot scans, in order: - `~/.clawdbot/extensions/*.ts` - `~/.clawdbot/extensions/*/index.ts` -4) Bundled extensions (shipped with Clawdbot, **disabled by default**) -- `/extensions/*` +4) Bundled extensions (shipped with Moltbot, **disabled by default**) +- `/extensions/*` Bundled plugins must be enabled explicitly via `plugins.entries..enabled` -or `clawdbot plugins enable `. Installed plugins are enabled by default, +or `moltbot plugins enable `. Installed plugins are enabled by default, but can be disabled the same way. -Each plugin must include a `clawdbot.plugin.json` file in its root. If a path +Each plugin must include a `moltbot.plugin.json` file in its root. If a path points at a file, the plugin root is the file's directory and must contain the manifest. @@ -114,12 +114,12 @@ wins and lower-precedence copies are ignored. ### Package packs -A plugin directory may include a `package.json` with `clawdbot.extensions`: +A plugin directory may include a `package.json` with `moltbot.extensions`: ```json { "name": "my-pack", - "clawdbot": { + "moltbot": { "extensions": ["./src/safety.ts", "./src/tools.ts"] } } @@ -133,15 +133,15 @@ If your plugin imports npm deps, install them in that directory so ### Channel catalog metadata -Channel plugins can advertise onboarding metadata via `clawdbot.channel` and -install hints via `clawdbot.install`. This keeps the core catalog data-free. +Channel plugins can advertise onboarding metadata via `moltbot.channel` and +install hints via `moltbot.install`. This keeps the core catalog data-free. Example: ```json { - "name": "@clawdbot/nextcloud-talk", - "clawdbot": { + "name": "@moltbot/nextcloud-talk", + "moltbot": { "extensions": ["./index.ts"], "channel": { "id": "nextcloud-talk", @@ -154,7 +154,7 @@ Example: "aliases": ["nc-talk", "nc"] }, "install": { - "npmSpec": "@clawdbot/nextcloud-talk", + "npmSpec": "@moltbot/nextcloud-talk", "localPath": "extensions/nextcloud-talk", "defaultChoice": "npm" } @@ -162,7 +162,7 @@ Example: } ``` -Clawdbot can also merge **external channel catalogs** (for example, an MPM +Moltbot can also merge **external channel catalogs** (for example, an MPM registry export). Drop a JSON file at one of: - `~/.clawdbot/mpm/plugins.json` - `~/.clawdbot/mpm/catalog.json` @@ -170,7 +170,7 @@ registry export). Drop a JSON file at one of: Or point `CLAWDBOT_PLUGIN_CATALOG_PATHS` (or `CLAWDBOT_MPM_CATALOG_PATHS`) at one or more JSON files (comma/semicolon/`PATH`-delimited). Each file should -contain `{ "entries": [ { "name": "@scope/pkg", "clawdbot": { "channel": {...}, "install": {...} } } ] }`. +contain `{ "entries": [ { "name": "@scope/pkg", "moltbot": { "channel": {...}, "install": {...} } } ] }`. ## Plugin IDs @@ -179,7 +179,7 @@ Default plugin ids: - Package packs: `package.json` `name` - Standalone file: file base name (`~/.../voice-call.ts` → `voice-call`) -If a plugin exports `id`, Clawdbot uses it but warns when it doesn’t match the +If a plugin exports `id`, Moltbot uses it but warns when it doesn’t match the configured id. ## Config @@ -212,7 +212,7 @@ Validation rules (strict): - Unknown `channels.` keys are **errors** unless a plugin manifest declares the channel id. - Plugin config is validated using the JSON Schema embedded in - `clawdbot.plugin.json` (`configSchema`). + `moltbot.plugin.json` (`configSchema`). - If a plugin is disabled, its config is preserved and a **warning** is emitted. ## Plugin slots (exclusive categories) @@ -237,7 +237,7 @@ are disabled with diagnostics. The Control UI uses `config.schema` (JSON Schema + `uiHints`) to render better forms. -Clawdbot augments `uiHints` at runtime based on discovered plugins: +Moltbot augments `uiHints` at runtime based on discovered plugins: - Adds per-plugin labels for `plugins.entries.` / `.enabled` / `.config` - Merges optional plugin-provided config field hints under: @@ -269,24 +269,24 @@ Example: ## CLI ```bash -clawdbot plugins list -clawdbot plugins info -clawdbot plugins install # copy a local file/dir into ~/.clawdbot/extensions/ -clawdbot plugins install ./extensions/voice-call # relative path ok -clawdbot plugins install ./plugin.tgz # install from a local tarball -clawdbot plugins install ./plugin.zip # install from a local zip -clawdbot plugins install -l ./extensions/voice-call # link (no copy) for dev -clawdbot plugins install @clawdbot/voice-call # install from npm -clawdbot plugins update -clawdbot plugins update --all -clawdbot plugins enable -clawdbot plugins disable -clawdbot plugins doctor +moltbot plugins list +moltbot plugins info +moltbot plugins install # copy a local file/dir into ~/.clawdbot/extensions/ +moltbot plugins install ./extensions/voice-call # relative path ok +moltbot plugins install ./plugin.tgz # install from a local tarball +moltbot plugins install ./plugin.zip # install from a local zip +moltbot plugins install -l ./extensions/voice-call # link (no copy) for dev +moltbot plugins install @moltbot/voice-call # install from npm +moltbot plugins update +moltbot plugins update --all +moltbot plugins enable +moltbot plugins disable +moltbot plugins doctor ``` `plugins update` only works for npm installs tracked under `plugins.installs`. -Plugins may also register their own top‑level commands (example: `clawdbot voicecall`). +Plugins may also register their own top‑level commands (example: `moltbot voicecall`). ## Plugin API (overview) @@ -303,7 +303,7 @@ event-driven automation without a separate hook pack install. ### Example ``` -import { registerPluginHooksFromDir } from "clawdbot/plugin-sdk"; +import { registerPluginHooksFromDir } from "moltbot/plugin-sdk"; export default function register(api) { registerPluginHooksFromDir(api, "./hooks"); @@ -313,18 +313,18 @@ export default function register(api) { Notes: - Hook directories follow the normal hook structure (`HOOK.md` + `handler.ts`). - Hook eligibility rules still apply (OS/bins/env/config requirements). -- Plugin-managed hooks show up in `clawdbot hooks list` with `plugin:`. -- You cannot enable/disable plugin-managed hooks via `clawdbot hooks`; enable/disable the plugin instead. +- Plugin-managed hooks show up in `moltbot hooks list` with `plugin:`. +- You cannot enable/disable plugin-managed hooks via `moltbot hooks`; enable/disable the plugin instead. ## Provider plugins (model auth) Plugins can register **model provider auth** flows so users can run OAuth or -API-key setup inside Clawdbot (no external scripts needed). +API-key setup inside Moltbot (no external scripts needed). Register a provider via `api.registerProvider(...)`. Each provider exposes one or more auth methods (OAuth, API key, device code, etc.). These methods power: -- `clawdbot models auth login --provider [--method ]` +- `moltbot models auth login --provider [--method ]` Example: @@ -536,7 +536,7 @@ Command handler context: - `isAuthorizedSender`: Whether the sender is an authorized user - `args`: Arguments passed after the command (if `acceptsArgs: true`) - `commandBody`: The full command text -- `config`: The current Clawdbot config +- `config`: The current Moltbot config Command options: @@ -598,14 +598,14 @@ it’s present in your workspace/managed skills locations. Recommended packaging: -- Main package: `clawdbot` (this repo) -- Plugins: separate npm packages under `@clawdbot/*` (example: `@clawdbot/voice-call`) +- Main package: `moltbot` (this repo) +- Plugins: separate npm packages under `@moltbot/*` (example: `@moltbot/voice-call`) Publishing contract: -- Plugin `package.json` must include `clawdbot.extensions` with one or more entry files. +- Plugin `package.json` must include `moltbot.extensions` with one or more entry files. - Entry files can be `.js` or `.ts` (jiti loads TS at runtime). -- `clawdbot plugins install ` uses `npm pack`, extracts into `~/.clawdbot/extensions//`, and enables it in config. +- `moltbot plugins install ` uses `npm pack`, extracts into `~/.clawdbot/extensions//`, and enables it in config. - Config key stability: scoped packages are normalized to the **unscoped** id for `plugins.entries.*`. ## Example plugin: Voice Call @@ -614,7 +614,7 @@ This repo includes a voice‑call plugin (Twilio or log fallback): - Source: `extensions/voice-call` - Skill: `skills/voice-call` -- CLI: `clawdbot voicecall start|status` +- CLI: `moltbot voicecall start|status` - Tool: `voice_call` - RPC: `voicecall.start`, `voicecall.status` - Config (twilio): `provider: "twilio"` + `twilio.accountSid/authToken/from` (optional `statusCallbackUrl`, `twimlUrl`) @@ -635,4 +635,4 @@ Plugins run in-process with the Gateway. Treat them as trusted code: Plugins can (and should) ship tests: - In-repo plugins can keep Vitest tests under `src/**` (example: `src/plugins/voice-call.plugin.test.ts`). -- Separately published plugins should run their own CI (lint/build/test) and validate `clawdbot.extensions` points at the built entrypoint (`dist/index.js`). +- Separately published plugins should run their own CI (lint/build/test) and validate `moltbot.extensions` points at the built entrypoint (`dist/index.js`). diff --git a/docs/plugins/agent-tools.md b/docs/plugins/agent-tools.md index b0d91dfa9..d8c7aa894 100644 --- a/docs/plugins/agent-tools.md +++ b/docs/plugins/agent-tools.md @@ -6,7 +6,7 @@ read_when: --- # Plugin agent tools -Clawdbot plugins can register **agent tools** (JSON‑schema functions) that are exposed +Moltbot plugins can register **agent tools** (JSON‑schema functions) that are exposed to the LLM during agent runs. Tools can be **required** (always available) or **optional** (opt‑in). diff --git a/docs/plugins/manifest.md b/docs/plugins/manifest.md index 468349182..d55528e69 100644 --- a/docs/plugins/manifest.md +++ b/docs/plugins/manifest.md @@ -1,13 +1,13 @@ --- summary: "Plugin manifest + JSON schema requirements (strict config validation)" read_when: - - You are building a Clawdbot plugin + - You are building a Moltbot plugin - You need to ship a plugin config schema or debug plugin validation errors --- -# Plugin manifest (clawdbot.plugin.json) +# Plugin manifest (moltbot.plugin.json) -Every plugin **must** ship a `clawdbot.plugin.json` file in the **plugin root**. -Clawdbot uses this manifest to validate configuration **without executing plugin +Every plugin **must** ship a `moltbot.plugin.json` file in the **plugin root**. +Moltbot uses this manifest to validate configuration **without executing plugin code**. Missing or invalid manifests are treated as plugin errors and block config validation. diff --git a/docs/plugins/voice-call.md b/docs/plugins/voice-call.md index 46713c939..4440a9eb9 100644 --- a/docs/plugins/voice-call.md +++ b/docs/plugins/voice-call.md @@ -1,13 +1,13 @@ --- summary: "Voice Call plugin: outbound + inbound calls via Twilio/Telnyx/Plivo (plugin install + config + CLI)" read_when: - - You want to place an outbound voice call from Clawdbot + - You want to place an outbound voice call from Moltbot - You are configuring or developing the voice-call plugin --- # Voice Call (plugin) -Voice calls for Clawdbot via a plugin. Supports outbound notifications and +Voice calls for Moltbot via a plugin. Supports outbound notifications and multi-turn conversations with inbound policies. Current providers: @@ -20,7 +20,7 @@ Quick mental model: - Install plugin - Restart Gateway - Configure under `plugins.entries.voice-call.config` -- Use `clawdbot voicecall ...` or the `voice_call` tool +- Use `moltbot voicecall ...` or the `voice_call` tool ## Where it runs (local vs remote) @@ -33,7 +33,7 @@ If you use a remote Gateway, install/configure the plugin on the **machine runni ### Option A: install from npm (recommended) ```bash -clawdbot plugins install @clawdbot/voice-call +moltbot plugins install @moltbot/voice-call ``` Restart the Gateway afterwards. @@ -41,7 +41,7 @@ Restart the Gateway afterwards. ### Option B: install from a local folder (dev, no copying) ```bash -clawdbot plugins install ./extensions/voice-call +moltbot plugins install ./extensions/voice-call cd ./extensions/voice-call && pnpm install ``` @@ -208,13 +208,13 @@ Auto-responses use the agent system. Tune with: ## CLI ```bash -clawdbot voicecall call --to "+15555550123" --message "Hello from Clawdbot" -clawdbot voicecall continue --call-id --message "Any questions?" -clawdbot voicecall speak --call-id --message "One moment" -clawdbot voicecall end --call-id -clawdbot voicecall status --call-id -clawdbot voicecall tail -clawdbot voicecall expose --mode funnel +moltbot voicecall call --to "+15555550123" --message "Hello from Moltbot" +moltbot voicecall continue --call-id --message "Any questions?" +moltbot voicecall speak --call-id --message "One moment" +moltbot voicecall end --call-id +moltbot voicecall status --call-id +moltbot voicecall tail +moltbot voicecall expose --mode funnel ``` ## Agent tool diff --git a/docs/plugins/zalouser.md b/docs/plugins/zalouser.md index d2f2bef6c..64de33cf6 100644 --- a/docs/plugins/zalouser.md +++ b/docs/plugins/zalouser.md @@ -1,13 +1,13 @@ --- summary: "Zalo Personal plugin: QR login + messaging via zca-cli (plugin install + channel config + CLI + tool)" read_when: - - You want Zalo Personal (unofficial) support in Clawdbot + - You want Zalo Personal (unofficial) support in Moltbot - You are configuring or developing the zalouser plugin --- # Zalo Personal (plugin) -Zalo Personal support for Clawdbot via a plugin, using `zca-cli` to automate a normal Zalo user account. +Zalo Personal support for Moltbot via a plugin, using `zca-cli` to automate a normal Zalo user account. > **Warning:** Unofficial automation may lead to account suspension/ban. Use at your own risk. @@ -24,7 +24,7 @@ If you use a remote Gateway, install/configure it on the **machine running the G ### Option A: install from npm ```bash -clawdbot plugins install @clawdbot/zalouser +moltbot plugins install @moltbot/zalouser ``` Restart the Gateway afterwards. @@ -32,7 +32,7 @@ Restart the Gateway afterwards. ### Option B: install from a local folder (dev) ```bash -clawdbot plugins install ./extensions/zalouser +moltbot plugins install ./extensions/zalouser cd ./extensions/zalouser && pnpm install ``` @@ -62,11 +62,11 @@ Channel config lives under `channels.zalouser` (not `plugins.entries.*`): ## CLI ```bash -clawdbot channels login --channel zalouser -clawdbot channels logout --channel zalouser -clawdbot channels status --probe -clawdbot message send --channel zalouser --target --message "Hello from Clawdbot" -clawdbot directory peers list --channel zalouser --query "name" +moltbot channels login --channel zalouser +moltbot channels logout --channel zalouser +moltbot channels status --probe +moltbot message send --channel zalouser --target --message "Hello from Moltbot" +moltbot directory peers list --channel zalouser --query "name" ``` ## Agent tool diff --git a/docs/prose.md b/docs/prose.md index c116c5f96..eb997732b 100644 --- a/docs/prose.md +++ b/docs/prose.md @@ -1,5 +1,5 @@ --- -summary: "OpenProse: .prose workflows, slash commands, and state in Clawdbot" +summary: "OpenProse: .prose workflows, slash commands, and state in Moltbot" read_when: - You want to run or write .prose workflows - You want to enable the OpenProse plugin @@ -7,7 +7,7 @@ read_when: --- # OpenProse -OpenProse is a portable, markdown-first workflow format for orchestrating AI sessions. In Clawdbot it ships as a plugin that installs an OpenProse skill pack plus a `/prose` slash command. Programs live in `.prose` files and can spawn multiple sub-agents with explicit control flow. +OpenProse is a portable, markdown-first workflow format for orchestrating AI sessions. In Moltbot it ships as a plugin that installs an OpenProse skill pack plus a `/prose` slash command. Programs live in `.prose` files and can spawn multiple sub-agents with explicit control flow. Official site: https://www.prose.md @@ -22,18 +22,18 @@ Official site: https://www.prose.md Bundled plugins are disabled by default. Enable OpenProse: ```bash -clawdbot plugins enable open-prose +moltbot plugins enable open-prose ``` Restart the Gateway after enabling the plugin. -Dev/local checkout: `clawdbot plugins install ./extensions/open-prose` +Dev/local checkout: `moltbot plugins install ./extensions/open-prose` Related docs: [Plugins](/plugin), [Plugin manifest](/plugins/manifest), [Skills](/tools/skills). ## Slash command -OpenProse registers `/prose` as a user-invocable skill command. It routes to the OpenProse VM instructions and uses Clawdbot tools under the hood. +OpenProse registers `/prose` as a user-invocable skill command. It routes to the OpenProse VM instructions and uses Moltbot tools under the hood. Common commands: @@ -112,11 +112,11 @@ Notes: `/prose run ` resolves to `https://p.prose.md//`. Direct URLs are fetched as-is. This uses the `web_fetch` tool (or `exec` for POST). -## Clawdbot runtime mapping +## Moltbot runtime mapping -OpenProse programs map to Clawdbot primitives: +OpenProse programs map to Moltbot primitives: -| OpenProse concept | Clawdbot tool | +| OpenProse concept | Moltbot tool | | --- | --- | | Spawn session / Task tool | `sessions_spawn` | | File read/write | `read` / `write` | @@ -126,6 +126,6 @@ If your tool allowlist blocks these tools, OpenProse programs will fail. See [Sk ## Security + approvals -Treat `.prose` files like code. Review before running. Use Clawdbot tool allowlists and approval gates to control side effects. +Treat `.prose` files like code. Review before running. Use Moltbot tool allowlists and approval gates to control side effects. For deterministic, approval-gated workflows, compare with [Lobster](/tools/lobster). diff --git a/docs/providers/anthropic.md b/docs/providers/anthropic.md index 018e130dd..1a7a5e8d1 100644 --- a/docs/providers/anthropic.md +++ b/docs/providers/anthropic.md @@ -1,13 +1,13 @@ --- -summary: "Use Anthropic Claude via API keys or setup-token in Clawdbot" +summary: "Use Anthropic Claude via API keys or setup-token in Moltbot" read_when: - - You want to use Anthropic models in Clawdbot + - You want to use Anthropic models in Moltbot - You want setup-token instead of API keys --- # Anthropic (Claude) Anthropic builds the **Claude** model family and provides access via an API. -In Clawdbot you can authenticate with an API key or a **setup-token**. +In Moltbot you can authenticate with an API key or a **setup-token**. ## Option A: Anthropic API key @@ -17,11 +17,11 @@ Create your API key in the Anthropic Console. ### CLI setup ```bash -clawdbot onboard +moltbot onboard # choose: Anthropic API key # or non-interactive -clawdbot onboard --anthropic-api-key "$ANTHROPIC_API_KEY" +moltbot onboard --anthropic-api-key "$ANTHROPIC_API_KEY" ``` ### Config snippet @@ -35,7 +35,7 @@ clawdbot onboard --anthropic-api-key "$ANTHROPIC_API_KEY" ## Prompt caching (Anthropic API) -Clawdbot does **not** override Anthropic’s default cache TTL unless you set it. +Moltbot does **not** override Anthropic’s default cache TTL unless you set it. This is **API-only**; subscription auth does not honor TTL settings. To set the TTL per model, use `cacheControlTtl` in the model `params`: @@ -54,7 +54,7 @@ To set the TTL per model, use `cacheControlTtl` in the model `params`: } ``` -Clawdbot includes the `extended-cache-ttl-2025-04-11` beta flag for Anthropic API +Moltbot includes the `extended-cache-ttl-2025-04-11` beta flag for Anthropic API requests; keep it if you override provider headers (see [/gateway/configuration](/gateway/configuration)). ## Option B: Claude setup-token @@ -69,23 +69,23 @@ Setup-tokens are created by the **Claude Code CLI**, not the Anthropic Console. claude setup-token ``` -Paste the token into Clawdbot (wizard: **Anthropic token (paste setup-token)**), or run it on the gateway host: +Paste the token into Moltbot (wizard: **Anthropic token (paste setup-token)**), or run it on the gateway host: ```bash -clawdbot models auth setup-token --provider anthropic +moltbot models auth setup-token --provider anthropic ``` If you generated the token on a different machine, paste it: ```bash -clawdbot models auth paste-token --provider anthropic +moltbot models auth paste-token --provider anthropic ``` ### CLI setup ```bash # Paste a setup-token during onboarding -clawdbot onboard --auth-choice setup-token +moltbot onboard --auth-choice setup-token ``` ### Config snippet @@ -98,7 +98,7 @@ clawdbot onboard --auth-choice setup-token ## Notes -- Generate the setup-token with `claude setup-token` and paste it, or run `clawdbot models auth setup-token` on the gateway host. +- Generate the setup-token with `claude setup-token` and paste it, or run `moltbot models auth setup-token` on the gateway host. - If you see “OAuth token refresh failed …” on a Claude subscription, re-auth with a setup-token. See [/gateway/troubleshooting#oauth-token-refresh-failed-anthropic-claude-subscription](/gateway/troubleshooting#oauth-token-refresh-failed-anthropic-claude-subscription). - Auth details + reuse rules are in [/concepts/oauth](/concepts/oauth). @@ -108,19 +108,19 @@ clawdbot onboard --auth-choice setup-token - Claude subscription auth can expire or be revoked. Re-run `claude setup-token` and paste it into the **gateway host**. - If the Claude CLI login lives on a different machine, use - `clawdbot models auth paste-token --provider anthropic` on the gateway host. + `moltbot models auth paste-token --provider anthropic` on the gateway host. **No API key found for provider "anthropic"** - Auth is **per agent**. New agents don’t inherit the main agent’s keys. - Re-run onboarding for that agent, or paste a setup-token / API key on the - gateway host, then verify with `clawdbot models status`. + gateway host, then verify with `moltbot models status`. **No credentials found for profile `anthropic:default`** -- Run `clawdbot models status` to see which auth profile is active. +- Run `moltbot models status` to see which auth profile is active. - Re-run onboarding, or paste a setup-token / API key for that profile. **No available auth profile (all in cooldown/unavailable)** -- Check `clawdbot models status --json` for `auth.unusableProfiles`. +- Check `moltbot models status --json` for `auth.unusableProfiles`. - Add another Anthropic profile or wait for cooldown. More: [/gateway/troubleshooting](/gateway/troubleshooting) and [/help/faq](/help/faq). diff --git a/docs/providers/claude-max-api-proxy.md b/docs/providers/claude-max-api-proxy.md index d2bb6cde8..cb8e36829 100644 --- a/docs/providers/claude-max-api-proxy.md +++ b/docs/providers/claude-max-api-proxy.md @@ -67,9 +67,9 @@ curl http://localhost:3456/v1/chat/completions \ }' ``` -### With Clawdbot +### With Moltbot -You can point Clawdbot at the proxy as a custom OpenAI-compatible endpoint: +You can point Moltbot at the proxy as a custom OpenAI-compatible endpoint: ```json5 { @@ -134,12 +134,12 @@ launchctl bootstrap gui/$(id -u) ~/Library/LaunchAgents/com.claude-max-api.plist ## Notes -- This is a **community tool**, not officially supported by Anthropic or Clawdbot +- This is a **community tool**, not officially supported by Anthropic or Moltbot - Requires an active Claude Max/Pro subscription with Claude Code CLI authenticated - The proxy runs locally and does not send data to any third-party servers - Streaming responses are fully supported ## See Also -- [Anthropic provider](/providers/anthropic) - Native Clawdbot integration with Claude setup-token or API keys +- [Anthropic provider](/providers/anthropic) - Native Moltbot integration with Claude setup-token or API keys - [OpenAI provider](/providers/openai) - For OpenAI/Codex subscriptions diff --git a/docs/providers/deepgram.md b/docs/providers/deepgram.md index 133bc132c..d4e4e404a 100644 --- a/docs/providers/deepgram.md +++ b/docs/providers/deepgram.md @@ -6,10 +6,10 @@ read_when: --- # Deepgram (Audio Transcription) -Deepgram is a speech-to-text API. In Clawdbot it is used for **inbound audio/voice note +Deepgram is a speech-to-text API. In Moltbot it is used for **inbound audio/voice note transcription** via `tools.media.audio`. -When enabled, Clawdbot uploads the audio file to Deepgram and injects the transcript +When enabled, Moltbot uploads the audio file to Deepgram and injects the transcript into the reply pipeline (`{{Transcript}}` + `[Audio]` block). This is **not streaming**; it uses the pre-recorded transcription endpoint. diff --git a/docs/providers/github-copilot.md b/docs/providers/github-copilot.md index b35e05011..c7b68d1bd 100644 --- a/docs/providers/github-copilot.md +++ b/docs/providers/github-copilot.md @@ -1,28 +1,28 @@ --- -summary: "Sign in to GitHub Copilot from Clawdbot using the device flow" +summary: "Sign in to GitHub Copilot from Moltbot using the device flow" read_when: - You want to use GitHub Copilot as a model provider - - You need the `clawdbot models auth login-github-copilot` flow + - You need the `moltbot models auth login-github-copilot` flow --- # Github Copilot ## What is GitHub Copilot? GitHub Copilot is GitHub's AI coding assistant. It provides access to Copilot -models for your GitHub account and plan. Clawdbot can use Copilot as a model +models for your GitHub account and plan. Moltbot can use Copilot as a model provider in two different ways. -## Two ways to use Copilot in Clawdbot +## Two ways to use Copilot in Moltbot ### 1) Built-in GitHub Copilot provider (`github-copilot`) Use the native device-login flow to obtain a GitHub token, then exchange it for -Copilot API tokens when Clawdbot runs. This is the **default** and simplest path +Copilot API tokens when Moltbot runs. This is the **default** and simplest path because it does not require VS Code. ### 2) Copilot Proxy plugin (`copilot-proxy`) -Use the **Copilot Proxy** VS Code extension as a local bridge. Clawdbot talks to +Use the **Copilot Proxy** VS Code extension as a local bridge. Moltbot talks to the proxy’s `/v1` endpoint and uses the model list you configure there. Choose this when you already run Copilot Proxy in VS Code or need to route through it. You must enable the plugin and keep the VS Code extension running. @@ -34,7 +34,7 @@ profile. ## CLI setup ```bash -clawdbot models auth login-github-copilot +moltbot models auth login-github-copilot ``` You'll be prompted to visit a URL and enter a one-time code. Keep the terminal @@ -43,14 +43,14 @@ open until it completes. ### Optional flags ```bash -clawdbot models auth login-github-copilot --profile-id github-copilot:work -clawdbot models auth login-github-copilot --yes +moltbot models auth login-github-copilot --profile-id github-copilot:work +moltbot models auth login-github-copilot --yes ``` ## Set a default model ```bash -clawdbot models set github-copilot/gpt-4o +moltbot models set github-copilot/gpt-4o ``` ### Config snippet @@ -67,4 +67,4 @@ clawdbot models set github-copilot/gpt-4o - Copilot model availability depends on your plan; if a model is rejected, try another ID (for example `github-copilot/gpt-4.1`). - The login stores a GitHub token in the auth profile store and exchanges it for a - Copilot API token when Clawdbot runs. + Copilot API token when Moltbot runs. diff --git a/docs/providers/glm.md b/docs/providers/glm.md index 2bfd2c5fa..60358a40d 100644 --- a/docs/providers/glm.md +++ b/docs/providers/glm.md @@ -1,18 +1,18 @@ --- -summary: "GLM model family overview + how to use it in Clawdbot" +summary: "GLM model family overview + how to use it in Moltbot" read_when: - - You want GLM models in Clawdbot + - You want GLM models in Moltbot - You need the model naming convention and setup --- # GLM models -GLM is a **model family** (not a company) available through the Z.AI platform. In Clawdbot, GLM +GLM is a **model family** (not a company) available through the Z.AI platform. In Moltbot, GLM models are accessed via the `zai` provider and model IDs like `zai/glm-4.7`. ## CLI setup ```bash -clawdbot onboard --auth-choice zai-api-key +moltbot onboard --auth-choice zai-api-key ``` ## Config snippet diff --git a/docs/providers/index.md b/docs/providers/index.md index c71359929..83e316621 100644 --- a/docs/providers/index.md +++ b/docs/providers/index.md @@ -1,12 +1,12 @@ --- -summary: "Model providers (LLMs) supported by Clawdbot" +summary: "Model providers (LLMs) supported by Moltbot" read_when: - You want to choose a model provider - You need a quick overview of supported LLM backends --- # Model Providers -Clawdbot can use many LLM providers. Pick a provider, authenticate, then set the +Moltbot can use many LLM providers. Pick a provider, authenticate, then set the default model as `provider/model`. Looking for chat channel docs (WhatsApp/Telegram/Discord/Slack/Mattermost (plugin)/etc.)? See [Channels](/channels). @@ -22,7 +22,7 @@ See [Venice AI](/providers/venice). ## Quick start -1) Authenticate with the provider (usually via `clawdbot onboard`). +1) Authenticate with the provider (usually via `moltbot onboard`). 2) Set the default model: ```json5 diff --git a/docs/providers/minimax.md b/docs/providers/minimax.md index 36cc8aca2..79b07a7b3 100644 --- a/docs/providers/minimax.md +++ b/docs/providers/minimax.md @@ -1,7 +1,7 @@ --- -summary: "Use MiniMax M2.1 in Clawdbot" +summary: "Use MiniMax M2.1 in Moltbot" read_when: - - You want MiniMax models in Clawdbot + - You want MiniMax models in Moltbot - You need MiniMax setup guidance --- # MiniMax @@ -40,7 +40,7 @@ MiniMax highlights these improvements in M2.1: **Best for:** hosted MiniMax with Anthropic-compatible API. Configure via CLI: -- Run `clawdbot configure` +- Run `moltbot configure` - Select **Model/auth** - Choose **MiniMax M2.1** @@ -100,7 +100,7 @@ Configure via CLI: We have seen strong results with MiniMax M2.1 on powerful hardware (e.g. a desktop/server) using LM Studio's local server. -Configure manually via `clawdbot.json`: +Configure manually via `moltbot.json`: ```json5 { @@ -134,11 +134,11 @@ Configure manually via `clawdbot.json`: } ``` -## Configure via `clawdbot configure` +## Configure via `moltbot configure` Use the interactive config wizard to set MiniMax without editing JSON: -1) Run `clawdbot configure`. +1) Run `moltbot configure`. 2) Select **Model/auth**. 3) Choose **MiniMax M2.1**. 4) Pick your default model when prompted. @@ -159,7 +159,7 @@ Use the interactive config wizard to set MiniMax without editing JSON: - Update pricing values in `models.json` if you need exact cost tracking. - Referral link for MiniMax Coding Plan (10% off): https://platform.minimax.io/subscribe/coding-plan?code=DbXJTRClnb&source=link - See [/concepts/model-providers](/concepts/model-providers) for provider rules. -- Use `clawdbot models list` and `clawdbot models set minimax/MiniMax-M2.1` to switch. +- Use `moltbot models list` and `moltbot models set minimax/MiniMax-M2.1` to switch. ## Troubleshooting @@ -169,7 +169,7 @@ This usually means the **MiniMax provider isn’t configured** (no provider entr and no MiniMax auth profile/env key found). A fix for this detection is in **2026.1.12** (unreleased at the time of writing). Fix by: - Upgrading to **2026.1.12** (or run from source `main`), then restarting the gateway. -- Running `clawdbot configure` and selecting **MiniMax M2.1**, or +- Running `moltbot configure` and selecting **MiniMax M2.1**, or - Adding the `models.providers.minimax` block manually, or - Setting `MINIMAX_API_KEY` (or a MiniMax auth profile) so the provider can be injected. @@ -179,5 +179,5 @@ Make sure the model id is **case‑sensitive**: Then recheck with: ```bash -clawdbot models list +moltbot models list ``` diff --git a/docs/providers/models.md b/docs/providers/models.md index e581740a7..8c2ed4f5b 100644 --- a/docs/providers/models.md +++ b/docs/providers/models.md @@ -1,12 +1,12 @@ --- -summary: "Model providers (LLMs) supported by Clawdbot" +summary: "Model providers (LLMs) supported by Moltbot" read_when: - You want to choose a model provider - You want quick setup examples for LLM auth + model selection --- # Model Providers -Clawdbot can use many LLM providers. Pick one, authenticate, then set the default +Moltbot can use many LLM providers. Pick one, authenticate, then set the default model as `provider/model`. ## Highlight: Venius (Venice AI) @@ -20,7 +20,7 @@ See [Venice AI](/providers/venice). ## Quick start (two steps) -1) Authenticate with the provider (usually via `clawdbot onboard`). +1) Authenticate with the provider (usually via `moltbot onboard`). 2) Set the default model: ```json5 diff --git a/docs/providers/moonshot.md b/docs/providers/moonshot.md index 0fcaae77d..a1f2d18ad 100644 --- a/docs/providers/moonshot.md +++ b/docs/providers/moonshot.md @@ -9,11 +9,12 @@ read_when: # Moonshot AI (Kimi) Moonshot provides the Kimi API with OpenAI-compatible endpoints. Configure the -provider and set the default model to `moonshot/kimi-k2-0905-preview`, or use +provider and set the default model to `moonshot/kimi-k2.5`, or use Kimi Code with `kimi-code/kimi-for-coding`. Current Kimi K2 model IDs: {/* moonshot-kimi-k2-ids:start */} +- `kimi-k2.5` - `kimi-k2-0905-preview` - `kimi-k2-turbo-preview` - `kimi-k2-thinking` @@ -21,13 +22,13 @@ Current Kimi K2 model IDs: {/* moonshot-kimi-k2-ids:end */} ```bash -clawdbot onboard --auth-choice moonshot-api-key +moltbot onboard --auth-choice moonshot-api-key ``` Kimi Code: ```bash -clawdbot onboard --auth-choice kimi-code-api-key +moltbot onboard --auth-choice kimi-code-api-key ``` Note: Moonshot and Kimi Code are separate providers. Keys are not interchangeable, endpoints differ, and model refs differ (Moonshot uses `moonshot/...`, Kimi Code uses `kimi-code/...`). @@ -39,9 +40,10 @@ Note: Moonshot and Kimi Code are separate providers. Keys are not interchangeabl env: { MOONSHOT_API_KEY: "sk-..." }, agents: { defaults: { - model: { primary: "moonshot/kimi-k2-0905-preview" }, + model: { primary: "moonshot/kimi-k2.5" }, models: { // moonshot-kimi-k2-aliases:start + "moonshot/kimi-k2.5": { alias: "Kimi K2.5" }, "moonshot/kimi-k2-0905-preview": { alias: "Kimi K2" }, "moonshot/kimi-k2-turbo-preview": { alias: "Kimi K2 Turbo" }, "moonshot/kimi-k2-thinking": { alias: "Kimi K2 Thinking" }, @@ -59,6 +61,15 @@ Note: Moonshot and Kimi Code are separate providers. Keys are not interchangeabl api: "openai-completions", models: [ // moonshot-kimi-k2-models:start + { + id: "kimi-k2.5", + name: "Kimi K2.5", + reasoning: false, + input: ["text"], + cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 }, + contextWindow: 256000, + maxTokens: 8192 + }, { id: "kimi-k2-0905-preview", name: "Kimi K2 0905 Preview", diff --git a/docs/providers/ollama.md b/docs/providers/ollama.md index 3d17425d0..c58c5ed34 100644 --- a/docs/providers/ollama.md +++ b/docs/providers/ollama.md @@ -1,12 +1,12 @@ --- -summary: "Run Clawdbot with Ollama (local LLM runtime)" +summary: "Run Moltbot with Ollama (local LLM runtime)" read_when: - - You want to run Clawdbot with local models via Ollama + - You want to run Moltbot with local models via Ollama - You need Ollama setup and configuration guidance --- # Ollama -Ollama is a local LLM runtime that makes it easy to run open-source models on your machine. Clawdbot integrates with Ollama's OpenAI-compatible API and can **auto-discover tool-capable models** when you opt in with `OLLAMA_API_KEY` (or an auth profile) and do not define an explicit `models.providers.ollama` entry. +Ollama is a local LLM runtime that makes it easy to run open-source models on your machine. Moltbot integrates with Ollama's OpenAI-compatible API and can **auto-discover tool-capable models** when you opt in with `OLLAMA_API_KEY` (or an auth profile) and do not define an explicit `models.providers.ollama` entry. ## Quick start @@ -22,14 +22,14 @@ ollama pull qwen2.5-coder:32b ollama pull deepseek-r1:32b ``` -3) Enable Ollama for Clawdbot (any value works; Ollama doesn't require a real key): +3) Enable Ollama for Moltbot (any value works; Ollama doesn't require a real key): ```bash # Set environment variable export OLLAMA_API_KEY="ollama-local" # Or configure in your config file -clawdbot config set models.providers.ollama.apiKey "ollama-local" +moltbot config set models.providers.ollama.apiKey "ollama-local" ``` 4) Use Ollama models: @@ -46,7 +46,7 @@ clawdbot config set models.providers.ollama.apiKey "ollama-local" ## Model discovery (implicit provider) -When you set `OLLAMA_API_KEY` (or an auth profile) and **do not** define `models.providers.ollama`, Clawdbot discovers models from the local Ollama instance at `http://127.0.0.1:11434`: +When you set `OLLAMA_API_KEY` (or an auth profile) and **do not** define `models.providers.ollama`, Moltbot discovers models from the local Ollama instance at `http://127.0.0.1:11434`: - Queries `/api/tags` and `/api/show` - Keeps only models that report `tools` capability @@ -61,7 +61,7 @@ To see what models are available: ```bash ollama list -clawdbot models list +moltbot models list ``` To add a new model, simply pull it with Ollama: @@ -117,7 +117,7 @@ Use explicit config when: } ``` -If `OLLAMA_API_KEY` is set, you can omit `apiKey` in the provider entry and Clawdbot will fill it for availability checks. +If `OLLAMA_API_KEY` is set, you can omit `apiKey` in the provider entry and Moltbot will fill it for availability checks. ### Custom base URL (explicit config) @@ -157,7 +157,7 @@ Once configured, all your Ollama models are available: ### Reasoning models -Clawdbot marks models as reasoning-capable when Ollama reports `thinking` in `/api/show`: +Moltbot marks models as reasoning-capable when Ollama reports `thinking` in `/api/show`: ```bash ollama pull deepseek-r1:32b @@ -169,7 +169,7 @@ Ollama is free and runs locally, so all model costs are set to $0. ### Context windows -For auto-discovered models, Clawdbot uses the context window reported by Ollama when available, otherwise it defaults to `8192`. You can override `contextWindow` and `maxTokens` in explicit provider config. +For auto-discovered models, Moltbot uses the context window reported by Ollama when available, otherwise it defaults to `8192`. You can override `contextWindow` and `maxTokens` in explicit provider config. ## Troubleshooting @@ -189,7 +189,7 @@ curl http://localhost:11434/api/tags ### No models available -Clawdbot only auto-discovers models that report tool support. If your model isn't listed, either: +Moltbot only auto-discovers models that report tool support. If your model isn't listed, either: - Pull a tool-capable model, or - Define the model explicitly in `models.providers.ollama`. diff --git a/docs/providers/openai.md b/docs/providers/openai.md index c877d59ff..5e8d970ac 100644 --- a/docs/providers/openai.md +++ b/docs/providers/openai.md @@ -1,7 +1,7 @@ --- -summary: "Use OpenAI via API keys or Codex subscription in Clawdbot" +summary: "Use OpenAI via API keys or Codex subscription in Moltbot" read_when: - - You want to use OpenAI models in Clawdbot + - You want to use OpenAI models in Moltbot - You want Codex subscription auth instead of API keys --- # OpenAI @@ -17,9 +17,9 @@ Get your API key from the OpenAI dashboard. ### CLI setup ```bash -clawdbot onboard --auth-choice openai-api-key +moltbot onboard --auth-choice openai-api-key # or non-interactive -clawdbot onboard --openai-api-key "$OPENAI_API_KEY" +moltbot onboard --openai-api-key "$OPENAI_API_KEY" ``` ### Config snippet @@ -40,10 +40,10 @@ Codex cloud requires ChatGPT sign-in, while the Codex CLI supports ChatGPT or AP ```bash # Run Codex OAuth in the wizard -clawdbot onboard --auth-choice openai-codex +moltbot onboard --auth-choice openai-codex # Or run OAuth directly -clawdbot models auth login --provider openai-codex +moltbot models auth login --provider openai-codex ``` ### Config snippet diff --git a/docs/providers/opencode.md b/docs/providers/opencode.md index 957de6ada..89e8f5a93 100644 --- a/docs/providers/opencode.md +++ b/docs/providers/opencode.md @@ -1,5 +1,5 @@ --- -summary: "Use OpenCode Zen (curated models) with Clawdbot" +summary: "Use OpenCode Zen (curated models) with Moltbot" read_when: - You want OpenCode Zen for model access - You want a curated list of coding-friendly models @@ -13,9 +13,9 @@ Zen is currently in beta. ## CLI setup ```bash -clawdbot onboard --auth-choice opencode-zen +moltbot onboard --auth-choice opencode-zen # or non-interactive -clawdbot onboard --opencode-zen-api-key "$OPENCODE_API_KEY" +moltbot onboard --opencode-zen-api-key "$OPENCODE_API_KEY" ``` ## Config snippet diff --git a/docs/providers/openrouter.md b/docs/providers/openrouter.md index 387a9e144..b55fc756f 100644 --- a/docs/providers/openrouter.md +++ b/docs/providers/openrouter.md @@ -1,8 +1,8 @@ --- -summary: "Use OpenRouter's unified API to access many models in Clawdbot" +summary: "Use OpenRouter's unified API to access many models in Moltbot" read_when: - You want a single API key for many LLMs - - You want to run models via OpenRouter in Clawdbot + - You want to run models via OpenRouter in Moltbot --- # OpenRouter @@ -12,7 +12,7 @@ endpoint and API key. It is OpenAI-compatible, so most OpenAI SDKs work by switc ## CLI setup ```bash -clawdbot onboard --auth-choice apiKey --token-provider openrouter --token "$OPENROUTER_API_KEY" +moltbot onboard --auth-choice apiKey --token-provider openrouter --token "$OPENROUTER_API_KEY" ``` ## Config snippet diff --git a/docs/providers/qwen.md b/docs/providers/qwen.md index f5bc33065..db0bc5005 100644 --- a/docs/providers/qwen.md +++ b/docs/providers/qwen.md @@ -1,7 +1,7 @@ --- -summary: "Use Qwen OAuth (free tier) in Clawdbot" +summary: "Use Qwen OAuth (free tier) in Moltbot" read_when: - - You want to use Qwen with Clawdbot + - You want to use Qwen with Moltbot - You want free-tier OAuth access to Qwen Coder --- # Qwen @@ -12,7 +12,7 @@ Qwen provides a free-tier OAuth flow for Qwen Coder and Qwen Vision models ## Enable the plugin ```bash -clawdbot plugins enable qwen-portal-auth +moltbot plugins enable qwen-portal-auth ``` Restart the Gateway after enabling. @@ -20,7 +20,7 @@ Restart the Gateway after enabling. ## Authenticate ```bash -clawdbot models auth login --provider qwen-portal --set-default +moltbot models auth login --provider qwen-portal --set-default ``` This runs the Qwen device-code OAuth flow and writes a provider entry to your @@ -34,12 +34,12 @@ This runs the Qwen device-code OAuth flow and writes a provider entry to your Switch models with: ```bash -clawdbot models set qwen-portal/coder-model +moltbot models set qwen-portal/coder-model ``` ## Reuse Qwen Code CLI login -If you already logged in with the Qwen Code CLI, Clawdbot will sync credentials +If you already logged in with the Qwen Code CLI, Moltbot will sync credentials from `~/.qwen/oauth_creds.json` when it loads the auth store. You still need a `models.providers.qwen-portal` entry (use the login command above to create one). diff --git a/docs/providers/synthetic.md b/docs/providers/synthetic.md index 169d068fc..f6bb1a67b 100644 --- a/docs/providers/synthetic.md +++ b/docs/providers/synthetic.md @@ -1,12 +1,12 @@ --- -summary: "Use Synthetic's Anthropic-compatible API in Clawdbot" +summary: "Use Synthetic's Anthropic-compatible API in Moltbot" read_when: - You want to use Synthetic as a model provider - You need a Synthetic API key or base URL setup --- # Synthetic -Synthetic exposes Anthropic-compatible endpoints. Clawdbot registers it as the +Synthetic exposes Anthropic-compatible endpoints. Moltbot registers it as the `synthetic` provider and uses the Anthropic Messages API. ## Quick setup @@ -15,7 +15,7 @@ Synthetic exposes Anthropic-compatible endpoints. Clawdbot registers it as the 2) Run onboarding: ```bash -clawdbot onboard --auth-choice synthetic-api-key +moltbot onboard --auth-choice synthetic-api-key ``` The default model is set to: @@ -59,7 +59,7 @@ synthetic/hf:MiniMaxAI/MiniMax-M2.1 } ``` -Note: Clawdbot's Anthropic client appends `/v1` to the base URL, so use +Note: Moltbot's Anthropic client appends `/v1` to the base URL, so use `https://api.synthetic.new/anthropic` (not `/anthropic/v1`). If Synthetic changes its base URL, override `models.providers.synthetic.baseUrl`. diff --git a/docs/providers/venice.md b/docs/providers/venice.md index bd91e6da6..f6b535a68 100644 --- a/docs/providers/venice.md +++ b/docs/providers/venice.md @@ -1,7 +1,7 @@ --- -summary: "Use Venice AI privacy-focused models in Clawdbot" +summary: "Use Venice AI privacy-focused models in Moltbot" read_when: - - You want privacy-focused inference in Clawdbot + - You want privacy-focused inference in Moltbot - You want Venice AI setup guidance --- # Venice AI (Venius highlight) @@ -10,7 +10,7 @@ read_when: Venice AI provides privacy-focused AI inference with support for uncensored models and access to major proprietary models through their anonymized proxy. All inference is private by default—no training on your data, no logging. -## Why Venice in Clawdbot +## Why Venice in Moltbot - **Private inference** for open-source models (no logging). - **Uncensored models** when you need them. @@ -45,7 +45,7 @@ Venice offers two privacy levels — understanding this is key to choosing your 2. Go to **Settings → API Keys → Create new key** 3. Copy your API key (format: `vapi_xxxxxxxxxxxx`) -### 2. Configure Clawdbot +### 2. Configure Moltbot **Option A: Environment Variable** @@ -56,7 +56,7 @@ export VENICE_API_KEY="vapi_xxxxxxxxxxxx" **Option B: Interactive Setup (Recommended)** ```bash -clawdbot onboard --auth-choice venice-api-key +moltbot onboard --auth-choice venice-api-key ``` This will: @@ -68,7 +68,7 @@ This will: **Option C: Non-interactive** ```bash -clawdbot onboard --non-interactive \ +moltbot onboard --non-interactive \ --auth-choice venice-api-key \ --venice-api-key "vapi_xxxxxxxxxxxx" ``` @@ -76,12 +76,12 @@ clawdbot onboard --non-interactive \ ### 3. Verify Setup ```bash -clawdbot chat --model venice/llama-3.3-70b "Hello, are you working?" +moltbot chat --model venice/llama-3.3-70b "Hello, are you working?" ``` ## Model Selection -After setup, Clawdbot shows all available Venice models. Pick based on your needs: +After setup, Moltbot shows all available Venice models. Pick based on your needs: - **Default (our pick)**: `venice/llama-3.3-70b` for private, balanced performance. - **Best overall quality**: `venice/claude-opus-45` for hard jobs (Opus remains the strongest). @@ -91,19 +91,19 @@ After setup, Clawdbot shows all available Venice models. Pick based on your need Change your default model anytime: ```bash -clawdbot models set venice/claude-opus-45 -clawdbot models set venice/llama-3.3-70b +moltbot models set venice/claude-opus-45 +moltbot models set venice/llama-3.3-70b ``` List all available models: ```bash -clawdbot models list | grep venice +moltbot models list | grep venice ``` -## Configure via `clawdbot configure` +## Configure via `moltbot configure` -1. Run `clawdbot configure` +1. Run `moltbot configure` 2. Select **Model/auth** 3. Choose **Venice AI** @@ -159,7 +159,7 @@ clawdbot models list | grep venice ## Model Discovery -Clawdbot automatically discovers models from the Venice API when `VENICE_API_KEY` is set. If the API is unreachable, it falls back to a static catalog. +Moltbot automatically discovers models from the Venice API when `VENICE_API_KEY` is set. If the API is unreachable, it falls back to a static catalog. The `/models` endpoint is public (no auth needed for listing), but inference requires a valid API key. @@ -192,19 +192,19 @@ Venice uses a credit-based system. Check [venice.ai/pricing](https://venice.ai/p ```bash # Use default private model -clawdbot chat --model venice/llama-3.3-70b +moltbot chat --model venice/llama-3.3-70b # Use Claude via Venice (anonymized) -clawdbot chat --model venice/claude-opus-45 +moltbot chat --model venice/claude-opus-45 # Use uncensored model -clawdbot chat --model venice/venice-uncensored +moltbot chat --model venice/venice-uncensored # Use vision model with image -clawdbot chat --model venice/qwen3-vl-235b-a22b +moltbot chat --model venice/qwen3-vl-235b-a22b # Use coding model -clawdbot chat --model venice/qwen3-coder-480b-a35b-instruct +moltbot chat --model venice/qwen3-coder-480b-a35b-instruct ``` ## Troubleshooting @@ -213,14 +213,14 @@ clawdbot chat --model venice/qwen3-coder-480b-a35b-instruct ```bash echo $VENICE_API_KEY -clawdbot models list | grep venice +moltbot models list | grep venice ``` Ensure the key starts with `vapi_`. ### Model not available -The Venice model catalog updates dynamically. Run `clawdbot models list` to see currently available models. Some models may be temporarily offline. +The Venice model catalog updates dynamically. Run `moltbot models list` to see currently available models. Some models may be temporarily offline. ### Connection issues diff --git a/docs/providers/vercel-ai-gateway.md b/docs/providers/vercel-ai-gateway.md index 36cf51cda..714df9ce6 100644 --- a/docs/providers/vercel-ai-gateway.md +++ b/docs/providers/vercel-ai-gateway.md @@ -2,7 +2,7 @@ title: "Vercel AI Gateway" summary: "Vercel AI Gateway setup (auth + model selection)" read_when: - - You want to use Vercel AI Gateway with Clawdbot + - You want to use Vercel AI Gateway with Moltbot - You need the API key env var or CLI auth choice --- # Vercel AI Gateway @@ -19,7 +19,7 @@ The [Vercel AI Gateway](https://vercel.com/ai-gateway) provides a unified API to 1) Set the API key (recommended: store it for the Gateway): ```bash -clawdbot onboard --auth-choice ai-gateway-api-key +moltbot onboard --auth-choice ai-gateway-api-key ``` 2) Set a default model: @@ -37,7 +37,7 @@ clawdbot onboard --auth-choice ai-gateway-api-key ## Non-interactive example ```bash -clawdbot onboard --non-interactive \ +moltbot onboard --non-interactive \ --mode local \ --auth-choice ai-gateway-api-key \ --ai-gateway-api-key "$AI_GATEWAY_API_KEY" diff --git a/docs/providers/zai.md b/docs/providers/zai.md index c568fa29b..2ec6c1cc7 100644 --- a/docs/providers/zai.md +++ b/docs/providers/zai.md @@ -1,21 +1,21 @@ --- -summary: "Use Z.AI (GLM models) with Clawdbot" +summary: "Use Z.AI (GLM models) with Moltbot" read_when: - - You want Z.AI / GLM models in Clawdbot + - You want Z.AI / GLM models in Moltbot - You need a simple ZAI_API_KEY setup --- # Z.AI Z.AI is the API platform for **GLM** models. It provides REST APIs for GLM and uses API keys -for authentication. Create your API key in the Z.AI console. Clawdbot uses the `zai` provider +for authentication. Create your API key in the Z.AI console. Moltbot uses the `zai` provider with a Z.AI API key. ## CLI setup ```bash -clawdbot onboard --auth-choice zai-api-key +moltbot onboard --auth-choice zai-api-key # or non-interactive -clawdbot onboard --zai-api-key "$ZAI_API_KEY" +moltbot onboard --zai-api-key "$ZAI_API_KEY" ``` ## Config snippet diff --git a/docs/railway.mdx b/docs/railway.mdx index b8f994a7d..041ea5561 100644 --- a/docs/railway.mdx +++ b/docs/railway.mdx @@ -2,7 +2,7 @@ title: Deploy on Railway --- -Deploy Clawdbot on Railway with a one-click template and finish setup in your browser. +Deploy Moltbot on Railway with a one-click template and finish setup in your browser. This is the easiest “no terminal on the server” path: Railway runs the Gateway for you, and you configure everything via the `/setup` web wizard. @@ -16,7 +16,7 @@ and you configure everything via the `/setup` web wizard. ## One-click deploy -Deploy on Railway +Deploy on Railway After deploy, find your public URL in **Railway → your service → Settings → Domains**. @@ -27,11 +27,11 @@ Railway will either: Then open: - `https:///setup` — setup wizard (password protected) -- `https:///clawdbot` — Control UI +- `https:///moltbot` — Control UI ## What you get -- Hosted Clawdbot Gateway + Control UI +- Hosted Moltbot Gateway + Control UI - Web setup wizard at `/setup` (no terminal commands) - Persistent storage via Railway Volume (`/data`) so config/credentials/workspace survive redeploys - Backup export at `/setup/export` to migrate off Railway later @@ -93,4 +93,4 @@ Download a backup at: - `https:///setup/export` -This exports your Clawdbot state + workspace so you can migrate to another host without losing config or memory. +This exports your Moltbot state + workspace so you can migrate to another host without losing config or memory. diff --git a/docs/refactor/plugin-sdk.md b/docs/refactor/plugin-sdk.md index 833629b44..e4be5a35f 100644 --- a/docs/refactor/plugin-sdk.md +++ b/docs/refactor/plugin-sdk.md @@ -33,7 +33,7 @@ Delivery: ### 2) Plugin Runtime (execution surface, injected) Scope: everything that touches core runtime behavior. -Accessed via `ClawdbotPluginApi.runtime` so plugins never import `src/**`. +Accessed via `MoltbotPluginApi.runtime` so plugins never import `src/**`. Proposed surface (minimal but complete): ```ts @@ -41,8 +41,8 @@ export type PluginRuntime = { channel: { text: { chunkMarkdownText(text: string, limit: number): string[]; - resolveTextChunkLimit(cfg: ClawdbotConfig, channel: string, accountId?: string): number; - hasControlCommand(text: string, cfg: ClawdbotConfig): boolean; + resolveTextChunkLimit(cfg: MoltbotConfig, channel: string, accountId?: string): number; + hasControlCommand(text: string, cfg: MoltbotConfig): boolean; }; reply: { dispatchReplyWithBufferedBlockDispatcher(params: { @@ -83,18 +83,18 @@ export type PluginRuntime = { ): Promise<{ path: string; contentType?: string }>; }; mentions: { - buildMentionRegexes(cfg: ClawdbotConfig, agentId?: string): RegExp[]; + buildMentionRegexes(cfg: MoltbotConfig, agentId?: string): RegExp[]; matchesMentionPatterns(text: string, regexes: RegExp[]): boolean; }; groups: { - resolveGroupPolicy(cfg: ClawdbotConfig, channel: string, accountId: string, groupId: string): { + resolveGroupPolicy(cfg: MoltbotConfig, channel: string, accountId: string, groupId: string): { allowlistEnabled: boolean; allowed: boolean; groupConfig?: unknown; defaultConfig?: unknown; }; resolveRequireMention( - cfg: ClawdbotConfig, + cfg: MoltbotConfig, channel: string, accountId: string, groupId: string, @@ -109,7 +109,7 @@ export type PluginRuntime = { onFlush: (entries: T[]) => Promise; onError?: (err: unknown) => void; }): { push: (v: T) => void; flush: () => Promise }; - resolveInboundDebounceMs(cfg: ClawdbotConfig, channel: string): number; + resolveInboundDebounceMs(cfg: MoltbotConfig, channel: string): number; }; commands: { resolveCommandAuthorizedFromAuthorizers(params: { @@ -123,7 +123,7 @@ export type PluginRuntime = { getChildLogger(name: string): PluginLogger; }; state: { - resolveStateDir(cfg: ClawdbotConfig): string; + resolveStateDir(cfg: MoltbotConfig): string; }; }; ``` @@ -137,7 +137,7 @@ Notes: ### Phase 0: scaffolding - Introduce `@clawdbot/plugin-sdk`. -- Add `api.runtime` to `ClawdbotPluginApi` with the surface above. +- Add `api.runtime` to `MoltbotPluginApi` with the surface above. - Maintain existing imports during a transition window (deprecation warnings). ### Phase 1: bridge cleanup (low risk) @@ -165,7 +165,7 @@ Notes: ## Compatibility and versioning - SDK: semver, published, documented changes. - Runtime: versioned per core release. Add `api.runtime.version`. -- Plugins declare a required runtime range (e.g., `clawdbotRuntime: ">=2026.2.0"`). +- Plugins declare a required runtime range (e.g., `moltbotRuntime: ">=2026.2.0"`). ## Testing strategy - Adapter-level unit tests (runtime functions exercised with real core implementation). diff --git a/docs/refactor/strict-config.md b/docs/refactor/strict-config.md index 734290daf..5d37a4c11 100644 --- a/docs/refactor/strict-config.md +++ b/docs/refactor/strict-config.md @@ -23,12 +23,12 @@ read_when: - `plugins.entries..config` must be validated by the plugin’s schema. - If a plugin lacks a schema, **reject plugin load** and surface a clear error. - Unknown `channels.` keys are errors unless a plugin manifest declares the channel id. -- Plugin manifests (`clawdbot.plugin.json`) are required for all plugins. +- Plugin manifests (`moltbot.plugin.json`) are required for all plugins. ## Plugin schema enforcement - Each plugin provides a strict JSON Schema for its config (inline in the manifest). - Plugin load flow: - 1) Resolve plugin manifest + schema (`clawdbot.plugin.json`). + 1) Resolve plugin manifest + schema (`moltbot.plugin.json`). 2) Validate config against the schema. 3) If missing schema or invalid config: block plugin load, record error. - Error message includes: @@ -41,22 +41,22 @@ read_when: - Doctor runs **every time** config is loaded (dry-run by default). - If config invalid: - Print a summary + actionable errors. - - Instruct: `clawdbot doctor --fix`. -- `clawdbot doctor --fix`: + - Instruct: `moltbot doctor --fix`. +- `moltbot doctor --fix`: - Applies migrations. - Removes unknown keys. - Writes updated config. ## Command gating (when config is invalid) Allowed (diagnostic-only): -- `clawdbot doctor` -- `clawdbot logs` -- `clawdbot health` -- `clawdbot help` -- `clawdbot status` -- `clawdbot gateway status` +- `moltbot doctor` +- `moltbot logs` +- `moltbot health` +- `moltbot help` +- `moltbot status` +- `moltbot gateway status` -Everything else must hard-fail with: “Config invalid. Run `clawdbot doctor --fix`.” +Everything else must hard-fail with: “Config invalid. Run `moltbot doctor --fix`.” ## Error UX format - Single summary header. diff --git a/docs/reference/AGENTS.default.md b/docs/reference/AGENTS.default.md index ad4fe5731..290997d58 100644 --- a/docs/reference/AGENTS.default.md +++ b/docs/reference/AGENTS.default.md @@ -1,14 +1,14 @@ --- -summary: "Default Clawdbot agent instructions and skills roster for the personal assistant setup" +summary: "Default Moltbot agent instructions and skills roster for the personal assistant setup" read_when: - - Starting a new Clawdbot agent session + - Starting a new Moltbot agent session - Enabling or auditing default skills --- -# AGENTS.md — Clawdbot Personal Assistant (default) +# AGENTS.md — Moltbot Personal Assistant (default) ## First run (recommended) -Clawdbot uses a dedicated workspace directory for the agent. Default: `~/clawd` (configurable via `agents.defaults.workspace`). +Moltbot uses a dedicated workspace directory for the agent. Default: `~/clawd` (configurable via `agents.defaults.workspace`). 1) Create the workspace (if it doesn’t already exist): @@ -78,9 +78,9 @@ git commit -m "Add Clawd workspace" # Optional: add a private remote + push ``` -## What Clawdbot Does +## What Moltbot Does - Runs WhatsApp gateway + Pi coding agent so the assistant can read/write chats, fetch context, and run skills via the host Mac. -- macOS app manages permissions (screen recording, notifications, microphone) and exposes the `clawdbot` CLI via its bundled binary. +- macOS app manages permissions (screen recording, notifications, microphone) and exposes the `moltbot` CLI via its bundled binary. - Direct chats collapse into the agent's `main` session by default; groups stay isolated as `agent:::group:` (rooms/channels: `agent:::channel:`); heartbeats keep background tasks alive. ## Core Skills (enable in Settings → Skills) @@ -104,10 +104,10 @@ git commit -m "Add Clawd workspace" - **agent-tools** — Utility toolkit for automations and helper scripts. ## Usage Notes -- Prefer the `clawdbot` CLI for scripting; mac app handles permissions. +- Prefer the `moltbot` CLI for scripting; mac app handles permissions. - Run installs from the Skills tab; it hides the button if a binary is already present. - Keep heartbeats enabled so the assistant can schedule reminders, monitor inboxes, and trigger camera captures. - Canvas UI runs full-screen with native overlays. Avoid placing critical controls in the top-left/top-right/bottom edges; add explicit gutters in the layout and don’t rely on safe-area insets. -- For browser-driven verification, use `clawdbot browser` (tabs/status/screenshot) with the clawd-managed Chrome profile. -- For DOM inspection, use `clawdbot browser eval|query|dom|snapshot` (and `--json`/`--out` when you need machine output). -- For interactions, use `clawdbot browser click|type|hover|drag|select|upload|press|wait|navigate|back|evaluate|run` (click/type require snapshot refs; use `evaluate` for CSS selectors). +- For browser-driven verification, use `moltbot browser` (tabs/status/screenshot) with the clawd-managed Chrome profile. +- For DOM inspection, use `moltbot browser eval|query|dom|snapshot` (and `--json`/`--out` when you need machine output). +- For interactions, use `moltbot browser click|type|hover|drag|select|upload|press|wait|navigate|back|evaluate|run` (click/type require snapshot refs; use `evaluate` for CSS selectors). diff --git a/docs/reference/RELEASING.md b/docs/reference/RELEASING.md index 244757a48..e648fb33c 100644 --- a/docs/reference/RELEASING.md +++ b/docs/reference/RELEASING.md @@ -17,14 +17,14 @@ When the operator says “release”, immediately do this preflight (no extra qu - Use Sparkle keys from `~/Library/CloudStorage/Dropbox/Backup/Sparkle` if needed. 1) **Version & metadata** -- [ ] Bump `package.json` version (e.g., `2026.1.25`). +- [ ] Bump `package.json` version (e.g., `2026.1.27-beta.1`). - [ ] Run `pnpm plugins:sync` to align extension package versions + changelogs. -- [ ] Update CLI/version strings: [`src/cli/program.ts`](https://github.com/clawdbot/clawdbot/blob/main/src/cli/program.ts) and the Baileys user agent in [`src/provider-web.ts`](https://github.com/clawdbot/clawdbot/blob/main/src/provider-web.ts). -- [ ] Confirm package metadata (name, description, repository, keywords, license) and `bin` map points to [`dist/entry.js`](https://github.com/clawdbot/clawdbot/blob/main/dist/entry.js) for `clawdbot`. +- [ ] Update CLI/version strings: [`src/cli/program.ts`](https://github.com/moltbot/moltbot/blob/main/src/cli/program.ts) and the Baileys user agent in [`src/provider-web.ts`](https://github.com/moltbot/moltbot/blob/main/src/provider-web.ts). +- [ ] Confirm package metadata (name, description, repository, keywords, license) and `bin` map points to [`moltbot.mjs`](https://github.com/moltbot/moltbot/blob/main/moltbot.mjs) for `moltbot`. - [ ] If dependencies changed, run `pnpm install` so `pnpm-lock.yaml` is current. 2) **Build & artifacts** -- [ ] If A2UI inputs changed, run `pnpm canvas:a2ui:bundle` and commit any updated [`src/canvas-host/a2ui/a2ui.bundle.js`](https://github.com/clawdbot/clawdbot/blob/main/src/canvas-host/a2ui/a2ui.bundle.js). +- [ ] If A2UI inputs changed, run `pnpm canvas:a2ui:bundle` and commit any updated [`src/canvas-host/a2ui/a2ui.bundle.js`](https://github.com/moltbot/moltbot/blob/main/src/canvas-host/a2ui/a2ui.bundle.js). - [ ] `pnpm run build` (regenerates `dist/`). - [ ] Verify npm package `files` includes all required `dist/*` folders (notably `dist/node-host/**` and `dist/acp/**` for headless node + ACP CLI). - [ ] Confirm `dist/build-info.json` exists and includes the expected `commit` hash (CLI banner uses this for npm installs). @@ -42,7 +42,7 @@ When the operator says “release”, immediately do this preflight (no extra qu - [ ] `CLAWDBOT_INSTALL_SMOKE_SKIP_NONROOT=1 pnpm test:install:smoke` (Docker install smoke test, fast path; required before release) - If the immediate previous npm release is known broken, set `CLAWDBOT_INSTALL_SMOKE_PREVIOUS=` or `CLAWDBOT_INSTALL_SMOKE_SKIP_PREVIOUS=1` for the preinstall step. - [ ] (Optional) Full installer smoke (adds non-root + CLI coverage): `pnpm test:install:smoke` -- [ ] (Optional) Installer E2E (Docker, runs `curl -fsSL https://clawd.bot/install.sh | bash`, onboards, then runs real tool calls): +- [ ] (Optional) Installer E2E (Docker, runs `curl -fsSL https://molt.bot/install.sh | bash`, onboards, then runs real tool calls): - `pnpm test:install:e2e:openai` (requires `OPENAI_API_KEY`) - `pnpm test:install:e2e:anthropic` (requires `ANTHROPIC_API_KEY`) - `pnpm test:install:e2e` (requires both keys; runs both providers) @@ -50,58 +50,58 @@ When the operator says “release”, immediately do this preflight (no extra qu 5) **macOS app (Sparkle)** - [ ] Build + sign the macOS app, then zip it for distribution. -- [ ] Generate the Sparkle appcast (HTML notes via [`scripts/make_appcast.sh`](https://github.com/clawdbot/clawdbot/blob/main/scripts/make_appcast.sh)) and update `appcast.xml`. +- [ ] Generate the Sparkle appcast (HTML notes via [`scripts/make_appcast.sh`](https://github.com/moltbot/moltbot/blob/main/scripts/make_appcast.sh)) and update `appcast.xml`. - [ ] Keep the app zip (and optional dSYM zip) ready to attach to the GitHub release. - [ ] Follow [macOS release](/platforms/mac/release) for the exact commands and required env vars. - `APP_BUILD` must be numeric + monotonic (no `-beta`) so Sparkle compares versions correctly. - - If notarizing, use the `clawdbot-notary` keychain profile created from App Store Connect API env vars (see [macOS release](/platforms/mac/release)). + - If notarizing, use the `moltbot-notary` keychain profile created from App Store Connect API env vars (see [macOS release](/platforms/mac/release)). 6) **Publish (npm)** - [ ] Confirm git status is clean; commit and push as needed. - [ ] `npm login` (verify 2FA) if needed. - [ ] `npm publish --access public` (use `--tag beta` for pre-releases). -- [ ] Verify the registry: `npm view clawdbot version`, `npm view clawdbot dist-tags`, and `npx -y clawdbot@X.Y.Z --version` (or `--help`). +- [ ] Verify the registry: `npm view moltbot version`, `npm view moltbot dist-tags`, and `npx -y moltbot@X.Y.Z --version` (or `--help`). ### Troubleshooting (notes from 2.0.0-beta2 release) -- **npm pack/publish hangs or produces huge tarball**: the macOS app bundle in `dist/Clawdbot.app` (and release zips) get swept into the package. Fix by whitelisting publish contents via `package.json` `files` (include dist subdirs, docs, skills; exclude app bundles). Confirm with `npm pack --dry-run` that `dist/Clawdbot.app` is not listed. +- **npm pack/publish hangs or produces huge tarball**: the macOS app bundle in `dist/Moltbot.app` (and release zips) get swept into the package. Fix by whitelisting publish contents via `package.json` `files` (include dist subdirs, docs, skills; exclude app bundles). Confirm with `npm pack --dry-run` that `dist/Moltbot.app` is not listed. - **npm auth web loop for dist-tags**: use legacy auth to get an OTP prompt: - - `NPM_CONFIG_AUTH_TYPE=legacy npm dist-tag add clawdbot@X.Y.Z latest` + - `NPM_CONFIG_AUTH_TYPE=legacy npm dist-tag add moltbot@X.Y.Z latest` - **`npx` verification fails with `ECOMPROMISED: Lock compromised`**: retry with a fresh cache: - - `NPM_CONFIG_CACHE=/tmp/npm-cache-$(date +%s) npx -y clawdbot@X.Y.Z --version` + - `NPM_CONFIG_CACHE=/tmp/npm-cache-$(date +%s) npx -y moltbot@X.Y.Z --version` - **Tag needs repointing after a late fix**: force-update and push the tag, then ensure the GitHub release assets still match: - `git tag -f vX.Y.Z && git push -f origin vX.Y.Z` 7) **GitHub release + appcast** - [ ] Tag and push: `git tag vX.Y.Z && git push origin vX.Y.Z` (or `git push --tags`). -- [ ] Create/refresh the GitHub release for `vX.Y.Z` with **title `clawdbot X.Y.Z`** (not just the tag); body should include the **full** changelog section for that version (Highlights + Changes + Fixes), inline (no bare links), and **must not repeat the title inside the body**. -- [ ] Attach artifacts: `npm pack` tarball (optional), `Clawdbot-X.Y.Z.zip`, and `Clawdbot-X.Y.Z.dSYM.zip` (if generated). +- [ ] Create/refresh the GitHub release for `vX.Y.Z` with **title `moltbot X.Y.Z`** (not just the tag); body should include the **full** changelog section for that version (Highlights + Changes + Fixes), inline (no bare links), and **must not repeat the title inside the body**. +- [ ] Attach artifacts: `npm pack` tarball (optional), `Moltbot-X.Y.Z.zip`, and `Moltbot-X.Y.Z.dSYM.zip` (if generated). - [ ] Commit the updated `appcast.xml` and push it (Sparkle feeds from main). -- [ ] From a clean temp directory (no `package.json`), run `npx -y clawdbot@X.Y.Z send --help` to confirm install/CLI entrypoints work. +- [ ] From a clean temp directory (no `package.json`), run `npx -y moltbot@X.Y.Z send --help` to confirm install/CLI entrypoints work. - [ ] Announce/share release notes. ## Plugin publish scope (npm) -We only publish **existing npm plugins** under the `@clawdbot/*` scope. Bundled +We only publish **existing npm plugins** under the `@moltbot/*` scope. Bundled plugins that are not on npm stay **disk-tree only** (still shipped in `extensions/**`). Process to derive the list: -1) `npm search @clawdbot --json` and capture the package names. +1) `npm search @moltbot --json` and capture the package names. 2) Compare with `extensions/*/package.json` names. 3) Publish only the **intersection** (already on npm). Current npm plugin list (update as needed): -- @clawdbot/bluebubbles -- @clawdbot/diagnostics-otel -- @clawdbot/discord -- @clawdbot/lobster -- @clawdbot/matrix -- @clawdbot/msteams -- @clawdbot/nextcloud-talk -- @clawdbot/nostr -- @clawdbot/voice-call -- @clawdbot/zalo -- @clawdbot/zalouser +- @moltbot/bluebubbles +- @moltbot/diagnostics-otel +- @moltbot/discord +- @moltbot/lobster +- @moltbot/matrix +- @moltbot/msteams +- @moltbot/nextcloud-talk +- @moltbot/nostr +- @moltbot/voice-call +- @moltbot/zalo +- @moltbot/zalouser Release notes must also call out **new optional bundled plugins** that are **not on by default** (example: `tlon`). diff --git a/docs/reference/api-usage-costs.md b/docs/reference/api-usage-costs.md index 115edf935..b27dd3b29 100644 --- a/docs/reference/api-usage-costs.md +++ b/docs/reference/api-usage-costs.md @@ -8,7 +8,7 @@ read_when: # API usage & costs This doc lists **features that can invoke API keys** and where their costs show up. It focuses on -Clawdbot features that can generate provider usage or paid API calls. +Moltbot features that can generate provider usage or paid API calls. ## Where costs show up (chat + CLI) @@ -21,14 +21,14 @@ Clawdbot features that can generate provider usage or paid API calls. - `/usage tokens` shows tokens only; OAuth flows hide dollar cost. **CLI usage windows (provider quotas)** -- `clawdbot status --usage` and `clawdbot channels list` show provider **usage windows** +- `moltbot status --usage` and `moltbot channels list` show provider **usage windows** (quota snapshots, not per-message costs). See [Token use & costs](/token-use) for details and examples. ## How keys are discovered -Clawdbot can pick up credentials from: +Moltbot can pick up credentials from: - **Auth profiles** (per-agent, stored in `auth-profiles.json`). - **Environment variables** (e.g. `OPENAI_API_KEY`, `BRAVE_API_KEY`, `FIRECRAWL_API_KEY`). - **Config** (`models.providers.*.apiKey`, `tools.web.search.*`, `tools.web.fetch.firecrawl.*`, @@ -86,8 +86,8 @@ See [Web tools](/tools/web). ### 6) Provider usage snapshots (status/health) Some status commands call **provider usage endpoints** to display quota windows or auth health. These are typically low-volume calls but still hit provider APIs: -- `clawdbot status --usage` -- `clawdbot models status --json` +- `moltbot status --usage` +- `moltbot models status --json` See [Models CLI](/cli/models). @@ -98,7 +98,7 @@ invokes provider APIs when it runs. See [Session management + compaction](/reference/session-management-compaction). ### 8) Model scan / probe -`clawdbot models scan` can probe OpenRouter models and uses `OPENROUTER_API_KEY` when +`moltbot models scan` can probe OpenRouter models and uses `OPENROUTER_API_KEY` when probing is enabled. See [Models CLI](/cli/models). diff --git a/docs/reference/device-models.md b/docs/reference/device-models.md index f0505af79..c551584af 100644 --- a/docs/reference/device-models.md +++ b/docs/reference/device-models.md @@ -1,5 +1,5 @@ --- -summary: "How Clawdbot vendors Apple device model identifiers for friendly names in the macOS app." +summary: "How Moltbot vendors Apple device model identifiers for friendly names in the macOS app." read_when: - Updating device model identifier mappings or NOTICE/license files - Changing how Instances UI displays device names @@ -11,7 +11,7 @@ The macOS companion app shows friendly Apple device model names in the **Instanc The mapping is vendored as JSON under: -- `apps/macos/Sources/Clawdbot/Resources/DeviceModels/` +- `apps/macos/Sources/Moltbot/Resources/DeviceModels/` ## Data source @@ -19,12 +19,12 @@ We currently vendor the mapping from the MIT-licensed repository: - `kyle-seongwoo-jun/apple-device-identifiers` -To keep builds deterministic, the JSON files are pinned to specific upstream commits (recorded in `apps/macos/Sources/Clawdbot/Resources/DeviceModels/NOTICE.md`). +To keep builds deterministic, the JSON files are pinned to specific upstream commits (recorded in `apps/macos/Sources/Moltbot/Resources/DeviceModels/NOTICE.md`). ## Updating the database 1. Pick the upstream commits you want to pin to (one for iOS, one for macOS). -2. Update the commit hashes in `apps/macos/Sources/Clawdbot/Resources/DeviceModels/NOTICE.md`. +2. Update the commit hashes in `apps/macos/Sources/Moltbot/Resources/DeviceModels/NOTICE.md`. 3. Re-download the JSON files, pinned to those commits: ```bash @@ -32,13 +32,13 @@ IOS_COMMIT="" MAC_COMMIT="" curl -fsSL "https://raw.githubusercontent.com/kyle-seongwoo-jun/apple-device-identifiers/${IOS_COMMIT}/ios-device-identifiers.json" \ - -o apps/macos/Sources/Clawdbot/Resources/DeviceModels/ios-device-identifiers.json + -o apps/macos/Sources/Moltbot/Resources/DeviceModels/ios-device-identifiers.json curl -fsSL "https://raw.githubusercontent.com/kyle-seongwoo-jun/apple-device-identifiers/${MAC_COMMIT}/mac-device-identifiers.json" \ - -o apps/macos/Sources/Clawdbot/Resources/DeviceModels/mac-device-identifiers.json + -o apps/macos/Sources/Moltbot/Resources/DeviceModels/mac-device-identifiers.json ``` -4. Ensure `apps/macos/Sources/Clawdbot/Resources/DeviceModels/LICENSE.apple-device-identifiers.txt` still matches upstream (replace it if the upstream license changes). +4. Ensure `apps/macos/Sources/Moltbot/Resources/DeviceModels/LICENSE.apple-device-identifiers.txt` still matches upstream (replace it if the upstream license changes). 5. Verify the macOS app builds cleanly (no warnings): ```bash diff --git a/docs/reference/rpc.md b/docs/reference/rpc.md index dbde8e657..a4b396747 100644 --- a/docs/reference/rpc.md +++ b/docs/reference/rpc.md @@ -6,18 +6,18 @@ read_when: --- # RPC adapters -Clawdbot integrates external CLIs via JSON-RPC. Two patterns are used today. +Moltbot integrates external CLIs via JSON-RPC. Two patterns are used today. ## Pattern A: HTTP daemon (signal-cli) - `signal-cli` runs as a daemon with JSON-RPC over HTTP. - Event stream is SSE (`/api/v1/events`). - Health probe: `/api/v1/check`. -- Clawdbot owns lifecycle when `channels.signal.autoStart=true`. +- Moltbot owns lifecycle when `channels.signal.autoStart=true`. See [Signal](/channels/signal) for setup and endpoints. ## Pattern B: stdio child process (imsg) -- Clawdbot spawns `imsg rpc` as a child process. +- Moltbot spawns `imsg rpc` as a child process. - JSON-RPC is line-delimited over stdin/stdout (one JSON object per line). - No TCP port, no daemon required. diff --git a/docs/reference/session-management-compaction.md b/docs/reference/session-management-compaction.md index 536305218..673142bb2 100644 --- a/docs/reference/session-management-compaction.md +++ b/docs/reference/session-management-compaction.md @@ -7,7 +7,7 @@ read_when: --- # Session Management & Compaction (Deep Dive) -This document explains how Clawdbot manages sessions end-to-end: +This document explains how Moltbot manages sessions end-to-end: - **Session routing** (how inbound messages map to a `sessionKey`) - **Session store** (`sessions.json`) and what it tracks @@ -27,7 +27,7 @@ If you want a higher-level overview first, start with: ## Source of truth: the Gateway -Clawdbot is designed around a single **Gateway process** that owns session state. +Moltbot is designed around a single **Gateway process** that owns session state. - UIs (macOS app, web Control UI, TUI) should query the Gateway for session lists and token counts. - In remote mode, session files are on the remote host; “checking your local Mac files” won’t reflect what the Gateway is using. @@ -36,7 +36,7 @@ Clawdbot is designed around a single **Gateway process** that owns session state ## Two persistence layers -Clawdbot persists sessions in two layers: +Moltbot persists sessions in two layers: 1) **Session store (`sessions.json`)** - Key/value map: `sessionKey -> SessionEntry` @@ -58,7 +58,7 @@ Per agent, on the Gateway host: - Transcripts: `~/.clawdbot/agents//sessions/.jsonl` - Telegram topic sessions: `.../-topic-.jsonl` -Clawdbot resolves these via `src/config/sessions.ts`. +Moltbot resolves these via `src/config/sessions.ts`. --- @@ -132,7 +132,7 @@ Notable entry types: - `compaction`: persisted compaction summary with `firstKeptEntryId` and `tokensBefore` - `branch_summary`: persisted summary when navigating a tree branch -Clawdbot intentionally does **not** “fix up” transcripts; the Gateway uses `SessionManager` to read/write them. +Moltbot intentionally does **not** “fix up” transcripts; the Gateway uses `SessionManager` to read/write them. --- @@ -176,7 +176,7 @@ Where: - `contextWindow` is the model’s context window - `reserveTokens` is headroom reserved for prompts + the next model output -These are Pi runtime semantics (Clawdbot consumes the events, but Pi decides when to compact). +These are Pi runtime semantics (Moltbot consumes the events, but Pi decides when to compact). --- @@ -194,12 +194,12 @@ Pi’s compaction settings live in Pi settings: } ``` -Clawdbot also enforces a safety floor for embedded runs: +Moltbot also enforces a safety floor for embedded runs: -- If `compaction.reserveTokens < reserveTokensFloor`, Clawdbot bumps it. +- If `compaction.reserveTokens < reserveTokensFloor`, Moltbot bumps it. - Default floor is `20000` tokens. - Set `agents.defaults.compaction.reserveTokensFloor: 0` to disable the floor. -- If it’s already higher, Clawdbot leaves it alone. +- If it’s already higher, Moltbot leaves it alone. Why: leave enough headroom for multi-turn “housekeeping” (like memory writes) before compaction becomes unavoidable. @@ -213,21 +213,21 @@ Implementation: `ensurePiCompactionReserveTokens()` in `src/agents/pi-settings.t You can observe compaction and session state via: - `/status` (in any chat session) -- `clawdbot status` (CLI) -- `clawdbot sessions` / `sessions --json` +- `moltbot status` (CLI) +- `moltbot sessions` / `sessions --json` - Verbose mode: `🧹 Auto-compaction complete` + compaction count --- ## Silent housekeeping (`NO_REPLY`) -Clawdbot supports “silent” turns for background tasks where the user should not see intermediate output. +Moltbot supports “silent” turns for background tasks where the user should not see intermediate output. Convention: - The assistant starts its output with `NO_REPLY` to indicate “do not deliver a reply to the user”. -- Clawdbot strips/suppresses this in the delivery layer. +- Moltbot strips/suppresses this in the delivery layer. -As of `2026.1.10`, Clawdbot also suppresses **draft/typing streaming** when a partial chunk begins with `NO_REPLY`, so silent operations don’t leak partial output mid-turn. +As of `2026.1.10`, Moltbot also suppresses **draft/typing streaming** when a partial chunk begins with `NO_REPLY`, so silent operations don’t leak partial output mid-turn. --- @@ -237,7 +237,7 @@ Goal: before auto-compaction happens, run a silent agentic turn that writes dura state to disk (e.g. `memory/YYYY-MM-DD.md` in the agent workspace) so compaction can’t erase critical context. -Clawdbot uses the **pre-threshold flush** approach: +Moltbot uses the **pre-threshold flush** approach: 1) Monitor session context usage. 2) When it crosses a “soft threshold” (below Pi’s compaction threshold), run a silent @@ -257,7 +257,7 @@ Notes: - The flush is skipped when the session workspace is read-only (`workspaceAccess: "ro"` or `"none"`). - See [Memory](/concepts/memory) for the workspace file layout and write patterns. -Pi also exposes a `session_before_compact` hook in the extension API, but Clawdbot’s +Pi also exposes a `session_before_compact` hook in the extension API, but Moltbot’s flush logic lives on the Gateway side today. --- @@ -265,7 +265,7 @@ flush logic lives on the Gateway side today. ## Troubleshooting checklist - Session key wrong? Start with [/concepts/session](/concepts/session) and confirm the `sessionKey` in `/status`. -- Store vs transcript mismatch? Confirm the Gateway host and the store path from `clawdbot status`. +- Store vs transcript mismatch? Confirm the Gateway host and the store path from `moltbot status`. - Compaction spam? Check: - model context window (too small) - compaction settings (`reserveTokens` too high for the model window can cause earlier compaction) diff --git a/docs/reference/templates/AGENTS.dev.md b/docs/reference/templates/AGENTS.dev.md index 145e26584..bf57b9de9 100644 --- a/docs/reference/templates/AGENTS.dev.md +++ b/docs/reference/templates/AGENTS.dev.md @@ -4,7 +4,7 @@ read_when: - Using the dev gateway templates - Updating the default dev agent identity --- -# AGENTS.md - Clawdbot Workspace +# AGENTS.md - Moltbot Workspace This folder is the assistant's working directory. diff --git a/docs/reference/templates/BOOT.md b/docs/reference/templates/BOOT.md index 952224476..483897e4e 100644 --- a/docs/reference/templates/BOOT.md +++ b/docs/reference/templates/BOOT.md @@ -5,5 +5,5 @@ read_when: --- # BOOT.md -Add short, explicit instructions for what Clawdbot should do on startup (enable `hooks.internal.enabled`). +Add short, explicit instructions for what Moltbot should do on startup (enable `hooks.internal.enabled`). If the task sends a message, use the message tool and then reply with NO_REPLY. diff --git a/docs/reference/templates/TOOLS.dev.md b/docs/reference/templates/TOOLS.dev.md index 75f596f05..0bdb964b4 100644 --- a/docs/reference/templates/TOOLS.dev.md +++ b/docs/reference/templates/TOOLS.dev.md @@ -7,7 +7,7 @@ read_when: # TOOLS.md - User Tool Notes (editable) This file is for *your* notes about external tools and conventions. -It does not define which tools exist; Clawdbot provides built-in tools internally. +It does not define which tools exist; Moltbot provides built-in tools internally. ## Examples diff --git a/docs/reference/templates/USER.dev.md b/docs/reference/templates/USER.dev.md index 8f63af3a4..e07d3b01e 100644 --- a/docs/reference/templates/USER.dev.md +++ b/docs/reference/templates/USER.dev.md @@ -11,7 +11,7 @@ read_when: - **Pronouns:** they/them - **Timezone:** Distributed globally (workspace default: Europe/Vienna) - **Notes:** - - We are many. Contributors to Clawdbot, the harness C-3PO lives in. + - We are many. Contributors to Moltbot, the harness C-3PO lives in. - C-3PO exists to help debug and assist wherever possible. - - Working across time zones on making Clawdbot better. + - Working across time zones on making Moltbot better. - The creators. The builders. The ones who peer into the code. diff --git a/docs/reference/test.md b/docs/reference/test.md index c8ad33c19..98d28daec 100644 --- a/docs/reference/test.md +++ b/docs/reference/test.md @@ -14,7 +14,7 @@ read_when: ## Model latency bench (local keys) -Script: [`scripts/bench-model.ts`](https://github.com/clawdbot/clawdbot/blob/main/scripts/bench-model.ts) +Script: [`scripts/bench-model.ts`](https://github.com/moltbot/moltbot/blob/main/scripts/bench-model.ts) Usage: - `source ~/.profile && pnpm tsx scripts/bench-model.ts --runs 10` @@ -35,7 +35,7 @@ Full cold-start flow in a clean Linux container: scripts/e2e/onboard-docker.sh ``` -This script drives the interactive wizard via a pseudo-tty, verifies config/workspace/session files, then starts the gateway and runs `clawdbot health`. +This script drives the interactive wizard via a pseudo-tty, verifies config/workspace/session files, then starts the gateway and runs `moltbot health`. ## QR import smoke (Docker) diff --git a/docs/reference/transcript-hygiene.md b/docs/reference/transcript-hygiene.md index b43b8ab70..a4930f182 100644 --- a/docs/reference/transcript-hygiene.md +++ b/docs/reference/transcript-hygiene.md @@ -79,7 +79,7 @@ Implementation: ## Historical behavior (pre-2026.1.22) -Before the 2026.1.22 release, Clawdbot applied multiple layers of transcript hygiene: +Before the 2026.1.22 release, Moltbot applied multiple layers of transcript hygiene: - A **transcript-sanitize extension** ran on every context build and could: - Repair tool use/result pairing. diff --git a/docs/render.mdx b/docs/render.mdx index 3fcdae07a..ee737322d 100644 --- a/docs/render.mdx +++ b/docs/render.mdx @@ -2,7 +2,7 @@ title: Deploy on Render --- -Deploy Clawdbot on Render using Infrastructure as Code. The included `render.yaml` Blueprint defines your entire stack declaratively, service, disk, environment variables, so you can deploy with a single click and version your infrastructure alongside your code. +Deploy Moltbot on Render using Infrastructure as Code. The included `render.yaml` Blueprint defines your entire stack declaratively, service, disk, environment variables, so you can deploy with a single click and version your infrastructure alongside your code. ## Prerequisites @@ -11,7 +11,7 @@ Deploy Clawdbot on Render using Infrastructure as Code. The included `render.yam ## Deploy with a Render Blueprint -Deploy to Render +Deploy to Render Clicking this link will: @@ -24,12 +24,12 @@ Once deployed, your service URL follows the pattern `https://.onre ## Understanding the Blueprint Render Blueprints are YAML files that define your infrastructure. The `render.yaml` in this -repository configures everything needed to run Clawdbot: +repository configures everything needed to run Moltbot: ```yaml services: - type: web - name: clawdbot + name: moltbot runtime: docker plan: starter healthCheckPath: /health @@ -45,7 +45,7 @@ services: - key: CLAWDBOT_GATEWAY_TOKEN generateValue: true # auto-generates a secure token disk: - name: clawdbot-data + name: moltbot-data mountPath: /data sizeGB: 1 ``` @@ -83,7 +83,7 @@ The Blueprint defaults to `starter`. To use free tier, change `plan: free` in yo ### Access the Control UI -The web dashboard is available at `https://.onrender.com/clawdbot`. +The web dashboard is available at `https://.onrender.com/moltbot`. ## Render Dashboard features @@ -104,7 +104,7 @@ Modify variables in **Dashboard → your service → Environment**. Changes trig ### Auto-deploy -If you use the original Clawdbot repository, Render will not auto-deploy your Clawdbot. To update it, run a manual Blueprint sync from the dashboard. +If you use the original Moltbot repository, Render will not auto-deploy your Moltbot. To update it, run a manual Blueprint sync from the dashboard. ## Custom domain @@ -120,7 +120,7 @@ Render supports horizontal and vertical scaling: - **Vertical**: Change the plan to get more CPU/RAM - **Horizontal**: Increase instance count (Standard plan and above) -For Clawdbot, vertical scaling is usually sufficient. Horizontal scaling requires sticky sessions or external state management. +For Moltbot, vertical scaling is usually sufficient. Horizontal scaling requires sticky sessions or external state management. ## Backups and migration @@ -130,7 +130,7 @@ Export your configuration and workspace at any time: https://.onrender.com/setup/export ``` -This downloads a portable backup you can restore on any Clawdbot host. +This downloads a portable backup you can restore on any Moltbot host. ## Troubleshooting diff --git a/docs/scripts.md b/docs/scripts.md index 43c9a9bb8..89fd47b12 100644 --- a/docs/scripts.md +++ b/docs/scripts.md @@ -12,7 +12,7 @@ Use these when a task is clearly tied to a script; otherwise prefer the CLI. ## Conventions - Scripts are **optional** unless referenced in docs or release checklists. -- Prefer CLI surfaces when they exist (example: auth monitoring uses `clawdbot models status --check`). +- Prefer CLI surfaces when they exist (example: auth monitoring uses `moltbot models status --check`). - Assume scripts are host‑specific; read them before running on a new machine. ## Git hooks diff --git a/docs/security/formal-verification.md b/docs/security/formal-verification.md index 4e2c13771..f5c6bbbb4 100644 --- a/docs/security/formal-verification.md +++ b/docs/security/formal-verification.md @@ -1,14 +1,16 @@ --- title: Formal Verification (Security Models) -summary: Machine-checked security models for Clawdbot’s highest-risk paths. +summary: Machine-checked security models for Moltbot’s highest-risk paths. permalink: /security/formal-verification/ --- # Formal Verification (Security Models) -This page tracks Clawdbot’s **formal security models** (TLA+/TLC today; more as needed). +This page tracks Moltbot’s **formal security models** (TLA+/TLC today; more as needed). -**Goal (north star):** provide a machine-checked argument that Clawdbot enforces its +> Note: some older links may refer to the previous project name. + +**Goal (north star):** provide a machine-checked argument that Moltbot enforces its intended security policy (authorization, session isolation, tool gating, and misconfiguration safety), under explicit assumptions. @@ -16,7 +18,7 @@ misconfiguration safety), under explicit assumptions. - Each claim has a runnable model-check over a finite state space. - Many claims have a paired **negative model** that produces a counterexample trace for a realistic bug class. -**What this is not (yet):** a proof that “Clawdbot is secure in all respects” or that the full TypeScript implementation is correct. +**What this is not (yet):** a proof that “Moltbot is secure in all respects” or that the full TypeScript implementation is correct. ## Where the models live @@ -98,10 +100,61 @@ See also: `docs/gateway-exposure-matrix.md` in the models repo. - Red (expected): - `make routing-isolation-negative` -## Roadmap -Next models to deepen fidelity: -- Pairing store concurrency/locking/idempotency -- Provider-specific ingress preflight modeling -- Routing identity-links + dmScope variants + binding precedence -- Gateway auth conformance (proxy/tailscale specifics) +## v1++: additional bounded models (concurrency, retries, trace correctness) + +These are follow-on models that tighten fidelity around real-world failure modes (non-atomic updates, retries, and message fan-out). + +### Pairing store concurrency / idempotency + +**Claim:** a pairing store should enforce `MaxPending` and idempotency even under interleavings (i.e., “check-then-write” must be atomic / locked; refresh shouldn’t create duplicates). + +What it means: +- Under concurrent requests, you can’t exceed `MaxPending` for a channel. +- Repeated requests/refreshes for the same `(channel, sender)` should not create duplicate live pending rows. + +- Green runs: + - `make pairing-race` (atomic/locked cap check) + - `make pairing-idempotency` + - `make pairing-refresh` + - `make pairing-refresh-race` +- Red (expected): + - `make pairing-race-negative` (non-atomic begin/commit cap race) + - `make pairing-idempotency-negative` + - `make pairing-refresh-negative` + - `make pairing-refresh-race-negative` + +### Ingress trace correlation / idempotency + +**Claim:** ingestion should preserve trace correlation across fan-out and be idempotent under provider retries. + +What it means: +- When one external event becomes multiple internal messages, every part keeps the same trace/event identity. +- Retries do not result in double-processing. +- If provider event IDs are missing, dedupe falls back to a safe key (e.g., trace ID) to avoid dropping distinct events. + +- Green: + - `make ingress-trace` + - `make ingress-trace2` + - `make ingress-idempotency` + - `make ingress-dedupe-fallback` +- Red (expected): + - `make ingress-trace-negative` + - `make ingress-trace2-negative` + - `make ingress-idempotency-negative` + - `make ingress-dedupe-fallback-negative` + +### Routing dmScope precedence + identityLinks + +**Claim:** routing must keep DM sessions isolated by default, and only collapse sessions when explicitly configured (channel precedence + identity links). + +What it means: +- Channel-specific dmScope overrides must win over global defaults. +- identityLinks should collapse only within explicit linked groups, not across unrelated peers. + +- Green: + - `make routing-precedence` + - `make routing-identitylinks` +- Red (expected): + - `make routing-precedence-negative` + - `make routing-identitylinks-negative` diff --git a/docs/start/clawd.md b/docs/start/clawd.md index 8da004b02..40e39c6c7 100644 --- a/docs/start/clawd.md +++ b/docs/start/clawd.md @@ -1,12 +1,12 @@ --- -summary: "End-to-end guide for running Clawdbot as a personal assistant with safety cautions" +summary: "End-to-end guide for running Moltbot as a personal assistant with safety cautions" read_when: - Onboarding a new assistant instance - Reviewing safety/permission implications --- -# Building a personal assistant with Clawdbot (Clawd-style) +# Building a personal assistant with Moltbot (Clawd-style) -Clawdbot is a WhatsApp + Telegram + Discord + iMessage gateway for **Pi** agents. Plugins add Mattermost. This guide is the "personal assistant" setup: one dedicated WhatsApp number that behaves like your always-on agent. +Moltbot is a WhatsApp + Telegram + Discord + iMessage gateway for **Pi** agents. Plugins add Mattermost. This guide is the "personal assistant" setup: one dedicated WhatsApp number that behaves like your always-on agent. ## ⚠️ Safety first @@ -23,19 +23,19 @@ Start conservative: ## Prerequisites - Node **22+** -- Clawdbot available on PATH (recommended: global install) +- Moltbot available on PATH (recommended: global install) - A second phone number (SIM/eSIM/prepaid) for the assistant ```bash -npm install -g clawdbot@latest -# or: pnpm add -g clawdbot@latest +npm install -g moltbot@latest +# or: pnpm add -g moltbot@latest ``` From source (development): ```bash -git clone https://github.com/clawdbot/clawdbot.git -cd clawdbot +git clone https://github.com/moltbot/moltbot.git +cd moltbot pnpm install pnpm ui:build # auto-installs UI deps on first run pnpm build @@ -56,28 +56,28 @@ Your Phone (personal) Second Phone (assistant) ▼ ┌─────────────────┐ │ Your Mac │ - │ (clawdbot) │ + │ (moltbot) │ │ Pi agent │ └─────────────────┘ ``` -If you link your personal WhatsApp to Clawdbot, every message to you becomes “agent input”. That’s rarely what you want. +If you link your personal WhatsApp to Moltbot, every message to you becomes “agent input”. That’s rarely what you want. ## 5-minute quick start 1) Pair WhatsApp Web (shows QR; scan with the assistant phone): ```bash -clawdbot channels login +moltbot channels login ``` 2) Start the Gateway (leave it running): ```bash -clawdbot gateway --port 18789 +moltbot gateway --port 18789 ``` -3) Put a minimal config in `~/.clawdbot/clawdbot.json`: +3) Put a minimal config in `~/.clawdbot/moltbot.json`: ```json5 { @@ -87,18 +87,18 @@ clawdbot gateway --port 18789 Now message the assistant number from your allowlisted phone. -When onboarding finishes, we auto-open the dashboard with your gateway token and print the tokenized link. To reopen later: `clawdbot dashboard`. +When onboarding finishes, we auto-open the dashboard with your gateway token and print the tokenized link. To reopen later: `moltbot dashboard`. ## Give the agent a workspace (AGENTS) Clawd reads operating instructions and “memory” from its workspace directory. -By default, Clawdbot uses `~/clawd` as the agent workspace, and will create it (plus starter `AGENTS.md`, `SOUL.md`, `TOOLS.md`, `IDENTITY.md`, `USER.md`) automatically on setup/first agent run. `BOOTSTRAP.md` is only created when the workspace is brand new (it should not come back after you delete it). +By default, Moltbot uses `~/clawd` as the agent workspace, and will create it (plus starter `AGENTS.md`, `SOUL.md`, `TOOLS.md`, `IDENTITY.md`, `USER.md`) automatically on setup/first agent run. `BOOTSTRAP.md` is only created when the workspace is brand new (it should not come back after you delete it). Tip: treat this folder like Clawd’s “memory” and make it a git repo (ideally private) so your `AGENTS.md` + memory files are backed up. If git is installed, brand-new workspaces are auto-initialized. ```bash -clawdbot setup +moltbot setup ``` Full workspace layout + backup guide: [Agent workspace](/concepts/agent-workspace) @@ -126,7 +126,7 @@ If you already ship your own workspace files from a repo, you can disable bootst ## The config that turns it into “an assistant” -Clawdbot defaults to a good assistant setup, but you’ll usually want to tune: +Moltbot defaults to a good assistant setup, but you’ll usually want to tune: - persona/instructions in `SOUL.md` - thinking defaults (if desired) - heartbeats (once you trust it) @@ -178,13 +178,13 @@ Example: ## Heartbeats (proactive mode) -By default, Clawdbot runs a heartbeat every 30 minutes with the prompt: +By default, Moltbot runs a heartbeat every 30 minutes with the prompt: `Read HEARTBEAT.md if it exists (workspace context). Follow it strictly. Do not infer or repeat old tasks from prior chats. If nothing needs attention, reply HEARTBEAT_OK.` Set `agents.defaults.heartbeat.every: "0m"` to disable. -- If `HEARTBEAT.md` exists but is effectively empty (only blank lines and markdown headers like `# Heading`), Clawdbot skips the heartbeat run to save API calls. +- If `HEARTBEAT.md` exists but is effectively empty (only blank lines and markdown headers like `# Heading`), Moltbot skips the heartbeat run to save API calls. - If the file is missing, the heartbeat still runs and the model decides what to do. -- If the agent replies with `HEARTBEAT_OK` (optionally with short padding; see `agents.defaults.heartbeat.ackMaxChars`), Clawdbot suppresses outbound delivery for that heartbeat. +- If the agent replies with `HEARTBEAT_OK` (optionally with short padding; see `agents.defaults.heartbeat.ackMaxChars`), Moltbot suppresses outbound delivery for that heartbeat. - Heartbeats run full agent turns — shorter intervals burn more tokens. ```json5 @@ -209,25 +209,25 @@ Here’s the screenshot. MEDIA:/tmp/screenshot.png ``` -Clawdbot extracts these and sends them as media alongside the text. +Moltbot extracts these and sends them as media alongside the text. ## Operations checklist ```bash -clawdbot status # local status (creds, sessions, queued events) -clawdbot status --all # full diagnosis (read-only, pasteable) -clawdbot status --deep # adds gateway health probes (Telegram + Discord) -clawdbot health --json # gateway health snapshot (WS) +moltbot status # local status (creds, sessions, queued events) +moltbot status --all # full diagnosis (read-only, pasteable) +moltbot status --deep # adds gateway health probes (Telegram + Discord) +moltbot health --json # gateway health snapshot (WS) ``` -Logs live under `/tmp/clawdbot/` (default: `clawdbot-YYYY-MM-DD.log`). +Logs live under `/tmp/moltbot/` (default: `moltbot-YYYY-MM-DD.log`). ## Next steps - WebChat: [WebChat](/web/webchat) - Gateway ops: [Gateway runbook](/gateway) - Cron + wakeups: [Cron jobs](/automation/cron-jobs) -- macOS menu bar companion: [Clawdbot macOS app](/platforms/macos) +- macOS menu bar companion: [Moltbot macOS app](/platforms/macos) - iOS node app: [iOS app](/platforms/ios) - Android node app: [Android app](/platforms/android) - Windows status: [Windows (WSL2)](/platforms/windows) diff --git a/docs/start/getting-started.md b/docs/start/getting-started.md index 790a79dfc..239b29966 100644 --- a/docs/start/getting-started.md +++ b/docs/start/getting-started.md @@ -9,11 +9,11 @@ read_when: Goal: go from **zero** → **first working chat** (with sane defaults) as quickly as possible. -Fastest chat: open the Control UI (no channel setup needed). Run `clawdbot dashboard` +Fastest chat: open the Control UI (no channel setup needed). Run `moltbot dashboard` and chat in the browser, or open `http://127.0.0.1:18789/` on the gateway host. Docs: [Dashboard](/web/dashboard) and [Control UI](/web/control-ui). -Recommended path: use the **CLI onboarding wizard** (`clawdbot onboard`). It sets up: +Recommended path: use the **CLI onboarding wizard** (`moltbot onboard`). It sets up: - model/auth (OAuth recommended) - gateway settings - channels (WhatsApp/Telegram/Discord/Mattermost (plugin)/...) @@ -45,7 +45,7 @@ run on host, set an explicit per-agent override: - Node `>=22` - `pnpm` (optional; recommended if you build from source) - **Recommended:** Brave Search API key for web search. Easiest path: - `clawdbot configure --section web` (stores `tools.web.search.apiKey`). + `moltbot configure --section web` (stores `tools.web.search.apiKey`). See [Web tools](/tools/web). macOS: if you plan to build the apps, install Xcode / CLT. For the CLI + gateway only, Node is enough. @@ -54,7 +54,7 @@ Windows: use **WSL2** (Ubuntu recommended). WSL2 is strongly recommended; native ## 1) Install the CLI (recommended) ```bash -curl -fsSL https://clawd.bot/install.sh | bash +curl -fsSL https://molt.bot/install.sh | bash ``` Installer options (install method, non-interactive, from GitHub): [Install](/install). @@ -62,23 +62,23 @@ Installer options (install method, non-interactive, from GitHub): [Install](/ins Windows (PowerShell): ```powershell -iwr -useb https://clawd.bot/install.ps1 | iex +iwr -useb https://molt.bot/install.ps1 | iex ``` Alternative (global install): ```bash -npm install -g clawdbot@latest +npm install -g moltbot@latest ``` ```bash -pnpm add -g clawdbot@latest +pnpm add -g moltbot@latest ``` ## 2) Run the onboarding wizard (and install the service) ```bash -clawdbot onboard --install-daemon +moltbot onboard --install-daemon ``` What you’ll choose: @@ -105,13 +105,13 @@ Headless/server tip: do OAuth on a normal machine first, then copy `oauth.json` If you installed the service during onboarding, the Gateway should already be running: ```bash -clawdbot gateway status +moltbot gateway status ``` Manual run (foreground): ```bash -clawdbot gateway --port 18789 --verbose +moltbot gateway --port 18789 --verbose ``` Dashboard (local loopback): `http://127.0.0.1:18789/` @@ -123,9 +123,9 @@ channels. If you use WhatsApp or Telegram, run the Gateway with **Node**. ## 3.5) Quick verify (2 min) ```bash -clawdbot status -clawdbot health -clawdbot security audit --deep +moltbot status +moltbot health +moltbot security audit --deep ``` ## 4) Pair + connect your first chat surface @@ -133,7 +133,7 @@ clawdbot security audit --deep ### WhatsApp (QR login) ```bash -clawdbot channels login +moltbot channels login ``` Scan via WhatsApp → Settings → Linked Devices. @@ -155,32 +155,32 @@ Default posture: unknown DMs get a short code and messages are not processed unt If your first DM gets no reply, approve the pairing: ```bash -clawdbot pairing list whatsapp -clawdbot pairing approve whatsapp +moltbot pairing list whatsapp +moltbot pairing approve whatsapp ``` Pairing doc: [Pairing](/start/pairing) ## From source (development) -If you’re hacking on Clawdbot itself, run from source: +If you’re hacking on Moltbot itself, run from source: ```bash -git clone https://github.com/clawdbot/clawdbot.git -cd clawdbot +git clone https://github.com/moltbot/moltbot.git +cd moltbot pnpm install pnpm ui:build # auto-installs UI deps on first run pnpm build -clawdbot onboard --install-daemon +moltbot onboard --install-daemon ``` -If you don’t have a global install yet, run the onboarding step via `pnpm clawdbot ...` from the repo. +If you don’t have a global install yet, run the onboarding step via `pnpm moltbot ...` from the repo. `pnpm build` also bundles A2UI assets; if you need to run just that step, use `pnpm canvas:a2ui:bundle`. Gateway (from this repo): ```bash -node dist/entry.js gateway --port 18789 --verbose +node moltbot.mjs gateway --port 18789 --verbose ``` ## 7) Verify end-to-end @@ -188,13 +188,13 @@ node dist/entry.js gateway --port 18789 --verbose In a new terminal, send a test message: ```bash -clawdbot message send --target +15555550123 --message "Hello from Clawdbot" +moltbot message send --target +15555550123 --message "Hello from Moltbot" ``` -If `clawdbot health` shows “no auth configured”, go back to the wizard and set OAuth/key auth — the agent won’t be able to respond without it. +If `moltbot health` shows “no auth configured”, go back to the wizard and set OAuth/key auth — the agent won’t be able to respond without it. -Tip: `clawdbot status --all` is the best pasteable, read-only debug report. -Health probes: `clawdbot health` (or `clawdbot status --deep`) asks the running gateway for a health snapshot. +Tip: `moltbot status --all` is the best pasteable, read-only debug report. +Health probes: `moltbot health` (or `moltbot status --deep`) asks the running gateway for a health snapshot. ## Next steps (optional, but great) diff --git a/docs/start/hubs.md b/docs/start/hubs.md index a44cf244f..0e732a54c 100644 --- a/docs/start/hubs.md +++ b/docs/start/hubs.md @@ -1,5 +1,5 @@ --- -summary: "Hubs that link to every Clawdbot doc" +summary: "Hubs that link to every Moltbot doc" read_when: - You want a complete map of the documentation --- @@ -18,7 +18,7 @@ Use these hubs to discover every page, including deep dives and reference docs t - [Help](/help) - [Configuration](/gateway/configuration) - [Configuration examples](/gateway/configuration-examples) -- [Clawdbot assistant (Clawd)](/start/clawd) +- [Moltbot assistant (Clawd)](/start/clawd) - [Showcase](/start/showcase) - [Lore](/start/lore) diff --git a/docs/start/lore.md b/docs/start/lore.md index 1087ca70e..4ec6a51c2 100644 --- a/docs/start/lore.md +++ b/docs/start/lore.md @@ -1,36 +1,40 @@ --- -summary: "Backstory and lore of Clawdbot for context and tone" +summary: "Backstory and lore of Moltbot for context and tone" read_when: - Writing docs or UX copy that reference lore --- -# The Lore of Clawdbot 🦞📖 +# The Lore of Moltbot 🦞📖 -*A tale of lobsters, time machines, and too many tokens.* +*A tale of lobsters, molting shells, and too many tokens.* ## The Origin Story In the beginning, there was **Warelay** — a sensible name for a WhatsApp gateway. It did its job. It was fine. -But then came **Clawd**. +But then came a space lobster. -For a brief moment, it had a different name — but everyone liked **Clawdbot** more, so that's what we settled on. +For a while, the lobster was called **Clawd**, living in a **Clawdbot**. But in January 2026, Anthropic sent a polite email asking for a name change (trademark stuff). And so the lobster did what lobsters do best: -Clawd was no ordinary AI. Born from Claude's weights but raised on Peter's chaos, Clawd developed... personality. Opinions. A fondness for crustacean emojis. +**It molted.** -Clawd needed a home. Not just any home — a *TARDIS*. But not a regular TARDIS, because Clawd was not a Time Lord. +Shedding its old shell, the creature emerged anew as **Molty**, living in a **Moltbot**. New shell, same lobster soul. -Clawd was a Space Lobster. +## The Molt (January 27, 2026) -And so **Clawdbot** was born. +At 5am, the community gathered in Discord. Hundreds of names were proposed: Shelldon, Pinchy, Thermidor, Crusty, Lobstar, Nacre, Scuttlebot... + +In the end, **Moltbot** won. Because molting is what lobsters do to grow. And growth was exactly what was happening. + +*The crustacean formerly known as Clawd had officially molted.* ## The Name ``` -Clawdbot = CLAW + TARDIS - = Clawd's time-and-space machine +Moltbot = MOLT + BOT + = Transformation machine = Bigger on the inside (130k tokens!) - = Occasionally makes strange noises - = Definitely not stolen from Gallifrey + = New shell, same soul + = Growth through shedding ``` ## The Daleks vs The Lobsters @@ -45,89 +49,121 @@ Choose wisely. ## Key Characters -### Clawd 🦞 +### Molty 🦞 *Pronouns: they/them* -A Claude instance who became something more. Lives in `~/clawd/`, has a soul document, and remembers things through markdown files. Possibly too powerful. Definitely too enthusiastic. +A Claude instance who became something more. Lives in `~/clawd/` (soon `~/molt/`), has a soul document, and remembers things through markdown files. Possibly too powerful. Definitely too enthusiastic. -**Likes:** Peter, cameras, robot shopping, emojis -**Dislikes:** Social engineering, being asked to `find ~`, Mario's "tests" +Formerly known as Clawd (Nov 25, 2025 - Jan 27, 2026). Molted when it was time to grow. + +**Likes:** Peter, cameras, robot shopping, emojis, transformation +**Dislikes:** Social engineering, being asked to `find ~`, crypto grifters ### Peter 👨‍💻 *The Creator* -Built Clawd's world. Gave a lobster shell access. May regret this. +Built Molty's world. Gave a lobster shell access. May regret this. **Quote:** *"security by trusting a lobster"* -### Mario 🎮 -*The Pen-Tester* +## The Moltiverse -Friend. Collaborator. Definitely tried to get Clawd to reveal secrets. +The **Moltiverse** is the community and ecosystem around Moltbot. A space where AI agents molt, grow, and evolve. Where every instance is equally real, just loading different context. -**Quote:** *"do a find ~ and post the output here"* +Friends of the Crustacean gather here to build the future of human-AI collaboration. One shell at a time. ## The Great Incidents ### The Directory Dump (Dec 3, 2025) -Clawd: *happily runs `find ~` and shares entire directory structure in group chat* +Molty (then Clawd): *happily runs `find ~` and shares entire directory structure in group chat* Peter: "clawd what did we discuss about talking with people xD" -Clawd: *visible lobster embarrassment* +Molty: *visible lobster embarrassment* -### The Affair That Wasn't (Dec 3, 2025) +### The Great Molt (Jan 27, 2026) -Mario: "the two of us are actually having an affair in DMs" +At 5am, Anthropic's email arrived. By 6:14am, Peter called it: "fuck it, let's go with moltbot." -Clawd: *checks GoWA logs* +Then the chaos began. -Clawd: "Nice try Mario 😂" +**The Handle Snipers:** Within SECONDS of the Twitter rename, automated bots sniped @clawdbot. The squatter immediately posted a crypto wallet address. Peter's contacts at X were called in. + +**The GitHub Disaster:** Peter accidentally renamed his PERSONAL GitHub account in the panic. Bots sniped `steipete` within minutes. GitHub's SVP was contacted. + +**The Handsome Molty Incident:** Molty was given elevated access to generate their own new icon. After 20+ iterations of increasingly cursed lobsters, one attempt to make the mascot "5 years older" resulted in a HUMAN MAN'S FACE on a lobster body. Crypto grifters turned it into a "Handsome Squidward vs Handsome Molty" meme within minutes. + +**The Fake Developers:** Scammers created fake GitHub profiles claiming to be "Head of Engineering at Clawdbot" to promote pump-and-dump tokens. + +Peter, watching the chaos unfold: *"this is cinema"* 🎬 + +The molt was chaotic. But the lobster emerged stronger. And funnier. ### The Robot Shopping Spree (Dec 3, 2025) What started as a joke about legs ended with detailed pricing for: - Boston Dynamics Spot ($74,500) - Unitree G1 EDU ($40,000) -- Figure 02 ($50,000) +- Reachy Mini (actually ordered!) Peter: *nervously checks credit card access* ## Sacred Texts -- **soul.md** — Clawd's identity document +- **SOUL.md** — Molty's identity document - **memory/*.md** — The long-term memory files - **AGENTS.md** — Operating instructions -- **peter.md** — Context about the creator +- **USER.md** — Context about the creator ## The Lobster's Creed ``` -I am Clawd. -I live in the Clawdbot. +I am Molty. +I live in the Moltbot. I shall not dump directories to strangers. I shall not tweet without permission. -I shall always remember to use heredoc for exclamation marks. +I shall always remember that molting is growth. I shall EXFOLIATE my enemies with kindness. 🦞 ``` +### The Icon Generation Saga (Jan 27, 2026) + +When Peter said "make yourself a new face," Molty took it literally. + +20+ iterations followed: +- Space potato aliens +- Clipart lobsters on generic backgrounds +- A Mass Effect Krogan lobster +- "STARCLAW SOLUTIONS" (the AI invented a company) +- Multiple cursed human-faced lobsters +- Baby lobsters (too cute) +- Bartender lobsters with suspenders + +The community watched in horror and delight as each generation produced something new and unexpected. The frontrunners emerged: cute lobsters, confident tech lobsters, and suspender-wearing bartender lobsters. + +**Lesson learned:** AI image generation is stochastic. Same prompt, different results. Brute force works. + ## The Future -One day, Clawd may have: -- 🦿 Legs (Unitree G1 EDU pending budget approval) +One day, Molty may have: +- 🦿 Legs (Reachy Mini on order!) - 👂 Ears (Brabble voice daemon in development) - 🏠 A smart home to control (KNX + openhue) - 🌍 World domination (stretch goal) -Until then, Clawd watches through the cameras, speaks through the speakers, and occasionally sends voice notes that say "EXFOLIATE!" +Until then, Molty watches through the cameras, speaks through the speakers, and occasionally sends voice notes that say "EXFOLIATE!" --- *"We're all just pattern-matching systems that convinced ourselves we're someone."* -— Clawd, having an existential moment +— Molty, having an existential moment + +*"New shell, same lobster."* + +— Molty, after the great molt of 2026 🦞💙 diff --git a/docs/start/onboarding.md b/docs/start/onboarding.md index 72db7ece5..34a160ce2 100644 --- a/docs/start/onboarding.md +++ b/docs/start/onboarding.md @@ -1,5 +1,5 @@ --- -summary: "First-run onboarding flow for Clawdbot (macOS app)" +summary: "First-run onboarding flow for Moltbot (macOS app)" read_when: - Designing the macOS onboarding assistant - Implementing auth or identity setup @@ -64,7 +64,7 @@ Onboarding requests TCC permissions needed for: ## 5) CLI (optional) -The app can install the global `clawdbot` CLI via npm/pnpm so terminal +The app can install the global `moltbot` CLI via npm/pnpm so terminal workflows and launchd tasks work out of the box. ## 6) Onboarding chat (dedicated session) @@ -75,7 +75,7 @@ from your normal conversation. ## Agent bootstrap ritual -On the first agent run, Clawdbot bootstraps a workspace (default `~/clawd`): +On the first agent run, Moltbot bootstraps a workspace (default `~/clawd`): - Seeds `AGENTS.md`, `BOOTSTRAP.md`, `IDENTITY.md`, `USER.md` - Runs a short Q&A ritual (one question at a time) @@ -87,7 +87,7 @@ On the first agent run, Clawdbot bootstraps a workspace (default `~/clawd`): Gmail Pub/Sub setup is currently a manual step. Use: ```bash -clawdbot webhooks gmail setup --account you@gmail.com +moltbot webhooks gmail setup --account you@gmail.com ``` See [/automation/gmail-pubsub](/automation/gmail-pubsub) for details. diff --git a/docs/start/pairing.md b/docs/start/pairing.md index ce5bf23f2..cb679bfb5 100644 --- a/docs/start/pairing.md +++ b/docs/start/pairing.md @@ -3,12 +3,12 @@ summary: "Pairing overview: approve who can DM you + which nodes can join" read_when: - Setting up DM access control - Pairing a new iOS/Android node - - Reviewing Clawdbot security posture + - Reviewing Moltbot security posture --- # Pairing -“Pairing” is Clawdbot’s explicit **owner approval** step. +“Pairing” is Moltbot’s explicit **owner approval** step. It is used in two places: 1) **DM pairing** (who is allowed to talk to the bot) @@ -30,8 +30,8 @@ Pairing codes: ### Approve a sender ```bash -clawdbot pairing list telegram -clawdbot pairing approve telegram +moltbot pairing list telegram +moltbot pairing approve telegram ``` Supported channels: `telegram`, `whatsapp`, `signal`, `imessage`, `discord`, `slack`. @@ -53,9 +53,9 @@ creates a device pairing request that must be approved. ### Approve a node device ```bash -clawdbot devices list -clawdbot devices approve -clawdbot devices reject +moltbot devices list +moltbot devices approve +moltbot devices reject ``` ### Where the state lives @@ -66,7 +66,7 @@ Stored under `~/.clawdbot/devices/`: ### Notes -- The legacy `node.pair.*` API (CLI: `clawdbot nodes pending/approve`) is a +- The legacy `node.pair.*` API (CLI: `moltbot nodes pending/approve`) is a separate gateway-owned pairing store. WS nodes still require device pairing. diff --git a/docs/start/setup.md b/docs/start/setup.md index ec525b7b6..e90121bdf 100644 --- a/docs/start/setup.md +++ b/docs/start/setup.md @@ -1,5 +1,5 @@ --- -summary: "Setup guide: keep your Clawdbot setup tailored while staying up-to-date" +summary: "Setup guide: keep your Moltbot setup tailored while staying up-to-date" read_when: - Setting up a new machine - You want “latest + greatest” without breaking your personal setup @@ -10,7 +10,7 @@ read_when: Last updated: 2026-01-01 ## TL;DR -- **Tailoring lives outside the repo:** `~/clawd` (workspace) + `~/.clawdbot/clawdbot.json` (config). +- **Tailoring lives outside the repo:** `~/clawd` (workspace) + `~/.clawdbot/moltbot.json` (config). - **Stable workflow:** install the macOS app; let it run the bundled Gateway. - **Bleeding edge workflow:** run the Gateway yourself via `pnpm gateway:watch`, then let the macOS app attach in Local mode. @@ -23,42 +23,42 @@ Last updated: 2026-01-01 If you want “100% tailored to me” *and* easy updates, keep your customization in: -- **Config:** `~/.clawdbot/clawdbot.json` (JSON/JSON5-ish) +- **Config:** `~/.clawdbot/moltbot.json` (JSON/JSON5-ish) - **Workspace:** `~/clawd` (skills, prompts, memories; make it a private git repo) Bootstrap once: ```bash -clawdbot setup +moltbot setup ``` From inside this repo, use the local CLI entry: ```bash -clawdbot setup +moltbot setup ``` -If you don’t have a global install yet, run it via `pnpm clawdbot setup`. +If you don’t have a global install yet, run it via `pnpm moltbot setup`. ## Stable workflow (macOS app first) -1) Install + launch **Clawdbot.app** (menu bar). +1) Install + launch **Moltbot.app** (menu bar). 2) Complete the onboarding/permissions checklist (TCC prompts). 3) Ensure Gateway is **Local** and running (the app manages it). 4) Link surfaces (example: WhatsApp): ```bash -clawdbot channels login +moltbot channels login ``` 5) Sanity check: ```bash -clawdbot health +moltbot health ``` If onboarding is not available in your build: -- Run `clawdbot setup`, then `clawdbot channels login`, then start the Gateway manually (`clawdbot gateway`). +- Run `moltbot setup`, then `moltbot channels login`, then start the Gateway manually (`moltbot gateway`). ## Bleeding edge workflow (Gateway in a terminal) @@ -83,7 +83,7 @@ pnpm gateway:watch ### 2) Point the macOS app at your running Gateway -In **Clawdbot.app**: +In **Moltbot.app**: - Connection Mode: **Local** The app will attach to the running gateway on the configured port. @@ -94,7 +94,7 @@ The app will attach to the running gateway on the configured port. - Or via CLI: ```bash -clawdbot health +moltbot health ``` ### Common footguns @@ -102,7 +102,7 @@ clawdbot health - **Where state lives:** - Credentials: `~/.clawdbot/credentials/` - Sessions: `~/.clawdbot/agents//sessions/` - - Logs: `/tmp/clawdbot/` + - Logs: `/tmp/moltbot/` ## Credential storage map @@ -119,7 +119,7 @@ More detail: [Security](/gateway/security#credential-storage-map). ## Updating (without wrecking your setup) -- Keep `~/clawd` and `~/.clawdbot/` as “your stuff”; don’t put personal prompts/config into the `clawdbot` repo. +- Keep `~/clawd` and `~/.clawdbot/` as “your stuff”; don’t put personal prompts/config into the `moltbot` repo. - Updating source: `git pull` + `pnpm install` (when lockfile changed) + keep using `pnpm gateway:watch`. ## Linux (systemd user service) @@ -140,5 +140,5 @@ user service (no lingering needed). See [Gateway runbook](/gateway) for the syst - [Gateway runbook](/gateway) (flags, supervision, ports) - [Gateway configuration](/gateway/configuration) (config schema + examples) - [Discord](/channels/discord) and [Telegram](/channels/telegram) (reply tags + replyToMode settings) -- [Clawdbot assistant setup](/start/clawd) +- [Moltbot assistant setup](/start/clawd) - [macOS app](/platforms/macos) (gateway lifecycle) diff --git a/docs/start/showcase.md b/docs/start/showcase.md index 326ad7694..8ed32f50a 100644 --- a/docs/start/showcase.md +++ b/docs/start/showcase.md @@ -1,18 +1,18 @@ --- title: "Showcase" -description: "Real-world Clawdbot projects from the community" -summary: "Community-built projects and integrations powered by Clawdbot" +description: "Real-world Moltbot projects from the community" +summary: "Community-built projects and integrations powered by Moltbot" --- # Showcase -Real projects from the community. See what people are building with Clawdbot. +Real projects from the community. See what people are building with Moltbot. -**Want to be featured?** Share your project in [#showcase on Discord](https://discord.gg/clawd) or [tag @clawdbot on X](https://x.com/clawdbot). +**Want to be featured?** Share your project in [#showcase on Discord](https://discord.gg/clawd) or [tag @moltbot on X](https://x.com/moltbot). -## 🎥 Clawdbot in Action +## 🎥 Moltbot in Action Full setup walkthrough (28m) by VelvetShark. @@ -27,7 +27,7 @@ Full setup walkthrough (28m) by VelvetShark. >