skykoi 2026.3.11 → 2026.3.13

package/docs/channels/bluebubbles.md

@@ -15,7 +15,7 @@ Status: bundled plugin that talks to the BlueBubbles macOS server over HTTP. **R
 
 - Runs on macOS via the BlueBubbles helper app ([bluebubbles.app](https://bluebubbles.app)).
 - Recommended/tested: macOS Sequoia (15). macOS Tahoe (26) works; edit is currently broken on Tahoe, and group icon updates may report success but not sync.
-- SkyKoi talks to it through its REST API (`GET /api/v1/ping`, `POST /message/text`, `POST /chat/:id/*`).
+- SKYKOI talks to it through its REST API (`GET /api/v1/ping`, `POST /message/text`, `POST /chat/:id/*`).
 - Incoming messages arrive via webhooks; outgoing replies, typing indicators, read receipts, and tapbacks are REST calls.
 - Attachments and stickers are ingested as inbound media (and surfaced to the agent when possible).
 - Pairing/allowlist works the same way as other channels (`/channels/pairing` etc) with `channels.bluebubbles.allowFrom` + pairing codes.
@@ -26,7 +26,7 @@ Status: bundled plugin that talks to the BlueBubbles macOS server over HTTP. **R
 
 1. Install the BlueBubbles server on your Mac (follow the instructions at [bluebubbles.app/install](https://bluebubbles.app/install)).
 2. In the BlueBubbles config, enable the web API and set a password.
-3. Run `SkyKoi onboard` and select BlueBubbles, or configure manually:
+3. Run `SKYKOI onboard` and select BlueBubbles, or configure manually:
 
    ```json5
    {
@@ -123,7 +123,7 @@ launchctl load ~/Library/LaunchAgents/com.user.poke-messages.plist
 BlueBubbles is available in the interactive setup wizard:
 
 ```
-SkyKoi onboard
+SKYKOI onboard
 ```
 
 The wizard prompts for:
@@ -137,7 +137,7 @@ The wizard prompts for:
 You can also add BlueBubbles via CLI:
 
 ```
-SkyKoi channels add bluebubbles --http-url http://192.168.1.100:1234 --password <password>
+SKYKOI channels add bluebubbles --http-url http://192.168.1.100:1234 --password <password>
 ```
 
 ## Access control (DMs + groups)
@@ -147,8 +147,8 @@ DMs:
 - Default: `channels.bluebubbles.dmPolicy = "pairing"`.
 - Unknown senders receive a pairing code; messages are ignored until approved (codes expire after 1 hour).
 - Approve via:
-  - `SkyKoi pairing list bluebubbles`
-  - `SkyKoi pairing approve bluebubbles <CODE>`
+  - `SKYKOI pairing list bluebubbles`
+  - `SKYKOI pairing approve bluebubbles <CODE>`
 - Pairing is the default token exchange. Details: [Pairing](/channels/pairing)
 
 Groups:
@@ -191,7 +191,7 @@ Per-group configuration:
 
 - **Typing indicators**: Sent automatically before and during response generation.
 - **Read receipts**: Controlled by `channels.bluebubbles.sendReadReceipts` (default: `true`).
-- **Typing indicators**: SkyKoi sends typing start events; BlueBubbles clears typing automatically on send or timeout (manual stop via DELETE is unreliable).
+- **Typing indicators**: SKYKOI sends typing start events; BlueBubbles clears typing automatically on send or timeout (manual stop via DELETE is unreliable).
 
 ```json5
 {
@@ -246,7 +246,7 @@ Available actions:
 
 ### Message IDs (short vs full)
 
-SkyKoi may surface _short_ message IDs (e.g., `1`, `2`) to save tokens.
+SKYKOI may surface _short_ message IDs (e.g., `1`, `2`) to save tokens.
 
 - `MessageSid` / `ReplyToId` can be short IDs.
 - `MessageSidFull` / `ReplyToIdFull` contain the provider full IDs.
@@ -318,7 +318,7 @@ Prefer `chat_guid` for stable routing:
 - `chat_id:123`
 - `chat_identifier:...`
 - Direct handles: `+15555550123`, `user@example.com`
-  - If a direct handle does not have an existing DM chat, SkyKoi will create one via `POST /api/v1/chat/new`. This requires the BlueBubbles Private API to be enabled.
+  - If a direct handle does not have an existing DM chat, SKYKOI will create one via `POST /api/v1/chat/new`. This requires the BlueBubbles Private API to be enabled.
 
 ## Security
 
@@ -330,11 +330,11 @@ Prefer `chat_guid` for stable routing:
 ## Troubleshooting
 
 - If typing/read events stop working, check the BlueBubbles webhook logs and verify the gateway path matches `channels.bluebubbles.webhookPath`.
-- Pairing codes expire after one hour; use `SkyKoi pairing list bluebubbles` and `SkyKoi pairing approve bluebubbles <code>`.
+- Pairing codes expire after one hour; use `SKYKOI pairing list bluebubbles` and `SKYKOI pairing approve bluebubbles <code>`.
 - Reactions require the BlueBubbles private API (`POST /api/v1/message/react`); ensure the server version exposes it.
 - Edit/unsend require macOS 13+ and a compatible BlueBubbles server version. On macOS 26 (Tahoe), edit is currently broken due to private API changes.
 - Group icon updates can be flaky on macOS 26 (Tahoe): the API may return success but the new icon does not sync.
-- SkyKoi auto-hides known-broken actions based on the BlueBubbles server's macOS version. If edit still appears on macOS 26 (Tahoe), disable it manually with `channels.bluebubbles.actions.edit=false`.
-- For status/health info: `SkyKoi status --all` or `SkyKoi status --deep`.
+- SKYKOI auto-hides known-broken actions based on the BlueBubbles server's macOS version. If edit still appears on macOS 26 (Tahoe), disable it manually with `channels.bluebubbles.actions.edit=false`.
+- For status/health info: `SKYKOI status --all` or `SKYKOI status --deep`.
 
 For general channel workflow reference, see [Channels](/channels) and the [Plugins](/tools/plugin) guide.

package/docs/channels/broadcast-groups.md

@@ -18,7 +18,7 @@ Broadcast Groups enable multiple agents to process and respond to the same messa
 
 Current scope: **WhatsApp only** (web channel).
 
-Broadcast groups are evaluated after channel allowlists and group activation rules. In WhatsApp groups, this means broadcasts happen when SkyKoi would normally reply (for example: on mention, depending on your group settings).
+Broadcast groups are evaluated after channel allowlists and group activation rules. In WhatsApp groups, this means broadcasts happen when SKYKOI would normally reply (for example: on mention, depending on your group settings).
 
 ## Use Cases
 
@@ -83,7 +83,7 @@ Add a top-level `broadcast` section (next to `bindings`). Keys are WhatsApp peer
 }
 ```
 
-**Result:** When SkyKoi would reply in this chat, it will run all three agents.
+**Result:** When SKYKOI would reply in this chat, it will run all three agents.
 
 ### Processing Strategy
 
@@ -192,7 +192,7 @@ In group `120363403215116621@g.us` with agents `["alfred", "baerbel"]`:
 ```
 Session: agent:alfred:whatsapp:group:120363403215116621@g.us
 History: [user message, alfred's previous responses]
-Workspace: /Users/pascal/SkyKoi-alfred/
+Workspace: /Users/pascal/SKYKOI-alfred/
 Tools: read, write, exec
 ```
 
@@ -201,7 +201,7 @@ Tools: read, write, exec
 ```
 Session: agent:baerbel:whatsapp:group:120363403215116621@g.us
 History: [user message, baerbel's previous responses]
-Workspace: /Users/pascal/SkyKoi-baerbel/
+Workspace: /Users/pascal/SKYKOI-baerbel/
 Tools: read only
 ```
 
@@ -317,7 +317,7 @@ Broadcast groups work alongside existing routing:
 **Debug:**
 
 ```bash
-tail -f ~/.skykoi/logs/gateway.log | grep broadcast
+tail -f ~/.SKYKOI/logs/gateway.log | grep broadcast
 ```
 
 ### Only One Agent Responding
@@ -403,7 +403,7 @@ tail -f ~/.skykoi/logs/gateway.log | grep broadcast
 ### Config Schema
 
 ```typescript
-interface SkyKoiConfig {
+interface SKYKOIConfig {
   broadcast?: {
     strategy?: "parallel" | "sequential";
     [peerId: string]: string[];

package/docs/channels/channel-routing.md

@@ -7,7 +7,7 @@ title: "Channel Routing"
 
 # Channels & routing
 
-SkyKoi routes replies **back to the channel where a message came from**. The
+SKYKOI 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.
 
@@ -54,7 +54,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 SkyKoi would normally reply** (for example: in WhatsApp groups, after mention/activation gating).
+Broadcast groups let you run **multiple agents** for the same peer **when SKYKOI would normally reply** (for example: in WhatsApp groups, after mention/activation gating).
 
 Config:
 
@@ -80,7 +80,7 @@ Example:
 ```json5
 {
   agents: {
-    list: [{ id: "support", name: "Support", workspace: "~/.skykoi/workspace-support" }],
+    list: [{ id: "support", name: "Support", workspace: "~/.SKYKOI/workspace-support" }],
   },
   bindings: [
     { match: { channel: "slack", teamId: "T123" }, agentId: "support" },
@@ -91,9 +91,9 @@ Example:
 
 ## Session storage
 
-Session stores live under the state directory (default `~/.skykoi`):
+Session stores live under the state directory (default `~/.SKYKOI`):
 
-- `~/.skykoi/agents/<agentId>/sessions/sessions.json`
+- `~/.SKYKOI/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/channels/discord.md

@@ -13,7 +13,7 @@ Status: ready for DM and guild text channels via the official Discord bot gatewa
 
 1. Create a Discord bot and copy the bot token.
 2. In the Discord app settings, enable **Message Content Intent** (and **Server Members Intent** if you plan to use allowlists or name lookups).
-3. Set the token for SkyKoi:
+3. Set the token for SKYKOI:
    - Env: `DISCORD_BOT_TOKEN=...`
    - Or config: `channels.discord.token: "..."`.
    - If both are set, config takes precedence (env fallback is default-account only).
@@ -36,7 +36,7 @@ Minimal config:
 
 ## Goals
 
-- Talk to SkyKoi via Discord DMs or guild channels.
+- Talk to SKYKOI via Discord DMs or guild channels.
 - Direct chats collapse into the agent's main session (default `agent:main:main`); guild channels stay isolated as `agent:<agentId>:discord:channel:<channelId>` (display names use `discord:<guildSlug>#<channelSlug>`).
 - Group DMs are ignored by default; enable via `channels.discord.dm.groupEnabled` and optionally restrict by `channels.discord.dm.groupChannels`.
 - Keep routing deterministic: replies always go back to the channel they arrived on.
@@ -45,12 +45,12 @@ Minimal config:
 
 1. Create a Discord application → Bot, enable the intents you need (DMs + guild messages + message content), and grab the bot token.
 2. Invite the bot to your server with the permissions required to read/send messages where you want to use it.
-3. Configure SkyKoi with `channels.discord.token` (or `DISCORD_BOT_TOKEN` as a fallback).
+3. Configure SKYKOI with `channels.discord.token` (or `DISCORD_BOT_TOKEN` as a fallback).
 4. Run the gateway; it auto-starts the Discord channel when a token is available (config first, env fallback) and `channels.discord.enabled` is not `false`.
    - If you prefer env vars, set `DISCORD_BOT_TOKEN` (a config block is optional).
 5. Direct chats: use `user:<id>` (or a `<@id>` mention) when delivering; all turns land in the shared `main` session. Bare numeric IDs are ambiguous and rejected.
 6. Guild channels: use `channel:<channelId>` for delivery. Mentions are required by default and can be set per guild or per channel.
-7. Direct chats: secure by default via `channels.discord.dm.policy` (default: `"pairing"`). Unknown senders get a pairing code (expires after 1 hour); approve via `SkyKoi pairing approve discord <code>`.
+7. Direct chats: secure by default via `channels.discord.dm.policy` (default: `"pairing"`). Unknown senders get a pairing code (expires after 1 hour); approve via `SKYKOI pairing approve discord <code>`.
    - To keep old “open to anyone” behavior: set `channels.discord.dm.policy="open"` and `channels.discord.dm.allowFrom=["*"]`.
    - To hard-allowlist: set `channels.discord.dm.policy="allowlist"` and list senders in `channels.discord.dm.allowFrom`.
    - To ignore all DMs: set `channels.discord.dm.enabled=false` or `channels.discord.dm.policy="disabled"`.
@@ -82,7 +82,7 @@ Disable with:
 
 ## How to create your own bot
 
-This is the “Discord Developer Portal” setup for running SkyKoi in a server (guild) channel like `#help`.
+This is the “Discord Developer Portal” setup for running SKYKOI in a server (guild) channel like `#help`.
 
 ### 1) Create the Discord app + bot user
 
@@ -91,7 +91,7 @@ This is the “Discord Developer Portal” setup for running SkyKoi in a server
    - **Bot** → **Add Bot**
    - Copy the **Bot Token** (this is what you put in `DISCORD_BOT_TOKEN`)
 
-### 2) Enable the gateway intents SkyKoi needs
+### 2) Enable the gateway intents SKYKOI needs
 
 Discord blocks “privileged intents” unless you explicitly enable them.
 
@@ -127,7 +127,7 @@ Copy the generated URL, open it, pick your server, and install the bot.
 
 ### 4) Get the ids (guild/user/channel)
 
-Discord uses numeric ids everywhere; SkyKoi config prefers ids.
+Discord uses numeric ids everywhere; SKYKOI config prefers ids.
 
 1. Discord (desktop/web) → **User Settings** → **Advanced** → enable **Developer Mode**
 2. Right-click:
@@ -135,7 +135,7 @@ Discord uses numeric ids everywhere; SkyKoi config prefers ids.
    - Channel (e.g. `#help`) → **Copy Channel ID**
    - Your user → **Copy User ID**
 
-### 5) Configure SkyKoi
+### 5) Configure SKYKOI
 
 #### Token
 
@@ -196,7 +196,7 @@ Notes:
 - If `channels` is present, any channel not listed is denied by default.
 - Use a `"*"` channel entry to apply defaults across all channels; explicit channel entries override the wildcard.
 - Threads inherit parent channel config (allowlist, `requireMention`, skills, prompts, etc.) unless you add the thread channel id explicitly.
-- Owner hint: when a per-guild or per-channel `users` allowlist matches the sender, SkyKoi treats that sender as the owner in the system prompt. For a global owner across channels, set `commands.ownerAllowFrom`.
+- Owner hint: when a per-guild or per-channel `users` allowlist matches the sender, SKYKOI treats that sender as the owner in the system prompt. For a global owner across channels, set `commands.ownerAllowFrom`.
 - Bot-authored messages are ignored by default; set `channels.discord.allowBots=true` to allow them (own messages remain filtered).
 - Warning: If you allow replies to other bots (`channels.discord.allowBots=true`), prevent bot-to-bot reply loops with `requireMention`, `channels.discord.guilds.*.channels.<id>.users` allowlists, and/or clear guardrails in `AGENTS.md` and `SOUL.md`.
 
@@ -208,7 +208,7 @@ Notes:
 
 ### Troubleshooting
 
-- First: run `SkyKoi doctor` and `SkyKoi channels status --probe` (actionable warnings + quick audits).
+- First: run `SKYKOI doctor` and `SKYKOI channels status --probe` (actionable warnings + quick audits).
 - **“Used disallowed intents”**: enable **Message Content Intent** (and likely **Server Members Intent**) in the Developer Portal, then restart the gateway.
 - **Bot connects but never replies in a guild channel**:
   - Missing **Message Content Intent**, or
@@ -287,12 +287,12 @@ Outbound Discord API calls retry on rate limits (429) using Discord `retry_after
         policy: "pairing", // pairing | allowlist | open | disabled
         allowFrom: ["123456789012345678", "steipete"],
         groupEnabled: false,
-        groupChannels: ["SkyKoi-dm"],
+        groupChannels: ["SKYKOI-dm"],
       },
       guilds: {
         "*": { requireMention: true },
         "123456789012345678": {
-          slug: "friends-of-SkyKoi",
+          slug: "friends-of-SKYKOI",
           requireMention: false,
           reactionNotifications: "own",
           users: ["987654321098765432", "steipete"],
@@ -368,7 +368,7 @@ Reaction notifications use `guilds.<id>.reactionNotifications`:
 ### PluralKit (PK) support
 
 Enable PK lookups so proxied messages resolve to the underlying system + member.
-When enabled, SkyKoi uses the member identity for allowlists and labels the
+When enabled, SKYKOI uses the member identity for allowlists and labels the
 sender as `Member (PK:System)` to avoid accidental Discord pings.
 
 ```json5
@@ -442,14 +442,14 @@ Allowlist matching notes:
 - When `guilds.<id>.channels` is omitted, all channels in the allowlisted guild are allowed.
 - To allow **no channels**, set `channels.discord.groupPolicy: "disabled"` (or keep an empty allowlist).
 - The configure wizard accepts `Guild/Channel` names (public + private) and resolves them to IDs when possible.
-- On startup, SkyKoi resolves channel/user names in allowlists to IDs (when the bot can search members)
+- On startup, SKYKOI resolves channel/user names in allowlists to IDs (when the bot can search members)
   and logs the mapping; unresolved entries are kept as typed.
 
 Native command notes:
 
-- The registered commands mirror SkyKoi’s chat commands.
+- The registered commands mirror SKYKOI’s chat commands.
 - Native commands honor the same allowlists as DMs/guild messages (`channels.discord.dm.allowFrom`, `channels.discord.guilds`, per-channel rules).
-- Slash commands may still be visible in Discord UI to users who aren’t allowlisted; SkyKoi enforces allowlists on execution and replies “not authorized”.
+- Slash commands may still be visible in Discord UI to users who aren’t allowlisted; SKYKOI enforces allowlists on execution and replies “not authorized”.
 
 ## Tool actions
 
@@ -473,4 +473,4 @@ Emoji can be unicode (e.g., `✅`) or custom emoji syntax like `<:party_blob:123
 
 - Treat the bot token like a password; prefer the `DISCORD_BOT_TOKEN` env var on supervised hosts or lock down the config file permissions.
 - Only grant the bot permissions it needs (typically Read/Send Messages).
-- If the bot is stuck or rate limited, restart the gateway (`SkyKoi gateway --force`) after confirming no other processes own the Discord session.
+- If the bot is stuck or rate limited, restart the gateway (`SKYKOI gateway --force`) after confirming no other processes own the Discord session.

package/docs/channels/feishu.md

@@ -8,7 +8,7 @@ title: Feishu
 
 # Feishu bot
 
-Feishu (Lark) is a team chat platform used by companies for messaging and collaboration. This plugin connects SkyKoi to a Feishu/Lark bot using the platform’s WebSocket event subscription so messages can be received without exposing a public webhook URL.
+Feishu (Lark) is a team chat platform used by companies for messaging and collaboration. This plugin connects SKYKOI to a Feishu/Lark bot using the platform’s WebSocket event subscription so messages can be received without exposing a public webhook URL.
 
 ---
 
@@ -17,13 +17,13 @@ Feishu (Lark) is a team chat platform used by companies for messaging and collab
 Install the Feishu plugin:
 
 ```bash
-SkyKoi plugins install @SkyKoi/feishu
+SKYKOI plugins install @SKYKOI/feishu
 ```
 
 Local checkout (when running from a git repo):
 
 ```bash
-SkyKoi plugins install ./extensions/feishu
+SKYKOI plugins install ./extensions/feishu
 ```
 
 ---
@@ -34,38 +34,38 @@ There are two ways to add the Feishu channel:
 
 ### Method 1: onboarding wizard (recommended)
 
-If you just installed SkyKoi, run the wizard:
+If you just installed SKYKOI, run the wizard:
 
 ```bash
-SkyKoi onboard
+SKYKOI onboard
 ```
 
 The wizard guides you through:
 
 1. Creating a Feishu app and collecting credentials
-2. Configuring app credentials in SkyKoi
+2. Configuring app credentials in SKYKOI
 3. Starting the gateway
 
 ✅ **After configuration**, check gateway status:
 
-- `SkyKoi gateway status`
-- `SkyKoi logs --follow`
+- `SKYKOI gateway status`
+- `SKYKOI logs --follow`
 
 ### Method 2: CLI setup
 
 If you already completed initial install, add the channel via CLI:
 
 ```bash
-SkyKoi channels add
+SKYKOI channels add
 ```
 
 Choose **Feishu**, then enter the App ID and App Secret.
 
 ✅ **After configuration**, manage the gateway:
 
-- `SkyKoi gateway status`
-- `SkyKoi gateway restart`
-- `SkyKoi logs --follow`
+- `SKYKOI gateway status`
+- `SKYKOI gateway restart`
+- `SKYKOI logs --follow`
 
 ---
 
@@ -141,8 +141,8 @@ In **App Capability** > **Bot**:
 
 ⚠️ **Important:** before setting event subscription, make sure:
 
-1. You already ran `SkyKoi channels add` for Feishu
-2. The gateway is running (`SkyKoi gateway status`)
+1. You already ran `SKYKOI channels add` for Feishu
+2. The gateway is running (`SKYKOI gateway status`)
 
 In **Event Subscription**:
 
@@ -161,19 +161,19 @@ In **Event Subscription**:
 
 ---
 
-## Step 2: Configure SkyKoi
+## Step 2: Configure SKYKOI
 
 ### Configure with the wizard (recommended)
 
 ```bash
-SkyKoi channels add
+SKYKOI channels add
 ```
 
 Choose **Feishu** and paste your App ID + App Secret.
 
 ### Configure via config file
 
-Edit `~/.skykoi/skykoi.json`:
+Edit `~/.SKYKOI/SKYKOI.json`:
 
 ```json5
 {
@@ -227,7 +227,7 @@ If your tenant is on Lark (international), set the domain to `lark` (or a full d
 ### 1. Start the gateway
 
 ```bash
-SkyKoi gateway
+SKYKOI gateway
 ```
 
 ### 2. Send a test message
@@ -239,7 +239,7 @@ In Feishu, find your bot and send a message.
 By default, the bot replies with a pairing code. Approve it:
 
 ```bash
-SkyKoi pairing approve feishu <CODE>
+SKYKOI pairing approve feishu <CODE>
 ```
 
 After approval, you can chat normally.
@@ -263,8 +263,8 @@ After approval, you can chat normally.
 - **Approve pairing**:
 
   ```bash
-  SkyKoi pairing list feishu
-  SkyKoi pairing approve feishu <CODE>
+  SKYKOI pairing list feishu
+  SKYKOI pairing approve feishu <CODE>
   ```
 
 - **Allowlist mode**: set `channels.feishu.allowFrom` with allowed Open IDs
@@ -337,7 +337,7 @@ Group IDs look like `oc_xxx`.
 **Method 1 (recommended)**
 
 1. Start the gateway and @mention the bot in the group
-2. Run `SkyKoi logs --follow` and look for `chat_id`
+2. Run `SKYKOI logs --follow` and look for `chat_id`
 
 **Method 2**
 
@@ -350,14 +350,14 @@ User IDs look like `ou_xxx`.
 **Method 1 (recommended)**
 
 1. Start the gateway and DM the bot
-2. Run `SkyKoi logs --follow` and look for `open_id`
+2. Run `SKYKOI logs --follow` and look for `open_id`
 
 **Method 2**
 
 Check pairing requests for user Open IDs:
 
 ```bash
-SkyKoi pairing list feishu
+SKYKOI pairing list feishu
 ```
 
 ---
@@ -376,11 +376,11 @@ SkyKoi pairing list feishu
 
 | Command                    | Description                   |
 | -------------------------- | ----------------------------- |
-| `SkyKoi gateway status`  | Show gateway status           |
-| `SkyKoi gateway install` | Install/start gateway service |
-| `SkyKoi gateway stop`    | Stop gateway service          |
-| `SkyKoi gateway restart` | Restart gateway service       |
-| `SkyKoi logs --follow`   | Tail gateway logs             |
+| `SKYKOI gateway status`  | Show gateway status           |
+| `SKYKOI gateway install` | Install/start gateway service |
+| `SKYKOI gateway stop`    | Stop gateway service          |
+| `SKYKOI gateway restart` | Restart gateway service       |
+| `SKYKOI logs --follow`   | Tail gateway logs             |
 
 ---
 
@@ -391,7 +391,7 @@ SkyKoi pairing list feishu
 1. Ensure the bot is added to the group
 2. Ensure you @mention the bot (default behavior)
 3. Check `groupPolicy` is not set to `"disabled"`
-4. Check logs: `SkyKoi logs --follow`
+4. Check logs: `SKYKOI logs --follow`
 
 ### Bot does not receive messages
 
@@ -399,8 +399,8 @@ SkyKoi pairing list feishu
 2. Ensure event subscription includes `im.message.receive_v1`
 3. Ensure **long connection** is enabled
 4. Ensure app permissions are complete
-5. Ensure the gateway is running: `SkyKoi gateway status`
-6. Check logs: `SkyKoi logs --follow`
+5. Ensure the gateway is running: `SKYKOI gateway status`
+6. Check logs: `SKYKOI logs --follow`
 
 ### App Secret leak
 
@@ -476,12 +476,12 @@ Use `bindings` to route Feishu DMs or groups to different agents.
       {
         id: "clawd-fan",
         workspace: "/home/user/clawd-fan",
-        agentDir: "/home/user/.skykoi/agents/clawd-fan/agent",
+        agentDir: "/home/user/.SKYKOI/agents/clawd-fan/agent",
       },
       {
         id: "clawd-xi",
         workspace: "/home/user/clawd-xi",
-        agentDir: "/home/user/.skykoi/agents/clawd-xi/agent",
+        agentDir: "/home/user/.SKYKOI/agents/clawd-xi/agent",
       },
     ],
   },

package/docs/channels/googlechat.md

@@ -16,7 +16,7 @@ Status: ready for DMs + spaces via Google Chat API webhooks (HTTP only).
    - Enable the API if it is not already enabled.
 2. Create a **Service Account**:
    - Press **Create Credentials** > **Service Account**.
-   - Name it whatever you want (e.g., `SkyKoi-chat`).
+   - Name it whatever you want (e.g., `SKYKOI-chat`).
    - Leave permissions blank (press **Continue**).
    - Leave principals with access blank (press **Done**).
 3. Create and download the **JSON Key**:
@@ -24,17 +24,17 @@ Status: ready for DMs + spaces via Google Chat API webhooks (HTTP only).
    - Go to the **Keys** tab.
    - Click **Add Key** > **Create new key**.
    - Select **JSON** and press **Create**.
-4. Store the downloaded JSON file on your gateway host (e.g., `~/.skykoi/googlechat-service-account.json`).
+4. Store the downloaded JSON file on your gateway host (e.g., `~/.SKYKOI/googlechat-service-account.json`).
 5. Create a Google Chat app in the [Google Cloud Console Chat Configuration](https://console.cloud.google.com/apis/api/chat.googleapis.com/hangouts-chat):
    - Fill in the **Application info**:
-     - **App name**: (e.g. `SkyKoi`)
-     - **Avatar URL**: (e.g. `https://skykoi.com/logo.png`)
+     - **App name**: (e.g. `SKYKOI`)
+     - **Avatar URL**: (e.g. `https://SKYKOI.com/logo.png`)
      - **Description**: (e.g. `Personal AI Assistant`)
    - Enable **Interactive features**.
    - Under **Functionality**, check **Join spaces and group conversations**.
    - Under **Connection settings**, select **HTTP endpoint URL**.
    - Under **Triggers**, select **Use a common HTTP endpoint URL for all triggers** and set it to your gateway's public URL followed by `/googlechat`.
-     - _Tip: Run `skykoi status` to find your gateway's public URL._
+     - _Tip: Run `SKYKOI status` to find your gateway's public URL._
    - Under **Visibility**, check **Make this Chat app available to specific people and groups in <Your Domain>**.
    - Enter your email address (e.g. `user@example.com`) in the text box.
    - Click **Save** at the bottom.
@@ -43,7 +43,7 @@ Status: ready for DMs + spaces via Google Chat API webhooks (HTTP only).
    - Look for the **App status** section (usually near the top or bottom after saving).
    - Change the status to **Live - available to users**.
    - Click **Save** again.
-7. Configure SkyKoi with the service account path + webhook audience:
+7. Configure SKYKOI with the service account path + webhook audience:
    - Env: `GOOGLE_CHAT_SERVICE_ACCOUNT_FILE=/path/to/service-account.json`
    - Or config: `channels.googlechat.serviceAccountFile: "/path/to/service-account.json"`.
 8. Set the webhook audience type + value (matches your Chat app config).
@@ -63,7 +63,7 @@ Once the gateway is running and your email is added to the visibility list:
 
 ## Public URL (Webhook-only)
 
-Google Chat webhooks require a public HTTPS endpoint. For security, **only expose the `/googlechat` path** to the internet. Keep the SkyKoi dashboard and other sensitive endpoints on your private network.
+Google Chat webhooks require a public HTTPS endpoint. For security, **only expose the `/googlechat` path** to the internet. Keep the SKYKOI dashboard and other sensitive endpoints on your private network.
 
 ### Option A: Tailscale Funnel (Recommended)
 
@@ -127,7 +127,7 @@ your-domain.com {
 }
 ```
 
-With this config, any request to `your-domain.com/` will be ignored or returned as 404, while `your-domain.com/googlechat` is safely routed to SkyKoi.
+With this config, any request to `your-domain.com/` will be ignored or returned as 404, while `your-domain.com/googlechat` is safely routed to SKYKOI.
 
 ### Option C: Cloudflare Tunnel
 
@@ -139,14 +139,14 @@ Configure your tunnel's ingress rules to only route the webhook path:
 ## How it works
 
 1. Google Chat sends webhook POSTs to the gateway. Each request includes an `Authorization: Bearer <token>` header.
-2. SkyKoi verifies the token against the configured `audienceType` + `audience`:
+2. SKYKOI verifies the token against the configured `audienceType` + `audience`:
    - `audienceType: "app-url"` → audience is your HTTPS webhook URL.
    - `audienceType: "project-number"` → audience is the Cloud project number.
 3. Messages are routed by space:
    - DMs use session key `agent:<agentId>:googlechat:dm:<spaceId>`.
    - Spaces use session key `agent:<agentId>:googlechat:group:<spaceId>`.
 4. DM access is pairing by default. Unknown senders receive a pairing code; approve with:
-   - `skykoi pairing approve googlechat <code>`
+   - `SKYKOI pairing approve googlechat <code>`
 5. Group spaces require @-mention by default. Use `botUser` if mention detection needs the app’s user name.
 
 ## Targets
@@ -212,7 +212,7 @@ This means the webhook handler isn't registered. Common causes:
 1. **Channel not configured**: The `channels.googlechat` section is missing from your config. Verify with:
 
    ```bash
-   skykoi config get channels.googlechat
+   SKYKOI config get channels.googlechat
    ```
 
    If it returns "Config path not found", add the configuration (see [Config highlights](#config-highlights)).
@@ -220,7 +220,7 @@ This means the webhook handler isn't registered. Common causes:
 2. **Plugin not enabled**: Check plugin status:
 
    ```bash
-   SkyKoi plugins list | grep googlechat
+   SKYKOI plugins list | grep googlechat
    ```
 
    If it shows "disabled", add `plugins.entries.googlechat.enabled: true` to your config.
@@ -228,22 +228,22 @@ This means the webhook handler isn't registered. Common causes:
 3. **Gateway not restarted**: After adding config, restart the gateway:
 
    ```bash
-   skykoi gateway restart
+   SKYKOI gateway restart
    ```
 
 Verify the channel is running:
 
 ```bash
-skykoi channels status
+SKYKOI channels status
 # Should show: Google Chat default: enabled, configured, ...
 ```
 
 ### Other issues
 
-- Check `skykoi channels status --probe` for auth errors or missing audience config.
+- Check `SKYKOI channels status --probe` for auth errors or missing audience config.
 - If no messages arrive, confirm the Chat app's webhook URL + event subscriptions.
 - If mention gating blocks replies, set `botUser` to the app's user resource name and verify `requireMention`.
-- Use `skykoi logs --follow` while sending a test message to see if requests reach the gateway.
+- Use `SKYKOI logs --follow` while sending a test message to see if requests reach the gateway.
 
 Related docs: