skykoi 2026.3.11 → 2026.3.13

package/docs/help/faq.md

@@ -1,5 +1,5 @@
 ---
-summary: "Frequently asked questions about SkyKoi setup, configuration, and usage"
+summary: "Frequently asked questions about SKYKOI setup, configuration, and usage"
 title: "FAQ"
 ---
 
@@ -11,7 +11,7 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
 
 - [Quick start and first-run setup]
   - [Im stuck whats the fastest way to get unstuck?](#im-stuck-whats-the-fastest-way-to-get-unstuck)
-  - [What's the recommended way to install and set up SkyKoi?](#whats-the-recommended-way-to-install-and-set-up-SkyKoi)
+  - [What's the recommended way to install and set up SKYKOI?](#whats-the-recommended-way-to-install-and-set-up-SKYKOI)
   - [How do I open the dashboard after onboarding?](#how-do-i-open-the-dashboard-after-onboarding)
   - [How do I authenticate the dashboard (token) on localhost vs remote?](#how-do-i-authenticate-the-dashboard-token-on-localhost-vs-remote)
   - [What runtime do I need?](#what-runtime-do-i-need)
@@ -20,18 +20,18 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
   - [It is stuck on "wake up my friend" / onboarding will not hatch. What now?](#it-is-stuck-on-wake-up-my-friend-onboarding-will-not-hatch-what-now)
   - [Can I migrate my setup to a new machine (Mac mini) without redoing onboarding?](#can-i-migrate-my-setup-to-a-new-machine-mac-mini-without-redoing-onboarding)
   - [Where do I see what is new in the latest version?](#where-do-i-see-what-is-new-in-the-latest-version)
-  - [I can't access docs.SkyKoi.ai (SSL error). What now?](#i-cant-access-docsSkyKoiai-ssl-error-what-now)
+  - [I can't access docs.SKYKOI.ai (SSL error). What now?](#i-cant-access-docsSKYKOIai-ssl-error-what-now)
   - [What's the difference between stable and beta?](#whats-the-difference-between-stable-and-beta)
   - [How do I install the beta version, and what's the difference between beta and dev?](#how-do-i-install-the-beta-version-and-whats-the-difference-between-beta-and-dev)
   - [How do I try the latest bits?](#how-do-i-try-the-latest-bits)
   - [How long does install and onboarding usually take?](#how-long-does-install-and-onboarding-usually-take)
   - [Installer stuck? How do I get more feedback?](#installer-stuck-how-do-i-get-more-feedback)
-  - [Windows install says git not found or SkyKoi not recognized](#windows-install-says-git-not-found-or-SkyKoi-not-recognized)
+  - [Windows install says git not found or SKYKOI not recognized](#windows-install-says-git-not-found-or-SKYKOI-not-recognized)
   - [The docs didn't answer my question - how do I get a better answer?](#the-docs-didnt-answer-my-question-how-do-i-get-a-better-answer)
-  - [How do I install SkyKoi on Linux?](#how-do-i-install-SkyKoi-on-linux)
-  - [How do I install SkyKoi on a VPS?](#how-do-i-install-SkyKoi-on-a-vps)
+  - [How do I install SKYKOI on Linux?](#how-do-i-install-SKYKOI-on-linux)
+  - [How do I install SKYKOI on a VPS?](#how-do-i-install-SKYKOI-on-a-vps)
   - [Where are the cloud/VPS install guides?](#where-are-the-cloudvps-install-guides)
-  - [Can I ask SkyKoi to update itself?](#can-i-ask-SkyKoi-to-update-itself)
+  - [Can I ask SKYKOI to update itself?](#can-i-ask-SKYKOI-to-update-itself)
   - [What does the onboarding wizard actually do?](#what-does-the-onboarding-wizard-actually-do)
   - [Do I need a Claude or OpenAI subscription to run this?](#do-i-need-a-claude-or-openai-subscription-to-run-this)
   - [Can I use Claude Max subscription without an API key](#can-i-use-claude-max-subscription-without-an-api-key)
@@ -47,24 +47,24 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
   - [How do I keep hosted model traffic in a specific region?](#how-do-i-keep-hosted-model-traffic-in-a-specific-region)
   - [Do I have to buy a Mac Mini to install this?](#do-i-have-to-buy-a-mac-mini-to-install-this)
   - [Do I need a Mac mini for iMessage support?](#do-i-need-a-mac-mini-for-imessage-support)
-  - [If I buy a Mac mini to run SkyKoi, can I connect it to my MacBook Pro?](#if-i-buy-a-mac-mini-to-run-SkyKoi-can-i-connect-it-to-my-macbook-pro)
+  - [If I buy a Mac mini to run SKYKOI, can I connect it to my MacBook Pro?](#if-i-buy-a-mac-mini-to-run-SKYKOI-can-i-connect-it-to-my-macbook-pro)
   - [Can I use Bun?](#can-i-use-bun)
   - [Telegram: what goes in `allowFrom`?](#telegram-what-goes-in-allowfrom)
-  - [Can multiple people use one WhatsApp number with different SkyKoi instances?](#can-multiple-people-use-one-whatsapp-number-with-different-SkyKoi-instances)
+  - [Can multiple people use one WhatsApp number with different SKYKOI instances?](#can-multiple-people-use-one-whatsapp-number-with-different-SKYKOI-instances)
   - [Can I run a "fast chat" agent and an "Opus for coding" agent?](#can-i-run-a-fast-chat-agent-and-an-opus-for-coding-agent)
   - [Does Homebrew work on Linux?](#does-homebrew-work-on-linux)
   - [What's the difference between the hackable (git) install and npm install?](#whats-the-difference-between-the-hackable-git-install-and-npm-install)
   - [Can I switch between npm and git installs later?](#can-i-switch-between-npm-and-git-installs-later)
   - [Should I run the Gateway on my laptop or a VPS?](#should-i-run-the-gateway-on-my-laptop-or-a-vps)
-  - [How important is it to run SkyKoi on a dedicated machine?](#how-important-is-it-to-run-SkyKoi-on-a-dedicated-machine)
+  - [How important is it to run SKYKOI on a dedicated machine?](#how-important-is-it-to-run-SKYKOI-on-a-dedicated-machine)
   - [What are the minimum VPS requirements and recommended OS?](#what-are-the-minimum-vps-requirements-and-recommended-os)
-  - [Can I run SkyKoi in a VM and what are the requirements](#can-i-run-SkyKoi-in-a-vm-and-what-are-the-requirements)
-- [What is SkyKoi?](#what-is-SkyKoi)
-  - [What is SkyKoi, in one paragraph?](#what-is-SkyKoi-in-one-paragraph)
+  - [Can I run SKYKOI in a VM and what are the requirements](#can-i-run-SKYKOI-in-a-vm-and-what-are-the-requirements)
+- [What is SKYKOI?](#what-is-SKYKOI)
+  - [What is SKYKOI, in one paragraph?](#what-is-SKYKOI-in-one-paragraph)
   - [What's the value proposition?](#whats-the-value-proposition)
   - [I just set it up what should I do first](#i-just-set-it-up-what-should-i-do-first)
-  - [What are the top five everyday use cases for SkyKoi](#what-are-the-top-five-everyday-use-cases-for-SkyKoi)
-  - [Can SkyKoi help with lead gen outreach ads and blogs for a SaaS](#can-SkyKoi-help-with-lead-gen-outreach-ads-and-blogs-for-a-saas)
+  - [What are the top five everyday use cases for SKYKOI](#what-are-the-top-five-everyday-use-cases-for-SKYKOI)
+  - [Can SKYKOI help with lead gen outreach ads and blogs for a SaaS](#can-SKYKOI-help-with-lead-gen-outreach-ads-and-blogs-for-a-saas)
   - [What are the advantages vs Claude Code for web development?](#what-are-the-advantages-vs-claude-code-for-web-development)
 - [Skills and automation](#skills-and-automation)
   - [How do I customize skills without keeping the repo dirty?](#how-do-i-customize-skills-without-keeping-the-repo-dirty)
@@ -73,7 +73,7 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
   - [The bot freezes while doing heavy work. How do I offload that?](#the-bot-freezes-while-doing-heavy-work-how-do-i-offload-that)
   - [Cron or reminders do not fire. What should I check?](#cron-or-reminders-do-not-fire-what-should-i-check)
   - [How do I install skills on Linux?](#how-do-i-install-skills-on-linux)
-  - [Can SkyKoi run tasks on a schedule or continuously in the background?](#can-SkyKoi-run-tasks-on-a-schedule-or-continuously-in-the-background)
+  - [Can SKYKOI run tasks on a schedule or continuously in the background?](#can-SKYKOI-run-tasks-on-a-schedule-or-continuously-in-the-background)
   - [Can I run Apple macOS-only skills from Linux?](#can-i-run-apple-macos-only-skills-from-linux)
   - [Do you have a Notion or HeyGen integration?](#do-you-have-a-notion-or-heygen-integration)
   - [How do I install the Chrome extension for browser takeover?](#how-do-i-install-the-chrome-extension-for-browser-takeover)
@@ -85,11 +85,11 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
   - [Does memory persist forever? What are the limits?](#does-memory-persist-forever-what-are-the-limits)
   - [Does semantic memory search require an OpenAI API key?](#does-semantic-memory-search-require-an-openai-api-key)
 - [Where things live on disk](#where-things-live-on-disk)
-  - [Is all data used with SkyKoi saved locally?](#is-all-data-used-with-SkyKoi-saved-locally)
-  - [Where does SkyKoi store its data?](#where-does-SkyKoi-store-its-data)
+  - [Is all data used with SKYKOI saved locally?](#is-all-data-used-with-SKYKOI-saved-locally)
+  - [Where does SKYKOI store its data?](#where-does-SKYKOI-store-its-data)
   - [Where should AGENTS.md / SOUL.md / USER.md / MEMORY.md live?](#where-should-agentsmd-soulmd-usermd-memorymd-live)
   - [What's the recommended backup strategy?](#whats-the-recommended-backup-strategy)
-  - [How do I completely uninstall SkyKoi?](#how-do-i-completely-uninstall-SkyKoi)
+  - [How do I completely uninstall SKYKOI?](#how-do-i-completely-uninstall-SKYKOI)
   - [Can agents work outside the workspace?](#can-agents-work-outside-the-workspace)
   - [I'm in remote mode - where is the session store?](#im-in-remote-mode-where-is-the-session-store)
 - [Config basics](#config-basics)
@@ -100,13 +100,13 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
   - [How do I enable web search (and web fetch)?](#how-do-i-enable-web-search-and-web-fetch)
   - [config.apply wiped my config. How do I recover and avoid this?](#configapply-wiped-my-config-how-do-i-recover-and-avoid-this)
   - [How do I run a central Gateway with specialized workers across devices?](#how-do-i-run-a-central-gateway-with-specialized-workers-across-devices)
-  - [Can the skykoi browser run headless?](#can-the-SkyKoi-browser-run-headless)
+  - [Can the SKYKOI browser run headless?](#can-the-SKYKOI-browser-run-headless)
   - [How do I use Brave for browser control?](#how-do-i-use-brave-for-browser-control)
 - [Remote gateways and nodes](#remote-gateways-and-nodes)
   - [How do commands propagate between Telegram, the gateway, and nodes?](#how-do-commands-propagate-between-telegram-the-gateway-and-nodes)
   - [How can my agent access my computer if the Gateway is hosted remotely?](#how-can-my-agent-access-my-computer-if-the-gateway-is-hosted-remotely)
   - [Tailscale is connected but I get no replies. What now?](#tailscale-is-connected-but-i-get-no-replies-what-now)
-  - [Can two SkyKoi instances talk to each other (local + VPS)?](#can-two-SkyKoi-instances-talk-to-each-other-local-vps)
+  - [Can two SKYKOI instances talk to each other (local + VPS)?](#can-two-SKYKOI-instances-talk-to-each-other-local-vps)
   - [Do I need separate VPSes for multiple agents](#do-i-need-separate-vpses-for-multiple-agents)
   - [Is there a benefit to using a node on my personal laptop instead of SSH from a VPS?](#is-there-a-benefit-to-using-a-node-on-my-personal-laptop-instead-of-ssh-from-a-vps)
   - [Do nodes run a gateway service?](#do-nodes-run-a-gateway-service)
@@ -116,21 +116,21 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
   - [How do I connect a Mac node to a remote Gateway (Tailscale Serve)?](#how-do-i-connect-a-mac-node-to-a-remote-gateway-tailscale-serve)
   - [Should I install on a second laptop or just add a node?](#should-i-install-on-a-second-laptop-or-just-add-a-node)
 - [Env vars and .env loading](#env-vars-and-env-loading)
-  - [How does SkyKoi load environment variables?](#how-does-SkyKoi-load-environment-variables)
+  - [How does SKYKOI load environment variables?](#how-does-SKYKOI-load-environment-variables)
   - ["I started the Gateway via the service and my env vars disappeared." What now?](#i-started-the-gateway-via-the-service-and-my-env-vars-disappeared-what-now)
   - [I set `COPILOT_GITHUB_TOKEN`, but models status shows "Shell env: off." Why?](#i-set-copilotgithubtoken-but-models-status-shows-shell-env-off-why)
 - [Sessions and multiple chats](#sessions-and-multiple-chats)
   - [How do I start a fresh conversation?](#how-do-i-start-a-fresh-conversation)
   - [Do sessions reset automatically if I never send `/new`?](#do-sessions-reset-automatically-if-i-never-send-new)
-  - [Is there a way to make a team of SkyKoi instances one CEO and many agents](#is-there-a-way-to-make-a-team-of-SkyKoi-instances-one-ceo-and-many-agents)
+  - [Is there a way to make a team of SKYKOI instances one CEO and many agents](#is-there-a-way-to-make-a-team-of-SKYKOI-instances-one-ceo-and-many-agents)
   - [Why did context get truncated mid-task? How do I prevent it?](#why-did-context-get-truncated-midtask-how-do-i-prevent-it)
-  - [How do I completely reset SkyKoi but keep it installed?](#how-do-i-completely-reset-SkyKoi-but-keep-it-installed)
+  - [How do I completely reset SKYKOI but keep it installed?](#how-do-i-completely-reset-SKYKOI-but-keep-it-installed)
   - [I'm getting "context too large" errors - how do I reset or compact?](#im-getting-context-too-large-errors-how-do-i-reset-or-compact)
   - [Why am I seeing "LLM request rejected: messages.N.content.X.tool_use.input: Field required"?](#why-am-i-seeing-llm-request-rejected-messagesncontentxtooluseinput-field-required)
   - [Why am I getting heartbeat messages every 30 minutes?](#why-am-i-getting-heartbeat-messages-every-30-minutes)
   - [Do I need to add a "bot account" to a WhatsApp group?](#do-i-need-to-add-a-bot-account-to-a-whatsapp-group)
   - [How do I get the JID of a WhatsApp group?](#how-do-i-get-the-jid-of-a-whatsapp-group)
-  - [Why doesn't SkyKoi reply in a group?](#why-doesnt-SkyKoi-reply-in-a-group)
+  - [Why doesn't SKYKOI reply in a group?](#why-doesnt-SKYKOI-reply-in-a-group)
   - [Do groups/threads share context with DMs?](#do-groupsthreads-share-context-with-dms)
   - [How many workspaces and agents can I create?](#how-many-workspaces-and-agents-can-i-create)
   - [Can I run multiple bots or chats at the same time (Slack), and how should I set that up?](#can-i-run-multiple-bots-or-chats-at-the-same-time-slack-and-how-should-i-set-that-up)
@@ -139,7 +139,7 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
   - [What model do you recommend?](#what-model-do-you-recommend)
   - [How do I switch models without wiping my config?](#how-do-i-switch-models-without-wiping-my-config)
   - [Can I use self-hosted models (llama.cpp, vLLM, Ollama)?](#can-i-use-selfhosted-models-llamacpp-vllm-ollama)
-  - [What do SkyKoi, Flawd, and Krill use for models?](#what-do-SkyKoi-flawd-and-krill-use-for-models)
+  - [What do SKYKOI, Flawd, and Krill use for models?](#what-do-SKYKOI-flawd-and-krill-use-for-models)
   - [How do I switch models on the fly (without restarting)?](#how-do-i-switch-models-on-the-fly-without-restarting)
   - [Can I use GPT 5.2 for daily tasks and Codex 5.3 for coding](#can-i-use-gpt-52-for-daily-tasks-and-codex-53-for-coding)
   - [Why do I see "Model … is not allowed" and then no reply?](#why-do-i-see-model-is-not-allowed-and-then-no-reply)
@@ -160,10 +160,10 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
   - [OAuth vs API key: what's the difference?](#oauth-vs-api-key-whats-the-difference)
 - [Gateway: ports, "already running", and remote mode](#gateway-ports-already-running-and-remote-mode)
   - [What port does the Gateway use?](#what-port-does-the-gateway-use)
-  - [Why does `skykoi gateway status` say `Runtime: running` but `RPC probe: failed`?](#why-does-SkyKoi-gateway-status-say-runtime-running-but-rpc-probe-failed)
-  - [Why does `skykoi gateway status` show `Config (cli)` and `Config (service)` different?](#why-does-SkyKoi-gateway-status-show-config-cli-and-config-service-different)
+  - [Why does `SKYKOI gateway status` say `Runtime: running` but `RPC probe: failed`?](#why-does-SKYKOI-gateway-status-say-runtime-running-but-rpc-probe-failed)
+  - [Why does `SKYKOI gateway status` show `Config (cli)` and `Config (service)` different?](#why-does-SKYKOI-gateway-status-show-config-cli-and-config-service-different)
   - [What does "another gateway instance is already listening" mean?](#what-does-another-gateway-instance-is-already-listening-mean)
-  - [How do I run SkyKoi in remote mode (client connects to a Gateway elsewhere)?](#how-do-i-run-SkyKoi-in-remote-mode-client-connects-to-a-gateway-elsewhere)
+  - [How do I run SKYKOI in remote mode (client connects to a Gateway elsewhere)?](#how-do-i-run-SKYKOI-in-remote-mode-client-connects-to-a-gateway-elsewhere)
   - [The Control UI says "unauthorized" (or keeps reconnecting). What now?](#the-control-ui-says-unauthorized-or-keeps-reconnecting-what-now)
   - [I set `gateway.bind: "tailnet"` but it can't bind / nothing listens](#i-set-gatewaybind-tailnet-but-it-cant-bind-nothing-listens)
   - [Can I run multiple Gateways on the same host?](#can-i-run-multiple-gateways-on-the-same-host)
@@ -171,18 +171,18 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
 - [Logging and debugging](#logging-and-debugging)
   - [Where are logs?](#where-are-logs)
   - [How do I start/stop/restart the Gateway service?](#how-do-i-startstoprestart-the-gateway-service)
-  - [I closed my terminal on Windows - how do I restart SkyKoi?](#i-closed-my-terminal-on-windows-how-do-i-restart-SkyKoi)
+  - [I closed my terminal on Windows - how do I restart SKYKOI?](#i-closed-my-terminal-on-windows-how-do-i-restart-SKYKOI)
   - [The Gateway is up but replies never arrive. What should I check?](#the-gateway-is-up-but-replies-never-arrive-what-should-i-check)
   - ["Disconnected from gateway: no reason" - what now?](#disconnected-from-gateway-no-reason-what-now)
   - [Telegram setMyCommands fails with network errors. What should I check?](#telegram-setmycommands-fails-with-network-errors-what-should-i-check)
   - [TUI shows no output. What should I check?](#tui-shows-no-output-what-should-i-check)
   - [How do I completely stop then start the Gateway?](#how-do-i-completely-stop-then-start-the-gateway)
-  - [ELI5: `skykoi gateway restart` vs `skykoi gateway`](#eli5-SkyKoi-gateway-restart-vs-SkyKoi-gateway)
+  - [ELI5: `SKYKOI gateway restart` vs `SKYKOI gateway`](#eli5-SKYKOI-gateway-restart-vs-SKYKOI-gateway)
   - [What's the fastest way to get more details when something fails?](#whats-the-fastest-way-to-get-more-details-when-something-fails)
 - [Media and attachments](#media-and-attachments)
   - [My skill generated an image/PDF, but nothing was sent](#my-skill-generated-an-imagepdf-but-nothing-was-sent)
 - [Security and access control](#security-and-access-control)
-  - [Is it safe to expose SkyKoi to inbound DMs?](#is-it-safe-to-expose-SkyKoi-to-inbound-dms)
+  - [Is it safe to expose SKYKOI to inbound DMs?](#is-it-safe-to-expose-SKYKOI-to-inbound-dms)
   - [Is prompt injection only a concern for public bots?](#is-prompt-injection-only-a-concern-for-public-bots)
   - [Should my bot have its own email GitHub account or phone number](#should-my-bot-have-its-own-email-github-account-or-phone-number)
   - [Can I give it autonomy over my text messages and is that safe](#can-i-give-it-autonomy-over-my-text-messages-and-is-that-safe)
@@ -200,7 +200,7 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
 1. **Quick status (first check)**
 
    ```bash
-   SkyKoi status
+   SKYKOI status
    ```
 
    Fast local summary: OS + update, gateway/service reachability, agents/sessions, provider config + runtime issues (when gateway is reachable).
@@ -208,7 +208,7 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
 2. **Pasteable report (safe to share)**
 
    ```bash
-   SkyKoi status --all
+   SKYKOI status --all
    ```
 
    Read-only diagnosis with log tail (tokens redacted).
@@ -216,7 +216,7 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
 3. **Daemon + port state**
 
    ```bash
-   skykoi gateway status
+   SKYKOI gateway status
    ```
 
    Shows supervisor runtime vs RPC reachability, the probe target URL, and which config the service likely used.
@@ -224,7 +224,7 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
 4. **Deep probes**
 
    ```bash
-   SkyKoi status --deep
+   SKYKOI status --deep
    ```
 
    Runs gateway health checks + provider probes (requires a reachable gateway). See [Health](/gateway/health).
@@ -232,13 +232,13 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
 5. **Tail the latest log**
 
    ```bash
-   SkyKoi logs --follow
+   SKYKOI logs --follow
    ```
 
    If RPC is down, fall back to:
 
    ```bash
-   tail -f "$(ls -t /tmp/SkyKoi/SkyKoi-*.log | head -1)"
+   tail -f "$(ls -t /tmp/SKYKOI/SKYKOI-*.log | head -1)"
    ```
 
    File logs are separate from service logs; see [Logging](/logging) and [Troubleshooting](/gateway/troubleshooting).
@@ -246,7 +246,7 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
 6. **Run the doctor (repairs)**
 
    ```bash
-   skykoi doctor
+   SKYKOI doctor
    ```
 
    Repairs/migrates config/state + runs health checks. See [Doctor](/gateway/doctor).
@@ -254,8 +254,8 @@ Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS,
 7. **Gateway snapshot**
 
    ```bash
-   SkyKoi health --json
-   SkyKoi health --verbose   # shows the target URL + config path on errors
+   SKYKOI health --json
+   SKYKOI health --verbose   # shows the target URL + config path on errors
    ```
 
    Asks the running gateway for a full snapshot (WS-only). See [Health](/gateway/health).
@@ -276,10 +276,10 @@ setup (PATH, services, permissions, auth files). Give them the **full source che
 the hackable (git) install:
 
 ```bash
-curl -fsSL https://skykoi.com/install.sh | bash -s -- --install-method git
+curl -fsSL https://SKYKOI.com/install.sh | bash -s -- --install-method git
 ```
 
-This installs SkyKoi **from a git checkout**, so the agent can read the code + docs and
+This installs SKYKOI **from a git checkout**, so the agent can read the code + docs and
 reason about the exact version you are running. You can always switch back to stable later
 by re-running the installer without `--install-method git`.
 
@@ -287,36 +287,36 @@ Tip: ask the agent to **plan and supervise** the fix (step-by-step), then execut
 necessary commands. That keeps changes small and easier to audit.
 
 If you discover a real bug or fix, please file a GitHub issue or send a PR:
-[https://github.com/SkyKoi/SkyKoi/issues](https://github.com/SkyKoi/SkyKoi/issues)
-[https://github.com/SkyKoi/SkyKoi/pulls](https://github.com/SkyKoi/SkyKoi/pulls)
+[https://github.com/SKYKOI/SKYKOI/issues](https://github.com/SKYKOI/SKYKOI/issues)
+[https://github.com/SKYKOI/SKYKOI/pulls](https://github.com/SKYKOI/SKYKOI/pulls)
 
 Start with these commands (share outputs when asking for help):
 
 ```bash
-SkyKoi status
-SkyKoi models status
-skykoi doctor
+SKYKOI status
+SKYKOI models status
+SKYKOI doctor
 ```
 
 What they do:
 
-- `skykoi status`: quick snapshot of gateway/agent health + basic config.
-- `skykoi models status`: checks provider auth + model availability.
-- `skykoi doctor`: validates and repairs common config/state issues.
+- `SKYKOI status`: quick snapshot of gateway/agent health + basic config.
+- `SKYKOI models status`: checks provider auth + model availability.
+- `SKYKOI doctor`: validates and repairs common config/state issues.
 
-Other useful CLI checks: `skykoi status --all`, `skykoi logs --follow`,
-`skykoi gateway status`, `skykoi health --verbose`.
+Other useful CLI checks: `SKYKOI status --all`, `SKYKOI logs --follow`,
+`SKYKOI gateway status`, `SKYKOI health --verbose`.
 
 Quick debug loop: [First 60 seconds if something's broken](#first-60-seconds-if-somethings-broken).
 Install docs: [Install](/install), [Installer flags](/install/installer), [Updating](/install/updating).
 
-### What's the recommended way to install and set up SkyKoi
+### What's the recommended way to install and set up SKYKOI
 
 The repo recommends running from source and using the onboarding wizard:
 
 ```bash
-curl -fsSL https://skykoi.com/install.sh | bash
-skykoi onboard --install-daemon
+curl -fsSL https://SKYKOI.com/install.sh | bash
+SKYKOI onboard --install-daemon
 ```
 
 The wizard can also build UI assets automatically. After onboarding, you typically run the Gateway on port **18789**.
@@ -324,15 +324,15 @@ The wizard can also build UI assets automatically. After onboarding, you typical
 From source (contributors/dev):
 
 ```bash
-git clone https://github.com/SkyKoi/SkyKoi.git
-cd SkyKoi
+git clone https://github.com/SKYKOI/SKYKOI.git
+cd SKYKOI
 pnpm install
 pnpm build
 pnpm ui:build # auto-installs UI deps on first run
-skykoi onboard
+SKYKOI onboard
 ```
 
-If you don't have a global install yet, run it via `pnpm skykoi onboard`.
+If you don't have a global install yet, run it via `pnpm SKYKOI onboard`.
 
 ### How do I open the dashboard after onboarding
 
@@ -343,13 +343,13 @@ The wizard opens your browser with a clean (non-tokenized) dashboard URL right a
 **Localhost (same machine):**
 
 - Open `http://127.0.0.1:18789/`.
-- If it asks for auth, paste the token from `gateway.auth.token` (or `SkyKoi_GATEWAY_TOKEN`) into Control UI settings.
-- Retrieve it from the gateway host: `skykoi config get gateway.auth.token` (or generate one: `skykoi doctor --generate-gateway-token`).
+- If it asks for auth, paste the token from `gateway.auth.token` (or `SKYKOI_GATEWAY_TOKEN`) into Control UI settings.
+- Retrieve it from the gateway host: `SKYKOI config get gateway.auth.token` (or generate one: `SKYKOI doctor --generate-gateway-token`).
 
 **Not on localhost:**
 
-- **Tailscale Serve** (recommended): keep bind loopback, run `skykoi gateway --tailscale serve`, open `https://<magicdns>/`. If `gateway.auth.allowTailscale` is `true`, identity headers satisfy auth (no token).
-- **Tailnet bind**: run `skykoi gateway --bind tailnet --token "<token>"`, open `http://<tailscale-ip>:18789/`, paste token in dashboard settings.
+- **Tailscale Serve** (recommended): keep bind loopback, run `SKYKOI gateway --tailscale serve`, open `https://<magicdns>/`. If `gateway.auth.allowTailscale` is `true`, identity headers satisfy auth (no token).
+- **Tailnet bind**: run `SKYKOI gateway --bind tailnet --token "<token>"`, open `http://<tailscale-ip>:18789/`, paste token in dashboard settings.
 - **SSH tunnel**: `ssh -N -L 18789:127.0.0.1:18789 user@host` then open `http://127.0.0.1:18789/` and paste the token in Control UI settings.
 
 See [Dashboard](/web/dashboard) and [Web surfaces](/web) for bind modes and auth details.
@@ -389,21 +389,21 @@ and tokens stay at 0, the agent never ran.
 1. Restart the Gateway:
 
 ```bash
-skykoi gateway restart
+SKYKOI gateway restart
 ```
 
 2. Check status + auth:
 
 ```bash
-SkyKoi status
-SkyKoi models status
-SkyKoi logs --follow
+SKYKOI status
+SKYKOI models status
+SKYKOI logs --follow
 ```
 
 3. If it still hangs, run:
 
 ```bash
-skykoi doctor
+SKYKOI doctor
 ```
 
 If the Gateway is remote, ensure the tunnel/Tailscale connection is up and that the UI
@@ -415,40 +415,40 @@ Yes. Copy the **state directory** and **workspace**, then run Doctor once. This
 keeps your bot "exactly the same" (memory, session history, auth, and channel
 state) as long as you copy **both** locations:
 
-1. Install SkyKoi on the new machine.
-2. Copy `$SkyKoi_STATE_DIR` (default: `~/.SkyKoi`) from the old machine.
-3. Copy your workspace (default: `~/.skykoi/workspace`).
-4. Run `skykoi doctor` and restart the Gateway service.
+1. Install SKYKOI on the new machine.
+2. Copy `$SKYKOI_STATE_DIR` (default: `~/.SKYKOI`) from the old machine.
+3. Copy your workspace (default: `~/.SKYKOI/workspace`).
+4. Run `SKYKOI doctor` and restart the Gateway service.
 
 That preserves config, auth profiles, WhatsApp creds, sessions, and memory. If you're in
 remote mode, remember the gateway host owns the session store and workspace.
 
 **Important:** if you only commit/push your workspace to GitHub, you're backing
 up **memory + bootstrap files**, but **not** session history or auth. Those live
-under `~/.skykoi/` (for example `~/.skykoi/agents/<agentId>/sessions/`).
+under `~/.SKYKOI/` (for example `~/.SKYKOI/agents/<agentId>/sessions/`).
 
-Related: [Migrating](/install/migrating), [Where things live on disk](/help/faq#where-does-SkyKoi-store-its-data),
+Related: [Migrating](/install/migrating), [Where things live on disk](/help/faq#where-does-SKYKOI-store-its-data),
 [Agent workspace](/concepts/agent-workspace), [Doctor](/gateway/doctor),
 [Remote mode](/gateway/remote).
 
 ### Where do I see what is new in the latest version
 
 Check the GitHub changelog:
-[https://github.com/SkyKoi/SkyKoi/blob/main/CHANGELOG.md](https://github.com/SkyKoi/SkyKoi/blob/main/CHANGELOG.md)
+[https://github.com/SKYKOI/SKYKOI/blob/main/CHANGELOG.md](https://github.com/SKYKOI/SKYKOI/blob/main/CHANGELOG.md)
 
 Newest entries are at the top. If the top section is marked **Unreleased**, the next dated
 section is the latest shipped version. Entries are grouped by **Highlights**, **Changes**, and
 **Fixes** (plus docs/other sections when needed).
 
-### I cant access docs.SkyKoi.ai SSL error What now
+### I cant access docs.SKYKOI.ai SSL error What now
 
-Some Comcast/Xfinity connections incorrectly block `docs.SkyKoi.ai` via Xfinity
-Advanced Security. Disable it or allowlist `docs.SkyKoi.ai`, then retry. More
-detail: [Troubleshooting](/help/troubleshooting#docsSkyKoiai-shows-an-ssl-error-comcastxfinity).
+Some Comcast/Xfinity connections incorrectly block `docs.SKYKOI.ai` via Xfinity
+Advanced Security. Disable it or allowlist `docs.SKYKOI.ai`, then retry. More
+detail: [Troubleshooting](/help/troubleshooting#docsSKYKOIai-shows-an-ssl-error-comcastxfinity).
 Please help us unblock it by reporting here: [https://spa.xfinity.com/check_url_status](https://spa.xfinity.com/check_url_status).
 
 If you still can't reach the site, the docs are mirrored on GitHub:
-[https://github.com/SkyKoi/SkyKoi/tree/main/docs](https://github.com/SkyKoi/SkyKoi/tree/main/docs)
+[https://github.com/SKYKOI/SKYKOI/tree/main/docs](https://github.com/SKYKOI/SKYKOI/tree/main/docs)
 
 ### What's the difference between stable and beta
 
@@ -462,7 +462,7 @@ that same version to `latest`**. That's why beta and stable can point at the
 **same version**.
 
 See what changed:
-[https://github.com/SkyKoi/SkyKoi/blob/main/CHANGELOG.md](https://github.com/SkyKoi/SkyKoi/blob/main/CHANGELOG.md)
+[https://github.com/SKYKOI/SKYKOI/blob/main/CHANGELOG.md](https://github.com/SKYKOI/SKYKOI/blob/main/CHANGELOG.md)
 
 ### How do I install the beta version and whats the difference between beta and dev
 
@@ -472,15 +472,15 @@ See what changed:
 One-liners (macOS/Linux):
 
 ```bash
-curl -fsSL --proto '=https' --tlsv1.2 https://skykoi.com/install.sh | bash -s -- --beta
+curl -fsSL --proto '=https' --tlsv1.2 https://SKYKOI.com/install.sh | bash -s -- --beta
 ```
 
 ```bash
-curl -fsSL --proto '=https' --tlsv1.2 https://skykoi.com/install.sh | bash -s -- --install-method git
+curl -fsSL --proto '=https' --tlsv1.2 https://SKYKOI.com/install.sh | bash -s -- --install-method git
 ```
 
 Windows installer (PowerShell):
-[https://skykoi.com/install.ps1](https://skykoi.com/install.ps1)
+[https://SKYKOI.com/install.ps1](https://SKYKOI.com/install.ps1)
 
 More detail: [Development channels](/install/development-channels) and [Installer flags](/install/installer).
 
@@ -501,7 +501,7 @@ Two options:
 1. **Dev channel (git checkout):**
 
 ```bash
-skykoi update --channel dev
+SKYKOI update --channel dev
 ```
 
 This switches to the `main` branch and updates from source.
@@ -509,7 +509,7 @@ This switches to the `main` branch and updates from source.
 2. **Hackable install (from the installer site):**
 
 ```bash
-curl -fsSL https://skykoi.com/install.sh | bash -s -- --install-method git
+curl -fsSL https://SKYKOI.com/install.sh | bash -s -- --install-method git
 ```
 
 That gives you a local repo you can edit, then update via git.
@@ -517,8 +517,8 @@ That gives you a local repo you can edit, then update via git.
 If you prefer a clean clone manually, use:
 
 ```bash
-git clone https://github.com/SkyKoi/SkyKoi.git
-cd SkyKoi
+git clone https://github.com/SKYKOI/SKYKOI.git
+cd SKYKOI
 pnpm install
 pnpm build
 ```
@@ -531,24 +531,24 @@ Docs: [Update](/cli/update), [Development channels](/install/development-channel
 Re-run the installer with **verbose output**:
 
 ```bash
-curl -fsSL https://skykoi.com/install.sh | bash -s -- --verbose
+curl -fsSL https://SKYKOI.com/install.sh | bash -s -- --verbose
 ```
 
 Beta install with verbose:
 
 ```bash
-curl -fsSL https://skykoi.com/install.sh | bash -s -- --beta --verbose
+curl -fsSL https://SKYKOI.com/install.sh | bash -s -- --beta --verbose
 ```
 
 For a hackable (git) install:
 
 ```bash
-curl -fsSL https://skykoi.com/install.sh | bash -s -- --install-method git --verbose
+curl -fsSL https://SKYKOI.com/install.sh | bash -s -- --install-method git --verbose
 ```
 
 More options: [Installer flags](/install/installer).
 
-### Windows install says git not found or SkyKoi not recognized
+### Windows install says git not found or SKYKOI not recognized
 
 Two common Windows issues:
 
@@ -557,7 +557,7 @@ Two common Windows issues:
 - Install **Git for Windows** and make sure `git` is on your PATH.
 - Close and reopen PowerShell, then re-run the installer.
 
-**2) SkyKoi is not recognized after install**
+**2) SKYKOI is not recognized after install**
 
 - Your npm global bin folder is not on PATH.
 - Check the path:
@@ -578,12 +578,12 @@ Use the **hackable (git) install** so you have the full source and docs locally,
 your bot (or Claude/Codex) _from that folder_ so it can read the repo and answer precisely.
 
 ```bash
-curl -fsSL https://skykoi.com/install.sh | bash -s -- --install-method git
+curl -fsSL https://SKYKOI.com/install.sh | bash -s -- --install-method git
 ```
 
 More detail: [Install](/install) and [Installer flags](/install/installer).
 
-### How do I install SkyKoi on Linux
+### How do I install SKYKOI on Linux
 
 Short answer: follow the Linux guide, then run the onboarding wizard.
 
@@ -591,7 +591,7 @@ Short answer: follow the Linux guide, then run the onboarding wizard.
 - Full walkthrough: [Getting Started](/start/getting-started).
 - Installer + updates: [Install & updates](/install/updating).
 
-### How do I install SkyKoi on a VPS
+### How do I install SKYKOI on a VPS
 
 Any Linux VPS works. Install on the server, then use SSH/Tailscale to reach the Gateway.
 
@@ -618,7 +618,7 @@ Gateway in the cloud.
 Hub: [Platforms](/platforms). Remote access: [Gateway remote](/gateway/remote).
 Nodes: [Nodes](/nodes), [Nodes CLI](/cli/nodes).
 
-### Can I ask SkyKoi to update itself
+### Can I ask SKYKOI to update itself
 
 Short answer: **possible, not recommended**. The update flow can restart the
 Gateway (which drops the active session), may need a clean git checkout, and
@@ -627,25 +627,25 @@ can prompt for confirmation. Safer: run updates from a shell as the operator.
 Use the CLI:
 
 ```bash
-skykoi update
-skykoi update status
-skykoi update --channel stable|beta|dev
-skykoi update --tag <dist-tag|version>
-skykoi update --no-restart
+SKYKOI update
+SKYKOI update status
+SKYKOI update --channel stable|beta|dev
+SKYKOI update --tag <dist-tag|version>
+SKYKOI update --no-restart
 ```
 
 If you must automate from an agent:
 
 ```bash
-skykoi update --yes --no-restart
-skykoi gateway restart
+SKYKOI update --yes --no-restart
+SKYKOI gateway restart
 ```
 
 Docs: [Update](/cli/update), [Updating](/install/updating).
 
 ### What does the onboarding wizard actually do
 
-`skykoi onboard` is the recommended setup path. In **local mode** it walks you through:
+`SKYKOI onboard` is the recommended setup path. In **local mode** it walks you through:
 
 - **Model/auth setup** (Anthropic **setup-token** recommended for Claude subscriptions, OpenAI Codex OAuth supported, API keys optional, LM Studio local models supported)
 - **Workspace** location + bootstrap files
@@ -658,7 +658,7 @@ It also warns if your configured model is unknown or missing auth.
 
 ### Do I need a Claude or OpenAI subscription to run this
 
-No. You can run SkyKoi with **API keys** (Anthropic/OpenAI/others) or with
+No. You can run SKYKOI with **API keys** (Anthropic/OpenAI/others) or with
 **local-only models** so your data stays on your device. Subscriptions (Claude
 Pro/Max or OpenAI Codex) are optional ways to authenticate those providers.
 
@@ -677,7 +677,7 @@ If you want the most explicit, supported path, use an Anthropic API key.
 
 ### How does Anthropic setuptoken auth work
 
-`claude setup-token` generates a **token string** via the Claude Code CLI (it is not available in the web console). You can run it on **any machine**. Choose **Anthropic token (paste setup-token)** in the wizard or paste it with `skykoi models auth paste-token --provider anthropic`. The token is stored as an auth profile for the **anthropic** provider and used like an API key (no auto-refresh). More detail: [OAuth](/concepts/oauth).
+`claude setup-token` generates a **token string** via the Claude Code CLI (it is not available in the web console). You can run it on **any machine**. Choose **Anthropic token (paste setup-token)** in the wizard or paste it with `SKYKOI models auth paste-token --provider anthropic`. The token is stored as an auth profile for the **anthropic** provider and used like an API key (no auto-refresh). More detail: [OAuth](/concepts/oauth).
 
 ### Where do I find an Anthropic setuptoken
 
@@ -687,11 +687,11 @@ It is **not** in the Anthropic Console. The setup-token is generated by the **Cl
 claude setup-token
 ```
 
-Copy the token it prints, then choose **Anthropic token (paste setup-token)** in the wizard. If you want to run it on the gateway host, use `skykoi models auth setup-token --provider anthropic`. If you ran `claude setup-token` elsewhere, paste it on the gateway host with `skykoi models auth paste-token --provider anthropic`. See [Anthropic](/providers/anthropic).
+Copy the token it prints, then choose **Anthropic token (paste setup-token)** in the wizard. If you want to run it on the gateway host, use `SKYKOI models auth setup-token --provider anthropic`. If you ran `claude setup-token` elsewhere, paste it on the gateway host with `SKYKOI models auth paste-token --provider anthropic`. See [Anthropic](/providers/anthropic).
 
 ### Do you support Claude subscription auth (Claude Pro or Max)
 
-Yes - via **setup-token**. SkyKoi no longer reuses Claude Code CLI OAuth tokens; use a setup-token or an Anthropic API key. Generate the token anywhere and paste it on the gateway host. See [Anthropic](/providers/anthropic) and [OAuth](/concepts/oauth).
+Yes - via **setup-token**. SKYKOI no longer reuses Claude Code CLI OAuth tokens; use a setup-token or an Anthropic API key. Generate the token anywhere and paste it on the gateway host. See [Anthropic](/providers/anthropic) and [OAuth](/concepts/oauth).
 
 Note: Claude subscription access is governed by Anthropic's terms. For production or multi-user workloads, API keys are usually the safer choice.
 
@@ -702,7 +702,7 @@ use a **Claude subscription** (setup-token or Claude Code OAuth), wait for the w
 reset or upgrade your plan. If you use an **Anthropic API key**, check the Anthropic Console
 for usage/billing and raise limits as needed.
 
-Tip: set a **fallback model** so SkyKoi can keep replying while a provider is rate-limited.
+Tip: set a **fallback model** so SKYKOI can keep replying while a provider is rate-limited.
 See [Models](/cli/models) and [OAuth](/concepts/oauth).
 
 ### Is AWS Bedrock supported
@@ -711,29 +711,29 @@ Yes - via pi-ai's **Amazon Bedrock (Converse)** provider with **manual config**.
 
 ### How does Codex auth work
 
-SkyKoi supports **OpenAI Code (Codex)** via OAuth (ChatGPT sign-in). The wizard can run the OAuth flow and will set the default model to `openai-codex/gpt-5.3-codex` when appropriate. See [Model providers](/concepts/model-providers) and [Wizard](/start/wizard).
+SKYKOI supports **OpenAI Code (Codex)** via OAuth (ChatGPT sign-in). The wizard can run the OAuth flow and will set the default model to `openai-codex/gpt-5.3-codex` when appropriate. See [Model providers](/concepts/model-providers) and [Wizard](/start/wizard).
 
 ### Do you support OpenAI subscription auth Codex OAuth
 
-Yes. SkyKoi fully supports **OpenAI Code (Codex) subscription OAuth**. The onboarding wizard
+Yes. SKYKOI fully supports **OpenAI Code (Codex) subscription OAuth**. The onboarding wizard
 can run the OAuth flow for you.
 
 See [OAuth](/concepts/oauth), [Model providers](/concepts/model-providers), and [Wizard](/start/wizard).
 
 ### How do I set up Gemini CLI OAuth
 
-Gemini CLI uses a **plugin auth flow**, not a client id or secret in `SkyKoi.json`.
+Gemini CLI uses a **plugin auth flow**, not a client id or secret in `SKYKOI.json`.
 
 Steps:
 
-1. Enable the plugin: `skykoi plugins enable google-gemini-cli-auth`
-2. Login: `skykoi models auth login --provider google-gemini-cli --set-default`
+1. Enable the plugin: `SKYKOI plugins enable google-gemini-cli-auth`
+2. Login: `SKYKOI models auth login --provider google-gemini-cli --set-default`
 
 This stores OAuth tokens in auth profiles on the gateway host. Details: [Model providers](/concepts/model-providers).
 
 ### Is a local model OK for casual chats
 
-Usually no. SkyKoi needs large context + strong safety; small cards truncate and leak. If you must, run the **largest** MiniMax M2.1 build you can locally (LM Studio) and see [/gateway/local-models](/gateway/local-models). Smaller/quantized models increase prompt-injection risk - see [Security](/gateway/security).
+Usually no. SKYKOI needs large context + strong safety; small cards truncate and leak. If you must, run the **largest** MiniMax M2.1 build you can locally (LM Studio) and see [/gateway/local-models](/gateway/local-models). Smaller/quantized models increase prompt-injection risk - see [Security](/gateway/security).
 
 ### How do I keep hosted model traffic in a specific region
 
@@ -741,7 +741,7 @@ Pick region-pinned endpoints. OpenRouter exposes US-hosted options for MiniMax,
 
 ### Do I have to buy a Mac Mini to install this
 
-No. SkyKoi runs on macOS or Linux (Windows via WSL2). A Mac mini is optional - some people
+No. SKYKOI runs on macOS or Linux (Windows via WSL2). A Mac mini is optional - some people
 buy one as an always-on host, but a small VPS, home server, or Raspberry Pi-class box works too.
 
 You only need a Mac **for macOS-only tools**. For iMessage, use [BlueBubbles](/channels/bluebubbles) (recommended) - the BlueBubbles server runs on any Mac, and the Gateway can run on Linux or elsewhere. If you want other macOS-only tools, run the Gateway on a Mac or pair a macOS node.
@@ -761,7 +761,7 @@ Common setups:
 Docs: [BlueBubbles](/channels/bluebubbles), [Nodes](/nodes),
 [Mac remote mode](/platforms/mac/remote).
 
-### If I buy a Mac mini to run SkyKoi can I connect it to my MacBook Pro
+### If I buy a Mac mini to run SKYKOI can I connect it to my MacBook Pro
 
 Yes. The **Mac mini can run the Gateway**, and your MacBook Pro can connect as a
 **node** (companion device). Nodes don't run the Gateway - they provide extra
@@ -771,7 +771,7 @@ Common pattern:
 
 - Gateway on the Mac mini (always-on).
 - MacBook Pro runs the macOS app or a node host and pairs to the Gateway.
-- Use `skykoi nodes status` / `skykoi nodes list` to see it.
+- Use `SKYKOI nodes status` / `SKYKOI nodes list` to see it.
 
 Docs: [Nodes](/nodes), [Nodes CLI](/cli/nodes).
 
@@ -789,7 +789,7 @@ without WhatsApp/Telegram.
 
 Safer (no third-party bot):
 
-- DM your bot, then run `skykoi logs --follow` and read `from.id`.
+- DM your bot, then run `SKYKOI logs --follow` and read `from.id`.
 
 Official Bot API:
 
@@ -801,7 +801,7 @@ Third-party (less private):
 
 See [/channels/telegram](/channels/telegram#access-control-dms--groups).
 
-### Can multiple people use one WhatsApp number with different SkyKoi instances
+### Can multiple people use one WhatsApp number with different SKYKOI instances
 
 Yes, via **multi-agent routing**. Bind each sender's WhatsApp **DM** (peer `kind: "dm"`, sender E.164 like `+15551234567`) to a different `agentId`, so each person gets their own workspace and session store. Replies still come from the **same WhatsApp account**, and DM access control (`channels.whatsapp.dmPolicy` / `channels.whatsapp.allowFrom`) is global per WhatsApp account. See [Multi-Agent Routing](/concepts/multi-agent) and [WhatsApp](/channels/whatsapp).
 
@@ -820,7 +820,7 @@ eval "$(/home/linuxbrew/.linuxbrew/bin/brew shellenv)"
 brew install <formula>
 ```
 
-If you run SkyKoi via systemd, ensure the service PATH includes `/home/linuxbrew/.linuxbrew/bin` (or your brew prefix) so `brew`-installed tools resolve in non-login shells.
+If you run SKYKOI via systemd, ensure the service PATH includes `/home/linuxbrew/.linuxbrew/bin` (or your brew prefix) so `brew`-installed tools resolve in non-login shells.
 Recent builds also prepend common user bin dirs on Linux systemd services (for example `~/.local/bin`, `~/.npm-global/bin`, `~/.local/share/pnpm`, `~/.bun/bin`) and honor `PNPM_HOME`, `NPM_CONFIG_PREFIX`, `BUN_INSTALL`, `VOLTA_HOME`, `ASDF_DATA_DIR`, `NVM_DIR`, and `FNM_DIR` when set.
 
 ### What's the difference between the hackable git install and npm install
@@ -835,26 +835,26 @@ Docs: [Getting started](/start/getting-started), [Updating](/install/updating).
 ### Can I switch between npm and git installs later
 
 Yes. Install the other flavor, then run Doctor so the gateway service points at the new entrypoint.
-This **does not delete your data** - it only changes the SkyKoi code install. Your state
-(`~/.SkyKoi`) and workspace (`~/.skykoi/workspace`) stay untouched.
+This **does not delete your data** - it only changes the SKYKOI code install. Your state
+(`~/.SKYKOI`) and workspace (`~/.SKYKOI/workspace`) stay untouched.
 
 From npm → git:
 
 ```bash
-git clone https://github.com/SkyKoi/SkyKoi.git
-cd SkyKoi
+git clone https://github.com/SKYKOI/SKYKOI.git
+cd SKYKOI
 pnpm install
 pnpm build
-skykoi doctor
-skykoi gateway restart
+SKYKOI doctor
+SKYKOI gateway restart
 ```
 
 From git → npm:
 
 ```bash
-npm install -g SkyKoi@latest
-skykoi doctor
-skykoi gateway restart
+npm install -g SKYKOI@latest
+SKYKOI doctor
+SKYKOI gateway restart
 ```
 
 Doctor detects a gateway service entrypoint mismatch and offers to rewrite the service config to match the current install (use `--repair` in automation).
@@ -876,11 +876,11 @@ lowest friction and you're okay with sleep/restarts, run it locally.
 - **Pros:** always-on, stable network, no laptop sleep issues, easier to keep running.
 - **Cons:** often run headless (use screenshots), remote file access only, you must SSH for updates.
 
-**SkyKoi-specific note:** WhatsApp/Telegram/Slack/Mattermost (plugin)/Discord all work fine from a VPS. The only real trade-off is **headless browser** vs a visible window. See [Browser](/tools/browser).
+**SKYKOI-specific note:** WhatsApp/Telegram/Slack/Mattermost (plugin)/Discord all work fine from a VPS. The only real trade-off is **headless browser** vs a visible window. See [Browser](/tools/browser).
 
 **Recommended default:** VPS if you had gateway disconnects before. Local is great when you're actively using the Mac and want local file access or UI automation with a visible browser.
 
-### How important is it to run SkyKoi on a dedicated machine
+### How important is it to run SKYKOI on a dedicated machine
 
 Not required, but **recommended for reliability and isolation**.
 
@@ -892,7 +892,7 @@ For security guidance, read [Security](/gateway/security).
 
 ### What are the minimum VPS requirements and recommended OS
 
-SkyKoi is lightweight. For a basic Gateway + one chat channel:
+SKYKOI is lightweight. For a basic Gateway + one chat channel:
 
 - **Absolute minimum:** 1 vCPU, 1GB RAM, ~500MB disk.
 - **Recommended:** 1-2 vCPU, 2GB RAM or more for headroom (logs, media, multiple channels). Node tools and browser automation can be resource hungry.
@@ -901,7 +901,7 @@ OS: use **Ubuntu LTS** (or any modern Debian/Ubuntu). The Linux install path is
 
 Docs: [Linux](/platforms/linux), [VPS hosting](/vps).
 
-### Can I run SkyKoi in a VM and what are the requirements
+### Can I run SKYKOI in a VM and what are the requirements
 
 Yes. Treat a VM the same as a VPS: it needs to be always on, reachable, and have enough
 RAM for the Gateway and any channels you enable.
@@ -916,15 +916,15 @@ If you are on Windows, **WSL2 is the easiest VM style setup** and has the best t
 compatibility. See [Windows](/platforms/windows), [VPS hosting](/vps).
 If you are running macOS in a VM, see [macOS VM](/install/macos-vm).
 
-## What is SkyKoi?
+## What is SKYKOI?
 
-### What is SkyKoi in one paragraph
+### What is SKYKOI in one paragraph
 
-SkyKoi is a personal AI assistant you run on your own devices. It replies on the messaging surfaces you already use (WhatsApp, Telegram, Slack, Mattermost (plugin), Discord, Google Chat, Signal, iMessage, WebChat) and can also do voice + a live Canvas on supported platforms. The **Gateway** is the always-on control plane; the assistant is the product.
+SKYKOI is a personal AI assistant you run on your own devices. It replies on the messaging surfaces you already use (WhatsApp, Telegram, Slack, Mattermost (plugin), Discord, Google Chat, Signal, iMessage, WebChat) and can also do voice + a live Canvas on supported platforms. The **Gateway** is the always-on control plane; the assistant is the product.
 
 ### What's the value proposition
 
-SkyKoi is not "just a Claude wrapper." It's a **local-first control plane** that lets you run a
+SKYKOI is not "just a Claude wrapper." It's a **local-first control plane** that lets you run a
 capable assistant on **your own hardware**, reachable from the chat apps you already use, with
 stateful sessions, memory, and tools - without handing control of your workflows to a hosted
 SaaS.
@@ -957,7 +957,7 @@ Good first projects:
 It can handle large tasks, but it works best when you split them into phases and
 use sub agents for parallel work.
 
-### What are the top five everyday use cases for SkyKoi
+### What are the top five everyday use cases for SKYKOI
 
 Everyday wins usually look like:
 
@@ -967,21 +967,21 @@ Everyday wins usually look like:
 - **Browser automation:** filling forms, collecting data, and repeating web tasks.
 - **Cross device coordination:** send a task from your phone, let the Gateway run it on a server, and get the result back in chat.
 
-### Can SkyKoi help with lead gen outreach ads and blogs for a SaaS
+### Can SKYKOI help with lead gen outreach ads and blogs for a SaaS
 
 Yes for **research, qualification, and drafting**. It can scan sites, build shortlists,
 summarize prospects, and write outreach or ad copy drafts.
 
 For **outreach or ad runs**, keep a human in the loop. Avoid spam, follow local laws and
 platform policies, and review anything before it is sent. The safest pattern is to let
-SkyKoi draft and you approve.
+SKYKOI draft and you approve.
 
 Docs: [Security](/gateway/security).
 
 ### What are the advantages vs Claude Code for web development
 
-SkyKoi is a **personal assistant** and coordination layer, not an IDE replacement. Use
-Claude Code or Codex for the fastest direct coding loop inside a repo. Use SkyKoi when you
+SKYKOI is a **personal assistant** and coordination layer, not an IDE replacement. Use
+Claude Code or Codex for the fastest direct coding loop inside a repo. Use SKYKOI when you
 want durable memory, cross-device access, and tool orchestration.
 
 Advantages:
@@ -992,17 +992,17 @@ Advantages:
 - **Always-on Gateway** (run on a VPS, interact from anywhere)
 - **Nodes** for local browser/screen/camera/exec
 
-Showcase: [https://skykoi.com/showcase](https://skykoi.com/showcase)
+Showcase: [https://SKYKOI.com/showcase](https://SKYKOI.com/showcase)
 
 ## Skills and automation
 
 ### How do I customize skills without keeping the repo dirty
 
-Use managed overrides instead of editing the repo copy. Put your changes in `~/.skykoi/skills/<name>/SKILL.md` (or add a folder via `skills.load.extraDirs` in `~/.skykoi/skykoi.json`). Precedence is `<workspace>/skills` > `~/.skykoi/skills` > bundled, so managed overrides win without touching git. Only upstream-worthy edits should live in the repo and go out as PRs.
+Use managed overrides instead of editing the repo copy. Put your changes in `~/.SKYKOI/skills/<name>/SKILL.md` (or add a folder via `skills.load.extraDirs` in `~/.SKYKOI/SKYKOI.json`). Precedence is `<workspace>/skills` > `~/.SKYKOI/skills` > bundled, so managed overrides win without touching git. Only upstream-worthy edits should live in the repo and go out as PRs.
 
 ### Can I load skills from a custom folder
 
-Yes. Add extra directories via `skills.load.extraDirs` in `~/.skykoi/skykoi.json` (lowest precedence). Default precedence remains: `<workspace>/skills` → `~/.skykoi/skills` → bundled → `skills.load.extraDirs`. `SkyKoi Skills` installs into `./skills` by default, which SkyKoi treats as `<workspace>/skills`.
+Yes. Add extra directories via `skills.load.extraDirs` in `~/.SKYKOI/SKYKOI.json` (lowest precedence). Default precedence remains: `<workspace>/skills` → `~/.SKYKOI/skills` → bundled → `skills.load.extraDirs`. `SKYKOI Skills` installs into `./skills` by default, which SKYKOI treats as `<workspace>/skills`.
 
 ### How can I use different models for different tasks
 
@@ -1034,35 +1034,35 @@ scheduled jobs will not run.
 
 Checklist:
 
-- Confirm cron is enabled (`cron.enabled`) and `SkyKoi_SKIP_CRON` is not set.
+- Confirm cron is enabled (`cron.enabled`) and `SKYKOI_SKIP_CRON` is not set.
 - Check the Gateway is running 24/7 (no sleep/restarts).
 - Verify timezone settings for the job (`--tz` vs host timezone).
 
 Debug:
 
 ```bash
-SkyKoi cron run <jobId> --force
-SkyKoi cron runs --id <jobId> --limit 50
+SKYKOI cron run <jobId> --force
+SKYKOI cron runs --id <jobId> --limit 50
 ```
 
 Docs: [Cron jobs](/automation/cron-jobs), [Cron vs Heartbeat](/automation/cron-vs-heartbeat).
 
 ### How do I install skills on Linux
 
-Use **SkyKoi Skills** (CLI) or drop skills into your workspace. The macOS Skills UI isn't available on Linux.
-Browse skills at [https://skykoi.com/skills](https://skykoi.com/skills).
+Use **SKYKOI Skills** (CLI) or drop skills into your workspace. The macOS Skills UI isn't available on Linux.
+Browse skills at [https://SKYKOI.com/skills](https://SKYKOI.com/skills).
 
-Install the SkyKoi Skills CLI (pick one package manager):
+Install the SKYKOI Skills CLI (pick one package manager):
 
 ```bash
-npm i -g SkyKoi Skills
+npm i -g SKYKOI Skills
 ```
 
 ```bash
-pnpm add -g SkyKoi Skills
+pnpm add -g SKYKOI Skills
 ```
 
-### Can SkyKoi run tasks on a schedule or continuously in the background
+### Can SKYKOI run tasks on a schedule or continuously in the background
 
 Yes. Use the Gateway scheduler:
 
@@ -1075,15 +1075,15 @@ Docs: [Cron jobs](/automation/cron-jobs), [Cron vs Heartbeat](/automation/cron-v
 
 ### Can I run Apple macOS-only skills from Linux?
 
-Not directly. macOS skills are gated by `metadata.SkyKoi.os` plus required binaries, and skills only appear in the system prompt when they are eligible on the **Gateway host**. On Linux, `darwin`-only skills (like `apple-notes`, `apple-reminders`, `things-mac`) will not load unless you override the gating.
+Not directly. macOS skills are gated by `metadata.SKYKOI.os` plus required binaries, and skills only appear in the system prompt when they are eligible on the **Gateway host**. On Linux, `darwin`-only skills (like `apple-notes`, `apple-reminders`, `things-mac`) will not load unless you override the gating.
 
 You have three supported patterns:
 
 **Option A - run the Gateway on a Mac (simplest).**
-Run the Gateway where the macOS binaries exist, then connect from Linux in [remote mode](#how-do-i-run-SkyKoi-in-remote-mode-client-connects-to-a-gateway-elsewhere) or over Tailscale. The skills load normally because the Gateway host is macOS.
+Run the Gateway where the macOS binaries exist, then connect from Linux in [remote mode](#how-do-i-run-SKYKOI-in-remote-mode-client-connects-to-a-gateway-elsewhere) or over Tailscale. The skills load normally because the Gateway host is macOS.
 
 **Option B - use a macOS node (no SSH).**
-Run the Gateway on Linux, pair a macOS node (menubar app), and set **Node Run Commands** to "Always Ask" or "Always Allow" on the Mac. SkyKoi can treat macOS-only skills as eligible when the required binaries exist on the node. The agent runs those skills via the `nodes` tool. If you choose "Always Ask", approving "Always Allow" in the prompt adds that command to the allowlist.
+Run the Gateway on Linux, pair a macOS node (menubar app), and set **Node Run Commands** to "Always Ask" or "Always Allow" on the Mac. SKYKOI can treat macOS-only skills as eligible when the required binaries exist on the node. The agent runs those skills via the `nodes` tool. If you choose "Always Ask", approving "Always Allow" in the prompt adds that command to the allowlist.
 
 **Option C - proxy macOS binaries over SSH (advanced).**
 Keep the Gateway on Linux, but make the required CLI binaries resolve to SSH wrappers that run on a Mac. Then override the skill to allow Linux so it stays eligible.
@@ -1097,13 +1097,13 @@ Keep the Gateway on Linux, but make the required CLI binaries resolve to SSH wra
    ```
 
 2. Put the wrapper on `PATH` on the Linux host (for example `~/bin/memo`).
-3. Override the skill metadata (workspace or `~/.skykoi/skills`) to allow Linux:
+3. Override the skill metadata (workspace or `~/.SKYKOI/skills`) to allow Linux:
 
    ```markdown
    ---
    name: apple-notes
    description: Manage Apple Notes via the memo CLI on macOS.
-   metadata: { "SkyKoi": { "os": ["darwin", "linux"], "requires": { "bins": ["memo"] } } }
+   metadata: { "SKYKOI": { "os": ["darwin", "linux"], "requires": { "bins": ["memo"] } } }
    ---
    ```
 
@@ -1129,19 +1129,19 @@ targeting those APIs.
 Install skills:
 
 ```bash
-SkyKoi Skills install <skill-slug>
-SkyKoi Skills update --all
+SKYKOI Skills install <skill-slug>
+SKYKOI Skills update --all
 ```
 
-SkyKoi Skills installs into `./skills` under your current directory (or falls back to your configured SkyKoi workspace); SkyKoi treats that as `<workspace>/skills` on the next session. For shared skills across agents, place them in `~/.skykoi/skills/<name>/SKILL.md`. Some skills expect binaries installed via Homebrew; on Linux that means Linuxbrew (see the Homebrew Linux FAQ entry above). See [Skills](/tools/skills) and [SkyKoi Skills](/tools/SkyKoi Skills).
+SKYKOI Skills installs into `./skills` under your current directory (or falls back to your configured SKYKOI workspace); SKYKOI treats that as `<workspace>/skills` on the next session. For shared skills across agents, place them in `~/.SKYKOI/skills/<name>/SKILL.md`. Some skills expect binaries installed via Homebrew; on Linux that means Linuxbrew (see the Homebrew Linux FAQ entry above). See [Skills](/tools/skills) and [SKYKOI Skills](/tools/SKYKOI Skills).
 
 ### How do I install the Chrome extension for browser takeover
 
 Use the built-in installer, then load the unpacked extension in Chrome:
 
 ```bash
-skykoi browser extension install
-skykoi browser extension path
+SKYKOI browser extension install
+SKYKOI browser extension path
 ```
 
 Then Chrome → `chrome://extensions` → enable "Developer mode" → "Load unpacked" → pick that folder.
@@ -1163,8 +1163,8 @@ Yes. See [Sandboxing](/gateway/sandboxing). For Docker-specific setup (full gate
 The default image is security-first and runs as the `node` user, so it does not
 include system packages, Homebrew, or bundled browsers. For a fuller setup:
 
-- Persist `/home/node` with `SkyKoi_HOME_VOLUME` so caches survive.
-- Bake system deps into the image with `SkyKoi_DOCKER_APT_PACKAGES`.
+- Persist `/home/node` with `SKYKOI_HOME_VOLUME` so caches survive.
+- Bake system deps into the image with `SKYKOI_DOCKER_APT_PACKAGES`.
 - Install Playwright browsers via the bundled CLI:
   `node /app/node_modules/playwright-core/cli.js install chromium`
 - Set `PLAYWRIGHT_BROWSERS_PATH` and ensure the path is persisted.
@@ -1187,12 +1187,12 @@ Set `agents.defaults.sandbox.docker.binds` to `["host:path:mode"]` (e.g., `"/hom
 
 ### How does memory work
 
-SkyKoi memory is just Markdown files in the agent workspace:
+SKYKOI memory is just Markdown files in the agent workspace:
 
 - Daily notes in `memory/YYYY-MM-DD.md`
 - Curated long-term notes in `MEMORY.md` (main/private sessions only)
 
-SkyKoi also runs a **silent pre-compaction memory flush** to remind the model
+SKYKOI also runs a **silent pre-compaction memory flush** to remind the model
 to write durable notes before auto-compaction. This only runs when the workspace
 is writable (read-only sandboxes skip it). See [Memory](/concepts/memory).
 
@@ -1214,11 +1214,11 @@ does **not** grant embeddings access, so **signing in with Codex (OAuth or the
 Codex CLI login)** does not help for semantic memory search. OpenAI embeddings
 still need a real API key (`OPENAI_API_KEY` or `models.providers.openai.apiKey`).
 
-If you don't set a provider explicitly, SkyKoi auto-selects a provider when it
+If you don't set a provider explicitly, SKYKOI auto-selects a provider when it
 can resolve an API key (auth profiles, `models.providers.*.apiKey`, or env vars).
 It prefers OpenAI if an OpenAI key resolves, otherwise Gemini if a Gemini key
 resolves. If neither key is available, memory search stays disabled until you
-configure it. If you have a local model path configured and present, SkyKoi
+configure it. If you have a local model path configured and present, SKYKOI
 prefers `local`.
 
 If you'd rather stay local, set `memorySearch.provider = "local"` (and optionally
@@ -1238,12 +1238,12 @@ Docs: [Memory](/concepts/memory), [Context](/concepts/context).
 
 ## Where things live on disk
 
-### Is all data used with SkyKoi saved locally
+### Is all data used with SKYKOI saved locally
 
-No - **SkyKoi's state is local**, but **external services still see what you send them**.
+No - **SKYKOI's state is local**, but **external services still see what you send them**.
 
 - **Local by default:** sessions, memory files, config, and workspace live on the Gateway host
-  (`~/.SkyKoi` + your workspace directory).
+  (`~/.SKYKOI` + your workspace directory).
 - **Remote by necessity:** messages you send to model providers (Anthropic/OpenAI/etc.) go to
   their APIs, and chat platforms (WhatsApp/Telegram/Slack/etc.) store message data on their
   servers.
@@ -1252,39 +1252,39 @@ No - **SkyKoi's state is local**, but **external services still see what you sen
 
 Related: [Agent workspace](/concepts/agent-workspace), [Memory](/concepts/memory).
 
-### Where does SkyKoi store its data
+### Where does SKYKOI store its data
 
-Everything lives under `$SkyKoi_STATE_DIR` (default: `~/.SkyKoi`):
+Everything lives under `$SKYKOI_STATE_DIR` (default: `~/.SKYKOI`):
 
 | Path                                                            | Purpose                                                      |
 | --------------------------------------------------------------- | ------------------------------------------------------------ |
-| `$SkyKoi_STATE_DIR/SkyKoi.json`                             | Main config (JSON5)                                          |
-| `$SkyKoi_STATE_DIR/credentials/oauth.json`                    | Legacy OAuth import (copied into auth profiles on first use) |
-| `$SkyKoi_STATE_DIR/agents/<agentId>/agent/auth-profiles.json` | Auth profiles (OAuth + API keys)                             |
-| `$SkyKoi_STATE_DIR/agents/<agentId>/agent/auth.json`          | Runtime auth cache (managed automatically)                   |
-| `$SkyKoi_STATE_DIR/credentials/`                              | Provider state (e.g. `whatsapp/<accountId>/creds.json`)      |
-| `$SkyKoi_STATE_DIR/agents/`                                   | Per-agent state (agentDir + sessions)                        |
-| `$SkyKoi_STATE_DIR/agents/<agentId>/sessions/`                | Conversation history & state (per agent)                     |
-| `$SkyKoi_STATE_DIR/agents/<agentId>/sessions/sessions.json`   | Session metadata (per agent)                                 |
+| `$SKYKOI_STATE_DIR/SKYKOI.json`                             | Main config (JSON5)                                          |
+| `$SKYKOI_STATE_DIR/credentials/oauth.json`                    | Legacy OAuth import (copied into auth profiles on first use) |
+| `$SKYKOI_STATE_DIR/agents/<agentId>/agent/auth-profiles.json` | Auth profiles (OAuth + API keys)                             |
+| `$SKYKOI_STATE_DIR/agents/<agentId>/agent/auth.json`          | Runtime auth cache (managed automatically)                   |
+| `$SKYKOI_STATE_DIR/credentials/`                              | Provider state (e.g. `whatsapp/<accountId>/creds.json`)      |
+| `$SKYKOI_STATE_DIR/agents/`                                   | Per-agent state (agentDir + sessions)                        |
+| `$SKYKOI_STATE_DIR/agents/<agentId>/sessions/`                | Conversation history & state (per agent)                     |
+| `$SKYKOI_STATE_DIR/agents/<agentId>/sessions/sessions.json`   | Session metadata (per agent)                                 |
 
-Legacy single-agent path: `~/.skykoi/agent/*` (migrated by `skykoi doctor`).
+Legacy single-agent path: `~/.SKYKOI/agent/*` (migrated by `SKYKOI doctor`).
 
-Your **workspace** (AGENTS.md, memory files, skills, etc.) is separate and configured via `agents.defaults.workspace` (default: `~/.skykoi/workspace`).
+Your **workspace** (AGENTS.md, memory files, skills, etc.) is separate and configured via `agents.defaults.workspace` (default: `~/.SKYKOI/workspace`).
 
 ### Where should AGENTSmd SOULmd USERmd MEMORYmd live
 
-These files live in the **agent workspace**, not `~/.SkyKoi`.
+These files live in the **agent workspace**, not `~/.SKYKOI`.
 
 - **Workspace (per agent)**: `AGENTS.md`, `SOUL.md`, `IDENTITY.md`, `USER.md`,
   `MEMORY.md` (or `memory.md`), `memory/YYYY-MM-DD.md`, optional `HEARTBEAT.md`.
-- **State dir (`~/.SkyKoi`)**: config, credentials, auth profiles, sessions, logs,
-  and shared skills (`~/.skykoi/skills`).
+- **State dir (`~/.SKYKOI`)**: config, credentials, auth profiles, sessions, logs,
+  and shared skills (`~/.SKYKOI/skills`).
 
-Default workspace is `~/.skykoi/workspace`, configurable via:
+Default workspace is `~/.SKYKOI/workspace`, configurable via:
 
 ```json5
 {
-  agents: { defaults: { workspace: "~/.skykoi/workspace" } },
+  agents: { defaults: { workspace: "~/.SKYKOI/workspace" } },
 }
 ```
 
@@ -1303,13 +1303,13 @@ Put your **agent workspace** in a **private** git repo and back it up somewhere
 private (for example GitHub private). This captures memory + AGENTS/SOUL/USER
 files, and lets you restore the assistant's "mind" later.
 
-Do **not** commit anything under `~/.SkyKoi` (credentials, sessions, tokens).
+Do **not** commit anything under `~/.SKYKOI` (credentials, sessions, tokens).
 If you need a full restore, back up both the workspace and the state directory
 separately (see the migration question above).
 
 Docs: [Agent workspace](/concepts/agent-workspace).
 
-### How do I completely uninstall SkyKoi
+### How do I completely uninstall SKYKOI
 
 See the dedicated guide: [Uninstall](/install/uninstall).
 
@@ -1320,7 +1320,7 @@ Relative paths resolve inside the workspace, but absolute paths can access other
 host locations unless sandboxing is enabled. If you need isolation, use
 [`agents.defaults.sandbox`](/gateway/sandboxing) or per-agent sandbox settings. If you
 want a repo to be the default working directory, point that agent's
-`workspace` to the repo root. The SkyKoi repo is just source code; keep the
+`workspace` to the repo root. The SKYKOI repo is just source code; keep the
 workspace separate unless you intentionally want the agent to work inside it.
 
 Example (repo as default cwd):
@@ -1343,17 +1343,17 @@ Session state is owned by the **gateway host**. If you're in remote mode, the se
 
 ### What format is the config Where is it
 
-SkyKoi reads an optional **JSON5** config from `$SkyKoi_CONFIG_PATH` (default: `~/.skykoi/skykoi.json`):
+SKYKOI reads an optional **JSON5** config from `$SKYKOI_CONFIG_PATH` (default: `~/.SKYKOI/SKYKOI.json`):
 
 ```
-$SkyKoi_CONFIG_PATH
+$SKYKOI_CONFIG_PATH
 ```
 
-If the file is missing, it uses safe-ish defaults (including a default workspace of `~/.skykoi/workspace`).
+If the file is missing, it uses safe-ish defaults (including a default workspace of `~/.SKYKOI/workspace`).
 
 ### I set gatewaybind lan or tailnet and now nothing listens the UI says unauthorized
 
-Non-loopback binds **require auth**. Configure `gateway.auth.mode` + `gateway.auth.token` (or use `SkyKoi_GATEWAY_TOKEN`).
+Non-loopback binds **require auth**. Configure `gateway.auth.mode` + `gateway.auth.token` (or use `SKYKOI_GATEWAY_TOKEN`).
 
 ```json5
 {
@@ -1376,7 +1376,7 @@ Notes:
 
 The wizard generates a gateway token by default (even on loopback) so **local WS clients must authenticate**. This blocks other local processes from calling the Gateway. Paste the token into the Control UI settings (or your client config) to connect.
 
-If you **really** want open loopback, remove `gateway.auth` from your config. Doctor can generate a token for you any time: `skykoi doctor --generate-gateway-token`.
+If you **really** want open loopback, remove `gateway.auth` from your config. Doctor can generate a token for you any time: `SKYKOI doctor --generate-gateway-token`.
 
 ### Do I have to restart after changing config
 
@@ -1388,7 +1388,7 @@ The Gateway watches the config and supports hot-reload:
 ### How do I enable web search and web fetch
 
 `web_fetch` works without an API key. `web_search` requires a Brave Search API
-key. **Recommended:** run `skykoi configure --section web` to store it in
+key. **Recommended:** run `SKYKOI configure --section web` to store it in
 `tools.web.search.apiKey`. Environment alternative: set `BRAVE_API_KEY` for the
 Gateway process.
 
@@ -1413,7 +1413,7 @@ Notes:
 
 - If you use allowlists, add `web_search`/`web_fetch` or `group:web`.
 - `web_fetch` is enabled by default (unless explicitly disabled).
-- Daemons read env vars from `~/.skykoi/.env` (or the service environment).
+- Daemons read env vars from `~/.SKYKOI/.env` (or the service environment).
 
 Docs: [Web tools](/tools/web).
 
@@ -1429,7 +1429,7 @@ The common pattern is **one Gateway** (e.g. Raspberry Pi) plus **nodes** and **a
 
 Docs: [Nodes](/nodes), [Remote access](/gateway/remote), [Multi-Agent Routing](/concepts/multi-agent), [Sub-agents](/tools/subagents), [TUI](/web/tui).
 
-### Can the skykoi browser run headless
+### Can the SKYKOI browser run headless
 
 Yes. It's a config option:
 
@@ -1483,8 +1483,8 @@ Typical setup:
 5. Approve the node on the Gateway:
 
    ```bash
-   SkyKoi nodes pending
-   SkyKoi nodes approve <requestId>
+   SKYKOI nodes pending
+   SKYKOI nodes approve <requestId>
    ```
 
 No separate TCP bridge is required; nodes connect over the Gateway WebSocket.
@@ -1498,9 +1498,9 @@ Docs: [Nodes](/nodes), [Gateway protocol](/gateway/protocol), [macOS remote mode
 
 Check the basics:
 
-- Gateway is running: `skykoi gateway status`
-- Gateway health: `skykoi status`
-- Channel health: `skykoi channels status`
+- Gateway is running: `SKYKOI gateway status`
+- Gateway health: `SKYKOI status`
+- Channel health: `SKYKOI channels status`
 
 Then verify auth and routing:
 
@@ -1510,7 +1510,7 @@ Then verify auth and routing:
 
 Docs: [Tailscale](/gateway/tailscale), [Remote access](/gateway/remote), [Channels](/channels).
 
-### Can two SkyKoi instances talk to each other local VPS
+### Can two SKYKOI instances talk to each other local VPS
 
 Yes. There is no built-in "bot-to-bot" bridge, but you can wire it up in a few
 reliable ways:
@@ -1519,14 +1519,14 @@ reliable ways:
 Have Bot A send a message to Bot B, then let Bot B reply as usual.
 
 **CLI bridge (generic):** run a script that calls the other Gateway with
-`skykoi agent --message ... --deliver`, targeting a chat where the other bot
+`SKYKOI agent --message ... --deliver`, targeting a chat where the other bot
 listens. If one bot is on a remote VPS, point your CLI at that remote Gateway
 via SSH/Tailscale (see [Remote access](/gateway/remote)).
 
 Example pattern (run from a machine that can reach the target Gateway):
 
 ```bash
-SkyKoi agent --message "Hello from local bot" --deliver --channel telegram --reply-to <chat-id>
+SKYKOI agent --message "Hello from local bot" --deliver --channel telegram --reply-to <chat-id>
 ```
 
 Tip: add a guardrail so the two bots do not loop endlessly (mention-only, channel
@@ -1591,15 +1591,15 @@ else is removed.
 
 Recover:
 
-- Restore from backup (git or a copied `~/.skykoi/skykoi.json`).
-- If you have no backup, re-run `skykoi doctor` and reconfigure channels/models.
+- Restore from backup (git or a copied `~/.SKYKOI/SKYKOI.json`).
+- If you have no backup, re-run `SKYKOI doctor` and reconfigure channels/models.
 - If this was unexpected, file a bug and include your last known config or any backup.
 - A local coding agent can often reconstruct a working config from logs or history.
 
 Avoid it:
 
-- Use `skykoi config set` for small changes.
-- Use `skykoi configure` for interactive edits.
+- Use `SKYKOI config set` for small changes.
+- Use `SKYKOI configure` for interactive edits.
 
 Docs: [Config](/cli/config), [Configure](/cli/configure), [Doctor](/gateway/doctor).
 
@@ -1607,7 +1607,7 @@ Docs: [Config](/cli/config), [Configure](/cli/configure), [Doctor](/gateway/doct
 
 ```json5
 {
-  agents: { defaults: { workspace: "~/.skykoi/workspace" } },
+  agents: { defaults: { workspace: "~/.SKYKOI/workspace" } },
   channels: { whatsapp: { allowFrom: ["+15555550123"] } },
 }
 ```
@@ -1636,7 +1636,7 @@ Minimal steps:
 If you want the Control UI without SSH, use Tailscale Serve on the VPS:
 
 ```bash
-skykoi gateway --tailscale serve
+SKYKOI gateway --tailscale serve
 ```
 
 This keeps the gateway bound to loopback and exposes HTTPS via Tailscale. See [Tailscale](/gateway/tailscale).
@@ -1653,20 +1653,20 @@ Recommended setup:
 3. **Approve the node** on the gateway:
 
    ```bash
-   SkyKoi nodes pending
-   SkyKoi nodes approve <requestId>
+   SKYKOI nodes pending
+   SKYKOI nodes approve <requestId>
    ```
 
 Docs: [Gateway protocol](/gateway/protocol), [Discovery](/gateway/discovery), [macOS remote mode](/platforms/mac/remote).
 
 ## Env vars and .env loading
 
-### How does SkyKoi load environment variables
+### How does SKYKOI load environment variables
 
-SkyKoi reads env vars from the parent process (shell, launchd/systemd, CI, etc.) and additionally loads:
+SKYKOI reads env vars from the parent process (shell, launchd/systemd, CI, etc.) and additionally loads:
 
 - `.env` from the current working directory
-- a global fallback `.env` from `~/.skykoi/.env` (aka `$SkyKoi_STATE_DIR/.env`)
+- a global fallback `.env` from `~/.SKYKOI/.env` (aka `$SKYKOI_STATE_DIR/.env`)
 
 Neither `.env` file overrides existing env vars.
 
@@ -1687,7 +1687,7 @@ See [/environment](/help/environment) for full precedence and sources.
 
 Two common fixes:
 
-1. Put the missing keys in `~/.skykoi/.env` so they're picked up even when the service doesn't inherit your shell env.
+1. Put the missing keys in `~/.SKYKOI/.env` so they're picked up even when the service doesn't inherit your shell env.
 2. Enable shell import (opt-in convenience):
 
 ```json5
@@ -1702,18 +1702,18 @@ Two common fixes:
 ```
 
 This runs your login shell and imports only missing expected keys (never overrides). Env var equivalents:
-`SkyKoi_LOAD_SHELL_ENV=1`, `SkyKoi_SHELL_ENV_TIMEOUT_MS=15000`.
+`SKYKOI_LOAD_SHELL_ENV=1`, `SKYKOI_SHELL_ENV_TIMEOUT_MS=15000`.
 
 ### I set COPILOTGITHUBTOKEN but models status shows Shell env off Why
 
-`skykoi models status` reports whether **shell env import** is enabled. "Shell env: off"
-does **not** mean your env vars are missing - it just means SkyKoi won't load
+`SKYKOI models status` reports whether **shell env import** is enabled. "Shell env: off"
+does **not** mean your env vars are missing - it just means SKYKOI won't load
 your login shell automatically.
 
 If the Gateway runs as a service (launchd/systemd), it won't inherit your shell
 environment. Fix by doing one of these:
 
-1. Put the token in `~/.skykoi/.env`:
+1. Put the token in `~/.SKYKOI/.env`:
 
    ```
    COPILOT_GITHUB_TOKEN=...
@@ -1725,7 +1725,7 @@ environment. Fix by doing one of these:
 Then restart the gateway and recheck:
 
 ```bash
-SkyKoi models status
+SKYKOI models status
 ```
 
 Copilot tokens are read from `COPILOT_GITHUB_TOKEN` (also `GH_TOKEN` / `GITHUB_TOKEN`).
@@ -1751,7 +1751,7 @@ transcripts - it just starts a new session.
 }
 ```
 
-### Is there a way to make a team of SkyKoi instances one CEO and many agents
+### Is there a way to make a team of SKYKOI instances one CEO and many agents
 
 Yes, via **multi-agent routing** and **sub-agents**. You can create one coordinator
 agent and several worker agents with their own workspaces and models.
@@ -1776,31 +1776,31 @@ What helps:
 - Use sub-agents for long or parallel work so the main chat stays smaller.
 - Pick a model with a larger context window if this happens often.
 
-### How do I completely reset SkyKoi but keep it installed
+### How do I completely reset SKYKOI but keep it installed
 
 Use the reset command:
 
 ```bash
-SkyKoi reset
+SKYKOI reset
 ```
 
 Non-interactive full reset:
 
 ```bash
-SkyKoi reset --scope full --yes --non-interactive
+SKYKOI reset --scope full --yes --non-interactive
 ```
 
 Then re-run onboarding:
 
 ```bash
-skykoi onboard --install-daemon
+SKYKOI onboard --install-daemon
 ```
 
 Notes:
 
 - The onboarding wizard also offers **Reset** if it sees an existing config. See [Wizard](/start/wizard).
-- If you used profiles (`--profile` / `SkyKoi_PROFILE`), reset each state dir (defaults are `~/.SkyKoi-<profile>`).
-- Dev reset: `skykoi gateway --dev --reset` (dev-only; wipes dev config + credentials + sessions + workspace).
+- If you used profiles (`--profile` / `SKYKOI_PROFILE`), reset each state dir (defaults are `~/.SKYKOI-<profile>`).
+- Dev reset: `SKYKOI gateway --dev --reset` (dev-only; wipes dev config + credentials + sessions + workspace).
 
 ### Im getting context too large errors how do I reset or compact
 
@@ -1853,14 +1853,14 @@ Heartbeats run every **30m** by default. Tune or disable them:
 ```
 
 If `HEARTBEAT.md` exists but is effectively empty (only blank lines and markdown
-headers like `# Heading`), SkyKoi skips the heartbeat run to save API calls.
+headers like `# Heading`), SKYKOI skips the heartbeat run to save API calls.
 If the file is missing, the heartbeat still runs and the model decides what to do.
 
 Per-agent overrides use `agents.list[].heartbeat`. Docs: [Heartbeat](/gateway/heartbeat).
 
 ### Do I need to add a bot account to a WhatsApp group
 
-No. SkyKoi runs on **your own account**, so if you're in the group, SkyKoi can see it.
+No. SKYKOI runs on **your own account**, so if you're in the group, SKYKOI can see it.
 By default, group replies are blocked until you allow senders (`groupPolicy: "allowlist"`).
 
 If you want only **you** to be able to trigger group replies:
@@ -1881,7 +1881,7 @@ If you want only **you** to be able to trigger group replies:
 Option 1 (fastest): tail logs and send a test message in the group:
 
 ```bash
-SkyKoi logs --follow --json
+SKYKOI logs --follow --json
 ```
 
 Look for `chatId` (or `from`) ending in `@g.us`, like:
@@ -1890,12 +1890,12 @@ Look for `chatId` (or `from`) ending in `@g.us`, like:
 Option 2 (if already configured/allowlisted): list groups from config:
 
 ```bash
-SkyKoi directory groups list --channel whatsapp
+SKYKOI directory groups list --channel whatsapp
 ```
 
 Docs: [WhatsApp](/channels/whatsapp), [Directory](/cli/directory), [Logs](/cli/logs).
 
-### Why doesnt SkyKoi reply in a group
+### Why doesnt SKYKOI reply in a group
 
 Two common causes:
 
@@ -1912,7 +1912,7 @@ Direct chats collapse to the main session by default. Groups/channels have their
 
 No hard limits. Dozens (even hundreds) are fine, but watch for:
 
-- **Disk growth:** sessions + transcripts live under `~/.skykoi/agents/<agentId>/sessions/`.
+- **Disk growth:** sessions + transcripts live under `~/.SKYKOI/agents/<agentId>/sessions/`.
 - **Token cost:** more agents means more concurrent model usage.
 - **Ops overhead:** per-agent auth profiles, workspaces, and channel routing.
 
@@ -1920,7 +1920,7 @@ Tips:
 
 - Keep one **active** workspace per agent (`agents.defaults.workspace`).
 - Prune old sessions (delete JSONL or store entries) if disk grows.
-- Use `skykoi doctor` to spot stray workspaces and profile mismatches.
+- Use `SKYKOI doctor` to spot stray workspaces and profile mismatches.
 
 ### Can I run multiple bots or chats at the same time Slack and how should I set that up
 
@@ -1945,13 +1945,13 @@ Docs: [Multi-Agent Routing](/concepts/multi-agent), [Slack](/channels/slack),
 
 ### What is the default model
 
-SkyKoi's default model is whatever you set as:
+SKYKOI's default model is whatever you set as:
 
 ```
 agents.defaults.model.primary
 ```
 
-Models are referenced as `provider/model` (example: `anthropic/claude-opus-4-6`). If you omit the provider, SkyKoi currently assumes `anthropic` as a temporary deprecation fallback - but you should still **explicitly** set `provider/model`.
+Models are referenced as `provider/model` (example: `anthropic/claude-opus-4-6`). If you omit the provider, SKYKOI currently assumes `anthropic` as a temporary deprecation fallback - but you should still **explicitly** set `provider/model`.
 
 ### What model do you recommend
 
@@ -1993,18 +1993,18 @@ Use **model commands** or edit only the **model** fields. Avoid full config repl
 Safe options:
 
 - `/model` in chat (quick, per-session)
-- `skykoi models set ...` (updates just model config)
-- `skykoi configure --section model` (interactive)
-- edit `agents.defaults.model` in `~/.skykoi/skykoi.json`
+- `SKYKOI models set ...` (updates just model config)
+- `SKYKOI configure --section model` (interactive)
+- edit `agents.defaults.model` in `~/.SKYKOI/SKYKOI.json`
 
 Avoid `config.apply` with a partial object unless you intend to replace the whole config.
-If you did overwrite config, restore from backup or re-run `skykoi doctor` to repair.
+If you did overwrite config, restore from backup or re-run `SKYKOI doctor` to repair.
 
 Docs: [Models](/concepts/models), [Configure](/cli/configure), [Config](/cli/config), [Doctor](/gateway/doctor).
 
-### What do SkyKoi, Flawd, and Krill use for models
+### What do SKYKOI, Flawd, and Krill use for models
 
-- **SkyKoi + Flawd:** Anthropic Opus (`anthropic/claude-opus-4-6`) - see [Anthropic](/providers/anthropic).
+- **SKYKOI + Flawd:** Anthropic Opus (`anthropic/claude-opus-4-6`) - see [Anthropic](/providers/anthropic).
 - **Krill:** MiniMax M2.1 (`minimax/MiniMax-M2.1`) - see [MiniMax](/providers/minimax).
 
 ### How do I switch models on the fly without restarting
@@ -2088,7 +2088,7 @@ Fix checklist:
 4. Run:
 
    ```bash
-   SkyKoi models list
+   SKYKOI models list
    ```
 
    and pick from the list (or `/model list` in chat).
@@ -2133,7 +2133,7 @@ Docs: [Models](/concepts/models), [Multi-Agent Routing](/concepts/multi-agent),
 
 ### Are opus sonnet gpt builtin shortcuts
 
-Yes. SkyKoi ships a few default shorthands (only applied when the model exists in `agents.defaults.models`):
+Yes. SKYKOI ships a few default shorthands (only applied when the model exists in `agents.defaults.models`):
 
 - `opus` → `anthropic/claude-opus-4-6`
 - `sonnet` → `anthropic/claude-sonnet-4-5`
@@ -2203,12 +2203,12 @@ This usually means the **new agent** has an empty auth store. Auth is per-agent
 stored in:
 
 ```
-~/.skykoi/agents/<agentId>/agent/auth-profiles.json
+~/.SKYKOI/agents/<agentId>/agent/auth-profiles.json
 ```
 
 Fix options:
 
-- Run `skykoi agents add <id>` and configure auth during the wizard.
+- Run `SKYKOI agents add <id>` and configure auth during the wizard.
 - Or copy `auth-profiles.json` from the main agent's `agentDir` into the new agent's `agentDir`.
 
 Do **not** reuse `agentDir` across agents; it causes auth/session collisions.
@@ -2222,7 +2222,7 @@ Failover happens in two stages:
 1. **Auth profile rotation** within the same provider.
 2. **Model fallback** to the next model in `agents.defaults.model.fallbacks`.
 
-Cooldowns apply to failing profiles (exponential backoff), so SkyKoi can keep responding even when a provider is rate-limited or temporarily failing.
+Cooldowns apply to failing profiles (exponential backoff), so SKYKOI can keep responding even when a provider is rate-limited or temporarily failing.
 
 ### What does this error mean
 
@@ -2235,14 +2235,14 @@ It means the system attempted to use the auth profile ID `anthropic:default`, bu
 ### Fix checklist for No credentials found for profile anthropicdefault
 
 - **Confirm where auth profiles live** (new vs legacy paths)
-  - Current: `~/.skykoi/agents/<agentId>/agent/auth-profiles.json`
-  - Legacy: `~/.skykoi/agent/*` (migrated by `skykoi doctor`)
+  - Current: `~/.SKYKOI/agents/<agentId>/agent/auth-profiles.json`
+  - Legacy: `~/.SKYKOI/agent/*` (migrated by `SKYKOI doctor`)
 - **Confirm your env var is loaded by the Gateway**
-  - If you set `ANTHROPIC_API_KEY` in your shell but run the Gateway via systemd/launchd, it may not inherit it. Put it in `~/.skykoi/.env` or enable `env.shellEnv`.
+  - If you set `ANTHROPIC_API_KEY` in your shell but run the Gateway via systemd/launchd, it may not inherit it. Put it in `~/.SKYKOI/.env` or enable `env.shellEnv`.
 - **Make sure you're editing the correct agent**
   - Multi-agent setups mean there can be multiple `auth-profiles.json` files.
 - **Sanity-check model/auth status**
-  - Use `skykoi models status` to see configured models and whether providers are authenticated.
+  - Use `SKYKOI models status` to see configured models and whether providers are authenticated.
 
 **Fix checklist for No credentials found for profile anthropic**
 
@@ -2250,14 +2250,14 @@ This means the run is pinned to an Anthropic auth profile, but the Gateway
 can't find it in its auth store.
 
 - **Use a setup-token**
-  - Run `claude setup-token`, then paste it with `skykoi models auth setup-token --provider anthropic`.
-  - If the token was created on another machine, use `skykoi models auth paste-token --provider anthropic`.
+  - Run `claude setup-token`, then paste it with `SKYKOI models auth setup-token --provider anthropic`.
+  - If the token was created on another machine, use `SKYKOI models auth paste-token --provider anthropic`.
 - **If you want to use an API key instead**
-  - Put `ANTHROPIC_API_KEY` in `~/.skykoi/.env` on the **gateway host**.
+  - Put `ANTHROPIC_API_KEY` in `~/.SKYKOI/.env` on the **gateway host**.
   - Clear any pinned order that forces a missing profile:
 
     ```bash
-    SkyKoi models auth order clear --provider anthropic
+    SKYKOI models auth order clear --provider anthropic
     ```
 
 - **Confirm you're running commands on the gateway host**
@@ -2265,7 +2265,7 @@ can't find it in its auth store.
 
 ### Why did it also try Google Gemini and fail
 
-If your model config includes Google Gemini as a fallback (or you switched to a Gemini shorthand), SkyKoi will try it during model fallback. If you haven't configured Google credentials, you'll see `No API key found for provider "google"`.
+If your model config includes Google Gemini as a fallback (or you switched to a Gemini shorthand), SKYKOI will try it during model fallback. If you haven't configured Google credentials, you'll see `No API key found for provider "google"`.
 
 Fix: either provide Google auth, or remove/avoid Google models in `agents.defaults.model.fallbacks` / aliases so fallback doesn't route there.
 
@@ -2274,7 +2274,7 @@ Fix: either provide Google auth, or remove/avoid Google models in `agents.defaul
 Cause: the session history contains **thinking blocks without signatures** (often from
 an aborted/partial stream). Google Antigravity requires signatures for thinking blocks.
 
-Fix: SkyKoi now strips unsigned thinking blocks for Google Antigravity Claude. If it still appears, start a **new session** or set `/thinking off` for that agent.
+Fix: SKYKOI now strips unsigned thinking blocks for Google Antigravity Claude. If it still appears, start a **new session** or set `/thinking off` for that agent.
 
 ## Auth profiles: what they are and how to manage them
 
@@ -2285,12 +2285,12 @@ Related: [/concepts/oauth](/concepts/oauth) (OAuth flows, token storage, multi-a
 An auth profile is a named credential record (OAuth or API key) tied to a provider. Profiles live in:
 
 ```
-~/.skykoi/agents/<agentId>/agent/auth-profiles.json
+~/.SKYKOI/agents/<agentId>/agent/auth-profiles.json
 ```
 
 ### What are typical profile IDs
 
-SkyKoi uses provider-prefixed IDs like:
+SKYKOI uses provider-prefixed IDs like:
 
 - `anthropic:default` (common when no email identity exists)
 - `anthropic:<email>` for OAuth identities
@@ -2300,33 +2300,33 @@ SkyKoi uses provider-prefixed IDs like:
 
 Yes. Config supports optional metadata for profiles and an ordering per provider (`auth.order.<provider>`). This does **not** store secrets; it maps IDs to provider/mode and sets rotation order.
 
-SkyKoi may temporarily skip a profile if it's in a short **cooldown** (rate limits/timeouts/auth failures) or a longer **disabled** state (billing/insufficient credits). To inspect this, run `skykoi models status --json` and check `auth.unusableProfiles`. Tuning: `auth.cooldowns.billingBackoffHours*`.
+SKYKOI may temporarily skip a profile if it's in a short **cooldown** (rate limits/timeouts/auth failures) or a longer **disabled** state (billing/insufficient credits). To inspect this, run `SKYKOI models status --json` and check `auth.unusableProfiles`. Tuning: `auth.cooldowns.billingBackoffHours*`.
 
 You can also set a **per-agent** order override (stored in that agent's `auth-profiles.json`) via the CLI:
 
 ```bash
 # Defaults to the configured default agent (omit --agent)
-SkyKoi models auth order get --provider anthropic
+SKYKOI models auth order get --provider anthropic
 
 # Lock rotation to a single profile (only try this one)
-SkyKoi models auth order set --provider anthropic anthropic:default
+SKYKOI models auth order set --provider anthropic anthropic:default
 
 # Or set an explicit order (fallback within provider)
-SkyKoi models auth order set --provider anthropic anthropic:work anthropic:default
+SKYKOI models auth order set --provider anthropic anthropic:work anthropic:default
 
 # Clear override (fall back to config auth.order / round-robin)
-SkyKoi models auth order clear --provider anthropic
+SKYKOI models auth order clear --provider anthropic
 ```
 
 To target a specific agent:
 
 ```bash
-SkyKoi models auth order set --provider anthropic --agent main anthropic:default
+SKYKOI models auth order set --provider anthropic --agent main anthropic:default
 ```
 
 ### OAuth vs API key whats the difference
 
-SkyKoi supports both:
+SKYKOI supports both:
 
 - **OAuth** often leverages subscription access (where applicable).
 - **API keys** use pay-per-token billing.
@@ -2342,38 +2342,38 @@ The wizard explicitly supports Anthropic setup-token and OpenAI Codex OAuth and
 Precedence:
 
 ```
---port > SkyKoi_GATEWAY_PORT > gateway.port > default 18789
+--port > SKYKOI_GATEWAY_PORT > gateway.port > default 18789
 ```
 
-### Why does skykoi gateway status say Runtime running but RPC probe failed
+### Why does SKYKOI gateway status say Runtime running but RPC probe failed
 
 Because "running" is the **supervisor's** view (launchd/systemd/schtasks). The RPC probe is the CLI actually connecting to the gateway WebSocket and calling `status`.
 
-Use `skykoi gateway status` and trust these lines:
+Use `SKYKOI gateway status` and trust these lines:
 
 - `Probe target:` (the URL the probe actually used)
 - `Listening:` (what's actually bound on the port)
 - `Last gateway error:` (common root cause when the process is alive but the port isn't listening)
 
-### Why does skykoi gateway status show Config cli and Config service different
+### Why does SKYKOI gateway status show Config cli and Config service different
 
-You're editing one config file while the service is running another (often a `--profile` / `SkyKoi_STATE_DIR` mismatch).
+You're editing one config file while the service is running another (often a `--profile` / `SKYKOI_STATE_DIR` mismatch).
 
 Fix:
 
 ```bash
-skykoi gateway install --force
+SKYKOI gateway install --force
 ```
 
 Run that from the same `--profile` / environment you want the service to use.
 
 ### What does another gateway instance is already listening mean
 
-SkyKoi enforces a runtime lock by binding the WebSocket listener immediately on startup (default `ws://127.0.0.1:18789`). If the bind fails with `EADDRINUSE`, it throws `GatewayLockError` indicating another instance is already listening.
+SKYKOI enforces a runtime lock by binding the WebSocket listener immediately on startup (default `ws://127.0.0.1:18789`). If the bind fails with `EADDRINUSE`, it throws `GatewayLockError` indicating another instance is already listening.
 
-Fix: stop the other instance, free the port, or run with `skykoi gateway --port <port>`.
+Fix: stop the other instance, free the port, or run with `SKYKOI gateway --port <port>`.
 
-### How do I run SkyKoi in remote mode client connects to a Gateway elsewhere
+### How do I run SKYKOI in remote mode client connects to a Gateway elsewhere
 
 Set `gateway.mode: "remote"` and point to a remote WebSocket URL, optionally with a token/password:
 
@@ -2392,7 +2392,7 @@ Set `gateway.mode: "remote"` and point to a remote WebSocket URL, optionally wit
 
 Notes:
 
-- `skykoi gateway` only starts when `gateway.mode` is `local` (or you pass the override flag).
+- `SKYKOI gateway` only starts when `gateway.mode` is `local` (or you pass the override flag).
 - The macOS app watches the config file and switches modes live when these values change.
 
 ### The Control UI says unauthorized or keeps reconnecting What now
@@ -2401,16 +2401,16 @@ Your gateway is running with auth enabled (`gateway.auth.*`), but the UI is not
 
 Facts (from code):
 
-- The Control UI stores the token in browser localStorage key `SkyKoi.control.settings.v1`.
+- The Control UI stores the token in browser localStorage key `SKYKOI.control.settings.v1`.
 
 Fix:
 
-- Fastest: `skykoi dashboard` (prints + copies the dashboard URL, tries to open; shows SSH hint if headless).
-- If you don't have a token yet: `skykoi doctor --generate-gateway-token`.
+- Fastest: `SKYKOI dashboard` (prints + copies the dashboard URL, tries to open; shows SSH hint if headless).
+- If you don't have a token yet: `SKYKOI doctor --generate-gateway-token`.
 - If remote, tunnel first: `ssh -N -L 18789:127.0.0.1:18789 user@host` then open `http://127.0.0.1:18789/`.
-- Set `gateway.auth.token` (or `SkyKoi_GATEWAY_TOKEN`) on the gateway host.
+- Set `gateway.auth.token` (or `SKYKOI_GATEWAY_TOKEN`) on the gateway host.
 - In the Control UI settings, paste the same token.
-- Still stuck? Run `skykoi status --all` and follow [Troubleshooting](/gateway/troubleshooting). See [Dashboard](/web/dashboard) for auth details.
+- Still stuck? Run `SKYKOI status --all` and follow [Troubleshooting](/gateway/troubleshooting). See [Dashboard](/web/dashboard) for auth details.
 
 ### I set gatewaybind tailnet but it cant bind nothing listens
 
@@ -2429,18 +2429,18 @@ Usually no - one Gateway can run multiple messaging channels and agents. Use mul
 
 Yes, but you must isolate:
 
-- `SkyKoi_CONFIG_PATH` (per-instance config)
-- `SkyKoi_STATE_DIR` (per-instance state)
+- `SKYKOI_CONFIG_PATH` (per-instance config)
+- `SKYKOI_STATE_DIR` (per-instance state)
 - `agents.defaults.workspace` (workspace isolation)
 - `gateway.port` (unique ports)
 
 Quick setup (recommended):
 
-- Use `skykoi --profile <name> …` per instance (auto-creates `~/.SkyKoi-<name>`).
+- Use `SKYKOI --profile <name> …` per instance (auto-creates `~/.SKYKOI-<name>`).
 - Set a unique `gateway.port` in each profile config (or pass `--port` for manual runs).
-- Install a per-profile service: `skykoi --profile <name> gateway install`.
+- Install a per-profile service: `SKYKOI --profile <name> gateway install`.
 
-Profiles also suffix service names (`bot.molt.<profile>`; legacy `com.SkyKoi.*`, `SkyKoi-gateway-<profile>.service`, `skykoi Gateway (<profile>)`).
+Profiles also suffix service names (`bot.molt.<profile>`; legacy `com.SKYKOI.*`, `SKYKOI-gateway-<profile>.service`, `SKYKOI Gateway (<profile>)`).
 Full guide: [Multiple gateways](/gateway/multiple-gateways).
 
 ### What does invalid handshake code 1008 mean
@@ -2464,7 +2464,7 @@ Quick fixes:
 If you're using the CLI or TUI, the URL should look like:
 
 ```
-SkyKoi tui --url ws://<host>:18789 --token <token>
+SKYKOI tui --url ws://<host>:18789 --token <token>
 ```
 
 Protocol details: [Gateway protocol](/gateway/protocol).
@@ -2476,7 +2476,7 @@ Protocol details: [Gateway protocol](/gateway/protocol).
 File logs (structured):
 
 ```
-/tmp/SkyKoi/SkyKoi-YYYY-MM-DD.log
+/tmp/SKYKOI/SKYKOI-YYYY-MM-DD.log
 ```
 
 You can set a stable path via `logging.file`. File log level is controlled by `logging.level`. Console verbosity is controlled by `--verbose` and `logging.consoleLevel`.
@@ -2484,14 +2484,14 @@ You can set a stable path via `logging.file`. File log level is controlled by `l
 Fastest log tail:
 
 ```bash
-SkyKoi logs --follow
+SKYKOI logs --follow
 ```
 
 Service/supervisor logs (when the gateway runs via launchd/systemd):
 
-- macOS: `$SkyKoi_STATE_DIR/logs/gateway.log` and `gateway.err.log` (default: `~/.skykoi/logs/...`; profiles use `~/.SkyKoi-<profile>/logs/...`)
-- Linux: `journalctl --user -u SkyKoi-gateway[-<profile>].service -n 200 --no-pager`
-- Windows: `schtasks /Query /TN "skykoi gateway (<profile>)" /V /FO LIST`
+- macOS: `$SKYKOI_STATE_DIR/logs/gateway.log` and `gateway.err.log` (default: `~/.SKYKOI/logs/...`; profiles use `~/.SKYKOI-<profile>/logs/...`)
+- Linux: `journalctl --user -u SKYKOI-gateway[-<profile>].service -n 200 --no-pager`
+- Windows: `schtasks /Query /TN "SKYKOI gateway (<profile>)" /V /FO LIST`
 
 See [Troubleshooting](/gateway/troubleshooting#log-locations) for more.
 
@@ -2500,13 +2500,13 @@ See [Troubleshooting](/gateway/troubleshooting#log-locations) for more.
 Use the gateway helpers:
 
 ```bash
-skykoi gateway status
-skykoi gateway restart
+SKYKOI gateway status
+SKYKOI gateway restart
 ```
 
-If you run the gateway manually, `skykoi gateway --force` can reclaim the port. See [Gateway](/gateway).
+If you run the gateway manually, `SKYKOI gateway --force` can reclaim the port. See [Gateway](/gateway).
 
-### I closed my terminal on Windows how do I restart SkyKoi
+### I closed my terminal on Windows how do I restart SKYKOI
 
 There are **two Windows install modes**:
 
@@ -2516,14 +2516,14 @@ Open PowerShell, enter WSL, then restart:
 
 ```powershell
 wsl
-skykoi gateway status
-skykoi gateway restart
+SKYKOI gateway status
+SKYKOI gateway restart
 ```
 
 If you never installed the service, start it in the foreground:
 
 ```bash
-skykoi gateway run
+SKYKOI gateway run
 ```
 
 **2) Native Windows (not recommended):** the Gateway runs directly in Windows.
@@ -2531,14 +2531,14 @@ skykoi gateway run
 Open PowerShell and run:
 
 ```powershell
-skykoi gateway status
-skykoi gateway restart
+SKYKOI gateway status
+SKYKOI gateway restart
 ```
 
 If you run it manually (no service), use:
 
 ```powershell
-skykoi gateway run
+SKYKOI gateway run
 ```
 
 Docs: [Windows (WSL2)](/platforms/windows), [Gateway service runbook](/gateway).
@@ -2548,10 +2548,10 @@ Docs: [Windows (WSL2)](/platforms/windows), [Gateway service runbook](/gateway).
 Start with a quick health sweep:
 
 ```bash
-SkyKoi status
-SkyKoi models status
-skykoi channels status
-SkyKoi logs --follow
+SKYKOI status
+SKYKOI models status
+SKYKOI channels status
+SKYKOI logs --follow
 ```
 
 Common causes:
@@ -2569,15 +2569,15 @@ Docs: [Channels](/channels), [Troubleshooting](/gateway/troubleshooting), [Remot
 
 This usually means the UI lost the WebSocket connection. Check:
 
-1. Is the Gateway running? `skykoi gateway status`
-2. Is the Gateway healthy? `skykoi status`
-3. Does the UI have the right token? `skykoi dashboard`
+1. Is the Gateway running? `SKYKOI gateway status`
+2. Is the Gateway healthy? `SKYKOI status`
+3. Does the UI have the right token? `SKYKOI dashboard`
 4. If remote, is the tunnel/Tailscale link up?
 
 Then tail logs:
 
 ```bash
-SkyKoi logs --follow
+SKYKOI logs --follow
 ```
 
 Docs: [Dashboard](/web/dashboard), [Remote access](/gateway/remote), [Troubleshooting](/gateway/troubleshooting).
@@ -2587,8 +2587,8 @@ Docs: [Dashboard](/web/dashboard), [Remote access](/gateway/remote), [Troublesho
 Start with logs and channel status:
 
 ```bash
-skykoi channels status
-skykoi channels logs --channel telegram
+SKYKOI channels status
+SKYKOI channels logs --channel telegram
 ```
 
 If you are on a VPS or behind a proxy, confirm outbound HTTPS is allowed and DNS works.
@@ -2601,9 +2601,9 @@ Docs: [Telegram](/channels/telegram), [Channel troubleshooting](/channels/troubl
 First confirm the Gateway is reachable and the agent can run:
 
 ```bash
-SkyKoi status
-SkyKoi models status
-SkyKoi logs --follow
+SKYKOI status
+SKYKOI models status
+SKYKOI logs --follow
 ```
 
 In the TUI, use `/status` to see the current state. If you expect replies in a chat
@@ -2616,8 +2616,8 @@ Docs: [TUI](/web/tui), [Slash commands](/tools/slash-commands).
 If you installed the service:
 
 ```bash
-skykoi gateway stop
-skykoi gateway start
+SKYKOI gateway stop
+SKYKOI gateway start
 ```
 
 This stops/starts the **supervised service** (launchd on macOS, systemd on Linux).
@@ -2626,17 +2626,17 @@ Use this when the Gateway runs in the background as a daemon.
 If you're running in the foreground, stop with Ctrl-C, then:
 
 ```bash
-skykoi gateway run
+SKYKOI gateway run
 ```
 
 Docs: [Gateway service runbook](/gateway).
 
-### ELI5 skykoi gateway restart vs skykoi gateway
+### ELI5 SKYKOI gateway restart vs SKYKOI gateway
 
-- `skykoi gateway restart`: restarts the **background service** (launchd/systemd).
-- `skykoi gateway`: runs the gateway **in the foreground** for this terminal session.
+- `SKYKOI gateway restart`: restarts the **background service** (launchd/systemd).
+- `SKYKOI gateway`: runs the gateway **in the foreground** for this terminal session.
 
-If you installed the service, use the gateway commands. Use `skykoi gateway` when
+If you installed the service, use the gateway commands. Use `SKYKOI gateway` when
 you want a one-off, foreground run.
 
 ### What's the fastest way to get more details when something fails
@@ -2647,12 +2647,12 @@ Start the Gateway with `--verbose` to get more console detail. Then inspect the
 
 ### My skill generated an imagePDF but nothing was sent
 
-Outbound attachments from the agent must include a `MEDIA:<path-or-url>` line (on its own line). See [SkyKoi assistant setup](/start/SkyKoi) and [Agent send](/tools/agent-send).
+Outbound attachments from the agent must include a `MEDIA:<path-or-url>` line (on its own line). See [SKYKOI assistant setup](/start/SKYKOI) and [Agent send](/tools/agent-send).
 
 CLI sending:
 
 ```bash
-SkyKoi message send --target +15555550123 --message "Here you go" --media /path/to/file.png
+SKYKOI message send --target +15555550123 --message "Here you go" --media /path/to/file.png
 ```
 
 Also check:
@@ -2664,17 +2664,17 @@ See [Images](/nodes/images).
 
 ## Security and access control
 
-### Is it safe to expose SkyKoi to inbound DMs
+### Is it safe to expose SKYKOI to inbound DMs
 
 Treat inbound DMs as untrusted input. Defaults are designed to reduce risk:
 
 - Default behavior on DM-capable channels is **pairing**:
   - Unknown senders receive a pairing code; the bot does not process their message.
-  - Approve with: `skykoi pairing approve <channel> <code>`
-  - Pending requests are capped at **3 per channel**; check `skykoi pairing list <channel>` if a code didn't arrive.
+  - Approve with: `SKYKOI pairing approve <channel> <code>`
+  - Pending requests are capped at **3 per channel**; check `SKYKOI pairing list <channel>` if a code didn't arrive.
 - Opening DMs publicly requires explicit opt-in (`dmPolicy: "open"` and allowlist `"*"`).
 
-Run `skykoi doctor` to surface risky DM policies.
+Run `SKYKOI doctor` to surface risky DM policies.
 
 ### Is prompt injection only a concern for public bots
 
@@ -2729,7 +2729,7 @@ Pairing codes are sent **only** when an unknown sender messages the bot and
 Check pending requests:
 
 ```bash
-SkyKoi pairing list telegram
+SKYKOI pairing list telegram
 ```
 
 If you want immediate access, allowlist your sender id or set `dmPolicy: "open"`
@@ -2737,18 +2737,18 @@ for that account.
 
 ### WhatsApp will it message my contacts How does pairing work
 
-No. Default WhatsApp DM policy is **pairing**. Unknown senders only get a pairing code and their message is **not processed**. SkyKoi only replies to chats it receives or to explicit sends you trigger.
+No. Default WhatsApp DM policy is **pairing**. Unknown senders only get a pairing code and their message is **not processed**. SKYKOI only replies to chats it receives or to explicit sends you trigger.
 
 Approve pairing with:
 
 ```bash
-SkyKoi pairing approve whatsapp <code>
+SKYKOI pairing approve whatsapp <code>
 ```
 
 List pending requests:
 
 ```bash
-SkyKoi pairing list whatsapp
+SKYKOI pairing list whatsapp
 ```
 
 Wizard phone number prompt: it's used to set your **allowlist/owner** so your own DMs are permitted. It's not used for auto-sending. If you run on your personal WhatsApp number, use that number and enable `channels.whatsapp.selfChatMode`.
@@ -2800,7 +2800,7 @@ Most commands must be sent as a **standalone** message that starts with `/`, but
 
 ### How do I send a Discord message from Telegram Crosscontext messaging denied
 
-SkyKoi blocks **cross-provider** messaging by default. If a tool call is bound
+SKYKOI blocks **cross-provider** messaging by default. If a tool call is bound
 to Telegram, it won't send to Discord unless you explicitly allow it.
 
 Enable cross-provider messaging for the agent:
@@ -2841,8 +2841,8 @@ You can add options like `debounce:2s cap:25 drop:summarize` for followup modes.
 
 **Q: "What's the default model for Anthropic with an API key?"**
 
-**A:** In SkyKoi, credentials and model selection are separate. Setting `ANTHROPIC_API_KEY` (or storing an Anthropic API key in auth profiles) enables authentication, but the actual default model is whatever you configure in `agents.defaults.model.primary` (for example, `anthropic/claude-sonnet-4-5` or `anthropic/claude-opus-4-6`). If you see `No credentials found for profile "anthropic:default"`, it means the Gateway couldn't find Anthropic credentials in the expected `auth-profiles.json` for the agent that's running.
+**A:** In SKYKOI, credentials and model selection are separate. Setting `ANTHROPIC_API_KEY` (or storing an Anthropic API key in auth profiles) enables authentication, but the actual default model is whatever you configure in `agents.defaults.model.primary` (for example, `anthropic/claude-sonnet-4-5` or `anthropic/claude-opus-4-6`). If you see `No credentials found for profile "anthropic:default"`, it means the Gateway couldn't find Anthropic credentials in the expected `auth-profiles.json` for the agent that's running.
 
 ---
 
-Still stuck? Ask in [Discord](https://discord.com/invite/clawd) or open a [GitHub discussion](https://github.com/SkyKoi/SkyKoi/discussions).
+Still stuck? Ask in [Discord](https://discord.com/invite/clawd) or open a [GitHub discussion](https://github.com/SKYKOI/SKYKOI/discussions).