skykoi 2026.3.11 → 2026.3.13

package/docs/help/scripts.md

@@ -14,7 +14,7 @@ Use these when a task is clearly tied to a script; otherwise prefer the CLI.
 ## Conventions
 
 - Scripts are **optional** unless referenced in docs or release checklists.
-- Prefer CLI surfaces when they exist (example: auth monitoring uses `SkyKoi models status --check`).
+- Prefer CLI surfaces when they exist (example: auth monitoring uses `SKYKOI models status --check`).
 - Assume scripts are host‑specific; read them before running on a new machine.
 
 ## Auth monitoring scripts

package/docs/help/testing.md

@@ -9,7 +9,7 @@ title: "Testing"
 
 # Testing
 
-SkyKoi has three Vitest suites (unit/integration, e2e, live) and a small set of Docker runners.
+SKYKOI has three Vitest suites (unit/integration, e2e, live) and a small set of Docker runners.
 
 This doc is a “how we test” guide:
 
@@ -120,7 +120,7 @@ Live tests are split into two layers so we can isolate failures:
   - Separates “provider API is broken / key is invalid” from “gateway agent pipeline is broken”
   - Contains small, isolated regressions (example: OpenAI Responses/Codex Responses reasoning replay + tool-call flows)
 
-### Layer 2: Gateway + dev agent smoke (what “@SkyKoi” actually does)
+### Layer 2: Gateway + dev agent smoke (what “@SKYKOI” actually does)
 
 - Test: `src/gateway/gateway-models.profiles.live.test.ts`
 - Goal:
@@ -157,8 +157,8 @@ Live tests are split into two layers so we can isolate failures:
 Tip: to see what you can test on your machine (and the exact `provider/model` ids), run:
 
 ```bash
-SkyKoi models list
-SkyKoi models list --json
+SKYKOI models list
+SKYKOI models list --json
 ```
 
 ## Live: Anthropic setup-token smoke
@@ -177,7 +177,7 @@ SkyKoi models list --json
 Setup example:
 
 ```bash
-SkyKoi models auth paste-token --provider anthropic --profile-id anthropic:setup-token-test
+SKYKOI models auth paste-token --provider anthropic --profile-id anthropic:setup-token-test
 SKYKOI_LIVE_SETUP_TOKEN=1 SKYKOI_LIVE_SETUP_TOKEN_PROFILE=anthropic:setup-token-test pnpm test:live src/agents/anthropic.setup-token.live.test.ts
 ```
 
@@ -235,8 +235,8 @@ Notes:
 - `google-antigravity/...` uses the Antigravity OAuth bridge (Cloud Code Assist-style agent endpoint).
 - `google-gemini-cli/...` uses the local Gemini CLI on your machine (separate auth + tooling quirks).
 - Gemini API vs Gemini CLI:
-  - API: SkyKoi calls Google’s hosted Gemini API over HTTP (API key / profile auth); this is what most users mean by “Gemini”.
-  - CLI: SkyKoi shells out to a local `gemini` binary; it has its own auth and can behave differently (streaming/tool support/version skew).
+  - API: SKYKOI calls Google’s hosted Gemini API over HTTP (API key / profile auth); this is what most users mean by “Gemini”.
+  - CLI: SKYKOI shells out to a local `gemini` binary; it has its own auth and can behave differently (streaming/tool support/version skew).
 
 ## Live: model matrix (what we cover)
 
@@ -282,7 +282,7 @@ Include at least one image-capable model in `SKYKOI_LIVE_GATEWAY_MODELS` (Claude
 
 If you have keys enabled, we also support testing via:
 
-- OpenRouter: `openrouter/...` (hundreds of models; use `SkyKoi models scan` to find tool+image capable candidates)
+- OpenRouter: `openrouter/...` (hundreds of models; use `SKYKOI models scan` to find tool+image capable candidates)
 - OpenCode Zen: `opencode/...` (auth via `OPENCODE_API_KEY` / `OPENCODE_ZEN_API_KEY`)
 
 More providers you can include in the live matrix (if you have creds/config):
@@ -297,10 +297,10 @@ Tip: don’t try to hardcode “all models” in docs. The authoritative list is
 Live tests discover credentials the same way the CLI does. Practical implications:
 
 - If the CLI works, live tests should find the same keys.
-- If a live test says “no creds”, debug the same way you’d debug `SkyKoi models list` / model selection.
+- If a live test says “no creds”, debug the same way you’d debug `SKYKOI models list` / model selection.
 
-- Profile store: `~/.skykoi/credentials/` (preferred; what “profile keys” means in the tests)
-- Config: `~/.skykoi/skykoi.json` (or `SKYKOI_CONFIG_PATH`)
+- Profile store: `~/.SKYKOI/credentials/` (preferred; what “profile keys” means in the tests)
+- Config: `~/.SKYKOI/SKYKOI.json` (or `SKYKOI_CONFIG_PATH`)
 
 If you want to rely on env keys (e.g. exported in your `~/.profile`), run local tests after `source ~/.profile`, or use the Docker runners below (they can mount `~/.profile` into the container).
 
@@ -321,8 +321,8 @@ These run `pnpm test:live` inside the repo Docker image, mounting your local con
 
 Useful env vars:
 
-- `SKYKOI_CONFIG_DIR=...` (default: `~/.skykoi`) mounted to `/home/node/.skykoi`
-- `SKYKOI_WORKSPACE_DIR=...` (default: `~/.skykoi/workspace`) mounted to `/home/node/.skykoi/workspace`
+- `SKYKOI_CONFIG_DIR=...` (default: `~/.SKYKOI`) mounted to `/home/node/.SKYKOI`
+- `SKYKOI_WORKSPACE_DIR=...` (default: `~/.SKYKOI/workspace`) mounted to `/home/node/.SKYKOI/workspace`
 - `SKYKOI_PROFILE_FILE=...` (default: `~/.profile`) mounted to `/home/node/.profile` and sourced before running tests
 - `SKYKOI_LIVE_GATEWAY_MODELS=...` / `SKYKOI_LIVE_MODELS=...` to narrow the run
 - `SKYKOI_LIVE_REQUIRE_PROFILE_KEYS=1` to ensure creds come from the profile store (not env)

package/docs/help/troubleshooting.md

@@ -1,7 +1,7 @@
 ---
-summary: "Symptom first troubleshooting hub for SkyKoi"
+summary: "Symptom first troubleshooting hub for SKYKOI"
 read_when:
-  - SkyKoi is not working and you need the fastest path to a fix
+  - SKYKOI is not working and you need the fastest path to a fix
   - You want a triage flow before diving into deep runbooks
 title: "Troubleshooting"
 ---
@@ -15,30 +15,30 @@ If you only have 2 minutes, use this page as a triage front door.
 Run this exact ladder in order:
 
 ```bash
-SkyKoi status
-SkyKoi status --all
-SkyKoi gateway probe
-SkyKoi gateway status
-SkyKoi doctor
-SkyKoi channels status --probe
-SkyKoi logs --follow
+SKYKOI status
+SKYKOI status --all
+SKYKOI gateway probe
+SKYKOI gateway status
+SKYKOI doctor
+SKYKOI channels status --probe
+SKYKOI logs --follow
 ```
 
 Good output in one line:
 
-- `SkyKoi status` → shows configured channels and no obvious auth errors.
-- `SkyKoi status --all` → full report is present and shareable.
-- `SkyKoi gateway probe` → expected gateway target is reachable.
-- `SkyKoi gateway status` → `Runtime: running` and `RPC probe: ok`.
-- `SkyKoi doctor` → no blocking config/service errors.
-- `SkyKoi channels status --probe` → channels report `connected` or `ready`.
-- `SkyKoi logs --follow` → steady activity, no repeating fatal errors.
+- `SKYKOI status` → shows configured channels and no obvious auth errors.
+- `SKYKOI status --all` → full report is present and shareable.
+- `SKYKOI gateway probe` → expected gateway target is reachable.
+- `SKYKOI gateway status` → `Runtime: running` and `RPC probe: ok`.
+- `SKYKOI doctor` → no blocking config/service errors.
+- `SKYKOI channels status --probe` → channels report `connected` or `ready`.
+- `SKYKOI logs --follow` → steady activity, no repeating fatal errors.
 
 ## Decision tree
 
 ```mermaid
 flowchart TD
-  A[SkyKoi is not working] --> B{What breaks first}
+  A[SKYKOI is not working] --> B{What breaks first}
   B --> C[No replies]
   B --> D[Dashboard or Control UI will not connect]
   B --> E[Gateway will not start or service not running]
@@ -59,11 +59,11 @@ flowchart TD
 <AccordionGroup>
   <Accordion title="No replies">
     ```bash
-    SkyKoi status
-    SkyKoi gateway status
-    SkyKoi channels status --probe
-    SkyKoi pairing list <channel>
-    SkyKoi logs --follow
+    SKYKOI status
+    SKYKOI gateway status
+    SKYKOI channels status --probe
+    SKYKOI pairing list <channel>
+    SKYKOI logs --follow
     ```
 
     Good output looks like:
@@ -89,16 +89,16 @@ flowchart TD
 
   <Accordion title="Dashboard or Control UI will not connect">
     ```bash
-    SkyKoi status
-    SkyKoi gateway status
-    SkyKoi logs --follow
-    SkyKoi doctor
-    SkyKoi channels status --probe
+    SKYKOI status
+    SKYKOI gateway status
+    SKYKOI logs --follow
+    SKYKOI doctor
+    SKYKOI channels status --probe
     ```
 
     Good output looks like:
 
-    - `Dashboard: http://...` is shown in `SkyKoi gateway status`
+    - `Dashboard: http://...` is shown in `SKYKOI gateway status`
     - `RPC probe: ok`
     - No auth loop in logs
 
@@ -118,11 +118,11 @@ flowchart TD
 
   <Accordion title="Gateway will not start or service installed but not running">
     ```bash
-    SkyKoi status
-    SkyKoi gateway status
-    SkyKoi logs --follow
-    SkyKoi doctor
-    SkyKoi channels status --probe
+    SKYKOI status
+    SKYKOI gateway status
+    SKYKOI logs --follow
+    SKYKOI doctor
+    SKYKOI channels status --probe
     ```
 
     Good output looks like:
@@ -147,11 +147,11 @@ flowchart TD
 
   <Accordion title="Channel connects but messages do not flow">
     ```bash
-    SkyKoi status
-    SkyKoi gateway status
-    SkyKoi logs --follow
-    SkyKoi doctor
-    SkyKoi channels status --probe
+    SKYKOI status
+    SKYKOI gateway status
+    SKYKOI logs --follow
+    SKYKOI doctor
+    SKYKOI channels status --probe
     ```
 
     Good output looks like:
@@ -175,12 +175,12 @@ flowchart TD
 
   <Accordion title="Cron or heartbeat did not fire or did not deliver">
     ```bash
-    SkyKoi status
-    SkyKoi gateway status
-    SkyKoi cron status
-    SkyKoi cron list
-    SkyKoi cron runs --id <jobId> --limit 20
-    SkyKoi logs --follow
+    SKYKOI status
+    SKYKOI gateway status
+    SKYKOI cron status
+    SKYKOI cron list
+    SKYKOI cron runs --id <jobId> --limit 20
+    SKYKOI logs --follow
     ```
 
     Good output looks like:
@@ -206,11 +206,11 @@ flowchart TD
 
   <Accordion title="Node is paired but tool fails camera canvas screen exec">
     ```bash
-    SkyKoi status
-    SkyKoi gateway status
-    SkyKoi nodes status
-    SkyKoi nodes describe --node <idOrNameOrIp>
-    SkyKoi logs --follow
+    SKYKOI status
+    SKYKOI gateway status
+    SKYKOI nodes status
+    SKYKOI nodes describe --node <idOrNameOrIp>
+    SKYKOI logs --follow
     ```
 
     Good output looks like:
@@ -236,17 +236,17 @@ flowchart TD
 
   <Accordion title="Browser tool fails">
     ```bash
-    SkyKoi status
-    SkyKoi gateway status
-    SkyKoi browser status
-    SkyKoi logs --follow
-    SkyKoi doctor
+    SKYKOI status
+    SKYKOI gateway status
+    SKYKOI browser status
+    SKYKOI logs --follow
+    SKYKOI doctor
     ```
 
     Good output looks like:
 
     - Browser status shows `running: true` and a chosen browser/profile.
-    - `SkyKoi` profile starts or `chrome` relay has an attached tab.
+    - `SKYKOI` profile starts or `chrome` relay has an attached tab.
 
     Common log signatures:
 

package/docs/hooks/soul-evil.md

@@ -15,7 +15,7 @@ a purge window or by random chance. It does **not** modify files on disk.
 
 When `agent:bootstrap` runs, the hook can replace the `SOUL.md` content in memory
 before the system prompt is assembled. If `SOUL_EVIL.md` is missing or empty,
-SkyKoi logs a warning and keeps the normal `SOUL.md`.
+SKYKOI logs a warning and keeps the normal `SOUL.md`.
 
 Sub-agent runs do **not** include `SOUL.md` in their bootstrap files, so this hook
 has no effect on sub-agents.
@@ -23,7 +23,7 @@ has no effect on sub-agents.
 ## Enable
 
 ```bash
-SkyKoi hooks enable soul-evil
+SKYKOI hooks enable soul-evil
 ```
 
 Then set the config:

package/docs/index.md

@@ -1,22 +1,22 @@
 ---
-summary: "SkyKoi is a multi-channel gateway for AI agents that runs on any OS."
+summary: "SKYKOI is a multi-channel gateway for AI agents that runs on any OS."
 read_when:
-  - Introducing SkyKoi to newcomers
-title: "SkyKoi"
+  - Introducing SKYKOI to newcomers
+title: "SKYKOI"
 ---
 
-# SkyKoi 🦞
+# SKYKOI 🦞
 
 <p align="center">
     <img
-        src="/assets/SkyKoi-logo-text-dark.png"
-        alt="SkyKoi"
+        src="/assets/SKYKOI-logo-text-dark.png"
+        alt="SKYKOI"
         width="500"
         class="dark:hidden"
     />
     <img
-        src="/assets/SkyKoi-logo-text.png"
-        alt="SkyKoi"
+        src="/assets/SKYKOI-logo-text.png"
+        alt="SKYKOI"
         width="500"
         class="hidden dark:block"
     />
@@ -31,19 +31,19 @@ title: "SkyKoi"
 
 <Columns>
   <Card title="Get Started" href="/start/getting-started" icon="rocket">
-    Install SkyKoi and bring up the Gateway in minutes.
+    Install SKYKOI and bring up the Gateway in minutes.
   </Card>
   <Card title="Run the Wizard" href="/start/wizard" icon="sparkles">
-    Guided setup with `skykoi onboard` and pairing flows.
+    Guided setup with `SKYKOI onboard` and pairing flows.
   </Card>
   <Card title="Open the Control UI" href="/web/control-ui" icon="layout-dashboard">
     Launch the browser dashboard for chat, config, and sessions.
   </Card>
 </Columns>
 
-## What is SkyKoi?
+## What is SKYKOI?
 
-SkyKoi is a **self-hosted gateway** that connects your favorite chat apps — WhatsApp, Telegram, Discord, iMessage, and more — to AI coding agents like Pi. You run a single Gateway process on your own machine (or a server), and it becomes the bridge between your messaging apps and an always-available AI assistant.
+SKYKOI is a **self-hosted gateway** that connects your favorite chat apps — WhatsApp, Telegram, Discord, iMessage, and more — to AI coding agents like Pi. You run a single Gateway process on your own machine (or a server), and it becomes the bridge between your messaging apps and an always-available AI assistant.
 
 **Who is it for?** Developers and power users who want a personal AI assistant they can message from anywhere — without giving up control of their data or relying on a hosted service.
 
@@ -96,20 +96,20 @@ The Gateway is the single source of truth for sessions, routing, and channel con
 ## Quick start
 
 <Steps>
-  <Step title="Install SkyKoi">
+  <Step title="Install SKYKOI">
     ```bash
-    npm install -g SkyKoi@latest
+    npm install -g SKYKOI@latest
     ```
   </Step>
   <Step title="Onboard and install the service">
     ```bash
-    skykoi onboard --install-daemon
+    SKYKOI onboard --install-daemon
     ```
   </Step>
   <Step title="Pair WhatsApp and start the Gateway">
     ```bash
-    skykoi channels login
-    skykoi gateway --port 18789
+    SKYKOI channels login
+    SKYKOI gateway --port 18789
     ```
   </Step>
 </Steps>
@@ -124,14 +124,14 @@ Open the browser Control UI after the Gateway starts.
 - Remote access: [Web surfaces](/web) and [Tailscale](/gateway/tailscale)
 
 <p align="center">
-  <img src="whatsapp-SkyKoi.jpg" alt="SkyKoi" width="420" />
+  <img src="whatsapp-SKYKOI.jpg" alt="SKYKOI" width="420" />
 </p>
 
 ## Configuration (optional)
 
-Config lives at `~/.skykoi/skykoi.json`.
+Config lives at `~/.SKYKOI/SKYKOI.json`.
 
-- If you **do nothing**, SkyKoi uses the bundled Pi binary in RPC mode with per-sender sessions.
+- If you **do nothing**, SKYKOI uses the bundled Pi binary in RPC mode with per-sender sessions.
 - If you want to lock it down, start with `channels.whatsapp.allowFrom` and (for groups) mention rules.
 
 Example:
@@ -144,7 +144,7 @@ Example:
       groups: { "*": { requireMention: true } },
     },
   },
