@gguf/pigbot 0.0.1 → 0.0.3

package/docs/plugin.md

@@ -1,5 +1,5 @@
 ---
-summary: "Pigbot 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 Pigbot 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 Pigbot 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
-pigbot plugins list
+moltbot plugins list
 ```
 
 2) Install an official plugin (example: Voice Call):
 
 ```bash
-pigbot plugins install @pigbot/voice-call
+moltbot plugins install @moltbot/voice-call
 ```
 
 3) Restart the Gateway, then configure under `plugins.entries.<id>.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 `@pigbot/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) — `@pigbot/voice-call`
-- [Zalo Personal](/plugins/zalouser) — `@pigbot/zalouser`
-- [Matrix](/channels/matrix) — `@pigbot/matrix`
-- [Nostr](/channels/nostr) — `@pigbot/nostr`
-- [Zalo](/channels/zalo) — `@pigbot/zalo`
-- [Microsoft Teams](/channels/msteams) — `@pigbot/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)
 
-Pigbot 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).
 
@@ -67,29 +67,45 @@ Plugins can register:
 Plugins run **in‑process** with the Gateway, so treat them as trusted code.
 Tool authoring guide: [Plugin agent tools](/plugins/agent-tools).
 
+## Runtime helpers
+
+Plugins can access selected core helpers via `api.runtime`. For telephony TTS:
+
+```ts
+const result = await api.runtime.tts.textToSpeechTelephony({
+  text: "Hello from Moltbot",
+  cfg: api.config,
+});
+```
+
+Notes:
+- Uses core `messages.tts` configuration (OpenAI or ElevenLabs).
+- Returns PCM audio buffer + sample rate. Plugins must resample/encode for providers.
+- Edge TTS is not supported for telephony.
+
 ## Discovery & precedence
 
-Pigbot scans, in order:
+Moltbot scans, in order:
 
 1) Config paths
 - `plugins.load.paths` (file or directory)
 
 2) Workspace extensions
-- `<workspace>/.pigbot/extensions/*.ts`
-- `<workspace>/.pigbot/extensions/*/index.ts`
+- `<workspace>/.clawdbot/extensions/*.ts`
+- `<workspace>/.clawdbot/extensions/*/index.ts`
 
 3) Global extensions
-- `~/.pigbot/extensions/*.ts`
-- `~/.pigbot/extensions/*/index.ts`
+- `~/.clawdbot/extensions/*.ts`
+- `~/.clawdbot/extensions/*/index.ts`
 
-4) Bundled extensions (shipped with Pigbot, **disabled by default**)
-- `<pigbot>/extensions/*`
+4) Bundled extensions (shipped with Moltbot, **disabled by default**)
+- `<moltbot>/extensions/*`
 
 Bundled plugins must be enabled explicitly via `plugins.entries.<id>.enabled`
-or `pigbot plugins enable <id>`. Installed plugins are enabled by default,
+or `moltbot plugins enable <id>`. Installed plugins are enabled by default,
 but can be disabled the same way.
 
-Each plugin must include a `pigbot.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.
 
@@ -98,12 +114,12 @@ wins and lower-precedence copies are ignored.
 
 ### Package packs
 
-A plugin directory may include a `package.json` with `pigbot.extensions`:
+A plugin directory may include a `package.json` with `moltbot.extensions`:
 
 ```json
 {
   "name": "my-pack",
-  "pigbot": {
+  "moltbot": {
     "extensions": ["./src/safety.ts", "./src/tools.ts"]
   }
 }
@@ -117,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 `pigbot.channel` and
-install hints via `pigbot.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": "@pigbot/nextcloud-talk",
-  "pigbot": {
+  "name": "@moltbot/nextcloud-talk",
+  "moltbot": {
     "extensions": ["./index.ts"],
     "channel": {
       "id": "nextcloud-talk",
@@ -138,7 +154,7 @@ Example:
       "aliases": ["nc-talk", "nc"]
     },
     "install": {
-      "npmSpec": "@pigbot/nextcloud-talk",
+      "npmSpec": "@moltbot/nextcloud-talk",
       "localPath": "extensions/nextcloud-talk",
       "defaultChoice": "npm"
     }
@@ -146,15 +162,15 @@ Example:
 }
 ```
 
-Pigbot 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:
-- `~/.pigbot/mpm/plugins.json`
-- `~/.pigbot/mpm/catalog.json`
-- `~/.pigbot/plugins/catalog.json`
+- `~/.clawdbot/mpm/plugins.json`
+- `~/.clawdbot/mpm/catalog.json`
+- `~/.clawdbot/plugins/catalog.json`
 
-Or point `PIGBOT_PLUGIN_CATALOG_PATHS` (or `PIGBOT_MPM_CATALOG_PATHS`) at
+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", "pigbot": { "channel": {...}, "install": {...} } } ] }`.
+contain `{ "entries": [ { "name": "@scope/pkg", "moltbot": { "channel": {...}, "install": {...} } } ] }`.
 
 ## Plugin IDs
 
@@ -163,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`, Pigbot 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
@@ -196,7 +212,7 @@ Validation rules (strict):
 - Unknown `channels.<id>` keys are **errors** unless a plugin manifest declares
   the channel id.
 - Plugin config is validated using the JSON Schema embedded in
-  `pigbot.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)
@@ -221,7 +237,7 @@ are disabled with diagnostics.
 
 The Control UI uses `config.schema` (JSON Schema + `uiHints`) to render better forms.
 
