skykoi 2026.3.11 → 2026.3.13

package/docs/cli/memory.md

@@ -1,12 +1,12 @@
 ---
-summary: "CLI reference for `SkyKoi memory` (status/index/search)"
+summary: "CLI reference for `SKYKOI memory` (status/index/search)"
 read_when:
   - You want to index or search semantic memory
   - You’re debugging memory availability or indexing
 title: "memory"
 ---
 
-# `SkyKoi memory`
+# `SKYKOI memory`
 
 Manage semantic memory indexing and search.
 Provided by the active memory plugin (default: `memory-core`; set `plugins.slots.memory = "none"` to disable).
@@ -19,15 +19,15 @@ Related:
 ## Examples
 
 ```bash
-SkyKoi memory status
-SkyKoi memory status --deep
-SkyKoi memory status --deep --index
-SkyKoi memory status --deep --index --verbose
-SkyKoi memory index
-SkyKoi memory index --verbose
-SkyKoi memory search "release checklist"
-SkyKoi memory status --agent main
-SkyKoi memory index --agent main --verbose
+SKYKOI memory status
+SKYKOI memory status --deep
+SKYKOI memory status --deep --index
+SKYKOI memory status --deep --index --verbose
+SKYKOI memory index
+SKYKOI memory index --verbose
+SKYKOI memory search "release checklist"
+SKYKOI memory status --agent main
+SKYKOI memory index --agent main --verbose
 ```
 
 ## Options

package/docs/cli/message.md

@@ -1,12 +1,12 @@
 ---
-summary: "CLI reference for `SkyKoi message` (send + channel actions)"
+summary: "CLI reference for `SKYKOI message` (send + channel actions)"
 read_when:
   - Adding or modifying message CLI actions
   - Changing outbound channel behavior
 title: "message"
 ---
 
-# `SkyKoi message`
+# `SKYKOI message`
 
 Single outbound command for sending messages and channel actions
 (Discord/Google Chat/Slack/Mattermost (plugin)/Telegram/WhatsApp/Signal/iMessage/MS Teams).
@@ -14,7 +14,7 @@ Single outbound command for sending messages and channel actions
 ## Usage
 
 ```
-SkyKoi message <subcommand> [flags]
+SKYKOI message <subcommand> [flags]
 ```
 
 Channel selection:
@@ -38,7 +38,7 @@ Target formats (`--target`):
 Name lookup:
 
 - For supported providers (Discord/Slack/etc), channel names like `Help` or `#help` are resolved via the directory cache.
-- On cache miss, SkyKoi will attempt a live directory lookup when the provider supports it.
+- On cache miss, SKYKOI will attempt a live directory lookup when the provider supports it.
 
 ## Common flags
 
@@ -186,14 +186,14 @@ Name lookup:
 Send a Discord reply:
 
 ```
-SkyKoi message send --channel discord \
+SKYKOI message send --channel discord \
   --target channel:123 --message "hi" --reply-to 456
 ```
 
 Create a Discord poll:
 
 ```
-SkyKoi message poll --channel discord \
+SKYKOI message poll --channel discord \
   --target channel:123 \
   --poll-question "Snack?" \
   --poll-option Pizza --poll-option Sushi \
@@ -203,14 +203,14 @@ SkyKoi message poll --channel discord \
 Send a Teams proactive message:
 
 ```
-SkyKoi message send --channel msteams \
+SKYKOI message send --channel msteams \
   --target conversation:19:abc@thread.tacv2 --message "hi"
 ```
 
 Create a Teams poll:
 
 ```
-SkyKoi message poll --channel msteams \
+SKYKOI message poll --channel msteams \
   --target conversation:19:abc@thread.tacv2 \
   --poll-question "Lunch?" \
   --poll-option Pizza --poll-option Sushi
@@ -219,14 +219,14 @@ SkyKoi message poll --channel msteams \
 React in Slack:
 
 ```
-SkyKoi message react --channel slack \
+SKYKOI message react --channel slack \
   --target C123 --message-id 456 --emoji "✅"
 ```
 
 React in a Signal group:
 
 ```
-SkyKoi message react --channel signal \
+SKYKOI message react --channel signal \
   --target signal:group:abc123 --message-id 1737630212345 \
   --emoji "✅" --target-author-uuid 123e4567-e89b-12d3-a456-426614174000
 ```
