@gguf/pigbot 0.0.1 → 0.0.3

package/docs/concepts/agent-workspace.md

@@ -9,7 +9,7 @@ read_when:
 The workspace is the agent's home. It is the only working directory used for
 file tools and for workspace context. Keep it private and treat it as memory.
 
-This is separate from `~/.pigbot/`, which stores config, credentials, and
+This is separate from `~/.clawdbot/`, which stores config, credentials, and
 sessions.
 
 **Important:** the workspace is the **default cwd**, not a hard sandbox. Tools
@@ -17,14 +17,14 @@ resolve relative paths against the workspace, but absolute paths can still reach
 elsewhere on the host unless sandboxing is enabled. If you need isolation, use
 [`agents.defaults.sandbox`](/gateway/sandboxing) (and/or per‑agent sandbox config).
 When sandboxing is enabled and `workspaceAccess` is not `"rw"`, tools operate
-inside a sandbox workspace under `~/.pigbot/sandboxes`, not your host workspace.
+inside a sandbox workspace under `~/.clawdbot/sandboxes`, not your host workspace.
 
 ## Default location
 
 - Default: `~/clawd`
-- If `PIGBOT_PROFILE` is set and not `"default"`, the default becomes
+- If `CLAWDBOT_PROFILE` is set and not `"default"`, the default becomes
   `~/clawd-<profile>`.
-- Override in `~/.pigbot/pigbot.json`:
+- Override in `~/.clawdbot/moltbot.json`:
 
 ```json5
 {
@@ -34,7 +34,7 @@ inside a sandbox workspace under `~/.pigbot/sandboxes`, not your host workspace.
 }
 ```
 
-`pigbot onboard`, `pigbot configure`, or `pigbot setup` will create the
+`moltbot onboard`, `moltbot configure`, or `moltbot setup` will create the
 workspace and seed the bootstrap files if they are missing.
 
 If you already manage the workspace files yourself, you can disable bootstrap
@@ -46,20 +46,20 @@ file creation:
 
 ## Extra workspace folders
 
-Older installs may have created `~/pigbot`. Keeping multiple workspace
+Older installs may have created `~/moltbot`. Keeping multiple workspace
 directories around can cause confusing auth or state drift, because only one
 workspace is active at a time.
 
 **Recommendation:** keep a single active workspace. If you no longer use the
-extra folders, archive or move them to Trash (for example `trash ~/pigbot`).
+extra folders, archive or move them to Trash (for example `trash ~/moltbot`).
 If you intentionally keep multiple workspaces, make sure
 `agents.defaults.workspace` points to the active one.
 
-`pigbot doctor` warns when it detects extra workspace directories.
+`moltbot doctor` warns when it detects extra workspace directories.
 
 ## Workspace file map (what each file means)
 
-These are the standard files Pigbot expects inside the workspace:
+These are the standard files Moltbot expects inside the workspace:
 
 - `AGENTS.md`
   - Operating instructions for the agent and how it should use memory.
@@ -112,20 +112,20 @@ See [Memory](/concepts/memory) for the workflow and automatic memory flush.
 - `canvas/` (optional)
   - Canvas UI files for node displays (for example `canvas/index.html`).
 
-If any bootstrap file is missing, Pigbot injects a "missing file" marker into
+If any bootstrap file is missing, Moltbot injects a "missing file" marker into
 the session and continues. Large bootstrap files are truncated when injected;
 adjust the limit with `agents.defaults.bootstrapMaxChars` (default: 20000).
-`pigbot setup` can recreate missing defaults without overwriting existing
+`moltbot setup` can recreate missing defaults without overwriting existing
 files.
 
 ## What is NOT in the workspace
 
-These live under `~/.pigbot/` and should NOT be committed to the workspace repo:
+These live under `~/.clawdbot/` and should NOT be committed to the workspace repo:
 
