@gguf/pigbot 0.0.1 → 0.0.3

package/docs/concepts/model-failover.md

@@ -1,5 +1,5 @@
 ---
-summary: "How Pigbot rotates auth profiles and falls back across models"
+summary: "How Moltbot rotates auth profiles and falls back across models"
 read_when:
   - Diagnosing auth profile rotation, cooldowns, or model fallback behavior
   - Updating failover rules for auth profiles or models
@@ -7,7 +7,7 @@ read_when:
 
 # Model failover
 
-Pigbot handles failures in two stages:
+Moltbot handles failures in two stages:
 1) **Auth profile rotation** within the current provider.
 2) **Model fallback** to the next model in `agents.defaults.model.fallbacks`.
 
@@ -15,11 +15,11 @@ This doc explains the runtime rules and the data that backs them.
 
 ## Auth storage (keys + OAuth)
 
-Pigbot uses **auth profiles** for both API keys and OAuth tokens.
+Moltbot uses **auth profiles** for both API keys and OAuth tokens.
 
-- Secrets live in `~/.pigbot/agents/<agentId>/agent/auth-profiles.json` (legacy: `~/.pigbot/agent/auth-profiles.json`).
+- Secrets live in `~/.clawdbot/agents/<agentId>/agent/auth-profiles.json` (legacy: `~/.clawdbot/agent/auth-profiles.json`).
 - Config `auth.profiles` / `auth.order` are **metadata + routing only** (no secrets).
-- Legacy import-only OAuth file: `~/.pigbot/credentials/oauth.json` (imported into `auth-profiles.json` on first use).
+- Legacy import-only OAuth file: `~/.clawdbot/credentials/oauth.json` (imported into `auth-profiles.json` on first use).
 
 More detail: [/concepts/oauth](/concepts/oauth)
 
@@ -33,24 +33,24 @@ OAuth logins create distinct profiles so multiple accounts can coexist.
 - Default: `provider:default` when no email is available.
 - OAuth with email: `provider:<email>` (for example `google-antigravity:user@gmail.com`).
 
-Profiles live in `~/.pigbot/agents/<agentId>/agent/auth-profiles.json` under `profiles`.
+Profiles live in `~/.clawdbot/agents/<agentId>/agent/auth-profiles.json` under `profiles`.
 
 ## Rotation order
 
-When a provider has multiple profiles, Pigbot chooses an order like this:
+When a provider has multiple profiles, Moltbot chooses an order like this:
 
 1) **Explicit config**: `auth.order[provider]` (if set).
 2) **Configured profiles**: `auth.profiles` filtered by provider.
 3) **Stored profiles**: entries in `auth-profiles.json` for the provider.
 
-If no explicit order is configured, Pigbot uses a round‑robin order:
+If no explicit order is configured, Moltbot uses a round‑robin order:
 - **Primary key:** profile type (**OAuth before API keys**).
 - **Secondary key:** `usageStats.lastUsed` (oldest first, within each type).
 - **Cooldown/disabled profiles** are moved to the end, ordered by soonest expiry.
 
 ### Session stickiness (cache-friendly)
 
-Pigbot **pins the chosen auth profile per session** to keep provider caches warm.
+Moltbot **pins the chosen auth profile per session** to keep provider caches warm.
 It does **not** rotate on every request. The pinned profile is reused until:
 - the session is reset (`/new` / `/reset`)
 - a compaction completes (compaction count increments)
@@ -60,9 +60,9 @@ Manual selection via `/model …@<profileId>` sets a **user override** for that
 and is not auto‑rotated until a new session starts.
 
 Auto‑pinned profiles (selected by the session router) are treated as a **preference**:
-they are tried first, but Pigbot may rotate to another profile on rate limits/timeouts.
+they are tried first, but Moltbot may rotate to another profile on rate limits/timeouts.
 User‑pinned profiles stay locked to that profile; if it fails and model fallbacks
-are configured, Pigbot moves to the next model instead of switching profiles.
+are configured, Moltbot moves to the next model instead of switching profiles.
 
 ### Why OAuth can “look lost”
 