@@ -234,6 +234,6 @@ SkyKoi message react --channel signal \
 Send Telegram inline buttons:
 
 ```
-SkyKoi message send --channel telegram --target @mychat --message "Choose:" \
+SKYKOI message send --channel telegram --target @mychat --message "Choose:" \
   --buttons '[ [{"text":"Yes","callback_data":"cmd:yes"}], [{"text":"No","callback_data":"cmd:no"}] ]'
 ```

package/docs/cli/models.md

@@ -1,12 +1,12 @@
 ---
-summary: "CLI reference for `SkyKoi models` (status/list/set/scan, aliases, fallbacks, auth)"
+summary: "CLI reference for `SKYKOI models` (status/list/set/scan, aliases, fallbacks, auth)"
 read_when:
   - You want to change default models or view provider auth status
   - You want to scan available models/providers and debug auth profiles
 title: "models"
 ---
 
-# `SkyKoi models`
+# `SKYKOI models`
 
 Model discovery, scanning, and configuration (default model, fallbacks, auth profiles).
 
@@ -18,13 +18,13 @@ Related:
 ## Common commands
 
 ```bash
-SkyKoi models status
-SkyKoi models list
-SkyKoi models set <model-or-alias>
-SkyKoi models scan
+SKYKOI models status
+SKYKOI models list
+SKYKOI models set <model-or-alias>
+SKYKOI models scan
 ```
 
-`SkyKoi models status` shows the resolved default/fallbacks plus an auth overview.
+`SKYKOI models status` shows the resolved default/fallbacks plus an auth overview.
 When provider usage snapshots are available, the OAuth/token status section includes
 provider usage headers.
 Add `--probe` to run live auth probes against each configured provider profile.
@@ -37,7 +37,7 @@ Notes:
 
 - `models set <model-or-alias>` accepts `provider/model` or an alias.
 - Model refs are parsed by splitting on the **first** `/`. If the model ID includes `/` (OpenRouter-style), include the provider prefix (example: `openrouter/moonshotai/kimi-k2`).
-- If you omit the provider, SkyKoi treats the input as an alias or a model for the **default provider** (only works when there is no `/` in the model ID).
+- If you omit the provider, SKYKOI treats the input as an alias or a model for the **default provider** (only works when there is no `/` in the model ID).
 
 ### `models status`
 
@@ -57,21 +57,21 @@ Options:
 ## Aliases + fallbacks
 
 ```bash
-SkyKoi models aliases list
-SkyKoi models fallbacks list
+SKYKOI models aliases list
+SKYKOI models fallbacks list
 ```
 
 ## Auth profiles
 
 ```bash
-SkyKoi models auth add
-SkyKoi models auth login --provider <id>
-SkyKoi models auth setup-token
-SkyKoi models auth paste-token
+SKYKOI models auth add
+SKYKOI models auth login --provider <id>
+SKYKOI models auth setup-token
+SKYKOI models auth paste-token
 ```
 
 `models auth login` runs a provider plugin’s auth flow (OAuth/API key). Use
-`SkyKoi plugins list` to see which providers are installed.
+`SKYKOI plugins list` to see which providers are installed.
 
 Notes:
 

package/docs/cli/node.md

@@ -1,12 +1,12 @@
 ---
-summary: "CLI reference for `SkyKoi node` (headless node host)"
+summary: "CLI reference for `SKYKOI node` (headless node host)"
 read_when:
   - Running the headless node host
   - Pairing a non-macOS node for system.run
 title: "node"
 ---
 
-# `SkyKoi node`
+# `SKYKOI node`
 
 Run a **headless node host** that connects to the Gateway WebSocket and exposes
 `system.run` / `system.which` on this machine.
@@ -46,7 +46,7 @@ Disable it on the node if needed:
 ## Run (foreground)
 
 ```bash
-SkyKoi node run --host <gateway-host> --port 18789
+SKYKOI node run --host <gateway-host> --port 18789
 ```
 
 Options:
@@ -63,7 +63,7 @@ Options:
 Install a headless node host as a user service.
 
 ```bash
-SkyKoi node install --host <gateway-host> --port 18789
+SKYKOI node install --host <gateway-host> --port 18789
 ```
 
 Options:
@@ -80,13 +80,13 @@ Options:
 Manage the service:
 
 ```bash
-SkyKoi node status
-SkyKoi node stop
-SkyKoi node restart
-SkyKoi node uninstall
+SKYKOI node status
+SKYKOI node stop
+SKYKOI node restart
+SKYKOI node uninstall
 ```
 
-Use `SkyKoi node run` for a foreground node host (no service).
+Use `SKYKOI node run` for a foreground node host (no service).
 
 Service commands accept `--json` for machine-readable output.
 
@@ -96,17 +96,17 @@ The first connection creates a pending node pair request on the Gateway.
 Approve it via:
 
 ```bash
-SkyKoi nodes pending
-SkyKoi nodes approve <requestId>
+SKYKOI nodes pending
+SKYKOI nodes approve <requestId>
 ```
 
 The node host stores its node id, token, display name, and gateway connection info in
-`~/.skykoi/node.json`.
+`~/.SKYKOI/node.json`.
 
 ## Exec approvals
 
 `system.run` is gated by local exec approvals:
 
-- `~/.skykoi/exec-approvals.json`
+- `~/.SKYKOI/exec-approvals.json`
 - [Exec approvals](/tools/exec-approvals)
-- `SkyKoi approvals --node <id|name|ip>` (edit from the Gateway)
+- `SKYKOI approvals --node <id|name|ip>` (edit from the Gateway)

package/docs/cli/nodes.md

@@ -1,12 +1,12 @@
 ---
-summary: "CLI reference for `SkyKoi nodes` (list/status/approve/invoke, camera/canvas/screen)"
+summary: "CLI reference for `SKYKOI nodes` (list/status/approve/invoke, camera/canvas/screen)"
 read_when:
   - You’re managing paired nodes (cameras, screen, canvas)
   - You need to approve requests or invoke node commands
 title: "nodes"
 ---
 
-# `SkyKoi nodes`
+# `SKYKOI nodes`
 
 Manage paired nodes (devices) and invoke node capabilities.
 
@@ -23,14 +23,14 @@ Common options:
 ## Common commands
 
 ```bash
-SkyKoi nodes list
-SkyKoi nodes list --connected
-SkyKoi nodes list --last-connected 24h
-SkyKoi nodes pending
-SkyKoi nodes approve <requestId>
-SkyKoi nodes status
-SkyKoi nodes status --connected
-SkyKoi nodes status --last-connected 24h
+SKYKOI nodes list
+SKYKOI nodes list --connected
+SKYKOI nodes list --last-connected 24h
+SKYKOI nodes pending
+SKYKOI nodes approve <requestId>
+SKYKOI nodes status
+SKYKOI nodes status --connected
+SKYKOI nodes status --last-connected 24h
 ```
 
 `nodes list` prints pending/paired tables. Paired rows include the most recent connect age (Last Connect).
@@ -40,10 +40,10 @@ filter to nodes that connected within a duration (e.g. `24h`, `7d`).
 ## Invoke / run
 
 ```bash
-SkyKoi nodes invoke --node <id|name|ip> --command <command> --params <json>
-SkyKoi nodes run --node <id|name|ip> <command...>
-SkyKoi nodes run --raw "git status"
-SkyKoi nodes run --agent main --node <id|name|ip> --raw "git status"
+SKYKOI nodes invoke --node <id|name|ip> --command <command> --params <json>
+SKYKOI nodes run --node <id|name|ip> <command...>
+SKYKOI nodes run --raw "git status"
+SKYKOI nodes run --agent main --node <id|name|ip> --raw "git status"
 ```
 
 Invoke flags:

package/docs/cli/onboard.md

@@ -1,11 +1,11 @@
 ---
-summary: "CLI reference for `SkyKoi onboard` (interactive onboarding wizard)"
+summary: "CLI reference for `SKYKOI onboard` (interactive onboarding wizard)"
 read_when:
   - You want guided setup for gateway, workspace, auth, channels, and skills
 title: "onboard"
 ---
 
-# `SkyKoi onboard`
+# `SKYKOI onboard`
 
 Interactive onboarding wizard (local or remote Gateway setup).
 
@@ -19,23 +19,23 @@ Interactive onboarding wizard (local or remote Gateway setup).
 ## Examples
 
 ```bash
-SkyKoi onboard
-SkyKoi onboard --flow quickstart
-SkyKoi onboard --flow manual
-SkyKoi onboard --mode remote --remote-url ws://gateway-host:18789
+SKYKOI onboard
+SKYKOI onboard --flow quickstart
+SKYKOI onboard --flow manual
+SKYKOI onboard --mode remote --remote-url ws://gateway-host:18789
 ```
 
 Flow notes:
 
 - `quickstart`: minimal prompts, auto-generates a gateway token.
 - `manual`: full prompts for port/bind/auth (alias of `advanced`).
-- Fastest first chat: `SkyKoi dashboard` (Control UI, no channel setup).
+- Fastest first chat: `SKYKOI dashboard` (Control UI, no channel setup).
 
 ## Common follow-up commands
 
 ```bash
-SkyKoi configure
-SkyKoi agents add <name>
+SKYKOI configure
+SKYKOI agents add <name>
 ```
 
 <Note>

package/docs/cli/pairing.md

@@ -1,11 +1,11 @@
 ---
-summary: "CLI reference for `SkyKoi pairing` (approve/list pairing requests)"
+summary: "CLI reference for `SKYKOI pairing` (approve/list pairing requests)"
 read_when:
   - You’re using pairing-mode DMs and need to approve senders
 title: "pairing"
 ---
 
-# `SkyKoi pairing`
+# `SKYKOI pairing`
 
 Approve or inspect DM pairing requests (for channels that support pairing).
 
@@ -16,6 +16,6 @@ Related:
 ## Commands
 
 ```bash
-SkyKoi pairing list whatsapp
-SkyKoi pairing approve whatsapp <code> --notify
+SKYKOI pairing list whatsapp
+SKYKOI pairing approve whatsapp <code> --notify
 ```

package/docs/cli/plugins.md

@@ -1,12 +1,12 @@
 ---
-summary: "CLI reference for `SkyKoi plugins` (list, install, enable/disable, doctor)"
+summary: "CLI reference for `SKYKOI plugins` (list, install, enable/disable, doctor)"
 read_when:
   - You want to install or manage in-process Gateway plugins
   - You want to debug plugin load failures
 title: "plugins"
 ---
 
-# `SkyKoi plugins`
+# `SKYKOI plugins`
 
 Manage Gateway plugins/extensions (loaded in-process).
 
@@ -19,26 +19,26 @@ Related:
 ## Commands
 
 ```bash
-SkyKoi plugins list
-SkyKoi plugins info <id>
-SkyKoi plugins enable <id>
-SkyKoi plugins disable <id>
-SkyKoi plugins doctor
-SkyKoi plugins update <id>
-SkyKoi plugins update --all
+SKYKOI plugins list
+SKYKOI plugins info <id>
+SKYKOI plugins enable <id>
+SKYKOI plugins disable <id>
+SKYKOI plugins doctor
+SKYKOI plugins update <id>
+SKYKOI plugins update --all
 ```
 
-Bundled plugins ship with SkyKoi but start disabled. Use `plugins enable` to
+Bundled plugins ship with SKYKOI but start disabled. Use `plugins enable` to
 activate them.
 
-All plugins must ship a `SkyKoi.plugin.json` file with an inline JSON Schema
+All plugins must ship a `SKYKOI.plugin.json` file with an inline JSON Schema
 (`configSchema`, even if empty). Missing/invalid manifests or schemas prevent
 the plugin from loading and fail config validation.
 
 ### Install
 
 ```bash
-SkyKoi plugins install <path-or-spec>
+SKYKOI plugins install <path-or-spec>
 ```
 
 Security note: treat plugin installs like running code. Prefer pinned versions.
@@ -48,15 +48,15 @@ Supported archives: `.zip`, `.tgz`, `.tar.gz`, `.tar`.
 Use `--link` to avoid copying a local directory (adds to `plugins.load.paths`):
 
 ```bash
-SkyKoi plugins install -l ./my-plugin
+SKYKOI plugins install -l ./my-plugin
 ```
 
 ### Update
 
 ```bash
-SkyKoi plugins update <id>
-SkyKoi plugins update --all
-SkyKoi plugins update <id> --dry-run
+SKYKOI plugins update <id>
+SKYKOI plugins update --all
+SKYKOI plugins update <id> --dry-run
 ```
 
 Updates only apply to plugins installed from npm (tracked in `plugins.installs`).

package/docs/cli/reset.md

@@ -1,17 +1,17 @@
 ---
-summary: "CLI reference for `SkyKoi reset` (reset local state/config)"
+summary: "CLI reference for `SKYKOI reset` (reset local state/config)"
 read_when:
   - You want to wipe local state while keeping the CLI installed
   - You want a dry-run of what would be removed
 title: "reset"
 ---
 
-# `SkyKoi reset`
+# `SKYKOI reset`
 
 Reset local config/state (keeps the CLI installed).
 
 ```bash
-SkyKoi reset
-SkyKoi reset --dry-run
-SkyKoi reset --scope config+creds+sessions --yes --non-interactive
+SKYKOI reset
+SKYKOI reset --dry-run
+SKYKOI reset --scope config+creds+sessions --yes --non-interactive
 ```

package/docs/cli/sandbox.md

@@ -11,29 +11,29 @@ Manage Docker-based sandbox containers for isolated agent execution.
 
 ## Overview
 
-SkyKoi can run agents in isolated Docker containers for security. The `sandbox` commands help you manage these containers, especially after updates or configuration changes.
+SKYKOI can run agents in isolated Docker containers for security. The `sandbox` commands help you manage these containers, especially after updates or configuration changes.
 
 ## Commands
 
-### `SkyKoi sandbox explain`
+### `SKYKOI sandbox explain`
 
 Inspect the **effective** sandbox mode/scope/workspace access, sandbox tool policy, and elevated gates (with fix-it config key paths).
 
 ```bash
-SkyKoi sandbox explain
-SkyKoi sandbox explain --session agent:main:main
-SkyKoi sandbox explain --agent work
-SkyKoi sandbox explain --json
+SKYKOI sandbox explain
+SKYKOI sandbox explain --session agent:main:main
+SKYKOI sandbox explain --agent work
+SKYKOI sandbox explain --json
 ```
 
-### `SkyKoi sandbox list`
+### `SKYKOI sandbox list`
 
 List all sandbox containers with their status and configuration.
 
 ```bash
-SkyKoi sandbox list
-SkyKoi sandbox list --browser  # List only browser containers
-SkyKoi sandbox list --json     # JSON output
+SKYKOI sandbox list
+SKYKOI sandbox list --browser  # List only browser containers
+SKYKOI sandbox list --json     # JSON output
 ```
 
 **Output includes:**
@@ -44,16 +44,16 @@ SkyKoi sandbox list --json     # JSON output
 - Idle time (time since last use)
 - Associated session/agent
 
-### `SkyKoi sandbox recreate`
+### `SKYKOI sandbox recreate`
 
 Remove sandbox containers to force recreation with updated images/config.
 
 ```bash
-SkyKoi sandbox recreate --all                # Recreate all containers
-SkyKoi sandbox recreate --session main       # Specific session
-SkyKoi sandbox recreate --agent mybot        # Specific agent
-SkyKoi sandbox recreate --browser            # Only browser containers
-SkyKoi sandbox recreate --all --force        # Skip confirmation
+SKYKOI sandbox recreate --all                # Recreate all containers
+SKYKOI sandbox recreate --session main       # Specific session
+SKYKOI sandbox recreate --agent mybot        # Specific agent
+SKYKOI sandbox recreate --browser            # Only browser containers
+SKYKOI sandbox recreate --all --force        # Skip confirmation
 ```
 
 **Options:**