-- `~/.pigbot/pigbot.json` (config)
-- `~/.pigbot/credentials/` (OAuth tokens, API keys)
-- `~/.pigbot/agents/<agentId>/sessions/` (session transcripts + metadata)
-- `~/.pigbot/skills/` (managed skills)
+- `~/.clawdbot/moltbot.json` (config)
+- `~/.clawdbot/credentials/` (OAuth tokens, API keys)
+- `~/.clawdbot/agents/<agentId>/sessions/` (session transcripts + metadata)
+- `~/.clawdbot/skills/` (managed skills)
 
 If you need to migrate sessions or config, copy them separately and keep them
 out of version control.
@@ -199,11 +199,11 @@ git push
 Even in a private repo, avoid storing secrets in the workspace:
 
 - API keys, OAuth tokens, passwords, or private credentials.
-- Anything under `~/.pigbot/`.
+- Anything under `~/.clawdbot/`.
 - Raw dumps of chats or sensitive attachments.
 
 If you must store sensitive references, use placeholders and keep the real
-secret elsewhere (password manager, environment variables, or `~/.pigbot/`).
+secret elsewhere (password manager, environment variables, or `~/.clawdbot/`).
 
 Suggested `.gitignore` starter:
 
@@ -218,9 +218,9 @@ Suggested `.gitignore` starter:
 ## Moving the workspace to a new machine
 
 1. Clone the repo to the desired path (default `~/clawd`).
-2. Set `agents.defaults.workspace` to that path in `~/.pigbot/pigbot.json`.
-3. Run `pigbot setup --workspace <path>` to seed any missing files.
-4. If you need sessions, copy `~/.pigbot/agents/<agentId>/sessions/` from the
+2. Set `agents.defaults.workspace` to that path in `~/.clawdbot/moltbot.json`.
+3. Run `moltbot setup --workspace <path>` to seed any missing files.
+4. If you need sessions, copy `~/.clawdbot/agents/<agentId>/sessions/` from the
    old machine separately.
 
 ## Advanced notes

package/docs/concepts/agent.md

@@ -5,13 +5,13 @@ read_when:
 ---
 # Agent Runtime 🤖
 
-Pigbot runs a single embedded agent runtime derived from **p-mono**.
+Moltbot runs a single embedded agent runtime derived from **p-mono**.
 
 ## Workspace (required)
 
-Pigbot uses a single agent workspace directory (`agents.defaults.workspace`) as the agent’s **only** working directory (`cwd`) for tools and context.
+Moltbot uses a single agent workspace directory (`agents.defaults.workspace`) as the agent’s **only** working directory (`cwd`) for tools and context.
 
-Recommended: use `pigbot setup` to create `~/.pigbot/pigbot.json` if missing and initialize the workspace files.
+Recommended: use `moltbot setup` to create `~/.clawdbot/moltbot.json` if missing and initialize the workspace files.
 
 Full workspace layout + backup guide: [Agent workspace](/concepts/agent-workspace)
 
