@gguf/pigbot 0.0.1 → 0.0.2

package/docs/channels/line.md

@@ -0,0 +1,183 @@
+---
+summary: "LINE Messaging API plugin setup, config, and usage"
+read_when:
+  - You want to connect Moltbot to LINE
+  - You need LINE webhook + credential setup
+  - You want LINE-specific message options
+---
+
+# LINE (plugin)
+
+LINE connects to Moltbot via the LINE Messaging API. The plugin runs as a webhook
+receiver on the gateway and uses your channel access token + channel secret for
+authentication.
+
+Status: supported via plugin. Direct messages, group chats, media, locations, Flex
+messages, template messages, and quick replies are supported. Reactions and threads
+are not supported.
+
+## Plugin required
+
+Install the LINE plugin:
+
+```bash
+moltbot plugins install @moltbot/line
+```
+
+Local checkout (when running from a git repo):
+
+```bash
+moltbot plugins install ./extensions/line
+```
+
+## Setup
+
+1) Create a LINE Developers account and open the Console:
+   https://developers.line.biz/console/
+2) Create (or pick) a Provider and add a **Messaging API** channel.
+3) Copy the **Channel access token** and **Channel secret** from the channel settings.
+4) Enable **Use webhook** in the Messaging API settings.
+5) Set the webhook URL to your gateway endpoint (HTTPS required):
+
+```
+https://gateway-host/line/webhook
+```
+
+The gateway responds to LINE’s webhook verification (GET) and inbound events (POST).
+If you need a custom path, set `channels.line.webhookPath` or
+`channels.line.accounts.<id>.webhookPath` and update the URL accordingly.
+
+## Configure
+
+Minimal config:
+
+```json5
+{
+  channels: {
+    line: {
+      enabled: true,
+      channelAccessToken: "LINE_CHANNEL_ACCESS_TOKEN",
+      channelSecret: "LINE_CHANNEL_SECRET",
+      dmPolicy: "pairing"
+    }
+  }
+}
+```
+
+Env vars (default account only):
+
+- `LINE_CHANNEL_ACCESS_TOKEN`
+- `LINE_CHANNEL_SECRET`
+
+Token/secret files:
+
+```json5
+{
+  channels: {
+    line: {
+      tokenFile: "/path/to/line-token.txt",
+      secretFile: "/path/to/line-secret.txt"
+    }
+  }
+}
+```
+
+Multiple accounts:
+
+```json5
+{
+  channels: {
+    line: {
+      accounts: {
+        marketing: {
+          channelAccessToken: "...",
+          channelSecret: "...",
+          webhookPath: "/line/marketing"
+        }
+      }
+    }
+  }
+}
+```
+
+## Access control
+
+Direct messages default to pairing. Unknown senders get a pairing code and their
+messages are ignored until approved.
+
+```bash
+moltbot pairing list line
+moltbot pairing approve line <CODE>
+```
+
+Allowlists and policies:
+
+- `channels.line.dmPolicy`: `pairing | allowlist | open | disabled`
+- `channels.line.allowFrom`: allowlisted LINE user IDs for DMs
+- `channels.line.groupPolicy`: `allowlist | open | disabled`
+- `channels.line.groupAllowFrom`: allowlisted LINE user IDs for groups
+- Per-group overrides: `channels.line.groups.<groupId>.allowFrom`
+
+LINE IDs are case-sensitive. Valid IDs look like:
+
+- User: `U` + 32 hex chars
+- Group: `C` + 32 hex chars
+- Room: `R` + 32 hex chars
+
+## Message behavior
+
+- Text is chunked at 5000 characters.
+- Markdown formatting is stripped; code blocks and tables are converted into Flex
+  cards when possible.
+- Streaming responses are buffered; LINE receives full chunks with a loading
+  animation while the agent works.
+- Media downloads are capped by `channels.line.mediaMaxMb` (default 10).
+
+## Channel data (rich messages)
+
+Use `channelData.line` to send quick replies, locations, Flex cards, or template
+messages.
+
+```json5
+{
+  text: "Here you go",
+  channelData: {
+    line: {
+      quickReplies: ["Status", "Help"],
+      location: {
+        title: "Office",
+        address: "123 Main St",
+        latitude: 35.681236,
+        longitude: 139.767125
+      },
+      flexMessage: {
+        altText: "Status card",
+        contents: { /* Flex payload */ }
+      },
+      templateMessage: {
+        type: "confirm",
+        text: "Proceed?",
+        confirmLabel: "Yes",
+        confirmData: "yes",
+        cancelLabel: "No",
+        cancelData: "no"
+      }
+    }
+  }
+}
+```
+
+The LINE plugin also ships a `/card` command for Flex message presets:
+
+```
+/card info "Welcome" "Thanks for joining!"
+```
+
+## Troubleshooting
+
+- **Webhook verification fails:** ensure the webhook URL is HTTPS and the
+  `channelSecret` matches the LINE console.
+- **No inbound events:** confirm the webhook path matches `channels.line.webhookPath`
+  and that the gateway is reachable from LINE.
+- **Media download errors:** raise `channels.line.mediaMaxMb` if media exceeds the
+  default limit.