@@ -72,14 +72,14 @@ SkyKoi sandbox recreate --all --force        # Skip confirmation
 
 ```bash
 # Pull new image
-docker pull SkyKoi-sandbox:latest
-docker tag SkyKoi-sandbox:latest SkyKoi-sandbox:bookworm-slim
+docker pull SKYKOI-sandbox:latest
+docker tag SKYKOI-sandbox:latest SKYKOI-sandbox:bookworm-slim
 
 # Update config to use new image
 # Edit config: agents.defaults.sandbox.docker.image (or agents.list[].sandbox.docker.image)
 
 # Recreate containers
-SkyKoi sandbox recreate --all
+SKYKOI sandbox recreate --all
 ```
 
 ### After changing sandbox configuration
@@ -88,22 +88,22 @@ SkyKoi sandbox recreate --all
 # Edit config: agents.defaults.sandbox.* (or agents.list[].sandbox.*)
 
 # Recreate to apply new config
-SkyKoi sandbox recreate --all
+SKYKOI sandbox recreate --all
 ```
 
 ### After changing setupCommand
 
 ```bash
-SkyKoi sandbox recreate --all
+SKYKOI sandbox recreate --all
 # or just one agent:
-SkyKoi sandbox recreate --agent family
+SKYKOI sandbox recreate --agent family
 ```
 
 ### For a specific agent only
 
 ```bash
 # Update only one agent's containers
-SkyKoi sandbox recreate --agent alfred
+SKYKOI sandbox recreate --agent alfred
 ```
 
 ## Why is this needed?
@@ -114,14 +114,14 @@ SkyKoi sandbox recreate --agent alfred
 - Containers are only pruned after 24h of inactivity
 - Regularly-used agents keep old containers running indefinitely
 
-**Solution:** Use `SkyKoi sandbox recreate` to force removal of old containers. They'll be recreated automatically with current settings when next needed.
+**Solution:** Use `SKYKOI sandbox recreate` to force removal of old containers. They'll be recreated automatically with current settings when next needed.
 
-Tip: prefer `SkyKoi sandbox recreate` over manual `docker rm`. It uses the
+Tip: prefer `SKYKOI sandbox recreate` over manual `docker rm`. It uses the
 Gateway’s container naming and avoids mismatches when scope/session keys change.
 
 ## Configuration
 
-Sandbox settings live in `~/.skykoi/skykoi.json` under `agents.defaults.sandbox` (per-agent overrides go in `agents.list[].sandbox`):
+Sandbox settings live in `~/.SKYKOI/SKYKOI.json` under `agents.defaults.sandbox` (per-agent overrides go in `agents.list[].sandbox`):
 
 ```jsonc
 {
@@ -131,8 +131,8 @@ Sandbox settings live in `~/.skykoi/skykoi.json` under `agents.defaults.sandbox`
         "mode": "all", // off, non-main, all
         "scope": "agent", // session, agent, shared
         "docker": {
-          "image": "SkyKoi-sandbox:bookworm-slim",
-          "containerPrefix": "SkyKoi-sbx-",
+          "image": "SKYKOI-sandbox:bookworm-slim",
+          "containerPrefix": "SKYKOI-sbx-",
           // ... more Docker options
         },
         "prune": {

package/docs/cli/security.md

@@ -1,12 +1,12 @@
 ---
-summary: "CLI reference for `SkyKoi security` (audit and fix common security footguns)"
+summary: "CLI reference for `SKYKOI security` (audit and fix common security footguns)"
 read_when:
   - You want to run a quick security audit on config/state
   - You want to apply safe “fix” suggestions (chmod, tighten defaults)
 title: "security"
 ---
 
-# `SkyKoi security`
+# `SKYKOI security`
 
 Security tools (audit + optional fixes).
 
@@ -17,9 +17,9 @@ Related:
 ## Audit
 
 ```bash
-SkyKoi security audit
-SkyKoi security audit --deep
-SkyKoi security audit --fix
+SKYKOI security audit
+SKYKOI security audit --deep
+SKYKOI security audit --fix
 ```
 
 The audit warns when multiple DM senders share the main session and recommends **secure DM mode**: `session.dmScope="per-channel-peer"` (or `per-account-channel-peer` for multi-account channels) for shared inboxes.