@@ -21,7 +21,7 @@ per-session workspaces under `agents.defaults.sandbox.workspaceRoot` (see
 
 ## Bootstrap files (injected)
 
-Inside `agents.defaults.workspace`, Pigbot expects these user-editable files:
+Inside `agents.defaults.workspace`, Moltbot expects these user-editable files:
 - `AGENTS.md` — operating instructions + “memory”
 - `SOUL.md` — persona, boundaries, tone
 - `TOOLS.md` — user-maintained tool notes (e.g. `imsg`, `sag`, conventions)
@@ -29,11 +29,11 @@ Inside `agents.defaults.workspace`, Pigbot expects these user-editable files:
 - `IDENTITY.md` — agent name/vibe/emoji
 - `USER.md` — user profile + preferred address
 
-On the first turn of a new session, Pigbot injects the contents of these files directly into the agent context.
+On the first turn of a new session, Moltbot injects the contents of these files directly into the agent context.
 
 Blank files are skipped. Large files are trimmed and truncated with a marker so prompts stay lean (read the file for full content).
 
-If a file is missing, Pigbot injects a single “missing file” marker line (and `pigbot setup` will create a safe default template).
+If a file is missing, Moltbot injects a single “missing file” marker line (and `moltbot setup` will create a safe default template).
 
 `BOOTSTRAP.md` is only created for a **brand new workspace** (no other bootstrap files present). If you delete it after completing the ritual, it should not be recreated on later restarts.
 
@@ -52,16 +52,16 @@ guidance for how *you* want them used.
 
 ## Skills
 
-Pigbot loads skills from three locations (workspace wins on name conflict):
+Moltbot loads skills from three locations (workspace wins on name conflict):
 - Bundled (shipped with the install)
-- Managed/local: `~/.pigbot/skills`
+- Managed/local: `~/.clawdbot/skills`
 - Workspace: `<workspace>/skills`
 
 Skills can be gated by config/env (see `skills` in [Gateway configuration](/gateway/configuration)).
 
 ## p-mono integration
 
-Pigbot reuses pieces of the p-mono codebase (models/tools), but **session management, discovery, and tool wiring are Pigbot-owned**.
+Moltbot reuses pieces of the p-mono codebase (models/tools), but **session management, discovery, and tool wiring are Moltbot-owned**.
 
 - No p-coding agent runtime.
 - No `~/.pi/agent` or `<workspace>/.pi` settings are consulted.
@@ -69,9 +69,9 @@ Pigbot reuses pieces of the p-mono codebase (models/tools), but **session manage
 ## Sessions
 
 Session transcripts are stored as JSONL at:
-- `~/.pigbot/agents/<agentId>/sessions/<SessionId>.jsonl`
+- `~/.clawdbot/agents/<agentId>/sessions/<SessionId>.jsonl`
 
-The session ID is stable and chosen by Pigbot.
+The session ID is stable and chosen by Moltbot.
 Legacy Pi/Tau session folders are **not** read.
 
 ## Steering while streaming
@@ -104,7 +104,7 @@ Model refs in config (for example `agents.defaults.model` and `agents.defaults.m
 
 - Use `provider/model` when configuring models.
 - If the model ID itself contains `/` (OpenRouter-style), include the provider prefix (example: `openrouter/moonshotai/kimi-k2`).
-- If you omit the provider, Pigbot treats the input as an alias or a model for the **default provider** (only works when there is no `/` in the model ID).
+- If you omit the provider, Moltbot treats the input as an alias or a model for the **default provider** (only works when there is no `/` in the model ID).
 
 ## Configuration (minimal)
 

package/docs/concepts/architecture.md

@@ -72,7 +72,7 @@ Client                    Gateway
 - After handshake:
   - Requests: `{type:"req", id, method, params}` → `{type:"res", id, ok, payload|error}`
   - Events: `{type:"event", event, payload, seq?, stateVersion?}`
-- If `PIGBOT_GATEWAY_TOKEN` (or `--token`) is set, `connect.params.auth.token`
+- If `CLAWDBOT_GATEWAY_TOKEN` (or `--token`) is set, `connect.params.auth.token`
   must match or the socket closes.
 - Idempotency keys are required for side‑effecting methods (`send`, `agent`) to
   safely retry; the server keeps a short‑lived dedupe cache.
@@ -111,7 +111,7 @@ Details: [Gateway protocol](/gateway/protocol), [Pairing](/start/pairing),
 
 ## Operations snapshot
 
-- Start: `pigbot gateway` (foreground, logs to stdout).
+- Start: `moltbot gateway` (foreground, logs to stdout).
 - Health: `health` over WS (also included in `hello-ok`).
 - Supervision: launchd/systemd for auto‑restart.
 

package/docs/concepts/channel-routing.md

@@ -6,7 +6,7 @@ read_when:
 # Channels & routing
 
 
-Pigbot routes replies **back to the channel where a message came from**. The
+Moltbot routes replies **back to the channel where a message came from**. The
 model does not choose a channel; routing is deterministic and controlled by the
 host configuration.
 
@@ -53,7 +53,7 @@ The matched agent determines which workspace and session store are used.
 
 ## Broadcast groups (run multiple agents)
 
-Broadcast groups let you run **multiple agents** for the same peer **when Pigbot would normally reply** (for example: in WhatsApp groups, after mention/activation gating).
+Broadcast groups let you run **multiple agents** for the same peer **when Moltbot would normally reply** (for example: in WhatsApp groups, after mention/activation gating).
 
 Config:
 
@@ -92,9 +92,9 @@ Example:
 
 ## Session storage
 
-Session stores live under the state directory (default `~/.pigbot`):
+Session stores live under the state directory (default `~/.clawdbot`):
 
-- `~/.pigbot/agents/<agentId>/sessions/sessions.json`
+- `~/.clawdbot/agents/<agentId>/sessions/sessions.json`
 - JSONL transcripts live alongside the store
 
 You can override the store path via `session.store` and `{agentId}` templating.

package/docs/concepts/compaction.md

@@ -1,12 +1,12 @@
 ---
-summary: "Context window + compaction: how Pigbot keeps sessions under model limits"
+summary: "Context window + compaction: how Moltbot keeps sessions under model limits"
 read_when:
   - You want to understand auto-compaction and /compact
   - You are debugging long sessions hitting context limits
 ---
 # Context Window & Compaction
 
-Every model has a **context window** (max tokens it can see). Long-running chats accumulate messages and tool results; once the window is tight, Pigbot **compacts** older history to stay within limits.
+Every model has a **context window** (max tokens it can see). Long-running chats accumulate messages and tool results; once the window is tight, Moltbot **compacts** older history to stay within limits.
 
 ## What compaction is
 Compaction **summarizes older conversation** into a compact summary entry and keeps recent messages intact. The summary is stored in the session history, so future requests use:
@@ -19,13 +19,13 @@ Compaction **persists** in the session’s JSONL history.
 See [Compaction config & modes](/concepts/compaction) for the `agents.defaults.compaction` settings.
 
 ## Auto-compaction (default on)
-When a session nears or exceeds the model’s context window, Pigbot triggers auto-compaction and may retry the original request using the compacted context.
+When a session nears or exceeds the model’s context window, Moltbot triggers auto-compaction and may retry the original request using the compacted context.
 
 You’ll see:
 - `🧹 Auto-compaction complete` in verbose mode
 - `/status` showing `🧹 Compactions: <count>`
 
-Before compaction, Pigbot can run a **silent memory flush** turn to store
+Before compaction, Moltbot can run a **silent memory flush** turn to store
 durable notes to disk. See [Memory](/concepts/memory) for details and config.
 
 ## Manual compaction
@@ -35,7 +35,7 @@ Use `/compact` (optionally with instructions) to force a compaction pass:
 ```
 
 ## Context window source
-Context window is model-specific. Pigbot uses the model definition from the configured provider catalog to determine limits.
+Context window is model-specific. Moltbot uses the model definition from the configured provider catalog to determine limits.
 
 ## Compaction vs pruning
 - **Compaction**: summarises and **persists** in JSONL.

package/docs/concepts/context.md

@@ -1,16 +1,16 @@
 ---
 summary: "Context: what the model sees, how it is built, and how to inspect it"
 read_when:
-  - You want to understand what “context” means in Pigbot
+  - You want to understand what “context” means in Moltbot
   - You are debugging why the model “knows” something (or forgot it)
   - You want to reduce context overhead (/context, /status, /compact)
 ---
 # Context
 
-“Context” is **everything Pigbot sends to the model for a run**. It is bounded by the model’s **context window** (token limit).
+“Context” is **everything Moltbot sends to the model for a run**. It is bounded by the model’s **context window** (token limit).
 
 Beginner mental model:
-- **System prompt** (Pigbot-built): rules, tools, skills list, time/runtime, and injected workspace files.
+- **System prompt** (Moltbot-built): rules, tools, skills list, time/runtime, and injected workspace files.
 - **Conversation history**: your messages + the assistant’s messages for this session.
 - **Tool calls/results + attachments**: command output, file reads, images/audio, etc.
 
@@ -83,9 +83,9 @@ Everything the model receives counts, including:
 - Compaction summaries and pruning artifacts.
 - Provider “wrappers” or hidden headers (not visible, still counted).
 
-## How Pigbot builds the system prompt
+## How Moltbot builds the system prompt
 
-The system prompt is **Pigbot-owned** and rebuilt each run. It includes:
+The system prompt is **Moltbot-owned** and rebuilt each run. It includes:
 - Tool list + short descriptions.
 - Skills list (metadata only; see below).
 - Workspace location.
@@ -97,7 +97,7 @@ Full breakdown: [System Prompt](/concepts/system-prompt).
 
 ## Injected workspace files (Project Context)
 
-By default, Pigbot injects a fixed set of workspace files (if present):
+By default, Moltbot injects a fixed set of workspace files (if present):
 - `AGENTS.md`
 - `SOUL.md`
 - `TOOLS.md`

package/docs/concepts/group-messages.md

@@ -19,7 +19,7 @@ Note: `agents.list[].groupChat.mentionPatterns` is now used by Telegram/Discord/
 - Group system prompt: on the first turn of a group session (and whenever `/activation` changes the mode) we inject a short blurb into the system prompt like `You are replying inside the WhatsApp group "<subject>". Group members: Alice (+44...), Bob (+43...), … Activation: trigger-only … Address the specific sender noted in the message context.` If metadata isn’t available we still tell the agent it’s a group chat.
 
 ## Config example (WhatsApp)
-Add a `groupChat` block to `~/.pigbot/pigbot.json` so display-name pings work even when WhatsApp strips the visual `@` in the text body:
+Add a `groupChat` block to `~/.clawdbot/moltbot.json` so display-name pings work even when WhatsApp strips the visual `@` in the text body:
 
 ```json5
 {
@@ -37,7 +37,7 @@ Add a `groupChat` block to `~/.pigbot/pigbot.json` so display-name pings work ev
         groupChat: {
           historyLimit: 50,
           mentionPatterns: [
-            "@?pigbot",
+            "@?moltbot",
             "\\+?15555550123"
           ]
         }
@@ -48,7 +48,7 @@ Add a `groupChat` block to `~/.pigbot/pigbot.json` so display-name pings work ev
 ```
 
 Notes:
-- The regexes are case-insensitive; they cover a display-name ping like `@pigbot` and the raw number with or without `+`/spaces.
+- The regexes are case-insensitive; they cover a display-name ping like `@moltbot` and the raw number with or without `+`/spaces.
 - WhatsApp still sends canonical mentions via `mentionedJids` when someone taps the contact, so the number fallback is rarely needed but is a useful safety net.
 
 ### Activation command (owner-only)
@@ -60,8 +60,8 @@ Use the group chat command:
 Only the owner number (from `channels.whatsapp.allowFrom`, or the bot’s own E.164 when unset) can change this. Send `/status` as a standalone message in the group to see the current activation mode.
 
 ## How to use
-1) Add your WhatsApp account (the one running Pigbot) to the group.
-2) Say `@pigbot …` (or include the number). Only allowlisted senders can trigger it unless you set `groupPolicy: "open"`.
+1) Add your WhatsApp account (the one running Moltbot) to the group.
+2) Say `@moltbot …` (or include the number). Only allowlisted senders can trigger it unless you set `groupPolicy: "open"`.
 3) The agent prompt will include recent group context plus the trailing `[from: …]` marker so it can address the right person.
 4) Session-level directives (`/verbose on`, `/think high`, `/new` or `/reset`, `/compact`) apply only to that group’s session; send them as standalone messages so they register. Your personal DM session remains independent.
 
