skykoi 2026.3.11 → 2026.3.13

package/docs/tools/skills.md

@@ -6,31 +6,31 @@ read_when:
 title: "Skills"
 ---
 
-# Skills (SkyKoi)
+# Skills (SKYKOI)
 
-SkyKoi uses **[AgentSkills](https://agentskills.io)-compatible** skill folders to teach the agent how to use tools. Each skill is a directory containing a `SKILL.md` with YAML frontmatter and instructions. SkyKoi loads **bundled skills** plus optional local overrides, and filters them at load time based on environment, config, and binary presence.
+SKYKOI uses **[AgentSkills](https://agentskills.io)-compatible** skill folders to teach the agent how to use tools. Each skill is a directory containing a `SKILL.md` with YAML frontmatter and instructions. SKYKOI loads **bundled skills** plus optional local overrides, and filters them at load time based on environment, config, and binary presence.
 
 ## Locations and precedence
 
 Skills are loaded from **three** places:
 
-1. **Bundled skills**: shipped with the install (npm package or SkyKoi.app)
-2. **Managed/local skills**: `~/.skykoi/skills`
+1. **Bundled skills**: shipped with the install (npm package or SKYKOI.app)
+2. **Managed/local skills**: `~/.SKYKOI/skills`
 3. **Workspace skills**: `<workspace>/skills`
 
 If a skill name conflicts, precedence is:
 
-`<workspace>/skills` (highest) → `~/.skykoi/skills` → bundled skills (lowest)
+`<workspace>/skills` (highest) → `~/.SKYKOI/skills` → bundled skills (lowest)
 
 Additionally, you can configure extra skill folders (lowest precedence) via
-`skills.load.extraDirs` in `~/.skykoi/skykoi.json`.
+`skills.load.extraDirs` in `~/.SKYKOI/SKYKOI.json`.
 
 ## Per-agent vs shared skills
 
 In **multi-agent** setups, each agent has its own workspace. That means:
 
 - **Per-agent skills** live in `<workspace>/skills` for that agent only.
-- **Shared skills** live in `~/.skykoi/skills` (managed/local) and are visible
+- **Shared skills** live in `~/.SKYKOI/skills` (managed/local) and are visible
   to **all agents** on the same machine.
 - **Shared folders** can also be added via `skills.load.extraDirs` (lowest
   precedence) if you want a common skills pack used by multiple agents.
@@ -41,29 +41,29 @@ applies: workspace wins, then managed/local, then bundled.
 ## Plugins + skills
 
 Plugins can ship their own skills by listing `skills` directories in
-`SkyKoi.plugin.json` (paths relative to the plugin root). Plugin skills load
+`SKYKOI.plugin.json` (paths relative to the plugin root). Plugin skills load
 when the plugin is enabled and participate in the normal skill precedence rules.
-You can gate them via `metadata.SkyKoi.requires.config` on the plugin’s config
+You can gate them via `metadata.SKYKOI.requires.config` on the plugin’s config
 entry. See [Plugins](/tools/plugin) for discovery/config and [Tools](/tools) for the
 tool surface those skills teach.
 
-## SkyKoi Skills (install + sync)
+## SKYKOI Skills (install + sync)
 
-SkyKoi Skills is the public skills registry for SkyKoi. Browse at
-[https://skykoi.com/skills](https://skykoi.com/skills). Use it to discover, install, update, and back up skills.
-Full guide: [SkyKoi Skills](/tools/SkyKoi Skills).
+SKYKOI Skills is the public skills registry for SKYKOI. Browse at
+[https://SKYKOI.com/skills](https://SKYKOI.com/skills). Use it to discover, install, update, and back up skills.
+Full guide: [SKYKOI Skills](/tools/SKYKOI Skills).
 
 Common flows:
 
 - Install a skill into your workspace:
-  - `SkyKoi Skills install <skill-slug>`
+  - `SKYKOI Skills install <skill-slug>`
 - Update all installed skills:
-  - `SkyKoi Skills update --all`
+  - `SKYKOI Skills update --all`
 - Sync (scan + publish updates):
-  - `SkyKoi Skills sync --all`
+  - `SKYKOI Skills sync --all`
 
-By default, `SkyKoi Skills` installs into `./skills` under your current working
-directory (or falls back to the configured SkyKoi workspace). SkyKoi picks
+By default, `SKYKOI Skills` installs into `./skills` under your current working
+directory (or falls back to the configured SKYKOI workspace). SKYKOI picks
 that up as `<workspace>/skills` on the next session.
 
 ## Security notes
@@ -92,7 +92,7 @@ Notes:
 - `metadata` should be a **single-line JSON object**.
 - Use `{baseDir}` in instructions to reference the skill folder path.
 - Optional frontmatter keys:
-  - `homepage` — URL surfaced as “Website” in the macOS Skills UI (also supported via `metadata.SkyKoi.homepage`).
+  - `homepage` — URL surfaced as “Website” in the macOS Skills UI (also supported via `metadata.SKYKOI.homepage`).
   - `user-invocable` — `true|false` (default: `true`). When `true`, the skill is exposed as a user slash command.
   - `disable-model-invocation` — `true|false` (default: `false`). When `true`, the skill is excluded from the model prompt (still available via user invocation).
   - `command-dispatch` — `tool` (optional). When set to `tool`, the slash command bypasses the model and dispatches directly to a tool.
@@ -104,7 +104,7 @@ Notes:
 
 ## Gating (load-time filters)
 
-SkyKoi **filters skills at load time** using `metadata` (single-line JSON):
+SKYKOI **filters skills at load time** using `metadata` (single-line JSON):
 
 ```markdown
 ---
@@ -112,7 +112,7 @@ name: nano-banana-pro
 description: Generate or edit images via Gemini 3 Pro Image
 metadata:
   {
-    "SkyKoi":
+    "SKYKOI":
       {
         "requires": { "bins": ["uv"], "env": ["GEMINI_API_KEY"], "config": ["browser.enabled"] },
         "primaryEnv": "GEMINI_API_KEY",
@@ -121,7 +121,7 @@ metadata:
 ---
 ```
 
-Fields under `metadata.SkyKoi`:
+Fields under `metadata.SKYKOI`:
 
 - `always: true` — always include the skill (skip other gates).
 - `emoji` — optional emoji used by the macOS Skills UI.
@@ -130,7 +130,7 @@ Fields under `metadata.SkyKoi`:
 - `requires.bins` — list; each must exist on `PATH`.
 - `requires.anyBins` — list; at least one must exist on `PATH`.
 - `requires.env` — list; env var must exist **or** be provided in config.
-- `requires.config` — list of `SkyKoi.json` paths that must be truthy.
+- `requires.config` — list of `SKYKOI.json` paths that must be truthy.
 - `primaryEnv` — env var name associated with `skills.entries.<name>.apiKey`.
 - `install` — optional array of installer specs used by the macOS Skills UI (brew/node/go/uv/download).
 
@@ -152,7 +152,7 @@ name: gemini
 description: Use Gemini CLI for coding assistance and Google search lookups.
 metadata:
   {
-    "SkyKoi":
+    "SKYKOI":
       {
         "emoji": "♊️",
         "requires": { "bins": ["gemini"] },
@@ -174,18 +174,18 @@ metadata:
 Notes:
 
 - If multiple installers are listed, the gateway picks a **single** preferred option (brew when available, otherwise node).
-- If all installers are `download`, SkyKoi lists each entry so you can see the available artifacts.
+- If all installers are `download`, SKYKOI lists each entry so you can see the available artifacts.
 - Installer specs can include `os: ["darwin"|"linux"|"win32"]` to filter options by platform.
-- Node installs honor `skills.install.nodeManager` in `SkyKoi.json` (default: npm; options: npm/pnpm/yarn/bun).
+- Node installs honor `skills.install.nodeManager` in `SKYKOI.json` (default: npm; options: npm/pnpm/yarn/bun).
   This only affects **skill installs**; the Gateway runtime should still be Node
   (Bun is not recommended for WhatsApp/Telegram).
 - Go installs: if `go` is missing and `brew` is available, the gateway installs Go via Homebrew first and sets `GOBIN` to Homebrew’s `bin` when possible.
-- Download installs: `url` (required), `archive` (`tar.gz` | `tar.bz2` | `zip`), `extract` (default: auto when archive detected), `stripComponents`, `targetDir` (default: `~/.skykoi/tools/<skillKey>`).
+- Download installs: `url` (required), `archive` (`tar.gz` | `tar.bz2` | `zip`), `extract` (default: auto when archive detected), `stripComponents`, `targetDir` (default: `~/.SKYKOI/tools/<skillKey>`).
 
-If no `metadata.SkyKoi` is present, the skill is always eligible (unless
+If no `metadata.SKYKOI` is present, the skill is always eligible (unless
 disabled in config or blocked by `skills.allowBundled` for bundled skills).
 
-## Config overrides (`~/.skykoi/skykoi.json`)
+## Config overrides (`~/.SKYKOI/SKYKOI.json`)
 
 Bundled/managed skills can be toggled and supplied with env values:
 
@@ -214,20 +214,20 @@ Bundled/managed skills can be toggled and supplied with env values:
 Note: if the skill name contains hyphens, quote the key (JSON5 allows quoted keys).
 
 Config keys match the **skill name** by default. If a skill defines
-`metadata.SkyKoi.skillKey`, use that key under `skills.entries`.
+`metadata.SKYKOI.skillKey`, use that key under `skills.entries`.
 
 Rules:
 
 - `enabled: false` disables the skill even if it’s bundled/installed.
 - `env`: injected **only if** the variable isn’t already set in the process.
-- `apiKey`: convenience for skills that declare `metadata.SkyKoi.primaryEnv`.
+- `apiKey`: convenience for skills that declare `metadata.SKYKOI.primaryEnv`.
 - `config`: optional bag for custom per-skill fields; custom keys must live here.
 - `allowBundled`: optional allowlist for **bundled** skills only. If set, only
   bundled skills in the list are eligible (managed/workspace skills unaffected).
 
 ## Environment injection (per agent run)
 
-When an agent run starts, SkyKoi:
+When an agent run starts, SKYKOI:
 
 1. Reads skill metadata.
 2. Applies any `skills.entries.<key>.env` or `skills.entries.<key>.apiKey` to
@@ -239,19 +239,19 @@ This is **scoped to the agent run**, not a global shell environment.
 
 ## Session snapshot (performance)
 
-SkyKoi snapshots the eligible skills **when a session starts** and reuses that list for subsequent turns in the same session. Changes to skills or config take effect on the next new session.
+SKYKOI snapshots the eligible skills **when a session starts** and reuses that list for subsequent turns in the same session. Changes to skills or config take effect on the next new session.
 
 Skills can also refresh mid-session when the skills watcher is enabled or when a new eligible remote node appears (see below). Think of this as a **hot reload**: the refreshed list is picked up on the next agent turn.
 
 ## Remote macOS nodes (Linux gateway)
 
-If the Gateway is running on Linux but a **macOS node** is connected **with `system.run` allowed** (Exec approvals security not set to `deny`), SkyKoi can treat macOS-only skills as eligible when the required binaries are present on that node. The agent should execute those skills via the `nodes` tool (typically `nodes.run`).
+If the Gateway is running on Linux but a **macOS node** is connected **with `system.run` allowed** (Exec approvals security not set to `deny`), SKYKOI can treat macOS-only skills as eligible when the required binaries are present on that node. The agent should execute those skills via the `nodes` tool (typically `nodes.run`).
 
 This relies on the node reporting its command support and on a bin probe via `system.run`. If the macOS node goes offline later, the skills remain visible; invocations may fail until the node reconnects.
 
 ## Skills watcher (auto-refresh)
 
-By default, SkyKoi watches skill folders and bumps the skills snapshot when `SKILL.md` files change. Configure this under `skills.load`:
+By default, SKYKOI watches skill folders and bumps the skills snapshot when `SKILL.md` files change. Configure this under `skills.load`:
 
 ```json5
 {
@@ -266,7 +266,7 @@ By default, SkyKoi watches skill folders and bumps the skills snapshot when `SKI
 
 ## Token impact (skills list)
 
-When skills are eligible, SkyKoi injects a compact XML list of available skills into the system prompt (via `formatSkillsForPrompt` in `pi-coding-agent`). The cost is deterministic:
+When skills are eligible, SKYKOI injects a compact XML list of available skills into the system prompt (via `formatSkillsForPrompt` in `pi-coding-agent`). The cost is deterministic:
 
 - **Base overhead (only when ≥1 skill):** 195 characters.
 - **Per skill:** 97 characters + the length of the XML-escaped `<name>`, `<description>`, and `<location>` values.
@@ -284,8 +284,8 @@ Notes:
 
 ## Managed skills lifecycle
 
-SkyKoi ships a baseline set of skills as **bundled skills** as part of the
-install (npm package or SkyKoi.app). `~/.skykoi/skills` exists for local
+SKYKOI ships a baseline set of skills as **bundled skills** as part of the
+install (npm package or SKYKOI.app). `~/.SKYKOI/skills` exists for local
 overrides (for example, pinning/patching a skill without changing the bundled
 copy). Workspace skills are user-owned and override both on name conflicts.
 
@@ -295,6 +295,6 @@ See [Skills config](/tools/skills-config) for the full configuration schema.
 
 ## Looking for more skills?
 
-Browse [https://skykoi.com/skills](https://skykoi.com/skills).
+Browse [https://SKYKOI.com/skills](https://SKYKOI.com/skills).
 
 ---

package/docs/tools/slash-commands.md

@@ -53,7 +53,7 @@ They run immediately, are stripped before the model sees the message, and the re
   - Set `channels.discord.commands.nativeSkills`, `channels.telegram.commands.nativeSkills`, or `channels.slack.commands.nativeSkills` to override per provider (bool or `"auto"`).
 - `commands.bash` (default `false`) enables `! <cmd>` to run host shell commands (`/bash <cmd>` is an alias; requires `tools.elevated` allowlists).
 - `commands.bashForegroundMs` (default `2000`) controls how long bash waits before switching to background mode (`0` backgrounds immediately).
-- `commands.config` (default `false`) enables `/config` (reads/writes `skykoi.json`).
+- `commands.config` (default `false`) enables `/config` (reads/writes `SKYKOI.json`).
 - `commands.debug` (default `false`) enables `/debug` (runtime-only overrides).
 - `commands.useAccessGroups` (default `true`) enforces allowlists/policies for commands.
 
@@ -103,9 +103,9 @@ Notes:
 
 - Commands accept an optional `:` between the command and args (e.g. `/think: high`, `/send: on`, `/help:`).
 - `/new <model>` accepts a model alias, `provider/model`, or a provider name (fuzzy match); if no match, the text is treated as the message body.
-- For full provider usage breakdown, use `SkyKoi status --usage`.
+- For full provider usage breakdown, use `SKYKOI status --usage`.
 - `/allowlist add|remove` requires `commands.config=true` and honors channel `configWrites`.
-- `/usage` controls the per-response usage footer; `/usage cost` prints a local cost summary from SkyKoi session logs.
+- `/usage` controls the per-response usage footer; `/usage cost` prints a local cost summary from SKYKOI session logs.
 - `/restart` is disabled by default; set `commands.restart: true` to enable it.
 - `/verbose` is meant for debugging and extra visibility; keep it **off** in normal use.
 - `/reasoning` (and `/verbose`) are risky in group settings: they may reveal internal reasoning or tool output you did not intend to expose. Prefer leaving them off, especially in group chats.
@@ -157,7 +157,7 @@ Examples:
 
 ```
 /debug show
-/debug set messages.responsePrefix="[SkyKoi]"
+/debug set messages.responsePrefix="[SKYKOI]"
 /debug set channels.whatsapp.allowFrom=["+1555","+4477"]
 /debug unset messages.responsePrefix
 /debug reset
@@ -165,12 +165,12 @@ Examples:
 
 Notes:
 
-- Overrides apply immediately to new config reads, but do **not** write to `skykoi.json`.
+- Overrides apply immediately to new config reads, but do **not** write to `SKYKOI.json`.
 - Use `/debug reset` to clear all overrides and return to the on-disk config.
 
 ## Config updates
 
-`/config` writes to your on-disk config (`skykoi.json`). Owner-only. Disabled by default; enable with `commands.config: true`.
+`/config` writes to your on-disk config (`SKYKOI.json`). Owner-only. Disabled by default; enable with `commands.config: true`.
 
 Examples:
 
@@ -178,7 +178,7 @@ Examples:
 /config show
 /config show messages.responsePrefix
 /config get messages.responsePrefix
-/config set messages.responsePrefix="[SkyKoi]"
+/config set messages.responsePrefix="[SKYKOI]"
 /config unset messages.responsePrefix
 ```
 
@@ -195,4 +195,4 @@ Notes:
   - Slack: `agent:<agentId>:slack:slash:<userId>` (prefix configurable via `channels.slack.slashCommand.sessionPrefix`)
   - Telegram: `telegram:slash:<userId>` (targets the chat session via `CommandTargetSessionKey`)
 - **`/stop`** targets the active chat session so it can abort the current run.
-- **Slack:** `channels.slack.slashCommand` is still supported for a single `/SkyKoi`-style command. If you enable `commands.native`, you must create one Slack slash command per built-in command (same names as `/help`). Command argument menus for Slack are delivered as ephemeral Block Kit buttons.
+- **Slack:** `channels.slack.slashCommand` is still supported for a single `/SKYKOI`-style command. If you enable `commands.native`, you must create one Slack slash command per built-in command (same names as `/help`). Command argument menus for Slack are delivered as ephemeral Block Kit buttons.

package/docs/tools/web.md

@@ -9,7 +9,7 @@ title: "Web Tools"
 
 # Web tools
 
-SkyKoi ships two lightweight web tools:
+SKYKOI ships two lightweight web tools:
 
 - `web_search` — Search the web via Brave Search API (default) or Perplexity Sonar (direct or via OpenRouter).
 - `web_fetch` — HTTP fetch + readable extraction (HTML → markdown/text).
@@ -73,19 +73,19 @@ Example: switch to Perplexity Sonar (direct API):
 
 1. Create a Brave Search API account at [https://brave.com/search/api/](https://brave.com/search/api/)
 2. In the dashboard, choose the **Data for Search** plan (not “Data for AI”) and generate an API key.
-3. Run `SkyKoi configure --section web` to store the key in config (recommended), or set `BRAVE_API_KEY` in your environment.
+3. Run `SKYKOI configure --section web` to store the key in config (recommended), or set `BRAVE_API_KEY` in your environment.
 
 Brave provides a free tier plus paid plans; check the Brave API portal for the
 current limits and pricing.
 
 ### Where to set the key (recommended)
 
-**Recommended:** run `SkyKoi configure --section web`. It stores the key in
-`~/.skykoi/skykoi.json` under `tools.web.search.apiKey`.
+**Recommended:** run `SKYKOI configure --section web`. It stores the key in
+`~/.SKYKOI/SKYKOI.json` under `tools.web.search.apiKey`.
 
 **Environment alternative:** set `BRAVE_API_KEY` in the Gateway process
-environment. For a gateway install, put it in `~/.skykoi/.env` (or your
-service environment). See [Env vars](/help/faq#how-does-SkyKoi-load-environment-variables).
+environment. For a gateway install, put it in `~/.SKYKOI/.env` (or your
+service environment). See [Env vars](/help/faq#how-does-SKYKOI-load-environment-variables).
 
 ## Using Perplexity (direct or via OpenRouter)
 
@@ -123,9 +123,9 @@ crypto/prepaid).
 ```
 
 **Environment alternative:** set `OPENROUTER_API_KEY` or `PERPLEXITY_API_KEY` in the Gateway
-environment. For a gateway install, put it in `~/.skykoi/.env`.
+environment. For a gateway install, put it in `~/.SKYKOI/.env`.
 
-If no base URL is set, SkyKoi chooses a default based on the API key source:
+If no base URL is set, SKYKOI chooses a default based on the API key source:
 
 - `PERPLEXITY_API_KEY` or `pplx-...` → `https://api.perplexity.ai`
 - `OPENROUTER_API_KEY` or `sk-or-...` → `https://openrouter.ai/api/v1`

package/docs/tts.md

@@ -9,8 +9,8 @@ title: "Text-to-Speech"
 
 # Text-to-speech (TTS)
 
-SkyKoi can convert outbound replies into audio using ElevenLabs, OpenAI, or Edge TTS.
-It works anywhere SkyKoi can send audio; Telegram gets a round voice-note bubble.
+SKYKOI can convert outbound replies into audio using ElevenLabs, OpenAI, or Edge TTS.
+It works anywhere SKYKOI can send audio; Telegram gets a round voice-note bubble.
 
 ## Supported services
 
@@ -37,7 +37,7 @@ If you want OpenAI or ElevenLabs:
 - `ELEVENLABS_API_KEY` (or `XI_API_KEY`)
 - `OPENAI_API_KEY`
 
-Edge TTS does **not** require an API key. If no API keys are found, SkyKoi defaults
+Edge TTS does **not** require an API key. If no API keys are found, SKYKOI defaults
 to Edge TTS (unless disabled via `messages.tts.edge.enabled=false`).
 
 If multiple providers are configured, the selected provider is used first and the others are fallback options.
@@ -63,7 +63,7 @@ when no OpenAI or ElevenLabs API keys are available.
 
 ## Config
 
-TTS config lives under `messages.tts` in `skykoi.json`.
+TTS config lives under `messages.tts` in `SKYKOI.json`.
 Full schema is in [Gateway configuration](/gateway/configuration).
 
 ### Minimal config (enable + provider)
@@ -161,7 +161,7 @@ Full schema is in [Gateway configuration](/gateway/configuration).
       auto: "always",
       maxTextLength: 4000,
       timeoutMs: 30000,
-      prefsPath: "~/.skykoi/settings/tts.json",
+      prefsPath: "~/.SKYKOI/settings/tts.json",
     },
   },
 }
@@ -205,7 +205,7 @@ Then run:
 - `enabled`: legacy toggle (doctor migrates this to `auto`).
 - `mode`: `"final"` (default) or `"all"` (includes tool/block replies).
 - `provider`: `"elevenlabs"`, `"openai"`, or `"edge"` (fallback is automatic).
-- If `provider` is **unset**, SkyKoi prefers `openai` (if key), then `elevenlabs` (if key),
+- If `provider` is **unset**, SKYKOI prefers `openai` (if key), then `elevenlabs` (if key),
   otherwise `edge`.
 - `summaryModel`: optional cheap model for auto-summary; defaults to `agents.defaults.model.primary`.
   - Accepts `provider/model` or a configured model alias.
@@ -294,7 +294,7 @@ Optional allowlist (disable specific overrides while keeping tags enabled):
 ## Per-user preferences
 
 Slash commands write local overrides to `prefsPath` (default:
-`~/.skykoi/settings/tts.json`, override with `SKYKOI_TTS_PREFS` or
+`~/.SKYKOI/settings/tts.json`, override with `SKYKOI_TTS_PREFS` or
 `messages.tts.prefsPath`).
 
 Stored fields:
@@ -318,13 +318,13 @@ These override `messages.tts.*` for that host.
   - Output format values follow Microsoft Speech output formats (including Ogg/WebM Opus). citeturn1search0
   - Telegram `sendVoice` accepts OGG/MP3/M4A; use OpenAI/ElevenLabs if you need
     guaranteed Opus voice notes. citeturn1search1
-  - If the configured Edge output format fails, SkyKoi retries with MP3.
+  - If the configured Edge output format fails, SKYKOI retries with MP3.
 
 OpenAI/ElevenLabs formats are fixed; Telegram expects Opus for voice-note UX.
 
 ## Auto-TTS behavior
 
-When enabled, SkyKoi:
+When enabled, SKYKOI:
 
 - skips TTS if the reply already contains media or a `MEDIA:` directive.
 - skips very short replies (< 10 chars).
@@ -355,7 +355,7 @@ Reply -> TTS enabled?
 There is a single command: `/tts`.
 See [Slash commands](/tools/slash-commands) for enablement details.
 
-Discord note: `/tts` is a built-in Discord command, so SkyKoi registers
+Discord note: `/tts` is a built-in Discord command, so SKYKOI registers
 `/voice` as the native command there. Text `/tts ...` still works.
 
 ```
@@ -367,7 +367,7 @@ Discord note: `/tts` is a built-in Discord command, so SkyKoi registers
 /tts provider openai
 /tts limit 2000
 /tts summary off
-/tts audio Hello from SkyKoi
+/tts audio Hello from SKYKOI
 ```
 
 Notes:

package/docs/vps.md

@@ -1,5 +1,5 @@
 ---
-summary: "VPS hosting hub for SkyKoi (Oracle/Fly/Hetzner/GCP/exe.dev)"
+summary: "VPS hosting hub for SKYKOI (Oracle/Fly/Hetzner/GCP/exe.dev)"
 read_when:
   - You want to run the Gateway in the cloud
   - You need a quick map of VPS/hosting guides

package/docs/web/control-ui.md

@@ -11,7 +11,7 @@ title: "Control UI"
 The Control UI is a small **Vite + Lit** single-page app served by the Gateway:
 
 - default: `http://<host>:18789/`
-- optional prefix: set `gateway.controlUi.basePath` (e.g. `/SkyKoi`)
+- optional prefix: set `gateway.controlUi.basePath` (e.g. `/SKYKOI`)
 
 It speaks **directly to the Gateway WebSocket** on the same port.
 
@@ -21,7 +21,7 @@ If the Gateway is running on the same computer, open:
 
 - [http://127.0.0.1:18789/](http://127.0.0.1:18789/) (or [http://localhost:18789/](http://localhost:18789/))
 
-If the page fails to load, start the Gateway first: `SkyKoi gateway`.
+If the page fails to load, start the Gateway first: `SKYKOI gateway`.
 
 Auth is supplied during the WebSocket handshake via:
 
@@ -43,14 +43,14 @@ unauthorized access.
 
 ```bash
 # List pending requests
-SkyKoi devices list
+SKYKOI devices list
 
 # Approve by request ID
-SkyKoi devices approve <requestId>
+SKYKOI devices approve <requestId>
 ```
 
 Once approved, the device is remembered and won't require re-approval unless
-you revoke it with `SkyKoi devices revoke --device <id> --role <role>`. See
+you revoke it with `SKYKOI devices revoke --device <id> --role <role>`. See
 [Devices CLI](/cli/devices) for token rotation and revocation.
 
 **Notes:**
@@ -71,7 +71,7 @@ you revoke it with `SkyKoi devices revoke --device <id> --role <role>`. See
 - Skills: status, enable/disable, install, API key updates (`skills.*`)
 - Nodes: list + caps (`node.list`)
 - Exec approvals: edit gateway or node allowlists + ask policy for `exec host=gateway/node` (`exec.approvals.*`)
-- Config: view/edit `~/.skykoi/skykoi.json` (`config.get`, `config.set`)
+- Config: view/edit `~/.SKYKOI/SKYKOI.json` (`config.get`, `config.set`)
 - Config: apply + restart with validation (`config.apply`) and wake the last active session
 - Config writes include a base-hash guard to prevent clobbering concurrent edits
 - Config schema + form rendering (`config.schema`, including plugin + channel schemas); Raw JSON editor remains available
@@ -101,7 +101,7 @@ Cron jobs panel notes:
 Keep the Gateway on loopback and let Tailscale Serve proxy it with HTTPS:
 
 ```bash
-SkyKoi gateway --tailscale serve
+SKYKOI gateway --tailscale serve
 ```
 
 Open:
@@ -109,7 +109,7 @@ Open:
 - `https://<magicdns>/` (or your configured `gateway.controlUi.basePath`)
 
 By default, Serve requests can authenticate via Tailscale identity headers
-(`tailscale-user-login`) when `gateway.auth.allowTailscale` is `true`. SkyKoi
+(`tailscale-user-login`) when `gateway.auth.allowTailscale` is `true`. SKYKOI
 verifies the identity by resolving the `x-forwarded-for` address with
 `tailscale whois` and matching it to the header, and only accepts these when the
 request hits loopback with Tailscale’s `x-forwarded-*` headers. Set
@@ -119,7 +119,7 @@ if you want to require a token/password even for Serve traffic.
 ### Bind to tailnet + token
 
 ```bash
-SkyKoi gateway --bind tailnet --token "$(openssl rand -hex 32)"
+SKYKOI gateway --bind tailnet --token "$(openssl rand -hex 32)"
 ```
 
 Then open:
@@ -132,7 +132,7 @@ Paste the token into the UI settings (sent as `connect.params.auth.token`).
 
 If you open the dashboard over plain HTTP (`http://<lan-ip>` or `http://<tailscale-ip>`),
 the browser runs in a **non-secure context** and blocks WebCrypto. By default,
-SkyKoi **blocks** Control UI connections without device identity.
+SKYKOI **blocks** Control UI connections without device identity.
 
 **Recommended fix:** use HTTPS (Tailscale Serve) or open the UI locally:
 
@@ -167,7 +167,7 @@ pnpm ui:build # auto-installs UI deps on first run
 Optional absolute base (when you want fixed asset URLs):
 
 ```bash
-SKYKOI_CONTROL_UI_BASE_PATH=/SkyKoi/ pnpm ui:build
+SKYKOI_CONTROL_UI_BASE_PATH=/SKYKOI/ pnpm ui:build
 ```
 
 For local development (separate dev server):

package/docs/web/dashboard.md

@@ -30,7 +30,7 @@ Prefer localhost, Tailscale Serve, or an SSH tunnel.
 ## Fast path (recommended)
 
 - After onboarding, the CLI auto-opens the dashboard and prints a clean (non-tokenized) link.
-- Re-open anytime: `SkyKoi dashboard` (copies link, opens browser if possible, shows SSH hint if headless).
+- Re-open anytime: `SKYKOI dashboard` (copies link, opens browser if possible, shows SSH hint if headless).
 - If the UI prompts for auth, paste the token from `gateway.auth.token` (or `SKYKOI_GATEWAY_TOKEN`) into Control UI settings.
 
 ## Token basics (local vs remote)
@@ -41,6 +41,6 @@ Prefer localhost, Tailscale Serve, or an SSH tunnel.
 
 ## If you see “unauthorized” / 1008
 
-- Ensure the gateway is reachable (local: `SkyKoi status`; remote: SSH tunnel `ssh -N -L 18789:127.0.0.1:18789 user@host` then open `http://127.0.0.1:18789/`).
-- Retrieve the token from the gateway host: `SkyKoi config get gateway.auth.token` (or generate one: `SkyKoi doctor --generate-gateway-token`).
+- Ensure the gateway is reachable (local: `SKYKOI status`; remote: SSH tunnel `ssh -N -L 18789:127.0.0.1:18789 user@host` then open `http://127.0.0.1:18789/`).
+- Retrieve the token from the gateway host: `SKYKOI config get gateway.auth.token` (or generate one: `SKYKOI doctor --generate-gateway-token`).
 - In the dashboard settings, paste the token into the auth field, then connect.

package/docs/web/index.md

@@ -11,7 +11,7 @@ title: "Web"
 The Gateway serves a small **browser Control UI** (Vite + Lit) from the same port as the Gateway WebSocket:
 
 - default: `http://<host>:18789/`
-- optional prefix: set `gateway.controlUi.basePath` (e.g. `/SkyKoi`)
+- optional prefix: set `gateway.controlUi.basePath` (e.g. `/SKYKOI`)
 
 Capabilities live in [Control UI](/web/control-ui).
 This page focuses on bind modes, security, and web-facing surfaces.
@@ -29,7 +29,7 @@ You can control it via config:
 ```json5
 {
   gateway: {
-    controlUi: { enabled: true, basePath: "/SkyKoi" }, // basePath optional
+    controlUi: { enabled: true, basePath: "/SKYKOI" }, // basePath optional
   },
 }
 ```
@@ -52,7 +52,7 @@ Keep the Gateway on loopback and let Tailscale Serve proxy it:
 Then start the gateway:
 
 ```bash
-SkyKoi gateway
+SKYKOI gateway
 ```
 
 Open:
@@ -74,7 +74,7 @@ Open:
 Then start the gateway (token required for non-loopback binds):
 
 ```bash
-SkyKoi gateway
+SKYKOI gateway
 ```
 
 Open:

package/docs/web/tui.md

@@ -13,13 +13,13 @@ title: "TUI"
 1. Start the Gateway.
 
 ```bash
-SkyKoi gateway
+SKYKOI gateway
 ```
 
 2. Open the TUI.
 
 ```bash
-SkyKoi tui
+SKYKOI tui
 ```
 
 3. Type a message and press Enter.
@@ -27,7 +27,7 @@ SkyKoi tui
 Remote Gateway:
 
 ```bash
-SkyKoi tui --url ws://<host>:<port> --token <gateway-token>
+SKYKOI tui --url ws://<host>:<port> --token <gateway-token>
 ```
 
 Use `--password` if your Gateway uses password auth.
@@ -58,7 +58,7 @@ Use `--password` if your Gateway uses password auth.
 - Turn delivery on:
   - `/deliver on`
   - or the Settings panel
-  - or start with `SkyKoi tui --deliver`
+  - or start with `SKYKOI tui --deliver`
 
 ## Pickers + overlays
 
@@ -150,13 +150,13 @@ Pass `--token` or `--password` explicitly. Missing explicit credentials is an er
 No output after sending a message:
 
 - Run `/status` in the TUI to confirm the Gateway is connected and idle/busy.
-- Check the Gateway logs: `SkyKoi logs --follow`.
-- Confirm the agent can run: `SkyKoi status` and `SkyKoi models status`.
+- Check the Gateway logs: `SKYKOI logs --follow`.
+- Confirm the agent can run: `SKYKOI status` and `SKYKOI models status`.
 - If you expect messages in a chat channel, enable delivery (`/deliver on` or `--deliver`).
 - `--history-limit <n>`: History entries to load (default 200)
 
 ## Connection troubleshooting
 
 - `disconnected`: ensure the Gateway is running and your `--url/--token/--password` are correct.
-- No agents in picker: check `SkyKoi agents list` and your routing config.
+- No agents in picker: check `SKYKOI agents list` and your routing config.
 - Empty session picker: you might be in global scope or have no sessions yet.

package/docs/zh-CN/AGENTS.md

@@ -56,4 +56,4 @@ go run scripts/docs-i18n/main.go -mode segment docs/channels/matrix.md
 - 反馈来源：GitHub issue #6995
 - 反馈用户：@AaronWander、@taiyi747、@Explorer1092、@rendaoyuan
 - 变更要点：更新 prompt 规则、扩充 glossary、清理 TM、批量再生成 + 定点修复
-- 参考链接：https://github.com/SkyKoi/SkyKoi/issues/6995
+- 参考链接：https://github.com/SKYKOI/SKYKOI/issues/6995