-  messages: { groupChat: { mentionPatterns: ["@SkyKoi"] } },
+  messages: { groupChat: { mentionPatterns: ["@SKYKOI"] } },
 }
 ```
 

package/docs/install/ansible.md

@@ -1,5 +1,5 @@
 ---
-summary: "Automated, hardened SkyKoi installation with Ansible, Tailscale VPN, and firewall isolation"
+summary: "Automated, hardened SKYKOI installation with Ansible, Tailscale VPN, and firewall isolation"
 read_when:
   - You want automated server deployment with security hardening
   - You need firewall-isolated setup with VPN access
@@ -9,19 +9,19 @@ title: "Ansible"
 
 # Ansible Installation
 
-The recommended way to deploy SkyKoi to production servers is via **[SkyKoi-ansible](https://github.com/SkyKoi/SkyKoi-ansible)** — an automated installer with security-first architecture.
+The recommended way to deploy SKYKOI to production servers is via **[SKYKOI-ansible](https://github.com/SKYKOI/SKYKOI-ansible)** — an automated installer with security-first architecture.
 
 ## Quick Start
 
 One-command install:
 
 ```bash
-curl -fsSL https://raw.githubusercontent.com/SkyKoi/SkyKoi-ansible/main/install.sh | bash
+curl -fsSL https://raw.githubusercontent.com/SKYKOI/SKYKOI-ansible/main/install.sh | bash
 ```
 
-> **📦 Full guide: [github.com/SkyKoi/SkyKoi-ansible](https://github.com/SkyKoi/SkyKoi-ansible)**
+> **📦 Full guide: [github.com/SKYKOI/SKYKOI-ansible](https://github.com/SKYKOI/SKYKOI-ansible)**
 >
-> The SkyKoi-ansible repo is the source of truth for Ansible deployment. This page is a quick overview.
+> The SKYKOI-ansible repo is the source of truth for Ansible deployment. This page is a quick overview.
 
 ## What You Get
 
@@ -47,22 +47,22 @@ The Ansible playbook installs and configures:
 2. **UFW firewall** (SSH + Tailscale ports only)
 3. **Docker CE + Compose V2** (for agent sandboxes)
 4. **Node.js 22.x + pnpm** (runtime dependencies)
-5. **SkyKoi** (host-based, not containerized)
+5. **SKYKOI** (host-based, not containerized)
 6. **Systemd service** (auto-start with security hardening)
 
 Note: The gateway runs **directly on the host** (not in Docker), but agent sandboxes use Docker for isolation. See [Sandboxing](/gateway/sandboxing) for details.
 
 ## Post-Install Setup
 
-After installation completes, switch to the SkyKoi user:
+After installation completes, switch to the SKYKOI user:
 
 ```bash