@@ -74,5 +74,5 @@ Only the owner number (from `channels.whatsapp.allowFrom`, or the bot’s own E.
 ## Known considerations
 - Heartbeats are intentionally skipped for groups to avoid noisy broadcasts.
 - Echo suppression uses the combined batch string; if you send identical text twice without mentions, only the first will get a response.
-- Session store entries will appear as `agent:<agentId>:whatsapp:group:<jid>` in the session store (`~/.pigbot/agents/<agentId>/sessions/sessions.json` by default); a missing entry just means the group hasn’t triggered a run yet.
+- Session store entries will appear as `agent:<agentId>:whatsapp:group:<jid>` in the session store (`~/.clawdbot/agents/<agentId>/sessions/sessions.json` by default); a missing entry just means the group hasn’t triggered a run yet.
 - Typing indicators in groups follow `agents.defaults.typingMode` (default: `message` when unmentioned).

package/docs/concepts/groups.md

@@ -5,17 +5,17 @@ read_when:
 ---
 # Groups
 
-Pigbot treats group chats consistently across surfaces: WhatsApp, Telegram, Discord, Slack, Signal, iMessage, Microsoft Teams.
+Moltbot treats group chats consistently across surfaces: WhatsApp, Telegram, Discord, Slack, Signal, iMessage, Microsoft Teams.
 
 ## Beginner intro (2 minutes)
-Pigbot “lives” on your own messaging accounts. There is no separate WhatsApp bot user.
-If **you** are in a group, Pigbot can see that group and respond there.
+Moltbot “lives” on your own messaging accounts. There is no separate WhatsApp bot user.
+If **you** are in a group, Moltbot can see that group and respond there.
 
 Default behavior:
 - Groups are restricted (`groupPolicy: "allowlist"`).
 - Replies require a mention unless you explicitly disable mention gating.
 
-Translation: allowlisted senders can trigger Pigbot by mentioning it.
+Translation: allowlisted senders can trigger Moltbot by mentioning it.
 
 > TL;DR
 > - **DM access** is controlled by `*.allowFrom`.
@@ -215,7 +215,7 @@ Replying to a bot message counts as an implicit mention (when the channel suppor
       {
         id: "main",
         groupChat: {
-          mentionPatterns: ["@clawd", "pigbot", "\\+15555550123"],
+          mentionPatterns: ["@clawd", "moltbot", "\\+15555550123"],
           historyLimit: 50
         }
       }
@@ -232,6 +232,42 @@ Notes:
 - Discord defaults live in `channels.discord.guilds."*"` (overridable per guild/channel).
 - Group history context is wrapped uniformly across channels and is **pending-only** (messages skipped due to mention gating); use `messages.groupChat.historyLimit` for the global default and `channels.<channel>.historyLimit` (or `channels.<channel>.accounts.*.historyLimit`) for overrides. Set `0` to disable.
 
+## Group/channel tool restrictions (optional)
+Some channel configs support restricting which tools are available **inside a specific group/room/channel**.
+
+- `tools`: allow/deny tools for the whole group.
+- `toolsBySender`: per-sender overrides within the group (keys are sender IDs/usernames/emails/phone numbers depending on the channel). Use `"*"` as a wildcard.
+
+Resolution order (most specific wins):
+1) group/channel `toolsBySender` match
+2) group/channel `tools`
+3) default (`"*"`) `toolsBySender` match
+4) default (`"*"`) `tools`
+
+Example (Telegram):
+
+```json5
+{
+  channels: {
+    telegram: {
+      groups: {
+        "*": { tools: { deny: ["exec"] } },
+        "-1001234567890": {
+          tools: { deny: ["exec", "read", "write"] },
+          toolsBySender: {
+            "123456789": { alsoAllow: ["exec"] }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+Notes:
+- Group/channel tool restrictions are applied in addition to global/agent tool policy (deny still wins).
+- Some channels use different nesting for rooms/channels (e.g., Discord `guilds.*.channels.*`, Slack `channels.*`, MS Teams `teams.*.channels.*`).
+
 ## Group allowlists
 When `channels.whatsapp.groups`, `channels.telegram.groups`, or `channels.imessage.groups` is configured, the keys act as a group allowlist. Use `"*"` to allow all groups while still setting default mention behavior.
 

package/docs/concepts/markdown-formatting.md

@@ -7,7 +7,7 @@ read_when:
 ---
 # Markdown formatting
 
-Pigbot formats outbound Markdown by converting it into a shared intermediate
+Moltbot formats outbound Markdown by converting it into a shared intermediate
 representation (IR) before rendering channel-specific output. The IR keeps the
 source text intact while carrying style/link spans so chunking and rendering can
 stay consistent across channels.
@@ -39,7 +39,7 @@ stay consistent across channels.
 Input Markdown:
 
 ```markdown
