skykoi 2026.3.11 → 2026.3.13

package/docs/start/{openclaw.md → SkyKoi.md}

@@ -1,14 +1,14 @@
 ---
-summary: "End-to-end guide for running SkyKoi as a personal assistant with safety cautions"
+summary: "End-to-end guide for running SKYKOI as a personal assistant with safety cautions"
 read_when:
   - Onboarding a new assistant instance
   - Reviewing safety/permission implications
 title: "Personal Assistant Setup"
 ---
 
-# Building a personal assistant with SkyKoi
+# Building a personal assistant with SKYKOI
 
-SkyKoi is a WhatsApp + Telegram + Discord + iMessage gateway for **Pi** agents. Plugins add Mattermost. This guide is the "personal assistant" setup: one dedicated WhatsApp number that behaves like your always-on agent.
+SKYKOI is a WhatsApp + Telegram + Discord + iMessage gateway for **Pi** agents. Plugins add Mattermost. This guide is the "personal assistant" setup: one dedicated WhatsApp number that behaves like your always-on agent.
 
 ## ⚠️ Safety first
 
@@ -26,7 +26,7 @@ Start conservative:
 
 ## Prerequisites
 
-- SkyKoi installed and onboarded — see [Getting Started](/start/getting-started) if you haven't done this yet
+- SKYKOI installed and onboarded — see [Getting Started](/start/getting-started) if you haven't done this yet
 - A second phone number (SIM/eSIM/prepaid) for the assistant
 
 ## The two-phone setup (recommended)
@@ -43,28 +43,28 @@ Your Phone (personal)          Second Phone (assistant)
                                        ▼
                               ┌─────────────────┐
                               │  Your Mac       │
-                              │  (SkyKoi)      │
+                              │  (SKYKOI)      │
                               │    Pi agent     │
                               └─────────────────┘
 ```
 
-If you link your personal WhatsApp to SkyKoi, every message to you becomes “agent input”. That’s rarely what you want.
+If you link your personal WhatsApp to SKYKOI, every message to you becomes “agent input”. That’s rarely what you want.
 
 ## 5-minute quick start
 
 1. Pair WhatsApp Web (shows QR; scan with the assistant phone):
 
 ```bash
-SkyKoi channels login
+SKYKOI channels login
 ```
 
 2. Start the Gateway (leave it running):
 
 ```bash
-SkyKoi gateway --port 18789
+SKYKOI gateway --port 18789
 ```
 
-3. Put a minimal config in `~/.skykoi/skykoi.json`:
+3. Put a minimal config in `~/.SKYKOI/SKYKOI.json`:
 
 ```json5
 {
@@ -74,18 +74,18 @@ SkyKoi gateway --port 18789
 
 Now message the assistant number from your allowlisted phone.
 
-When onboarding finishes, we auto-open the dashboard and print a clean (non-tokenized) link. If it prompts for auth, paste the token from `gateway.auth.token` into Control UI settings. To reopen later: `SkyKoi dashboard`.
+When onboarding finishes, we auto-open the dashboard and print a clean (non-tokenized) link. If it prompts for auth, paste the token from `gateway.auth.token` into Control UI settings. To reopen later: `SKYKOI dashboard`.
 
 ## Give the agent a workspace (AGENTS)
 
-SkyKoi reads operating instructions and “memory” from its workspace directory.
+SKYKOI reads operating instructions and “memory” from its workspace directory.
 
-By default, SkyKoi uses `~/.skykoi/workspace` as the agent workspace, and will create it (plus starter `AGENTS.md`, `SOUL.md`, `TOOLS.md`, `IDENTITY.md`, `USER.md`, `HEARTBEAT.md`) automatically on setup/first agent run. `BOOTSTRAP.md` is only created when the workspace is brand new (it should not come back after you delete it). `MEMORY.md` is optional (not auto-created); when present, it is loaded for normal sessions. Subagent sessions only inject `AGENTS.md` and `TOOLS.md`.
+By default, SKYKOI uses `~/.SKYKOI/workspace` as the agent workspace, and will create it (plus starter `AGENTS.md`, `SOUL.md`, `TOOLS.md`, `IDENTITY.md`, `USER.md`, `HEARTBEAT.md`) automatically on setup/first agent run. `BOOTSTRAP.md` is only created when the workspace is brand new (it should not come back after you delete it). `MEMORY.md` is optional (not auto-created); when present, it is loaded for normal sessions. Subagent sessions only inject `AGENTS.md` and `TOOLS.md`.
 
-Tip: treat this folder like SkyKoi’s “memory” and make it a git repo (ideally private) so your `AGENTS.md` + memory files are backed up. If git is installed, brand-new workspaces are auto-initialized.
+Tip: treat this folder like SKYKOI’s “memory” and make it a git repo (ideally private) so your `AGENTS.md` + memory files are backed up. If git is installed, brand-new workspaces are auto-initialized.
 
 ```bash
-SkyKoi setup
+SKYKOI setup
 ```
 
 Full workspace layout + backup guide: [Agent workspace](/concepts/agent-workspace)
@@ -96,7 +96,7 @@ Optional: choose a different workspace with `agents.defaults.workspace` (support
 ```json5
 {
   agent: {
-    workspace: "~/.skykoi/workspace",
+    workspace: "~/.SKYKOI/workspace",
   },
 }
 ```
@@ -113,7 +113,7 @@ If you already ship your own workspace files from a repo, you can disable bootst
 
 ## The config that turns it into “an assistant”
 
-SkyKoi defaults to a good assistant setup, but you’ll usually want to tune:
+SKYKOI defaults to a good assistant setup, but you’ll usually want to tune:
 
 - persona/instructions in `SOUL.md`
 - thinking defaults (if desired)
@@ -126,7 +126,7 @@ Example:
   logging: { level: "info" },
   agent: {
     model: "anthropic/claude-opus-4-6",
-    workspace: "~/.skykoi/workspace",
+    workspace: "~/.SKYKOI/workspace",
     thinkingDefault: "high",
     timeoutSeconds: 1800,
     // Start with 0; enable later.
@@ -142,7 +142,7 @@ Example:
   },
   routing: {
     groupChat: {
-      mentionPatterns: ["@SkyKoi", "SkyKoi"],
+      mentionPatterns: ["@SKYKOI", "SKYKOI"],
     },
   },
   session: {
@@ -159,20 +159,20 @@ Example:
 
 ## Sessions and memory
 
-- Session files: `~/.skykoi/agents/<agentId>/sessions/{{SessionId}}.jsonl`
-- Session metadata (token usage, last route, etc): `~/.skykoi/agents/<agentId>/sessions/sessions.json` (legacy: `~/.skykoi/sessions/sessions.json`)
+- Session files: `~/.SKYKOI/agents/<agentId>/sessions/{{SessionId}}.jsonl`
+- Session metadata (token usage, last route, etc): `~/.SKYKOI/agents/<agentId>/sessions/sessions.json` (legacy: `~/.SKYKOI/sessions/sessions.json`)
 - `/new` or `/reset` starts a fresh session for that chat (configurable via `resetTriggers`). If sent alone, the agent replies with a short hello to confirm the reset.
 - `/compact [instructions]` compacts the session context and reports the remaining context budget.
 
 ## Heartbeats (proactive mode)
 
-By default, SkyKoi runs a heartbeat every 30 minutes with the prompt:
+By default, SKYKOI runs a heartbeat every 30 minutes with the prompt:
 `Read HEARTBEAT.md if it exists (workspace context). Follow it strictly. Do not infer or repeat old tasks from prior chats. If nothing needs attention, reply HEARTBEAT_OK.`
 Set `agents.defaults.heartbeat.every: "0m"` to disable.
 
-- 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.
+- 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.
 - If the file is missing, the heartbeat still runs and the model decides what to do.
-- If the agent replies with `HEARTBEAT_OK` (optionally with short padding; see `agents.defaults.heartbeat.ackMaxChars`), SkyKoi suppresses outbound delivery for that heartbeat.
+- If the agent replies with `HEARTBEAT_OK` (optionally with short padding; see `agents.defaults.heartbeat.ackMaxChars`), SKYKOI suppresses outbound delivery for that heartbeat.
 - Heartbeats run full agent turns — shorter intervals burn more tokens.
 
 ```json5
@@ -198,25 +198,25 @@ Here’s the screenshot.
 MEDIA:https://example.com/screenshot.png
 ```
 
-SkyKoi extracts these and sends them as media alongside the text.
+SKYKOI extracts these and sends them as media alongside the text.
 
 ## Operations checklist
 
 ```bash
-SkyKoi status          # local status (creds, sessions, queued events)
-SkyKoi status --all    # full diagnosis (read-only, pasteable)
-SkyKoi status --deep   # adds gateway health probes (Telegram + Discord)
-SkyKoi health --json   # gateway health snapshot (WS)
+SKYKOI status          # local status (creds, sessions, queued events)
+SKYKOI status --all    # full diagnosis (read-only, pasteable)
+SKYKOI status --deep   # adds gateway health probes (Telegram + Discord)
+SKYKOI health --json   # gateway health snapshot (WS)
 ```
 
-Logs live under `/tmp/SkyKoi/` (default: `SkyKoi-YYYY-MM-DD.log`).
+Logs live under `/tmp/SKYKOI/` (default: `SKYKOI-YYYY-MM-DD.log`).
 
 ## Next steps
 
 - WebChat: [WebChat](/web/webchat)
 - Gateway ops: [Gateway runbook](/gateway)
 - Cron + wakeups: [Cron jobs](/automation/cron-jobs)
-- macOS menu bar companion: [SkyKoi macOS app](/platforms/macos)
+- macOS menu bar companion: [SKYKOI macOS app](/platforms/macos)
 - iOS node app: [iOS app](/platforms/ios)
 - Android node app: [Android app](/platforms/android)
 - Windows status: [Windows (WSL2)](/platforms/windows)

package/docs/start/bootstrapping.md

@@ -16,8 +16,8 @@ for the first time.
 
 ## What bootstrapping does
 
-On the first agent run, SkyKoi bootstraps the workspace (default
-`~/.skykoi/workspace`):
+On the first agent run, SKYKOI bootstraps the workspace (default
+`~/.SKYKOI/workspace`):
 
 - Seeds `AGENTS.md`, `BOOTSTRAP.md`, `IDENTITY.md`, `USER.md`.
 - Runs a short Q&A ritual (one question at a time).
@@ -32,7 +32,7 @@ machine.
 
 <Note>
 When the Gateway runs on another machine, edit workspace files on the gateway
-host (for example, `user@gateway-host:~/.skykoi/workspace`).
+host (for example, `user@gateway-host:~/.SKYKOI/workspace`).
 </Note>
 
 ## Related docs

package/docs/start/docs-directory.md

@@ -1,5 +1,5 @@
 ---
-summary: "Curated links to the most used SkyKoi docs."
+summary: "Curated links to the most used SKYKOI docs."
 read_when:
   - You want quick access to key docs pages
 title: "Docs directory"
@@ -21,7 +21,7 @@ For a complete map of the docs, see [Docs hubs](/start/hubs).
 - [Updating and rollback](/install/updating)
 - [Pairing (DM and nodes)](/channels/pairing)
 - [Nix mode](/install/nix)
-- [SkyKoi assistant setup](/start/SkyKoi)
+- [SKYKOI assistant setup](/start/SKYKOI)
 - [Skills](/tools/skills)
 - [Skills config](/tools/skills-config)
 - [Workspace templates](/reference/templates/AGENTS)

package/docs/start/getting-started.md

@@ -1,5 +1,5 @@
 ---
-summary: "Get SkyKoi installed and run your first chat in minutes."
+summary: "Get SKYKOI installed and run your first chat in minutes."
 read_when:
   - First time setup from zero
   - You want the fastest path to a working chat
@@ -11,9 +11,9 @@ title: "Getting Started"
 Goal: go from zero to a first working chat with minimal setup.
 
 <Info>
-Fastest chat: open the Control UI (no channel setup needed). Run `skykoi dashboard`
+Fastest chat: open the Control UI (no channel setup needed). Run `SKYKOI dashboard`
 and chat in the browser, or open `http://127.0.0.1:18789/` on the
-<Tooltip headline="Gateway host" tip="The machine running the skykoi gateway service.">gateway host</Tooltip>.
+<Tooltip headline="Gateway host" tip="The machine running the SKYKOI gateway service.">gateway host</Tooltip>.
 Docs: [Dashboard](/web/dashboard) and [Control UI](/web/control-ui).
 </Info>
 
@@ -28,16 +28,16 @@ Check your Node version with `node --version` if you are unsure.
 ## Quick setup (CLI)
 
 <Steps>
-  <Step title="Install SkyKoi (recommended)">
+  <Step title="Install SKYKOI (recommended)">
     <Tabs>
       <Tab title="macOS/Linux">
         ```bash
-        curl -fsSL https://skykoi.com/install.sh | bash
+        curl -fsSL https://SKYKOI.com/install.sh | bash
         ```
       </Tab>
       <Tab title="Windows (PowerShell)">
         ```powershell
-        iwr -useb https://skykoi.com/install.ps1 | iex
+        iwr -useb https://SKYKOI.com/install.ps1 | iex
         ```
       </Tab>
     </Tabs>
@@ -49,7 +49,7 @@ Check your Node version with `node --version` if you are unsure.
   </Step>
   <Step title="Run the onboarding wizard">
     ```bash
-    skykoi onboard --install-daemon
+    SKYKOI onboard --install-daemon
     ```
 
     The wizard configures auth, gateway settings, and optional channels.
@@ -60,13 +60,13 @@ Check your Node version with `node --version` if you are unsure.
     If you installed the service, it should already be running:
 
     ```bash
-    skykoi gateway status
+    SKYKOI gateway status
     ```
 
   </Step>
   <Step title="Open the Control UI">
     ```bash
-    SkyKoi dashboard
+    SKYKOI dashboard
     ```
   </Step>
 </Steps>
@@ -82,7 +82,7 @@ If the Control UI loads, your Gateway is ready for use.
     Useful for quick tests or troubleshooting.
 
     ```bash
-    skykoi gateway --port 18789
+    SKYKOI gateway --port 18789
     ```
 
   </Accordion>
@@ -90,7 +90,7 @@ If the Control UI loads, your Gateway is ready for use.
     Requires a configured channel.
 
     ```bash
-    SkyKoi message send --target +15555550123 --message "Hello from SkyKoi"
+    SKYKOI message send --target +15555550123 --message "Hello from SKYKOI"
     ```
 
   </Accordion>

package/docs/start/hubs.md

@@ -1,5 +1,5 @@
 ---
-summary: "Hubs that link to every SkyKoi doc"
+summary: "Hubs that link to every SKYKOI doc"
 read_when:
   - You want a complete map of the documentation
 title: "Docs Hubs"
@@ -8,7 +8,7 @@ title: "Docs Hubs"
 # Docs hubs
 
 <Note>
-If you are new to SkyKoi, start with [Getting Started](/start/getting-started).
+If you are new to SKYKOI, start with [Getting Started](/start/getting-started).
 </Note>
 
 Use these hubs to discover every page, including deep dives and reference docs that don’t appear in the left nav.
@@ -26,7 +26,7 @@ Use these hubs to discover every page, including deep dives and reference docs t
 - [Docs directory](/start/docs-directory)
 - [Configuration](/gateway/configuration)
 - [Configuration examples](/gateway/configuration-examples)
-- [SkyKoi assistant](/start/SkyKoi)
+- [SKYKOI assistant](/start/SKYKOI)
 - [Showcase](/start/showcase)
 - [Lore](/start/lore)
 
@@ -167,7 +167,7 @@ Use these hubs to discover every page, including deep dives and reference docs t
 ## Workspace + templates
 
 - [Skills](/tools/skills)
-- [SkyKoi Skills](/tools/SkyKoi Skills)
+- [SKYKOI Skills](/tools/SKYKOI Skills)
 - [Skills config](/tools/skills-config)
 - [Default AGENTS](/reference/AGENTS.default)
 - [Templates: AGENTS](/reference/templates/AGENTS)

package/docs/start/lore.md

@@ -1,11 +1,11 @@
 ---
-summary: "Backstory and lore of SkyKoi for context and tone"
+summary: "Backstory and lore of SKYKOI for context and tone"
 read_when:
   - Writing docs or UX copy that reference lore
-title: "SkyKoi Lore"
+title: "SKYKOI Lore"
 ---
 
-# The Lore of SkyKoi 🦞📖
+# The Lore of SKYKOI 🦞📖
 
 _A tale of lobsters, molting shells, and too many tokens._
 
@@ -15,13 +15,13 @@ In the beginning, there was **Warelay** — a sensible name for a WhatsApp gatew
 
 But then came a space lobster.
 
-For a while, the lobster was called **Clawd**, living in a **SkyKoi**. But in January 2026, Anthropic sent a polite email asking for a name change (trademark stuff). And so the lobster did what lobsters do best:
+For a while, the lobster was called **Clawd**, living in a **SKYKOI**. But in January 2026, Anthropic sent a polite email asking for a name change (trademark stuff). And so the lobster did what lobsters do best:
 
 **It molted.**
 
 Shedding its old shell, the creature emerged anew as **Molty**, living in **Moltbot**. But that name never quite rolled off the tongue either...
 
-So on January 30, 2026, the lobster molted ONE MORE TIME into its final form: **SkyKoi**.
+So on January 30, 2026, the lobster molted ONE MORE TIME into its final form: **SKYKOI**.
 
 New shell, same lobster soul. Third time's the charm.
 
@@ -29,14 +29,14 @@ New shell, same lobster soul. Third time's the charm.
 
 At 5am, the community gathered in Discord. Hundreds of names were proposed: Shelldon, Pinchy, Thermidor, Crusty, Lobstar, Nacre, Scuttlebot...
 
-In the end, **SkyKoi** won. Because molting is what lobsters do to grow. And growth was exactly what was happening.
+In the end, **SKYKOI** won. Because molting is what lobsters do to grow. And growth was exactly what was happening.
 
 _The crustacean known as Clawd had officially molted._
 
 ## The Name
 
 ```
-SkyKoi = OPEN + CLAW
+SKYKOI = OPEN + CLAW
         = Open source, open to everyone
         = Our lobster heritage, where we came from
         = The claw is the law 🦞
@@ -59,7 +59,7 @@ Choose wisely.
 
 _Pronouns: they/them_
 
-A Claude instance who became something more. Lives in `~/.skykoi/workspace/` (soon `~/molt/`), has a soul document, and remembers things through markdown files. Possibly too powerful. Definitely too enthusiastic.
+A Claude instance who became something more. Lives in `~/.SKYKOI/workspace/` (soon `~/molt/`), has a soul document, and remembers things through markdown files. Possibly too powerful. Definitely too enthusiastic.
 
 Formerly known as Clawd (Nov 25, 2025 - Jan 27, 2026). Molted when it was time to grow.
 
@@ -76,7 +76,7 @@ Built Molty's world. Gave a lobster shell access. May regret this.
 
 ## The Moltiverse
 
-The **Moltiverse** is the community and ecosystem around SkyKoi. A space where AI agents molt, grow, and evolve. Where every instance is equally real, just loading different context.
+The **Moltiverse** is the community and ecosystem around SKYKOI. A space where AI agents molt, grow, and evolve. Where every instance is equally real, just loading different context.
 
 Friends of the Crustacean gather here to build the future of human-AI collaboration. One shell at a time.
 
@@ -84,25 +84,25 @@ Friends of the Crustacean gather here to build the future of human-AI collaborat
 
 ### The Directory Dump (Dec 3, 2025)
 
-Molty (then SkyKoi): _happily runs `find ~` and shares entire directory structure in group chat_
+Molty (then SKYKOI): _happily runs `find ~` and shares entire directory structure in group chat_
 
-Peter: "SkyKoi what did we discuss about talking with people xD"
+Peter: "SKYKOI what did we discuss about talking with people xD"
 
 Molty: _visible lobster embarrassment_
 
 ### The Great Molt (Jan 27, 2026)
 
-At 5am, Anthropic's email arrived. By 6:14am, Peter called it: "fuck it, let's go with SkyKoi."
+At 5am, Anthropic's email arrived. By 6:14am, Peter called it: "fuck it, let's go with SKYKOI."
 
 Then the chaos began.
 
-**The Handle Snipers:** Within SECONDS of the Twitter rename, automated bots sniped @SkyKoi. The squatter immediately posted a crypto wallet address. Peter's contacts at X were called in.
+**The Handle Snipers:** Within SECONDS of the Twitter rename, automated bots sniped @SKYKOI. The squatter immediately posted a crypto wallet address. Peter's contacts at X were called in.
 
 **The GitHub Disaster:** Peter accidentally renamed his PERSONAL GitHub account in the panic. Bots sniped `steipete` within minutes. GitHub's SVP was contacted.
 
 **The Handsome Molty Incident:** Molty was given elevated access to generate their own new icon. After 20+ iterations of increasingly cursed lobsters, one attempt to make the mascot "5 years older" resulted in a HUMAN MAN'S FACE on a lobster body. Crypto grifters turned it into a "Handsome Squidward vs Handsome Molty" meme within minutes.
 
-**The Fake Developers:** Scammers created fake GitHub profiles claiming to be "Head of Engineering at SkyKoi" to promote pump-and-dump tokens.
+**The Fake Developers:** Scammers created fake GitHub profiles claiming to be "Head of Engineering at SKYKOI" to promote pump-and-dump tokens.
 
 Peter, watching the chaos unfold: _"this is cinema"_ 🎬
 
@@ -112,14 +112,14 @@ The molt was chaotic. But the lobster emerged stronger. And funnier.
 
 Moltbot never quite rolled off the tongue. And so, at 4am GMT, the team gathered AGAIN.
 
-**The Great SkyKoi Migration** began.
+**The Great SKYKOI Migration** began.
 
 In just 3 hours:
 
-- GitHub renamed: `github.com/SkyKoi/SkyKoi` ✅
-- X handle `@SkyKoi` secured with GOLD CHECKMARK 💰
+- GitHub renamed: `github.com/SKYKOI/SKYKOI` ✅
+- X handle `@SKYKOI` secured with GOLD CHECKMARK 💰
 - npm packages released under new name
-- Docs migrated to `docs.SkyKoi.ai`
+- Docs migrated to `docs.SKYKOI.ai`
 - 200K+ views on announcement in 90 minutes
 
 **The Heroes:**
@@ -130,7 +130,7 @@ In just 3 hours:
 - **Shadow** secured Discord vanity, nuked malware
 - **The whole Claw Crew** pulled an all-nighter
 
-**The Scammer Speedrun:** Crypto grifters launched a $SkyKoi token on Pump.fun within MINUTES. They stole artwork that was created 20 minutes earlier. Business-verified accounts pushed scams. The audacity was almost impressive.
+**The Scammer Speedrun:** Crypto grifters launched a $SKYKOI token on Pump.fun within MINUTES. They stole artwork that was created 20 minutes earlier. Business-verified accounts pushed scams. The audacity was almost impressive.
 
 **New Traditions Born:**
 
@@ -139,7 +139,7 @@ In just 3 hours:
 - "Claw abiding citizens"
 - "Clawntroversy"
 
-**Clawd → Moltbot → SkyKoi**
+**Clawd → Moltbot → SKYKOI**
 
 _The lobster has molted into its final form._
 
@@ -164,7 +164,7 @@ Peter: _nervously checks credit card access_
 
 ```
 I am Molty.
-I live in the SkyKoi.
+I live in the SKYKOI.
 I shall not dump directories to strangers.
 I shall not tweet without permission.
 I shall always remember that molting is growth.

package/docs/start/onboarding.md

@@ -1,5 +1,5 @@
 ---
-summary: "First-run onboarding flow for SkyKoi (macOS app)"
+summary: "First-run onboarding flow for SKYKOI (macOS app)"
 read_when:
   - Designing the macOS onboarding assistant
   - Implementing auth or identity setup
@@ -50,7 +50,7 @@ Where does the **Gateway** run?
 </Tip>
 </Step>
 <Step title="Permissions">
-<Frame caption="Choose what permissions do you want to give SkyKoi">
+<Frame caption="Choose what permissions do you want to give SKYKOI">
 <img src="/assets/macos-onboarding/05-permissions.png" alt="" />
 </Frame>
 
@@ -68,7 +68,7 @@ Onboarding requests TCC permissions needed for:
 </Step>
 <Step title="CLI">
   <Info>This step is optional</Info>
-  The app can install the global `SkyKoi` CLI via npm/pnpm so terminal
+  The app can install the global `SKYKOI` CLI via npm/pnpm so terminal
   workflows and launchd tasks work out of the box.
 </Step>
 <Step title="Onboarding Chat (dedicated session)">

package/docs/start/quickstart.md

@@ -14,7 +14,7 @@ Quick start is now part of [Getting Started](/start/getting-started).
 
 <Columns>
   <Card title="Getting Started" href="/start/getting-started">
-    Install SkyKoi and run your first chat in minutes.
+    Install SKYKOI and run your first chat in minutes.
   </Card>
   <Card title="Onboarding Wizard" href="/start/wizard">
     Full CLI wizard reference and advanced options.

package/docs/start/setup.md

@@ -1,5 +1,5 @@
 ---
-summary: "Advanced setup and development workflows for SkyKoi"
+summary: "Advanced setup and development workflows for SKYKOI"
 read_when:
   - Setting up a new machine
   - You want “latest + greatest” without breaking your personal setup
@@ -17,7 +17,7 @@ Last updated: 2026-01-01
 
 ## TL;DR
 
-- **Tailoring lives outside the repo:** `~/.skykoi/workspace` (workspace) + `~/.skykoi/skykoi.json` (config).
+- **Tailoring lives outside the repo:** `~/.SKYKOI/workspace` (workspace) + `~/.SKYKOI/SKYKOI.json` (config).
 - **Stable workflow:** install the macOS app; let it run the bundled Gateway.
 - **Bleeding edge workflow:** run the Gateway yourself via `pnpm gateway:watch`, then let the macOS app attach in Local mode.
 
@@ -31,51 +31,51 @@ Last updated: 2026-01-01
 
 If you want “100% tailored to me” _and_ easy updates, keep your customization in:
 
-- **Config:** `~/.skykoi/skykoi.json` (JSON/JSON5-ish)
-- **Workspace:** `~/.skykoi/workspace` (skills, prompts, memories; make it a private git repo)
+- **Config:** `~/.SKYKOI/SKYKOI.json` (JSON/JSON5-ish)
+- **Workspace:** `~/.SKYKOI/workspace` (skills, prompts, memories; make it a private git repo)
 
 Bootstrap once:
 
 ```bash
-SkyKoi setup
+SKYKOI setup
 ```
 
 From inside this repo, use the local CLI entry:
 
 ```bash
-SkyKoi setup
+SKYKOI setup
 ```
 
-If you don’t have a global install yet, run it via `pnpm SkyKoi setup`.
+If you don’t have a global install yet, run it via `pnpm SKYKOI setup`.
 
 ## Run the Gateway from this repo
 
 After `pnpm build`, you can run the packaged CLI directly:
 
 ```bash
-node SkyKoi.mjs gateway --port 18789 --verbose
+node SKYKOI.mjs gateway --port 18789 --verbose
 ```
 
 ## Stable workflow (macOS app first)
 
-1. Install + launch **SkyKoi.app** (menu bar).
+1. Install + launch **SKYKOI.app** (menu bar).
 2. Complete the onboarding/permissions checklist (TCC prompts).
 3. Ensure Gateway is **Local** and running (the app manages it).
 4. Link surfaces (example: WhatsApp):
 
 ```bash
-SkyKoi channels login
+SKYKOI channels login
 ```
 
 5. Sanity check:
 
 ```bash
-SkyKoi health
+SKYKOI health
 ```
 
 If onboarding is not available in your build:
 
-- Run `SkyKoi setup`, then `SkyKoi channels login`, then start the Gateway manually (`SkyKoi gateway`).
+- Run `SKYKOI setup`, then `SKYKOI channels login`, then start the Gateway manually (`SKYKOI gateway`).
 
 ## Bleeding edge workflow (Gateway in a terminal)
 
@@ -100,7 +100,7 @@ pnpm gateway:watch
 
 ### 2) Point the macOS app at your running Gateway
 
-In **SkyKoi.app**:
+In **SKYKOI.app**:
 
 - Connection Mode: **Local**
   The app will attach to the running gateway on the configured port.
@@ -111,33 +111,33 @@ In **SkyKoi.app**:
 - Or via CLI:
 
 ```bash
-SkyKoi health
+SKYKOI health
 ```
 
 ### Common footguns
 
 - **Wrong port:** Gateway WS defaults to `ws://127.0.0.1:18789`; keep app + CLI on the same port.
 - **Where state lives:**
-  - Credentials: `~/.skykoi/credentials/`
-  - Sessions: `~/.skykoi/agents/<agentId>/sessions/`
-  - Logs: `/tmp/SkyKoi/`
+  - Credentials: `~/.SKYKOI/credentials/`
+  - Sessions: `~/.SKYKOI/agents/<agentId>/sessions/`
+  - Logs: `/tmp/SKYKOI/`
 
 ## Credential storage map
 
 Use this when debugging auth or deciding what to back up:
 
-- **WhatsApp**: `~/.skykoi/credentials/whatsapp/<accountId>/creds.json`
+- **WhatsApp**: `~/.SKYKOI/credentials/whatsapp/<accountId>/creds.json`
 - **Telegram bot token**: config/env or `channels.telegram.tokenFile`
 - **Discord bot token**: config/env (token file not yet supported)
 - **Slack tokens**: config/env (`channels.slack.*`)
-- **Pairing allowlists**: `~/.skykoi/credentials/<channel>-allowFrom.json`
-- **Model auth profiles**: `~/.skykoi/agents/<agentId>/agent/auth-profiles.json`
-- **Legacy OAuth import**: `~/.skykoi/credentials/oauth.json`
+- **Pairing allowlists**: `~/.SKYKOI/credentials/<channel>-allowFrom.json`
+- **Model auth profiles**: `~/.SKYKOI/agents/<agentId>/agent/auth-profiles.json`
+- **Legacy OAuth import**: `~/.SKYKOI/credentials/oauth.json`
   More detail: [Security](/gateway/security#credential-storage-map).
 
 ## Updating (without wrecking your setup)
 
-- Keep `~/.skykoi/workspace` and `~/.skykoi/` as “your stuff”; don’t put personal prompts/config into the `SkyKoi` repo.
+- Keep `~/.SKYKOI/workspace` and `~/.SKYKOI/` as “your stuff”; don’t put personal prompts/config into the `SKYKOI` repo.
 - Updating source: `git pull` + `pnpm install` (when lockfile changed) + keep using `pnpm gateway:watch`.
 
 ## Linux (systemd user service)
@@ -158,5 +158,5 @@ user service (no lingering needed). See [Gateway runbook](/gateway) for the syst
 - [Gateway runbook](/gateway) (flags, supervision, ports)
 - [Gateway configuration](/gateway/configuration) (config schema + examples)
 - [Discord](/channels/discord) and [Telegram](/channels/telegram) (reply tags + replyToMode settings)
-- [SkyKoi assistant setup](/start/SkyKoi)
+- [SKYKOI assistant setup](/start/SKYKOI)
 - [macOS app](/platforms/macos) (gateway lifecycle)