-Pigbot augments `uiHints` at runtime based on discovered plugins:
+Moltbot augments `uiHints` at runtime based on discovered plugins:
 
 - Adds per-plugin labels for `plugins.entries.<id>` / `.enabled` / `.config`
 - Merges optional plugin-provided config field hints under:
@@ -253,24 +269,24 @@ Example:
 ## CLI
 
 ```bash
-pigbot plugins list
-pigbot plugins info <id>
-pigbot plugins install <path>                 # copy a local file/dir into ~/.pigbot/extensions/<id>
-pigbot plugins install ./extensions/voice-call # relative path ok
-pigbot plugins install ./plugin.tgz           # install from a local tarball
-pigbot plugins install ./plugin.zip           # install from a local zip
-pigbot plugins install -l ./extensions/voice-call # link (no copy) for dev
-pigbot plugins install @pigbot/voice-call # install from npm
-pigbot plugins update <id>
-pigbot plugins update --all
-pigbot plugins enable <id>
-pigbot plugins disable <id>
-pigbot plugins doctor
+moltbot plugins list
+moltbot plugins info <id>
+moltbot plugins install <path>                 # copy a local file/dir into ~/.clawdbot/extensions/<id>
+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 <id>
+moltbot plugins update --all
+moltbot plugins enable <id>
+moltbot plugins disable <id>
+moltbot plugins doctor
 ```
 
 `plugins update` only works for npm installs tracked under `plugins.installs`.
 
-Plugins may also register their own top‑level commands (example: `pigbot voicecall`).
+Plugins may also register their own top‑level commands (example: `moltbot voicecall`).
 
 ## Plugin API (overview)
 