-Hello **world** — see [docs](https://docs.clawd.bot).
+Hello **world** — see [docs](https://docs.molt.bot).
 ```
 
 IR (schematic):
@@ -51,7 +51,7 @@ IR (schematic):
     { "start": 6, "end": 11, "style": "bold" }
   ],
   "links": [
-    { "start": 19, "end": 23, "href": "https://docs.clawd.bot" }
+    { "start": 19, "end": 23, "href": "https://docs.molt.bot" }
   ]
 }
 ```

package/docs/concepts/memory.md

@@ -1,12 +1,12 @@
 ---
-summary: "How Pigbot memory works (workspace files + automatic memory flush)"
+summary: "How Moltbot memory works (workspace files + automatic memory flush)"
 read_when:
   - You want the memory file layout and workflow
   - You want to tune the automatic pre-compaction memory flush
 ---
 # Memory
 
-Pigbot memory is **plain Markdown in the agent workspace**. The files are the
+Moltbot memory is **plain Markdown in the agent workspace**. The files are the
 source of truth; the model only "remembers" what gets written to disk.
 
 Memory search tools are provided by the active memory plugin (default:
@@ -36,7 +36,7 @@ These files live under the workspace (`agents.defaults.workspace`, default
 
 ## Automatic memory flush (pre-compaction ping)
 
-When a session is **close to auto-compaction**, Pigbot triggers a **silent,
+When a session is **close to auto-compaction**, Moltbot triggers a **silent,
 agentic turn** that reminds the model to write durable memory **before** the
 context is compacted. The default prompts explicitly say the model *may reply*,
 but usually `NO_REPLY` is the correct response so the user never sees this turn.
@@ -75,13 +75,13 @@ For the full compaction lifecycle, see
 
 ## Vector memory search
 
-Pigbot can build a small vector index over `MEMORY.md` and `memory/*.md` so
+Moltbot can build a small vector index over `MEMORY.md` and `memory/*.md` so
 semantic queries can find related notes even when wording differs.
 
 Defaults:
 - Enabled by default.
 - Watches memory files for changes (debounced).
-- Uses remote embeddings by default. If `memorySearch.provider` is not set, Pigbot auto-selects:
+- Uses remote embeddings by default. If `memorySearch.provider` is not set, Moltbot auto-selects:
   1. `local` if a `memorySearch.local.modelPath` is configured and the file exists.
   2. `openai` if an OpenAI key can be resolved.
   3. `gemini` if a Gemini key can be resolved.
@@ -89,7 +89,7 @@ Defaults:
 - Local mode uses node-llama-cpp and may require `pnpm approve-builds`.
 - Uses sqlite-vec (when available) to accelerate vector search inside SQLite.
 
-Remote embeddings **require** an API key for the embedding provider. Pigbot
+Remote embeddings **require** an API key for the embedding provider. Moltbot
 resolves keys from auth profiles, `models.providers.*.apiKey`, or environment
 variables. Codex OAuth only covers chat/completions and does **not** satisfy
 embeddings for memory search. For Gemini, use `GEMINI_API_KEY` or
@@ -195,17 +195,17 @@ Local mode:
 ### What gets indexed (and when)
 
 - File type: Markdown only (`MEMORY.md`, `memory/**/*.md`).
-- Index storage: per-agent SQLite at `~/.pigbot/memory/<agentId>.sqlite` (configurable via `agents.defaults.memorySearch.store.path`, supports `{agentId}` token).
+- Index storage: per-agent SQLite at `~/.clawdbot/memory/<agentId>.sqlite` (configurable via `agents.defaults.memorySearch.store.path`, supports `{agentId}` token).
 - Freshness: watcher on `MEMORY.md` + `memory/` marks the index dirty (debounce 1.5s). Sync is scheduled on session start, on search, or on an interval and runs asynchronously. Session transcripts use delta thresholds to trigger background sync.
-- Reindex triggers: the index stores the embedding **provider/model + endpoint fingerprint + chunking params**. If any of those change, Pigbot automatically resets and reindexes the entire store.
+- Reindex triggers: the index stores the embedding **provider/model + endpoint fingerprint + chunking params**. If any of those change, Moltbot automatically resets and reindexes the entire store.
 
 ### Hybrid search (BM25 + vector)
 
-When enabled, Pigbot combines:
+When enabled, Moltbot combines:
 - **Vector similarity** (semantic match, wording can differ)
 - **BM25 keyword relevance** (exact tokens like IDs, env vars, code symbols)
 
-If full-text search is unavailable on your platform, Pigbot falls back to vector-only search.
+If full-text search is unavailable on your platform, Moltbot falls back to vector-only search.
 
 #### Why hybrid?
 
@@ -266,7 +266,7 @@ agents: {
 
 ### Embedding cache
 
-Pigbot can cache **chunk embeddings** in SQLite so reindexing and frequent updates (especially session transcripts) don't re-embed unchanged text.
+Moltbot can cache **chunk embeddings** in SQLite so reindexing and frequent updates (especially session transcripts) don't re-embed unchanged text.
 
 Config:
 
@@ -305,7 +305,7 @@ Notes:
 - `memory_search` never blocks on indexing; results can be slightly stale until background sync finishes.
 - Results still include snippets only; `memory_get` remains limited to memory files.
 - Session indexing is isolated per agent (only that agent’s session logs are indexed).
-- Session logs live on disk (`~/.pigbot/agents/<agentId>/sessions/*.jsonl`). Any process/user with filesystem access can read them, so treat disk access as the trust boundary. For stricter isolation, run agents under separate OS users or hosts.
+- Session logs live on disk (`~/.clawdbot/agents/<agentId>/sessions/*.jsonl`). Any process/user with filesystem access can read them, so treat disk access as the trust boundary. For stricter isolation, run agents under separate OS users or hosts.
 
 Delta thresholds (defaults shown):
 
@@ -326,7 +326,7 @@ agents: {
 
 ### SQLite vector acceleration (sqlite-vec)
 
-When the sqlite-vec extension is available, Pigbot stores embeddings in a
+When the sqlite-vec extension is available, Moltbot stores embeddings in a
 SQLite virtual table (`vec0`) and performs vector distance queries in the
 database. This keeps search fast without loading every embedding into JS.
 
@@ -350,7 +350,7 @@ agents: {
 Notes:
 - `enabled` defaults to true; when disabled, search falls back to in-process
   cosine similarity over stored embeddings.
-- If the sqlite-vec extension is missing or fails to load, Pigbot logs the
+- If the sqlite-vec extension is missing or fails to load, Moltbot logs the
   error and continues with the JS fallback (no vector table).
 - `extensionPath` overrides the bundled sqlite-vec path (useful for custom builds
   or non-standard install locations).

package/docs/concepts/messages.md

@@ -7,7 +7,7 @@ read_when:
 ---
 # Messages
 
-This page ties together how Pigbot handles inbound messages, sessions, queueing,
+This page ties together how Moltbot handles inbound messages, sessions, queueing,
 streaming, and reasoning visibility.
 
 ## Message flow (high level)
@@ -29,7 +29,7 @@ See [Configuration](/gateway/configuration) for full schema.
 
 ## Inbound dedupe
 
-Channels can redeliver the same message after reconnects. Pigbot keeps a
+Channels can redeliver the same message after reconnects. Moltbot keeps a
 short-lived cache keyed by channel/account/peer/session/message id so duplicate
 deliveries do not trigger another agent run.
 
@@ -75,7 +75,7 @@ Details: [Session management](/concepts/session).
 
 ## Inbound bodies and history context
 
-Pigbot separates the **prompt body** from the **command body**:
+Moltbot separates the **prompt body** from the **command body**:
 - `Body`: prompt text sent to the agent. This may include channel envelopes and
   optional history wrappers.
 - `CommandBody`: raw user text for directive/command parsing.
@@ -127,7 +127,7 @@ Details: [Streaming + chunking](/concepts/streaming).
 
 ## Reasoning visibility and tokens
 
-Pigbot can expose or hide model reasoning:
+Moltbot can expose or hide model reasoning:
 - `/reasoning on|off|stream` controls visibility.
 - Reasoning content still counts toward token usage when produced by the model.
 - Telegram supports reasoning stream into the draft bubble.