@@ -73,7 +73,7 @@ If you have both an OAuth profile and an API key profile for the same provider,
 ## Cooldowns
 
 When a profile fails due to auth/rate‑limit errors (or a timeout that looks
-like rate limiting), Pigbot marks it in cooldown and moves to the next profile.
+like rate limiting), Moltbot marks it in cooldown and moves to the next profile.
 Format/invalid‑request errors (for example Cloud Code Assist tool call ID
 validation failures) are treated as failover‑worthy and use the same cooldowns.
 
@@ -99,7 +99,7 @@ State is stored in `auth-profiles.json` under `usageStats`:
 
 ## Billing disables
 
-Billing/credit failures (for example “insufficient credits” / “credit balance too low”) are treated as failover‑worthy, but they’re usually not transient. Instead of a short cooldown, Pigbot marks the profile as **disabled** (with a longer backoff) and rotates to the next profile/provider.
+Billing/credit failures (for example “insufficient credits” / “credit balance too low”) are treated as failover‑worthy, but they’re usually not transient. Instead of a short cooldown, Moltbot marks the profile as **disabled** (with a longer backoff) and rotates to the next profile/provider.
 
 State is stored in `auth-profiles.json`:
 
@@ -120,7 +120,7 @@ Defaults:
 
 ## Model fallback
 
-If all profiles for a provider fail, Pigbot moves to the next model in
+If all profiles for a provider fail, Moltbot moves to the next model in
 `agents.defaults.model.fallbacks`. This applies to auth failures, rate limits, and
 timeouts that exhausted profile rotation (other errors do not advance fallback).
 

package/docs/concepts/model-providers.md

@@ -13,11 +13,11 @@ For model selection rules, see [/concepts/models](/concepts/models).
 
 - Model refs use `provider/model` (example: `opencode/claude-opus-4-5`).
 - If you set `agents.defaults.models`, it becomes the allowlist.
-- CLI helpers: `pigbot onboard`, `pigbot models list`, `pigbot models set <provider/model>`.
+- CLI helpers: `moltbot onboard`, `moltbot models list`, `moltbot models set <provider/model>`.
 
 ## Built-in providers (pi-ai catalog)
 
-Pigbot ships with the pi‑ai catalog. These providers require **no**
+Moltbot ships with the pi‑ai catalog. These providers require **no**
 `models.providers` config; just set auth + pick a model.
 
 ### OpenAI
@@ -25,7 +25,7 @@ Pigbot ships with the pi‑ai catalog. These providers require **no**
 - Provider: `openai`
 - Auth: `OPENAI_API_KEY`
 - Example model: `openai/gpt-5.2`