package/docs/channels/location.md

@@ -7,7 +7,7 @@ read_when:
 
 # Channel location parsing
 
-Pigbot normalizes shared locations from chat channels into:
+Moltbot normalizes shared locations from chat channels into:
 - human-readable text appended to the inbound body, and
 - structured fields in the auto-reply context payload.
 

package/docs/channels/matrix.md

@@ -5,12 +5,12 @@ read_when:
 ---
 # Matrix (plugin)
 
-Matrix is an open, decentralized messaging protocol. Pigbot connects as a Matrix **user**
+Matrix is an open, decentralized messaging protocol. Moltbot connects as a Matrix **user**
 on any homeserver, so you need a Matrix account for the bot. Once it is logged in, you can DM
 the bot directly or invite it to rooms (Matrix "groups"). Beeper is a valid client option too,
 but it requires E2EE to be enabled.
 
-Status: supported via plugin (matrix-bot-sdk). Direct messages, rooms, threads, media, reactions,
+Status: supported via plugin (@vector-im/matrix-bot-sdk). Direct messages, rooms, threads, media, reactions,
 polls (send + poll-start as text), location, and E2EE (with crypto support).
 
 ## Plugin required
@@ -20,25 +20,25 @@ Matrix ships as a plugin and is not bundled with the core install.
 Install via CLI (npm registry):
 
 ```bash
-pigbot plugins install @pigbot/matrix
+moltbot plugins install @moltbot/matrix
 ```
 
 Local checkout (when running from a git repo):
 
 ```bash
-pigbot plugins install ./extensions/matrix
+moltbot plugins install ./extensions/matrix
 ```
 
 If you choose Matrix during configure/onboarding and a git checkout is detected,
-Pigbot will offer the local install path automatically.
+Moltbot will offer the local install path automatically.
 
 Details: [Plugins](/plugin)
 
 ## Setup
 
 1) Install the Matrix plugin:
-   - From npm: `pigbot plugins install @pigbot/matrix`
-   - From a local checkout: `pigbot plugins install ./extensions/matrix`
+   - From npm: `moltbot plugins install @moltbot/matrix`
+   - From a local checkout: `moltbot plugins install ./extensions/matrix`
 2) Create a Matrix account on a homeserver:
    - Browse hosting options at [https://matrix.org/ecosystem/hosting/](https://matrix.org/ecosystem/hosting/)
    - Or host it yourself.
@@ -60,8 +60,8 @@ Details: [Plugins](/plugin)
    ```
 
    - Replace `matrix.example.org` with your homeserver URL.
-   - Or set `channels.matrix.userId` + `channels.matrix.password`: Pigbot calls the same
-     login endpoint, stores the access token in `~/.pigbot/credentials/matrix/credentials.json`,
+   - Or set `channels.matrix.userId` + `channels.matrix.password`: Moltbot calls the same
+     login endpoint, stores the access token in `~/.clawdbot/credentials/matrix/credentials.json`,
      and reuses it on next start.
 4) Configure credentials:
    - Env: `MATRIX_HOMESERVER`, `MATRIX_ACCESS_TOKEN` (or `MATRIX_USER_ID` + `MATRIX_PASSWORD`)
@@ -113,17 +113,17 @@ Enable with `channels.matrix.encryption: true`:
 
 - If the crypto module loads, encrypted rooms are decrypted automatically.
 - Outbound media is encrypted when sending to encrypted rooms.
-- On first connection, Pigbot requests device verification from your other sessions.
+- On first connection, Moltbot requests device verification from your other sessions.
 - Verify the device in another Matrix client (Element, etc.) to enable key sharing.
 - If the crypto module cannot be loaded, E2EE is disabled and encrypted rooms will not decrypt;
-  Pigbot logs a warning.
+  Moltbot logs a warning.
 - If you see missing crypto module errors (for example, `@matrix-org/matrix-sdk-crypto-nodejs-*`),
   allow build scripts for `@matrix-org/matrix-sdk-crypto-nodejs` and run
   `pnpm rebuild @matrix-org/matrix-sdk-crypto-nodejs` or fetch the binary with
   `node node_modules/@matrix-org/matrix-sdk-crypto-nodejs/download-lib.js`.
 
 Crypto state is stored per account + access token in
-`~/.pigbot/matrix/accounts/<account>/<homeserver>__<user>/<token-hash>/crypto/`
+`~/.clawdbot/matrix/accounts/<account>/<homeserver>__<user>/<token-hash>/crypto/`
 (SQLite database). Sync state lives alongside it in `bot-storage.json`.
 If the access token (device) changes, a new store is created and the bot must be
 re-verified for encrypted rooms.
@@ -142,8 +142,8 @@ Once verified, the bot can decrypt messages in encrypted rooms.
 
 - Default: `channels.matrix.dm.policy = "pairing"`. Unknown senders get a pairing code.
 - Approve via:
-  - `pigbot pairing list matrix`
-  - `pigbot pairing approve matrix <CODE>`
+  - `moltbot pairing list matrix`
+  - `moltbot pairing approve matrix <CODE>`
 - Public DMs: `channels.matrix.dm.policy="open"` plus `channels.matrix.dm.allowFrom=["*"]`.
 - `channels.matrix.dm.allowFrom` accepts user IDs or display names. The wizard resolves display names to user IDs when directory search is available.
 
@@ -172,7 +172,7 @@ Once verified, the bot can decrypt messages in encrypted rooms.
 - `groupAllowFrom` restricts which senders can trigger the bot in rooms (optional).
 - Per-room `users` allowlists can further restrict senders inside a specific room.
 - The configure wizard prompts for room allowlists (room IDs, aliases, or names) and resolves names when possible.
-- On startup, Pigbot resolves room/user names in allowlists to IDs and logs the mapping; unresolved entries are kept as typed.
+- On startup, Moltbot resolves room/user names in allowlists to IDs and logs the mapping; unresolved entries are kept as typed.
 - Invites are auto-joined by default; control with `channels.matrix.autoJoin` and `channels.matrix.autoJoinAllowlist`.
 - To allow **no rooms**, set `channels.matrix.groupPolicy: "disabled"` (or keep an empty allowlist).
 - Legacy key: `channels.matrix.rooms` (same shape as `groups`).
@@ -215,7 +215,7 @@ Provider options:
 - `channels.matrix.initialSyncLimit`: initial sync limit.
 - `channels.matrix.threadReplies`: `off | inbound | always` (default: inbound).
 - `channels.matrix.textChunkLimit`: outbound text chunk size (chars).
-- `channels.matrix.chunkMode`: `length` (default) or `newline` to split on newlines before length chunking.
+- `channels.matrix.chunkMode`: `length` (default) or `newline` to split on blank lines (paragraph boundaries) before length chunking.
 - `channels.matrix.dm.policy`: `pairing | allowlist | open | disabled` (default: pairing).
 - `channels.matrix.dm.allowFrom`: DM allowlist (user IDs or display names). `open` requires `"*"`. The wizard resolves names to IDs when possible.
 - `channels.matrix.groupPolicy`: `allowlist | open | disabled` (default: allowlist).

package/docs/channels/mattermost.md

@@ -1,5 +1,5 @@
 ---
-summary: "Mattermost bot setup and Pigbot config"
+summary: "Mattermost bot setup and Moltbot config"
 read_when:
   - Setting up Mattermost
   - Debugging Mattermost routing
@@ -16,16 +16,16 @@ Mattermost ships as a plugin and is not bundled with the core install.
 
 Install via CLI (npm registry):
 ```bash
-pigbot plugins install @pigbot/mattermost
+moltbot plugins install @moltbot/mattermost
 ```
 
 Local checkout (when running from a git repo):
 ```bash
-pigbot plugins install ./extensions/mattermost
+moltbot plugins install ./extensions/mattermost
 ```
 
 If you choose Mattermost during configure/onboarding and a git checkout is detected,
-Pigbot will offer the local install path automatically.
+Moltbot will offer the local install path automatically.
 
 Details: [Plugins](/plugin)
 
@@ -33,7 +33,7 @@ Details: [Plugins](/plugin)
 1) Install the Mattermost plugin.
 2) Create a Mattermost bot account and copy the **bot token**.
 3) Copy the Mattermost **base URL** (e.g., `https://chat.example.com`).
-4) Configure Pigbot and start the gateway.
+4) Configure Moltbot and start the gateway.
 
 Minimal config:
 ```json5
@@ -83,8 +83,8 @@ Notes:
 ## Access control (DMs)
 - Default: `channels.mattermost.dmPolicy = "pairing"` (unknown senders get a pairing code).
 - Approve via:
-  - `pigbot pairing list mattermost`
-  - `pigbot pairing approve mattermost <CODE>`
+  - `moltbot pairing list mattermost`
+  - `moltbot pairing approve mattermost <CODE>`
 - Public DMs: `channels.mattermost.dmPolicy="open"` plus `channels.mattermost.allowFrom=["*"]`.
 
 ## Channels (groups)
@@ -93,7 +93,7 @@ Notes:
 - Open channels: `channels.mattermost.groupPolicy="open"` (mention-gated).
 
 ## Targets for outbound delivery
-Use these target formats with `pigbot message send` or cron/webhooks:
+Use these target formats with `moltbot message send` or cron/webhooks:
 
 - `channel:<id>` for a channel
 - `user:<id>` for a DM

package/docs/channels/msteams.md

@@ -21,23 +21,23 @@ Explainable: keeps core installs lighter and lets MS Teams dependencies update i
 
 Install via CLI (npm registry):
 ```bash