-sudo -i -u SkyKoi
+sudo -i -u SKYKOI
 ```
 
 The post-install script will guide you through:
 
-1. **Onboarding wizard**: Configure SkyKoi settings
+1. **Onboarding wizard**: Configure SKYKOI settings
 2. **Provider login**: Connect WhatsApp/Telegram/Discord/Signal
 3. **Gateway testing**: Verify the installation
 4. **Tailscale setup**: Connect to your VPN mesh
@@ -71,17 +71,17 @@ The post-install script will guide you through:
 
 ```bash
 # Check service status
-sudo systemctl status SkyKoi
+sudo systemctl status SKYKOI
 
 # View live logs
-sudo journalctl -u SkyKoi -f
+sudo journalctl -u SKYKOI -f
 
 # Restart gateway
-sudo systemctl restart SkyKoi
+sudo systemctl restart SKYKOI
 
-# Provider login (run as SkyKoi user)
-sudo -i -u SkyKoi
-SkyKoi channels login
+# Provider login (run as SKYKOI user)
+sudo -i -u SKYKOI
+SKYKOI channels login
 ```
 
 ## Security Architecture
@@ -118,8 +118,8 @@ If you prefer manual control over the automation:
 sudo apt update && sudo apt install -y ansible git
 
 # 2. Clone repository
-git clone https://github.com/SkyKoi/SkyKoi-ansible.git
-cd SkyKoi-ansible
+git clone https://github.com/SKYKOI/SKYKOI-ansible.git
+cd SKYKOI-ansible
 
 # 3. Install Ansible collections
 ansible-galaxy collection install -r requirements.yml
@@ -127,18 +127,18 @@ ansible-galaxy collection install -r requirements.yml
 # 4. Run playbook
 ./run-playbook.sh
 
-# Or run directly (then manually execute /tmp/SkyKoi-setup.sh after)
+# Or run directly (then manually execute /tmp/SKYKOI-setup.sh after)
 # ansible-playbook playbook.yml --ask-become-pass
 ```
 