@@ -287,7 +303,7 @@ event-driven automation without a separate hook pack install.
 ### Example
 
 ```
-import { registerPluginHooksFromDir } from "pigbot/plugin-sdk";
+import { registerPluginHooksFromDir } from "moltbot/plugin-sdk";
 
 export default function register(api) {
   registerPluginHooksFromDir(api, "./hooks");
@@ -297,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 `pigbot hooks list` with `plugin:<id>`.
-- You cannot enable/disable plugin-managed hooks via `pigbot hooks`; enable/disable the plugin instead.
+- Plugin-managed hooks show up in `moltbot hooks list` with `plugin:<id>`.
+- 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 Pigbot (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:
 
-- `pigbot models auth login --provider <id> [--method <id>]`
+- `moltbot models auth login --provider <id> [--method <id>]`
 
 Example:
 
@@ -520,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 Pigbot config
+- `config`: The current Moltbot config
 
 Command options:
 
@@ -582,14 +598,14 @@ it’s present in your workspace/managed skills locations.
 
 Recommended packaging:
 
-- Main package: `pigbot` (this repo)
-- Plugins: separate npm packages under `@pigbot/*` (example: `@pigbot/voice-call`)
+- Main package: `moltbot` (this repo)
+- Plugins: separate npm packages under `@moltbot/*` (example: `@moltbot/voice-call`)
 
 Publishing contract:
 
-- Plugin `package.json` must include `pigbot.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).
-- `pigbot plugins install <npm-spec>` uses `npm pack`, extracts into `~/.pigbot/extensions/<id>/`, and enables it in config.
+- `moltbot plugins install <npm-spec>` uses `npm pack`, extracts into `~/.clawdbot/extensions/<id>/`, and enables it in config.
 - Config key stability: scoped packages are normalized to the **unscoped** id for `plugins.entries.*`.
 
 ## Example plugin: Voice Call
@@ -598,7 +614,7 @@ This repo includes a voice‑call plugin (Twilio or log fallback):
 
 - Source: `extensions/voice-call`
 - Skill: `skills/voice-call`
-- CLI: `pigbot 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`)
@@ -619,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 `pigbot.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`).

package/docs/plugins/agent-tools.md

@@ -6,7 +6,7 @@ read_when:
 ---
 # Plugin agent tools
 
-Pigbot 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).
 

package/docs/plugins/manifest.md

@@ -1,13 +1,13 @@
 ---
 summary: "Plugin manifest + JSON schema requirements (strict config validation)"
 read_when:
-  - You are building a Pigbot plugin
+  - You are building a Moltbot plugin
   - You need to ship a plugin config schema or debug plugin validation errors
 ---
-# Plugin manifest (pigbot.plugin.json)
+# Plugin manifest (moltbot.plugin.json)
 
-Every plugin **must** ship a `pigbot.plugin.json` file in the **plugin root**.
-Pigbot 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.
 

package/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 Pigbot
+  - 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 Pigbot 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 `pigbot 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
-pigbot plugins install @pigbot/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
-pigbot plugins install ./extensions/voice-call
+moltbot plugins install ./extensions/voice-call
 cd ./extensions/voice-call && pnpm install
 ```
 
@@ -103,6 +103,90 @@ Notes:
 - Plivo requires a **publicly reachable** webhook URL.
 - `mock` is a local dev provider (no network calls).
 - `skipSignatureVerification` is for local testing only.
+- If you use ngrok free tier, set `publicUrl` to the exact ngrok URL; signature verification is always enforced.
+- `tunnel.allowNgrokFreeTierLoopbackBypass: true` allows Twilio webhooks with invalid signatures **only** when `tunnel.provider="ngrok"` and `serve.bind` is loopback (ngrok local agent). Use for local dev only.
+- Ngrok free tier URLs can change or add interstitial behavior; if `publicUrl` drifts, Twilio signatures will fail. For production, prefer a stable domain or Tailscale funnel.
+
+## TTS for calls
+
+Voice Call uses the core `messages.tts` configuration (OpenAI or ElevenLabs) for
+streaming speech on calls. You can override it under the plugin config with the
+**same shape** — it deep‑merges with `messages.tts`.
+
+```json5
+{
+  tts: {
+    provider: "elevenlabs",
+    elevenlabs: {
+      voiceId: "pMsXgVXv3BLzUgSXRplE",
+      modelId: "eleven_multilingual_v2"
+    }
+  }
+}
+```
+
+Notes:
+- **Edge TTS is ignored for voice calls** (telephony audio needs PCM; Edge output is unreliable).
+- Core TTS is used when Twilio media streaming is enabled; otherwise calls fall back to provider native voices.
+
+### More examples
+
+Use core TTS only (no override):
+
+```json5
+{
+  messages: {
+    tts: {
+      provider: "openai",
+      openai: { voice: "alloy" }
+    }
+  }
+}
+```
+
+Override to ElevenLabs just for calls (keep core default elsewhere):
+
+```json5
+{
+  plugins: {
+    entries: {
+      "voice-call": {
+        config: {
+          tts: {
+            provider: "elevenlabs",
+            elevenlabs: {
+              apiKey: "elevenlabs_key",
+              voiceId: "pMsXgVXv3BLzUgSXRplE",
+              modelId: "eleven_multilingual_v2"
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+Override only the OpenAI model for calls (deep‑merge example):
+
+```json5
+{
+  plugins: {
+    entries: {
+      "voice-call": {
+        config: {
+          tts: {
+            openai: {
+              model: "gpt-4o-mini-tts",
+              voice: "marin"
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
 
 ## Inbound calls
 
@@ -124,13 +208,13 @@ Auto-responses use the agent system. Tune with:
 ## CLI
 
 ```bash
-pigbot voicecall call --to "+15555550123" --message "Hello from Pigbot"
-pigbot voicecall continue --call-id <id> --message "Any questions?"
-pigbot voicecall speak --call-id <id> --message "One moment"
-pigbot voicecall end --call-id <id>
-pigbot voicecall status --call-id <id>
-pigbot voicecall tail
-pigbot voicecall expose --mode funnel
+moltbot voicecall call --to "+15555550123" --message "Hello from Moltbot"
+moltbot voicecall continue --call-id <id> --message "Any questions?"
+moltbot voicecall speak --call-id <id> --message "One moment"
+moltbot voicecall end --call-id <id>
+moltbot voicecall status --call-id <id>
+moltbot voicecall tail
+moltbot voicecall expose --mode funnel
 ```
 
 ## Agent tool

package/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 Pigbot
+  - You want Zalo Personal (unofficial) support in Moltbot
   - You are configuring or developing the zalouser plugin
 ---
 
 # Zalo Personal (plugin)
 
-Zalo Personal support for Pigbot 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
-pigbot plugins install @pigbot/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
-pigbot 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
-pigbot channels login --channel zalouser
-pigbot channels logout --channel zalouser
-pigbot channels status --probe
-pigbot message send --channel zalouser --target <threadId> --message "Hello from Pigbot"
-pigbot 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 <threadId> --message "Hello from Moltbot"
+moltbot directory peers list --channel zalouser --query "name"
 ```
 
 ## Agent tool

package/docs/prose.md

@@ -1,5 +1,5 @@
 ---
-summary: "OpenProse: .prose workflows, slash commands, and state in Pigbot"
+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 Pigbot 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
-pigbot plugins enable open-prose
+moltbot plugins enable open-prose
 ```
 
 Restart the Gateway after enabling the plugin.
 
-Dev/local checkout: `pigbot 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 Pigbot 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 <handle/slug>` resolves to `https://p.prose.md/<handle>/<slug>`.
 Direct URLs are fetched as-is. This uses the `web_fetch` tool (or `exec` for POST).
 
-## Pigbot runtime mapping
+## Moltbot runtime mapping
 
-OpenProse programs map to Pigbot primitives:
+OpenProse programs map to Moltbot primitives:
 
-| OpenProse concept | Pigbot 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 Pigbot 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).