-- CLI: `pigbot onboard --auth-choice openai-api-key`
+- CLI: `moltbot onboard --auth-choice openai-api-key`
 
 ```json5
 {
@@ -38,7 +38,7 @@ Pigbot ships with the pi‑ai catalog. These providers require **no**
 - Provider: `anthropic`
 - Auth: `ANTHROPIC_API_KEY` or `claude setup-token`
 - Example model: `anthropic/claude-opus-4-5`
-- CLI: `pigbot onboard --auth-choice token` (paste setup-token) or `pigbot models auth paste-token --provider anthropic`
+- CLI: `moltbot onboard --auth-choice token` (paste setup-token) or `moltbot models auth paste-token --provider anthropic`
 
 ```json5
 {
@@ -49,9 +49,9 @@ Pigbot ships with the pi‑ai catalog. These providers require **no**
 ### OpenAI Code (Codex)
 
 - Provider: `openai-codex`
-- Auth: OAuth or Codex CLI (`~/.codex/auth.json`)
+- Auth: OAuth (ChatGPT)
 - Example model: `openai-codex/gpt-5.2`
-- CLI: `pigbot onboard --auth-choice openai-codex` or `codex-cli`
+- CLI: `moltbot onboard --auth-choice openai-codex` or `moltbot models auth login --provider openai-codex`
 
 ```json5
 {
@@ -64,7 +64,7 @@ Pigbot ships with the pi‑ai catalog. These providers require **no**
 - Provider: `opencode`
 - Auth: `OPENCODE_API_KEY` (or `OPENCODE_ZEN_API_KEY`)
 - Example model: `opencode/claude-opus-4-5`
-- CLI: `pigbot onboard --auth-choice opencode-zen`
+- CLI: `moltbot onboard --auth-choice opencode-zen`
 
 ```json5
 {
@@ -77,19 +77,19 @@ Pigbot ships with the pi‑ai catalog. These providers require **no**
 - Provider: `google`
 - Auth: `GEMINI_API_KEY`
 - Example model: `google/gemini-3-pro-preview`
-- CLI: `pigbot onboard --auth-choice gemini-api-key`
+- CLI: `moltbot onboard --auth-choice gemini-api-key`
 
 ### Google Vertex / Antigravity / Gemini CLI
 
 - Providers: `google-vertex`, `google-antigravity`, `google-gemini-cli`
 - Auth: Vertex uses gcloud ADC; Antigravity/Gemini CLI use their respective auth flows
 - Antigravity OAuth is shipped as a bundled plugin (`google-antigravity-auth`, disabled by default).
-  - Enable: `pigbot plugins enable google-antigravity-auth`
-  - Login: `pigbot models auth login --provider google-antigravity --set-default`
+  - Enable: `moltbot plugins enable google-antigravity-auth`
+  - Login: `moltbot models auth login --provider google-antigravity --set-default`
 - Gemini CLI OAuth is shipped as a bundled plugin (`google-gemini-cli-auth`, disabled by default).
-  - Enable: `pigbot plugins enable google-gemini-cli-auth`
-  - Login: `pigbot models auth login --provider google-gemini-cli --set-default`
-  - Note: you do **not** paste a client id or secret into `pigbot.json`. The CLI login flow stores
+  - Enable: `moltbot plugins enable google-gemini-cli-auth`
+  - Login: `moltbot models auth login --provider google-gemini-cli --set-default`
+  - Note: you do **not** paste a client id or secret into `moltbot.json`. The CLI login flow stores
     tokens in auth profiles on the gateway host.
 
 ### Z.AI (GLM)
@@ -97,7 +97,7 @@ Pigbot ships with the pi‑ai catalog. These providers require **no**
 - Provider: `zai`
 - Auth: `ZAI_API_KEY`
 - Example model: `zai/glm-4.7`
-- CLI: `pigbot onboard --auth-choice zai-api-key`
+- CLI: `moltbot onboard --auth-choice zai-api-key`
   - Aliases: `z.ai/*` and `z-ai/*` normalize to `zai/*`
 
 ### Vercel AI Gateway
@@ -105,7 +105,7 @@ Pigbot ships with the pi‑ai catalog. These providers require **no**
 - Provider: `vercel-ai-gateway`
 - Auth: `AI_GATEWAY_API_KEY`
 - Example model: `vercel-ai-gateway/anthropic/claude-opus-4.5`
-- CLI: `pigbot onboard --auth-choice ai-gateway-api-key`
+- CLI: `moltbot onboard --auth-choice ai-gateway-api-key`
 
 ### Other built-in providers
 
@@ -191,8 +191,8 @@ Qwen provides OAuth access to Qwen Coder + Vision via a device-code flow.
 Enable the bundled plugin, then log in:
 
 ```bash
-pigbot plugins enable qwen-portal-auth
-pigbot models auth login --provider qwen-portal --set-default
+moltbot plugins enable qwen-portal-auth
+moltbot models auth login --provider qwen-portal --set-default
 ```
 
 Model refs:
@@ -208,7 +208,7 @@ Synthetic provides Anthropic-compatible models behind the `synthetic` provider:
 - Provider: `synthetic`
 - Auth: `SYNTHETIC_API_KEY`
 - Example model: `synthetic/hf:MiniMaxAI/MiniMax-M2.1`
-- CLI: `pigbot onboard --auth-choice synthetic-api-key`
+- CLI: `moltbot onboard --auth-choice synthetic-api-key`
 
 ```json5
 {
@@ -299,7 +299,7 @@ Example (OpenAI‑compatible):
 
 Notes:
 - For custom providers, `reasoning`, `input`, `cost`, `contextWindow`, and `maxTokens` are optional.
-  When omitted, Pigbot defaults to:
+  When omitted, Moltbot defaults to:
   - `reasoning: false`
   - `input: ["text"]`
   - `cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 }`
@@ -310,9 +310,9 @@ Notes:
 ## CLI examples
 
 ```bash
-pigbot onboard --auth-choice opencode-zen
-pigbot models set opencode/claude-opus-4-5
-pigbot models list
+moltbot onboard --auth-choice opencode-zen
+moltbot models set opencode/claude-opus-4-5
+moltbot models list
 ```
 
 See also: [/gateway/configuration](/gateway/configuration) for full configuration examples.

package/docs/concepts/models.md

@@ -13,7 +13,7 @@ Quick provider overview + examples: [/concepts/model-providers](/concepts/model-
 
 ## How model selection works
 
-Pigbot selects models in this order:
+Moltbot selects models in this order:
 
 1) **Primary** model (`agents.defaults.model.primary` or `agents.defaults.model`).
 2) **Fallbacks** in `agents.defaults.model.fallbacks` (in order).
@@ -21,7 +21,7 @@ Pigbot selects models in this order:
    next model.
 
 Related:
-- `agents.defaults.models` is the allowlist/catalog of models Pigbot can use (plus aliases).
+- `agents.defaults.models` is the allowlist/catalog of models Moltbot can use (plus aliases).
 - `agents.defaults.imageModel` is used **only when** the primary model can’t accept images.
 - Per-agent defaults can override `agents.defaults.model` via `agents.list[].model` plus bindings (see [/concepts/multi-agent](/concepts/multi-agent)).
 
@@ -35,7 +35,7 @@ Related:
 If you don’t want to hand-edit config, run the onboarding wizard:
 
 ```bash
-pigbot onboard
+moltbot onboard
 ```
 
 It can set up model + auth for common providers, including **OpenAI Code (Codex)
@@ -59,7 +59,7 @@ Provider configuration examples (including OpenCode Zen) live in
 
 If `agents.defaults.models` is set, it becomes the **allowlist** for `/model` and for
 session overrides. When a user selects a model that isn’t in that allowlist,
-Pigbot returns:
+Moltbot returns:
 
 ```
 Model "provider/model" is not allowed. Use /model to list available models.
@@ -104,34 +104,34 @@ Notes:
 - `/model status` is the detailed view (auth candidates and, when configured, provider endpoint `baseUrl` + `api` mode).
 - Model refs are parsed by splitting on the **first** `/`. Use `provider/model` when typing `/model <ref>`.
 - If the model ID itself contains `/` (OpenRouter-style), you must include the provider prefix (example: `/model 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).
 
 Full command behavior/config: [Slash commands](/tools/slash-commands).
 
 ## CLI commands
 
 ```bash
-pigbot models list
-pigbot models status
-pigbot models set <provider/model>
-pigbot models set-image <provider/model>
-
-pigbot models aliases list
-pigbot models aliases add <alias> <provider/model>
-pigbot models aliases remove <alias>
-
-pigbot models fallbacks list
-pigbot models fallbacks add <provider/model>
-pigbot models fallbacks remove <provider/model>
-pigbot models fallbacks clear
-
-pigbot models image-fallbacks list
-pigbot models image-fallbacks add <provider/model>
-pigbot models image-fallbacks remove <provider/model>
-pigbot models image-fallbacks clear
+moltbot models list
+moltbot models status
+moltbot models set <provider/model>
+moltbot models set-image <provider/model>
+
+moltbot models aliases list
+moltbot models aliases add <alias> <provider/model>
+moltbot models aliases remove <alias>
+
+moltbot models fallbacks list
+moltbot models fallbacks add <provider/model>
+moltbot models fallbacks remove <provider/model>
+moltbot models fallbacks clear
+
+moltbot models image-fallbacks list
+moltbot models image-fallbacks add <provider/model>
+moltbot models image-fallbacks remove <provider/model>
+moltbot models image-fallbacks clear
 ```
 
-`pigbot models` (no subcommand) is a shortcut for `models status`.
+`moltbot models` (no subcommand) is a shortcut for `models status`.
 
 ### `models list`
 
@@ -159,12 +159,12 @@ Preferred Anthropic auth is the Claude Code CLI setup-token (run anywhere; paste
 
 ```bash
 claude setup-token
-pigbot models status
+moltbot models status
 ```
 
 ## Scanning (OpenRouter free models)
 
-`pigbot models scan` inspects OpenRouter’s **free model catalog** and can
+`moltbot models scan` inspects OpenRouter’s **free model catalog** and can
 optionally probe models for tool and image support.
 
 Key flags:
@@ -198,5 +198,5 @@ mode, pass `--yes` to accept defaults.
 ## Models registry (`models.json`)
 
 Custom providers in `models.providers` are written into `models.json` under the
-agent directory (default `~/.pigbot/agents/<agentId>/models.json`). This file
+agent directory (default `~/.clawdbot/agents/<agentId>/models.json`). This file
 is merged by default unless `models.mode` is set to `replace`.

package/docs/concepts/multi-agent.md

@@ -15,12 +15,12 @@ An **agent** is a fully scoped brain with its own:
 
 - **Workspace** (files, AGENTS.md/SOUL.md/USER.md, local notes, persona rules).
 - **State directory** (`agentDir`) for auth profiles, model registry, and per-agent config.
-- **Session store** (chat history + routing state) under `~/.pigbot/agents/<agentId>/sessions`.
+- **Session store** (chat history + routing state) under `~/.clawdbot/agents/<agentId>/sessions`.
 
 Auth profiles are **per-agent**. Each agent reads from its own:
 
 ```
-~/.pigbot/agents/<agentId>/agent/auth-profiles.json
+~/.clawdbot/agents/<agentId>/agent/auth-profiles.json
 ```
 
 Main agent credentials are **not** shared automatically. Never reuse `agentDir`
@@ -28,7 +28,7 @@ across agents (it causes auth/session collisions). If you want to share creds,
 copy `auth-profiles.json` into the other agent's `agentDir`.
 
 Skills are per-agent via each workspace’s `skills/` folder, with shared skills
-available from `~/.pigbot/skills`. See [Skills: per-agent vs shared](/tools/skills#per-agent-vs-shared-skills).
+available from `~/.clawdbot/skills`. See [Skills: per-agent vs shared](/tools/skills#per-agent-vs-shared-skills).
 
 The Gateway can host **one agent** (default) or **many agents** side-by-side.
 
@@ -39,27 +39,27 @@ reach other host locations unless sandboxing is enabled. See
 
 ## Paths (quick map)
 
-- Config: `~/.pigbot/pigbot.json` (or `PIGBOT_CONFIG_PATH`)
-- State dir: `~/.pigbot` (or `PIGBOT_STATE_DIR`)
+- Config: `~/.clawdbot/moltbot.json` (or `CLAWDBOT_CONFIG_PATH`)
+- State dir: `~/.clawdbot` (or `CLAWDBOT_STATE_DIR`)
 - Workspace: `~/clawd` (or `~/clawd-<agentId>`)
-- Agent dir: `~/.pigbot/agents/<agentId>/agent` (or `agents.list[].agentDir`)
-- Sessions: `~/.pigbot/agents/<agentId>/sessions`
+- Agent dir: `~/.clawdbot/agents/<agentId>/agent` (or `agents.list[].agentDir`)
+- Sessions: `~/.clawdbot/agents/<agentId>/sessions`
 
 ### Single-agent mode (default)
 
-If you do nothing, Pigbot runs a single agent:
+If you do nothing, Moltbot runs a single agent:
 
 - `agentId` defaults to **`main`**.
 - Sessions are keyed as `agent:main:<mainKey>`.
-- Workspace defaults to `~/clawd` (or `~/clawd-<profile>` when `PIGBOT_PROFILE` is set).
-- State defaults to `~/.pigbot/agents/main/agent`.
+- Workspace defaults to `~/clawd` (or `~/clawd-<profile>` when `CLAWDBOT_PROFILE` is set).
+- State defaults to `~/.clawdbot/agents/main/agent`.
 
 ## Agent helper
 
 Use the agent wizard to add a new isolated agent:
 
 ```bash
-pigbot agents add work
+moltbot agents add work
 ```
 
 Then add `bindings` (or let the wizard do it) to route inbound messages.
@@ -67,7 +67,7 @@ Then add `bindings` (or let the wizard do it) to route inbound messages.
 Verify with:
 
 ```bash
-pigbot agents list --bindings
+moltbot agents list --bindings
 ```
 
 ## Multiple agents = multiple people, multiple personalities
@@ -139,7 +139,7 @@ multiple phone numbers without mixing sessions.
 
 ## Example: two WhatsApps → two agents
 
-`~/.pigbot/pigbot.json` (JSON5):
+`~/.clawdbot/moltbot.json` (JSON5):
 
 ```js
 {
@@ -150,13 +150,13 @@ multiple phone numbers without mixing sessions.
         default: true,
         name: "Home",
         workspace: "~/clawd-home",
-        agentDir: "~/.pigbot/agents/home/agent",
+        agentDir: "~/.clawdbot/agents/home/agent",
       },
       {
         id: "work",
         name: "Work",
         workspace: "~/clawd-work",
-        agentDir: "~/.pigbot/agents/work/agent",
+        agentDir: "~/.clawdbot/agents/work/agent",
       },
     ],
   },
@@ -189,12 +189,12 @@ multiple phone numbers without mixing sessions.
     whatsapp: {
       accounts: {
         personal: {
-          // Optional override. Default: ~/.pigbot/credentials/whatsapp/personal
-          // authDir: "~/.pigbot/credentials/whatsapp/personal",
+          // Optional override. Default: ~/.clawdbot/credentials/whatsapp/personal
+          // authDir: "~/.clawdbot/credentials/whatsapp/personal",
         },
         biz: {
-          // Optional override. Default: ~/.pigbot/credentials/whatsapp/biz
-          // authDir: "~/.pigbot/credentials/whatsapp/biz",
+          // Optional override. Default: ~/.clawdbot/credentials/whatsapp/biz
+          // authDir: "~/.clawdbot/credentials/whatsapp/biz",
         },
       },
     },

package/docs/concepts/oauth.md

@@ -1,25 +1,24 @@
 ---
-summary: "OAuth in Pigbot: token exchange, storage, CLI sync, and multi-account patterns"
+summary: "OAuth in Moltbot: token exchange, storage, and multi-account patterns"
 read_when:
-  - You want to understand Pigbot OAuth end-to-end
+  - You want to understand Moltbot OAuth end-to-end
   - You hit token invalidation / logout issues
-  - You want to reuse Claude Code / Codex CLI OAuth tokens
+  - You want setup-token or OAuth auth flows
   - You want multiple accounts or profile routing
 ---
 # OAuth
 
-Pigbot supports “subscription auth” via OAuth for providers that offer it (notably **Anthropic (Claude Pro/Max)** and **OpenAI Codex (ChatGPT OAuth)**). This page explains:
+Moltbot supports “subscription auth” via OAuth for providers that offer it (notably **OpenAI Codex (ChatGPT OAuth)**). For Anthropic subscriptions, use the **setup-token** flow. This page explains:
 
 - how the OAuth **token exchange** works (PKCE)
 - where tokens are **stored** (and why)
-- how we **reuse external CLI tokens** (Claude Code / Codex CLI)
 - how to handle **multiple accounts** (profiles + per-session overrides)
 
-Pigbot also supports **provider plugins** that ship their own OAuth or API‑key
+Moltbot also supports **provider plugins** that ship their own OAuth or API‑key
 flows. Run them via:
 
 ```bash
-pigbot models auth login --provider <id>
+moltbot models auth login --provider <id>
 ```
 
 ## The token sink (why it exists)
@@ -27,66 +26,57 @@ pigbot models auth login --provider <id>
 OAuth providers commonly mint a **new refresh token** during login/refresh flows. Some providers (or OAuth clients) can invalidate older refresh tokens when a new one is issued for the same user/app.
 
 Practical symptom:
-- you log in via Pigbot *and* via Claude Code / Codex CLI → one of them randomly gets “logged out” later
+- you log in via Moltbot *and* via Claude Code / Codex CLI → one of them randomly gets “logged out” later
 
-To reduce that, Pigbot treats `auth-profiles.json` as a **token sink**:
+To reduce that, Moltbot treats `auth-profiles.json` as a **token sink**:
 - the runtime reads credentials from **one place**
-- we can **sync in** credentials from external CLIs instead of doing a second login
 - we can keep multiple profiles and route them deterministically
 
 ## Storage (where tokens live)
 
 Secrets are stored **per-agent**:
 
-- Auth profiles (OAuth + API keys): `~/.pigbot/agents/<agentId>/agent/auth-profiles.json`
-- Runtime cache (managed automatically; don’t edit): `~/.pigbot/agents/<agentId>/agent/auth.json`
+- Auth profiles (OAuth + API keys): `~/.clawdbot/agents/<agentId>/agent/auth-profiles.json`
+- Runtime cache (managed automatically; don’t edit): `~/.clawdbot/agents/<agentId>/agent/auth.json`
 
 Legacy import-only file (still supported, but not the main store):
-- `~/.pigbot/credentials/oauth.json` (imported into `auth-profiles.json` on first use)
+- `~/.clawdbot/credentials/oauth.json` (imported into `auth-profiles.json` on first use)
 
-All of the above also respect `$PIGBOT_STATE_DIR` (state dir override). Full reference: [/gateway/configuration](/gateway/configuration#auth-storage-oauth--api-keys)
+All of the above also respect `$CLAWDBOT_STATE_DIR` (state dir override). Full reference: [/gateway/configuration](/gateway/configuration#auth-storage-oauth--api-keys)
 
-## Reusing Claude Code / Codex CLI OAuth tokens (recommended)
+## Anthropic setup-token (subscription auth)
 
-If you already signed in with the external CLIs *on the gateway host*, Pigbot can reuse those tokens without starting a separate OAuth flow:
+Run `claude setup-token` on any machine, then paste it into Moltbot:
 
-- Claude Code: `anthropic:claude-cli`
-  - macOS: Keychain item "Claude Code-credentials" (choose "Always Allow" to avoid launchd prompts)
-  - Linux/Windows: `~/.claude/.credentials.json`
-- Codex CLI: reads `~/.codex/auth.json` → profile `openai-codex:codex-cli`
-
-Sync happens when Pigbot loads the auth store (so it stays up-to-date when the CLIs refresh tokens).
-On macOS, the first read may trigger a Keychain prompt; run `pigbot models status`
-in a terminal once if the Gateway runs headless and can’t access the entry.
+```bash
+moltbot models auth setup-token --provider anthropic
+```
 
-How to verify:
+If you generated the token elsewhere, paste it manually:
 
 ```bash
-pigbot models status
-pigbot channels list
+moltbot models auth paste-token --provider anthropic
 ```
 
-Or JSON:
+Verify:
 
 ```bash
-pigbot channels list --json
+moltbot models status
 ```
 
 ## OAuth exchange (how login works)
 
-Pigbot’s interactive login flows are implemented in `@mariozechner/pi-ai` and wired into the wizards/commands.
+Moltbot’s interactive login flows are implemented in `@mariozechner/pi-ai` and wired into the wizards/commands.
 
-### Anthropic (Claude Pro/Max)
+### Anthropic (Claude Pro/Max) setup-token
 
-Flow shape (PKCE):
+Flow shape:
 
-1) generate PKCE verifier/challenge
-2) open `https://claude.ai/oauth/authorize?...`
-3) user pastes `code#state`
-4) exchange at `https://console.anthropic.com/v1/oauth/token`
-5) store `{ access, refresh, expires }` under an auth profile
+1) run `claude setup-token`
+2) paste the token into Moltbot
+3) store as a token auth profile (no refresh)
 
-The wizard path is `pigbot onboard` → auth choice `oauth` (Anthropic).
+The wizard path is `moltbot onboard` → auth choice `setup-token` (Anthropic).
 
 ### OpenAI Codex (ChatGPT OAuth)
 
@@ -99,7 +89,7 @@ Flow shape (PKCE):
 5) exchange at `https://auth.openai.com/oauth/token`
 6) extract `accountId` from the access token and store `{ access, refresh, expires, accountId }`
 
-Wizard path is `pigbot onboard` → auth choice `openai-codex` (or `codex-cli` to reuse an existing Codex CLI login).
+Wizard path is `moltbot onboard` → auth choice `openai-codex`.
 
 ## Refresh + expiry
 
@@ -111,23 +101,6 @@ At runtime:
 
 The refresh flow is automatic; you generally don't need to manage tokens manually.
 
-### Bidirectional sync with Claude Code
-
-When Pigbot refreshes an Anthropic OAuth token (profile `anthropic:claude-cli`), it **writes the new credentials back** to Claude Code's storage:
-
-- **Linux/Windows**: updates `~/.claude/.credentials.json`
-- **macOS**: updates Keychain item "Claude Code-credentials"
-
-This ensures both tools stay in sync and neither gets "logged out" after the other refreshes.
-
-**Why this matters for long-running agents:**
-
-Anthropic OAuth tokens expire after a few hours. Without bidirectional sync:
-1. Pigbot refreshes the token → gets new access token
-2. Claude Code still has the old token → gets logged out
-
-With bidirectional sync, both tools always have the latest valid token, enabling autonomous operation for days or weeks without manual intervention.
-
 ## Multiple accounts (profiles) + routing
 
 Two patterns:
@@ -137,8 +110,8 @@ Two patterns:
 If you want “personal” and “work” to never interact, use isolated agents (separate sessions + credentials + workspace):
 
 ```bash
-pigbot agents add work
-pigbot agents add personal
+moltbot agents add work
+moltbot agents add personal
 ```
 
 Then configure auth per-agent (wizard) and route chats to the right agent.
@@ -155,7 +128,7 @@ Example (session override):
 - `/model Opus@anthropic:work`
 
 How to see what profile IDs exist:
-- `pigbot channels list --json` (shows `auth[]`)
+- `moltbot channels list --json` (shows `auth[]`)
 
 Related docs:
 - [/concepts/model-failover](/concepts/model-failover) (rotation + cooldown rules)

package/docs/concepts/presence.md

@@ -1,5 +1,5 @@
 ---
-summary: "How Pigbot presence entries are produced, merged, and displayed"
+summary: "How Moltbot presence entries are produced, merged, and displayed"
 read_when:
   - Debugging the Instances tab
   - Investigating duplicate or stale instance rows
@@ -7,7 +7,7 @@ read_when:
 ---
 # Presence
 
-Pigbot “presence” is a lightweight, best‑effort view of:
+Moltbot “presence” is a lightweight, best‑effort view of:
 - the **Gateway** itself, and
 - **clients connected to the Gateway** (mac app, WebChat, CLI, etc.)
 

package/docs/concepts/retry.md

@@ -30,7 +30,7 @@ read_when:
 - Markdown parse errors are not retried; they fall back to plain text.
 
 ## Configuration
-Set retry policy per provider in `~/.pigbot/pigbot.json`:
+Set retry policy per provider in `~/.clawdbot/moltbot.json`:
 
 ```json5
 {

package/docs/concepts/session-pruning.md

@@ -18,7 +18,7 @@ Session pruning trims **old tool results** from the in-memory context right befo
 ## Smart defaults (Anthropic)
 - **OAuth or setup-token** profiles: enable `cache-ttl` pruning and set heartbeat to `1h`.
 - **API key** profiles: enable `cache-ttl` pruning, set heartbeat to `30m`, and default `cacheControlTtl` to `1h` on Anthropic models.
-- If you set any of these values explicitly, Pigbot does **not** override them.
+- If you set any of these values explicitly, Moltbot does **not** override them.
 
 ## What this improves (cost + cache behavior)
 - **Why prune:** Anthropic prompt caching only applies within the TTL. If a session goes idle past the TTL, the next request re-caches the full prompt unless you trim it first.