-## Updating SkyKoi
+## Updating SKYKOI
 
-The Ansible installer sets up SkyKoi for manual updates. See [Updating](/install/updating) for the standard update flow.
+The Ansible installer sets up SKYKOI for manual updates. See [Updating](/install/updating) for the standard update flow.
 
 To re-run the Ansible playbook (e.g., for configuration changes):
 
 ```bash
-cd SkyKoi-ansible
+cd SKYKOI-ansible
 ./run-playbook.sh
 ```
 
@@ -158,14 +158,14 @@ If you're locked out:
 
 ```bash
 # Check logs
-sudo journalctl -u SkyKoi -n 100
+sudo journalctl -u SKYKOI -n 100
 
 # Verify permissions
-sudo ls -la /opt/SkyKoi
+sudo ls -la /opt/SKYKOI
 
 # Test manual start
-sudo -i -u SkyKoi
-cd ~/SkyKoi
+sudo -i -u SKYKOI
+cd ~/SKYKOI
 pnpm start
 ```
 
@@ -176,33 +176,33 @@ pnpm start
 sudo systemctl status docker
 
 # Check sandbox image
-sudo docker images | grep SkyKoi-sandbox
+sudo docker images | grep SKYKOI-sandbox
 
 # Build sandbox image if missing
-cd /opt/SkyKoi/SkyKoi
-sudo -u SkyKoi ./scripts/sandbox-setup.sh
+cd /opt/SKYKOI/SKYKOI
+sudo -u SKYKOI ./scripts/sandbox-setup.sh
 ```
 
 ### Provider login fails
 
-Make sure you're running as the `SkyKoi` user:
+Make sure you're running as the `SKYKOI` user:
 
 ```bash