-pigbot plugins install @pigbot/msteams
+moltbot plugins install @moltbot/msteams
 ```
 
 Local checkout (when running from a git repo):
 ```bash
-pigbot plugins install ./extensions/msteams
+moltbot plugins install ./extensions/msteams
 ```
 
 If you choose Teams during configure/onboarding and a git checkout is detected,
-Pigbot will offer the local install path automatically.
+Moltbot will offer the local install path automatically.
 
 Details: [Plugins](/plugin)
 
 ## Quick setup (beginner)
 1) Install the Microsoft Teams plugin.
 2) Create an **Azure Bot** (App ID + client secret + tenant ID).
-3) Configure Pigbot with those credentials.
+3) Configure Moltbot with those credentials.
 4) Expose `/api/messages` (port 3978 by default) via a public URL or tunnel.
 5) Install the Teams app package and start the gateway.
 
@@ -58,7 +58,7 @@ Minimal config:
 Note: group chats are blocked by default (`channels.msteams.groupPolicy: "allowlist"`). To allow group replies, set `channels.msteams.groupAllowFrom` (or use `groupPolicy: "open"` to allow any member, mention-gated).
 
 ## Goals
-- Talk to Pigbot via Teams DMs, group chats, or channels.
+- Talk to Moltbot via Teams DMs, group chats, or channels.
 - Keep routing deterministic: replies always go back to the channel they arrived on.
 - Default to safe channel behavior (mentions required unless configured otherwise).
 
@@ -101,7 +101,7 @@ Example:
 - Keys can be team IDs or names; channel keys can be conversation IDs or names.
 - When `groupPolicy="allowlist"` and a teams allowlist is present, only listed teams/channels are accepted (mention‑gated).
 - The configure wizard accepts `Team/Channel` entries and stores them for you.
-- On startup, Pigbot resolves team/channel and user allowlist names to IDs (when Graph permissions allow)
+- On startup, Moltbot resolves team/channel and user allowlist names to IDs (when Graph permissions allow)
   and logs the mapping; unresolved entries are kept as typed.
 
 Example:
@@ -127,12 +127,12 @@ Example:
 2. Create an **Azure Bot** (App ID + secret + tenant ID).
 3. Build a **Teams app package** that references the bot and includes the RSC permissions below.
 4. Upload/install the Teams app into a team (or personal scope for DMs).
-5. Configure `msteams` in `~/.pigbot/pigbot.json` (or env vars) and start the gateway.
+5. Configure `msteams` in `~/.clawdbot/moltbot.json` (or env vars) and start the gateway.
 6. The gateway listens for Bot Framework webhook traffic on `/api/messages` by default.
 
 ## Azure Bot Setup (Prerequisites)
 
-Before configuring Pigbot, you need to create an Azure Bot resource.
+Before configuring Moltbot, you need to create an Azure Bot resource.
 
 ### Step 1: Create Azure Bot
 
@@ -141,7 +141,7 @@ Before configuring Pigbot, you need to create an Azure Bot resource.
 
    | Field | Value |
    |-------|-------|
-   | **Bot handle** | Your bot name, e.g., `pigbot-msteams` (must be unique) |
+   | **Bot handle** | Your bot name, e.g., `moltbot-msteams` (must be unique) |
    | **Subscription** | Select your Azure subscription |
    | **Resource group** | Create new or use existing |
    | **Pricing tier** | **Free** for dev/testing |
@@ -218,8 +218,8 @@ This is often easier than hand-editing JSON manifests.
 
 ## Setup (minimal text-only)
 1. **Install the Microsoft Teams plugin**
-   - From npm: `pigbot plugins install @pigbot/msteams`
-   - From a local checkout: `pigbot plugins install ./extensions/msteams`
+   - From npm: `moltbot plugins install @moltbot/msteams`
+   - From a local checkout: `moltbot plugins install ./extensions/msteams`
 
 2. **Bot registration**
    - Create an Azure Bot (see above) and note:
@@ -235,7 +235,7 @@ This is often easier than hand-editing JSON manifests.
    - Create icons: `outline.png` (32x32) and `color.png` (192x192).
    - Zip all three files together: `manifest.json`, `outline.png`, `color.png`.
 
-4. **Configure Pigbot**
+4. **Configure Moltbot**
    ```json
    {
      "msteams": {
@@ -289,14 +289,14 @@ Minimal, valid example with the required fields. Replace IDs and URLs.
   "manifestVersion": "1.23",
   "version": "1.0.0",
   "id": "00000000-0000-0000-0000-000000000000",
-  "name": { "short": "Pigbot" },
+  "name": { "short": "Moltbot" },
   "developer": {
     "name": "Your Org",
     "websiteUrl": "https://example.com",
     "privacyUrl": "https://example.com/privacy",
     "termsOfUseUrl": "https://example.com/terms"
   },
-  "description": { "short": "Pigbot in Teams", "full": "Pigbot in Teams" },
+  "description": { "short": "Moltbot in Teams", "full": "Moltbot in Teams" },
   "icons": { "outline": "outline.png", "color": "color.png" },
   "accentColor": "#5B6DEF",
   "bots": [
@@ -397,7 +397,7 @@ Teams delivers messages via HTTP webhook. If processing takes too long (e.g., sl
 - Teams retrying the message (causing duplicates)
 - Dropped replies
 
-Pigbot handles this by returning quickly and sending replies proactively, but very slow responses may still cause issues.
+Moltbot handles this by returning quickly and sending replies proactively, but very slow responses may still cause issues.
 
 ### Formatting
 Teams markdown is more limited than Slack or Discord:
@@ -415,14 +415,18 @@ Key settings (see `/gateway/configuration` for shared channel patterns):
 - `channels.msteams.dmPolicy`: `pairing | allowlist | open | disabled` (default: pairing)
 - `channels.msteams.allowFrom`: allowlist for DMs (AAD object IDs, UPNs, or display names). The wizard resolves names to IDs during setup when Graph access is available.
 - `channels.msteams.textChunkLimit`: outbound text chunk size.
-- `channels.msteams.chunkMode`: `length` (default) or `newline` to split on newlines before length chunking.
+- `channels.msteams.chunkMode`: `length` (default) or `newline` to split on blank lines (paragraph boundaries) before length chunking.
 - `channels.msteams.mediaAllowHosts`: allowlist for inbound attachment hosts (defaults to Microsoft/Teams domains).
 - `channels.msteams.requireMention`: require @mention in channels/groups (default true).
 - `channels.msteams.replyStyle`: `thread | top-level` (see [Reply Style](#reply-style-threads-vs-posts)).
 - `channels.msteams.teams.<teamId>.replyStyle`: per-team override.
 - `channels.msteams.teams.<teamId>.requireMention`: per-team override.
+- `channels.msteams.teams.<teamId>.tools`: default per-team tool policy overrides (`allow`/`deny`/`alsoAllow`) used when a channel override is missing.
+- `channels.msteams.teams.<teamId>.toolsBySender`: default per-team per-sender tool policy overrides (`"*"` wildcard supported).
 - `channels.msteams.teams.<teamId>.channels.<conversationId>.replyStyle`: per-channel override.
 - `channels.msteams.teams.<teamId>.channels.<conversationId>.requireMention`: per-channel override.
+- `channels.msteams.teams.<teamId>.channels.<conversationId>.tools`: per-channel tool policy overrides (`allow`/`deny`/`alsoAllow`).
+- `channels.msteams.teams.<teamId>.channels.<conversationId>.toolsBySender`: per-channel per-sender tool policy overrides (`"*"` wildcard supported).
 - `channels.msteams.sharePointSiteId`: SharePoint site ID for file uploads in group chats/channels (see [Sending files in group chats](#sending-files-in-group-chats)).
 
 ## Routing & Sessions
@@ -471,7 +475,7 @@ Teams recently introduced two channel UI styles over the same underlying data mo
 - **Channels/groups:** Attachments live in M365 storage (SharePoint/OneDrive). The webhook payload only includes an HTML stub, not the actual file bytes. **Graph API permissions are required** to download channel attachments.
 
 Without Graph permissions, channel messages with images will be received as text-only (the image content is not accessible to the bot).
-By default, Pigbot only downloads media from Microsoft/Teams hostnames. Override with `channels.msteams.mediaAllowHosts` (use `["*"]` to allow any host).
+By default, Moltbot only downloads media from Microsoft/Teams hostnames. Override with `channels.msteams.mediaAllowHosts` (use `["*"]` to allow any host).
 
 ## Sending files in group chats
 
@@ -508,7 +512,7 @@ Bots don't have a personal OneDrive drive (the `/me/drive` Graph API endpoint do
    # Response includes: "id": "contoso.sharepoint.com,guid1,guid2"
    ```
 
-4. **Configure Pigbot:**
+4. **Configure Moltbot:**
    ```json5
    {
      channels: {
@@ -540,13 +544,13 @@ Per-user sharing is more secure as only the chat participants can access the fil
 
 ### Files stored location
 
-Uploaded files are stored in a `/PigbotShared/` folder in the configured SharePoint site's default document library.
+Uploaded files are stored in a `/MoltbotShared/` folder in the configured SharePoint site's default document library.
 
 ## Polls (Adaptive Cards)
-Pigbot sends Teams polls as Adaptive Cards (there is no native Teams poll API).
+Moltbot sends Teams polls as Adaptive Cards (there is no native Teams poll API).
 
-- CLI: `pigbot message poll --channel msteams --target conversation:<id> ...`
-- Votes are recorded by the gateway in `~/.pigbot/msteams-polls.json`.
+- CLI: `moltbot message poll --channel msteams --target conversation:<id> ...`
+- Votes are recorded by the gateway in `~/.clawdbot/msteams-polls.json`.
 - The gateway must stay online to record votes.
 - Polls do not auto-post result summaries yet (inspect the store file if needed).
 
@@ -571,7 +575,7 @@ The `card` parameter accepts an Adaptive Card JSON object. When `card` is provid
 
 **CLI:**
 ```bash
-pigbot message send --channel msteams \
+moltbot message send --channel msteams \
   --target "conversation:19:abc...@thread.tacv2" \
   --card '{"type":"AdaptiveCard","version":"1.5","body":[{"type":"TextBlock","text":"Hello!"}]}'
 ```
@@ -592,16 +596,16 @@ MSTeams targets use prefixes to distinguish between users and conversations:
 **CLI examples:**
 ```bash
 # Send to a user by ID
-pigbot message send --channel msteams --target "user:40a1a0ed-..." --message "Hello"
+moltbot message send --channel msteams --target "user:40a1a0ed-..." --message "Hello"
 
 # Send to a user by display name (triggers Graph API lookup)
-pigbot message send --channel msteams --target "user:John Smith" --message "Hello"
+moltbot message send --channel msteams --target "user:John Smith" --message "Hello"
 
 # Send to a group chat or channel
-pigbot message send --channel msteams --target "conversation:19:abc...@thread.tacv2" --message "Hello"
+moltbot message send --channel msteams --target "conversation:19:abc...@thread.tacv2" --message "Hello"
 
 # Send an Adaptive Card to a conversation
-pigbot message send --channel msteams --target "conversation:19:abc...@thread.tacv2" \
+moltbot message send --channel msteams --target "conversation:19:abc...@thread.tacv2" \
   --card '{"type":"AdaptiveCard","version":"1.5","body":[{"type":"TextBlock","text":"Hello"}]}'
 ```
 

package/docs/channels/nextcloud-talk.md

@@ -12,16 +12,16 @@ Nextcloud Talk ships as a plugin and is not bundled with the core install.
 
 Install via CLI (npm registry):
 ```bash
-pigbot plugins install @pigbot/nextcloud-talk
+moltbot plugins install @moltbot/nextcloud-talk
 ```
 
 Local checkout (when running from a git repo):
 ```bash
-pigbot plugins install ./extensions/nextcloud-talk
+moltbot plugins install ./extensions/nextcloud-talk
 ```
 
 If you choose Nextcloud Talk during configure/onboarding and a git checkout is detected,
-Pigbot will offer the local install path automatically.
+Moltbot will offer the local install path automatically.
 
 Details: [Plugins](/plugin)
 
@@ -29,10 +29,10 @@ Details: [Plugins](/plugin)
 1) Install the Nextcloud Talk plugin.
 2) On your Nextcloud server, create a bot:
    ```bash
-   ./occ talk:bot:install "Pigbot" "<shared-secret>" "<webhook-url>" --feature reaction
+   ./occ talk:bot:install "Moltbot" "<shared-secret>" "<webhook-url>" --feature reaction
    ```
 3) Enable the bot in the target room settings.
-4) Configure Pigbot:
+4) Configure Moltbot:
    - Config: `channels.nextcloud-talk.baseUrl` + `channels.nextcloud-talk.botSecret`
    - Or env: `NEXTCLOUD_TALK_BOT_SECRET` (default account only)
 5) Restart the gateway (or finish onboarding).
@@ -60,8 +60,8 @@ Minimal config:
 ## Access control (DMs)
 - Default: `channels.nextcloud-talk.dmPolicy = "pairing"`. Unknown senders get a pairing code.
 - Approve via:
-  - `pigbot pairing list nextcloud-talk`
-  - `pigbot pairing approve nextcloud-talk <CODE>`
+  - `moltbot pairing list nextcloud-talk`
+  - `moltbot pairing approve nextcloud-talk <CODE>`
 - Public DMs: `channels.nextcloud-talk.dmPolicy="open"` plus `channels.nextcloud-talk.allowFrom=["*"]`.
 
 ## Rooms (groups)
@@ -114,7 +114,7 @@ Provider options:
 - `channels.nextcloud-talk.dmHistoryLimit`: DM history limit (0 disables).
 - `channels.nextcloud-talk.dms`: per-DM overrides (historyLimit).
 - `channels.nextcloud-talk.textChunkLimit`: outbound text chunk size (chars).
-- `channels.nextcloud-talk.chunkMode`: `length` (default) or `newline` to split on newlines before length chunking.
+- `channels.nextcloud-talk.chunkMode`: `length` (default) or `newline` to split on blank lines (paragraph boundaries) before length chunking.
 - `channels.nextcloud-talk.blockStreaming`: disable block streaming for this channel.
 - `channels.nextcloud-talk.blockStreamingCoalesce`: block streaming coalesce tuning.
 - `channels.nextcloud-talk.mediaMaxMb`: inbound media cap (MB).

package/docs/channels/nostr.md

@@ -1,20 +1,20 @@
 ---
 summary: "Nostr DM channel via NIP-04 encrypted messages"
 read_when:
-  - You want Pigbot to receive DMs via Nostr
+  - You want Moltbot to receive DMs via Nostr
   - You're setting up decentralized messaging
 ---
 # Nostr
 
 **Status:** Optional plugin (disabled by default).
 
-Nostr is a decentralized protocol for social networking. This channel enables Pigbot to receive and respond to encrypted direct messages (DMs) via NIP-04.
+Nostr is a decentralized protocol for social networking. This channel enables Moltbot to receive and respond to encrypted direct messages (DMs) via NIP-04.
 
 ## Install (on demand)
 
 ### Onboarding (recommended)
 
-- The onboarding wizard (`pigbot onboard`) and `pigbot channels add` list optional channel plugins.
+- The onboarding wizard (`moltbot onboard`) and `moltbot channels add` list optional channel plugins.
 - Selecting Nostr prompts you to install the plugin on demand.
 
 Install defaults:
@@ -27,13 +27,13 @@ You can always override the choice in the prompt.
 ### Manual install
 
 ```bash
-pigbot plugins install @pigbot/nostr
+moltbot plugins install @moltbot/nostr
 ```
 
 Use a local checkout (dev workflows):
 
 ```bash
-pigbot plugins install --link <path-to-pigbot>/extensions/nostr
+moltbot plugins install --link <path-to-moltbot>/extensions/nostr
 ```
 
 Restart the Gateway after installing or enabling plugins.
@@ -91,14 +91,14 @@ Example:
     "nostr": {
       "privateKey": "${NOSTR_PRIVATE_KEY}",
       "profile": {
-        "name": "pigbot",
-        "displayName": "Pigbot",
+        "name": "moltbot",
+        "displayName": "Moltbot",
         "about": "Personal assistant DM bot",
         "picture": "https://example.com/avatar.png",
         "banner": "https://example.com/banner.png",
         "website": "https://example.com",
-        "nip05": "pigbot@example.com",
-        "lud16": "pigbot@example.com"
+        "nip05": "moltbot@example.com",
+        "lud16": "moltbot@example.com"
       }
     }
   }