-sudo -i -u SkyKoi
-SkyKoi channels login
+sudo -i -u SKYKOI
+SKYKOI channels login
 ```
 
 ## Advanced Configuration
 
 For detailed security architecture and troubleshooting:
 
-- [Security Architecture](https://github.com/SkyKoi/SkyKoi-ansible/blob/main/docs/security.md)
-- [Technical Details](https://github.com/SkyKoi/SkyKoi-ansible/blob/main/docs/architecture.md)
-- [Troubleshooting Guide](https://github.com/SkyKoi/SkyKoi-ansible/blob/main/docs/troubleshooting.md)
+- [Security Architecture](https://github.com/SKYKOI/SKYKOI-ansible/blob/main/docs/security.md)
+- [Technical Details](https://github.com/SKYKOI/SKYKOI-ansible/blob/main/docs/architecture.md)
+- [Troubleshooting Guide](https://github.com/SKYKOI/SKYKOI-ansible/blob/main/docs/troubleshooting.md)
 
 ## Related
 
-- [SkyKoi-ansible](https://github.com/SkyKoi/SkyKoi-ansible) — full deployment guide
+- [SKYKOI-ansible](https://github.com/SKYKOI/SKYKOI-ansible) — full deployment guide
 - [Docker](/install/docker) — containerized gateway setup
 - [Sandboxing](/gateway/sandboxing) — agent sandbox configuration
 - [Multi-Agent Sandbox & Tools](/tools/multi-agent-sandbox-tools) — per-agent isolation

package/docs/install/development-channels.md

@@ -10,7 +10,7 @@ title: "Development Channels"
 
 Last updated: 2026-01-21
 
-SkyKoi ships three update channels:
+SKYKOI ships three update channels:
 
 - **stable**: npm dist-tag `latest`.
 - **beta**: npm dist-tag `beta` (builds under test).
@@ -24,9 +24,9 @@ without changing the version number — dist-tags are the source of truth for np
 Git checkout:
 
 ```bash
-SkyKoi update --channel stable
-SkyKoi update --channel beta
-SkyKoi update --channel dev
+SKYKOI update --channel stable
+SKYKOI update --channel beta
+SKYKOI update --channel dev
 ```
 
 - `stable`/`beta` check out the latest matching tag (often the same tag).
@@ -35,17 +35,17 @@ SkyKoi update --channel dev
 npm/pnpm global install:
 
 ```bash
-SkyKoi update --channel stable
-SkyKoi update --channel beta
-SkyKoi update --channel dev
+SKYKOI update --channel stable
+SKYKOI update --channel beta
+SKYKOI update --channel dev
 ```
 
 This updates via the corresponding npm dist-tag (`latest`, `beta`, `dev`).
 
-When you **explicitly** switch channels with `--channel`, SkyKoi also aligns
+When you **explicitly** switch channels with `--channel`, SKYKOI also aligns
 the install method:
 
-- `dev` ensures a git checkout (default `~/SkyKoi`, override with `SKYKOI_GIT_DIR`),
+- `dev` ensures a git checkout (default `~/SKYKOI`, override with `SKYKOI_GIT_DIR`),
   updates it, and installs the global CLI from that checkout.
 - `stable`/`beta` installs from npm using the matching dist-tag.
 
@@ -53,7 +53,7 @@ Tip: if you want stable + dev in parallel, keep two clones and point your gatewa
 
 ## Plugins and channels
 
-When you switch channels with `SkyKoi update`, SkyKoi also syncs plugin sources:
+When you switch channels with `SKYKOI update`, SKYKOI also syncs plugin sources:
 
 - `dev` prefers bundled plugins from the git checkout.
 - `stable` and `beta` restore npm-installed plugin packages.