skykoi 2026.3.11 → 2026.3.13

package/docs/tools/browser-linux-troubleshooting.md

@@ -1,5 +1,5 @@
 ---
-summary: "Fix Chrome/Brave/Edge/Chromium CDP startup issues for SkyKoi browser control on Linux"
+summary: "Fix Chrome/Brave/Edge/Chromium CDP startup issues for SKYKOI browser control on Linux"
 read_when: "Browser control fails on Linux, especially with snap Chromium"
 title: "Browser Troubleshooting"
 ---
@@ -8,15 +8,15 @@ title: "Browser Troubleshooting"
 
 ## Problem: "Failed to start Chrome CDP on port 18800"
 
-SkyKoi's browser control server fails to launch Chrome/Brave/Edge/Chromium with the error:
+SKYKOI's browser control server fails to launch Chrome/Brave/Edge/Chromium with the error:
 
 ```
-{"error":"Error: Failed to start Chrome CDP on port 18800 for profile \"SkyKoi\"."}
+{"error":"Error: Failed to start Chrome CDP on port 18800 for profile \"SKYKOI\"."}
 ```
 
 ### Root Cause
 
-On Ubuntu (and many Linux distros), the default Chromium installation is a **snap package**. Snap's AppArmor confinement interferes with how SkyKoi spawns and monitors the browser process.
+On Ubuntu (and many Linux distros), the default Chromium installation is a **snap package**. Snap's AppArmor confinement interferes with how SKYKOI spawns and monitors the browser process.
 
 The `apt install chromium` command installs a stub package that redirects to snap:
 
@@ -37,7 +37,7 @@ sudo dpkg -i google-chrome-stable_current_amd64.deb
 sudo apt --fix-broken install -y  # if there are dependency errors
 ```
 
-Then update your SkyKoi config (`~/.skykoi/skykoi.json`):
+Then update your SKYKOI config (`~/.SKYKOI/SKYKOI.json`):
 
 ```json
 {
@@ -52,7 +52,7 @@ Then update your SkyKoi config (`~/.skykoi/skykoi.json`):
 
 ### Solution 2: Use Snap Chromium with Attach-Only Mode
 
-If you must use snap Chromium, configure SkyKoi to attach to a manually-started browser:
+If you must use snap Chromium, configure SKYKOI to attach to a manually-started browser:
 
 1. Update config:
 
@@ -72,20 +72,20 @@ If you must use snap Chromium, configure SkyKoi to attach to a manually-started
 ```bash
 chromium-browser --headless --no-sandbox --disable-gpu \
   --remote-debugging-port=18800 \
-  --user-data-dir=$HOME/.skykoi/browser/SkyKoi/user-data \
+  --user-data-dir=$HOME/.SKYKOI/browser/SKYKOI/user-data \
   about:blank &
 ```
 
 3. Optionally create a systemd user service to auto-start Chrome:
 
 ```ini
-# ~/.config/systemd/user/SkyKoi-browser.service
+# ~/.config/systemd/user/SKYKOI-browser.service
 [Unit]
-Description=SkyKoi Browser (Chrome CDP)
+Description=SKYKOI Browser (Chrome CDP)
 After=network.target
 
 [Service]
-ExecStart=/snap/bin/chromium --headless --no-sandbox --disable-gpu --remote-debugging-port=18800 --user-data-dir=%h/.skykoi/browser/SkyKoi/user-data about:blank
+ExecStart=/snap/bin/chromium --headless --no-sandbox --disable-gpu --remote-debugging-port=18800 --user-data-dir=%h/.SKYKOI/browser/SKYKOI/user-data about:blank
 Restart=on-failure
 RestartSec=5
 
@@ -93,7 +93,7 @@ RestartSec=5
 WantedBy=default.target
 ```
 
-Enable with: `systemctl --user enable --now SkyKoi-browser.service`
+Enable with: `systemctl --user enable --now SKYKOI-browser.service`
 
 ### Verifying the Browser Works
 
@@ -123,17 +123,17 @@ curl -s http://127.0.0.1:18791/tabs
 
 ### Problem: "Chrome extension relay is running, but no tab is connected"
 
-You’re using the `chrome` profile (extension relay). It expects the SkyKoi
+You’re using the `chrome` profile (extension relay). It expects the SKYKOI
 browser extension to be attached to a live tab.
 
 Fix options:
 
-1. **Use the managed browser:** `SkyKoi browser start --browser-profile SkyKoi`
-   (or set `browser.defaultProfile: "SkyKoi"`).
+1. **Use the managed browser:** `SKYKOI browser start --browser-profile SKYKOI`
+   (or set `browser.defaultProfile: "SKYKOI"`).
 2. **Use the extension relay:** install the extension, open a tab, and click the
-   SkyKoi extension icon to attach it.
+   SKYKOI extension icon to attach it.
 
 Notes:
 
 - The `chrome` profile uses your **system default Chromium browser** when possible.
-- Local `SkyKoi` profiles auto-assign `cdpPort`/`cdpUrl`; only set those for remote CDP.
+- Local `SKYKOI` profiles auto-assign `cdpPort`/`cdpUrl`; only set those for remote CDP.

package/docs/tools/browser-login.md

@@ -10,7 +10,7 @@ title: "Browser Login"
 
 ## Manual login (recommended)
 
-When a site requires login, **sign in manually** in the **host** browser profile (the SkyKoi browser).
+When a site requires login, **sign in manually** in the **host** browser profile (the SKYKOI browser).
 
 Do **not** give the model your credentials. Automated logins often trigger anti‑bot defenses and can lock the account.
 
@@ -18,7 +18,7 @@ Back to the main browser docs: [Browser](/tools/browser).
 
 ## Which Chrome profile is used?
 
-SkyKoi controls a **dedicated Chrome profile** (named `SkyKoi`, orange‑tinted UI). This is separate from your daily browser profile.
+SKYKOI controls a **dedicated Chrome profile** (named `SKYKOI`, orange‑tinted UI). This is separate from your daily browser profile.
 
 Two easy ways to access it:
 
@@ -26,11 +26,11 @@ Two easy ways to access it:
 2. **Open it via CLI**:
 
 ```bash
-SkyKoi browser start
-SkyKoi browser open https://x.com
+SKYKOI browser start
+SKYKOI browser open https://x.com
 ```
 
-If you have multiple profiles, pass `--browser-profile <name>` (the default is `SkyKoi`).
+If you have multiple profiles, pass `--browser-profile <name>` (the default is `SKYKOI`).
 
 ## X/Twitter: recommended flow
 
@@ -61,7 +61,7 @@ If the agent is sandboxed, the browser tool defaults to the sandbox. To allow ho
 Then target the host browser:
 
 ```bash
-SkyKoi browser open https://x.com --browser-profile SkyKoi --target host
+SKYKOI browser open https://x.com --browser-profile SKYKOI --target host
 ```
 
 Or disable sandboxing for the agent that posts updates.

package/docs/tools/browser.md

@@ -2,31 +2,31 @@
 summary: "Integrated browser control service + action commands"
 read_when:
   - Adding agent-controlled browser automation
-  - Debugging why SkyKoi is interfering with your own Chrome
+  - Debugging why SKYKOI is interfering with your own Chrome
   - Implementing browser settings + lifecycle in the macOS app
-title: "Browser (SkyKoi-managed)"
+title: "Browser (SKYKOI-managed)"
 ---
 
-# Browser (SkyKoi-managed)
+# Browser (SKYKOI-managed)
 
-SkyKoi can run a **dedicated Chrome/Brave/Edge/Chromium profile** that the agent controls.
+SKYKOI can run a **dedicated Chrome/Brave/Edge/Chromium profile** that the agent controls.
 It is isolated from your personal browser and is managed through a small local
 control service inside the Gateway (loopback only).
 
 Beginner view:
 
 - Think of it as a **separate, agent-only browser**.
-- The `SkyKoi` profile does **not** touch your personal browser profile.
+- The `SKYKOI` profile does **not** touch your personal browser profile.
 - The agent can **open tabs, read pages, click, and type** in a safe lane.
 - The default `chrome` profile uses the **system default Chromium browser** via the
-  extension relay; switch to `SkyKoi` for the isolated managed browser.
+  extension relay; switch to `SKYKOI` for the isolated managed browser.
 
 ## What you get
 
-- A separate browser profile named **SkyKoi** (orange accent by default).
+- A separate browser profile named **SKYKOI** (orange accent by default).
 - Deterministic tab control (list/open/focus/close).
 - Agent actions (click/type/drag/select), snapshots, screenshots, PDFs.
-- Optional multi-profile support (`SkyKoi`, `work`, `remote`, ...).
+- Optional multi-profile support (`SKYKOI`, `work`, `remote`, ...).
 
 This browser is **not** your daily driver. It is a safe, isolated surface for
 agent automation and verification.
@@ -34,26 +34,26 @@ agent automation and verification.
 ## Quick start
 
 ```bash
-SkyKoi browser --browser-profile SkyKoi status
-SkyKoi browser --browser-profile SkyKoi start
-SkyKoi browser --browser-profile SkyKoi open https://example.com
-SkyKoi browser --browser-profile SkyKoi snapshot
+SKYKOI browser --browser-profile SKYKOI status
+SKYKOI browser --browser-profile SKYKOI start
+SKYKOI browser --browser-profile SKYKOI open https://example.com
+SKYKOI browser --browser-profile SKYKOI snapshot
 ```
 
 If you get “Browser disabled”, enable it in config (see below) and restart the
 Gateway.
 
-## Profiles: `SkyKoi` vs `chrome`
+## Profiles: `SKYKOI` vs `chrome`
 
-- `SkyKoi`: managed, isolated browser (no extension required).
-- `chrome`: extension relay to your **system browser** (requires the SkyKoi
+- `SKYKOI`: managed, isolated browser (no extension required).
+- `chrome`: extension relay to your **system browser** (requires the SKYKOI
   extension to be attached to a tab).
 
-Set `browser.defaultProfile: "SkyKoi"` if you want managed mode by default.
+Set `browser.defaultProfile: "SKYKOI"` if you want managed mode by default.
 
 ## Configuration
 
-Browser settings live in `~/.skykoi/skykoi.json`.
+Browser settings live in `~/.SKYKOI/SKYKOI.json`.
 
 ```json5
 {
@@ -69,7 +69,7 @@ Browser settings live in `~/.skykoi/skykoi.json`.
     attachOnly: false,
     executablePath: "/Applications/Brave Browser.app/Contents/MacOS/Brave Browser",
     profiles: {
-      SkyKoi: { cdpPort: 18800, color: "#FF4500" },
+      SKYKOI: { cdpPort: 18800, color: "#FF4500" },
       work: { cdpPort: 18801, color: "#0066CC" },
       remote: { cdpUrl: "http://10.0.0.42:9222", color: "#00AA00" },
     },
@@ -88,20 +88,20 @@ Notes:
 - `remoteCdpHandshakeTimeoutMs` applies to remote CDP WebSocket reachability checks.
 - `attachOnly: true` means “never launch a local browser; only attach if it is already running.”
 - `color` + per-profile `color` tint the browser UI so you can see which profile is active.
-- Default profile is `chrome` (extension relay). Use `defaultProfile: "SkyKoi"` for the managed browser.
+- Default profile is `chrome` (extension relay). Use `defaultProfile: "SKYKOI"` for the managed browser.
 - Auto-detect order: system default browser if Chromium-based; otherwise Chrome → Brave → Edge → Chromium → Chrome Canary.
-- Local `SkyKoi` profiles auto-assign `cdpPort`/`cdpUrl` — set those only for remote CDP.
+- Local `SKYKOI` profiles auto-assign `cdpPort`/`cdpUrl` — set those only for remote CDP.
 
 ## Use Brave (or another Chromium-based browser)
 
 If your **system default** browser is Chromium-based (Chrome/Brave/Edge/etc),
-SkyKoi uses it automatically. Set `browser.executablePath` to override
+SKYKOI uses it automatically. Set `browser.executablePath` to override
 auto-detection:
 
 CLI example:
 
 ```bash
-SkyKoi config set browser.executablePath "/usr/bin/google-chrome"
+SKYKOI config set browser.executablePath "/usr/bin/google-chrome"
 ```
 
 ```json5
@@ -132,20 +132,20 @@ SkyKoi config set browser.executablePath "/usr/bin/google-chrome"
 - **Local control (default):** the Gateway starts the loopback control service and can launch a local browser.
 - **Remote control (node host):** run a node host on the machine that has the browser; the Gateway proxies browser actions to it.
 - **Remote CDP:** set `browser.profiles.<name>.cdpUrl` (or `browser.cdpUrl`) to
-  attach to a remote Chromium-based browser. In this case, SkyKoi will not launch a local browser.
+  attach to a remote Chromium-based browser. In this case, SKYKOI will not launch a local browser.
 
 Remote CDP URLs can include auth:
 
 - Query tokens (e.g., `https://provider.example?token=<token>`)
 - HTTP Basic auth (e.g., `https://user:pass@provider.example`)
 
-SkyKoi preserves the auth when calling `/json/*` endpoints and when connecting
+SKYKOI preserves the auth when calling `/json/*` endpoints and when connecting
 to the CDP WebSocket. Prefer environment variables or secrets managers for
 tokens instead of committing them to config files.
 
 ## Node browser proxy (zero-config default)
 
-If you run a **node host** on the machine that has your browser, SkyKoi can
+If you run a **node host** on the machine that has your browser, SKYKOI can
 auto-route browser tool calls to that node without any extra browser config.
 This is the default path for remote gateways.
 
@@ -160,7 +160,7 @@ Notes:
 ## Browserless (hosted remote CDP)
 
 [Browserless](https://browserless.io) is a hosted Chromium service that exposes
-CDP endpoints over HTTPS. You can point a SkyKoi browser profile at a
+CDP endpoints over HTTPS. You can point a SKYKOI browser profile at a
 Browserless region endpoint and authenticate with your API key.
 
 Example:
@@ -202,15 +202,15 @@ Remote CDP tips:
 
 ## Profiles (multi-browser)
 
-SkyKoi supports multiple named profiles (routing configs). Profiles can be:
+SKYKOI supports multiple named profiles (routing configs). Profiles can be:
 
-- **SkyKoi-managed**: a dedicated Chromium-based browser instance with its own user data directory + CDP port
+- **SKYKOI-managed**: a dedicated Chromium-based browser instance with its own user data directory + CDP port
 - **remote**: an explicit CDP URL (Chromium-based browser running elsewhere)
 - **extension relay**: your existing Chrome tab(s) via the local relay + Chrome extension
 
 Defaults:
 
-- The `SkyKoi` profile is auto-created if missing.
+- The `SKYKOI` profile is auto-created if missing.
 - The `chrome` profile is built-in for the Chrome extension relay (points at `http://127.0.0.1:18792` by default).
 - Local CDP ports allocate from **18800–18899** by default.
 - Deleting a profile moves its local data directory to Trash.
@@ -219,7 +219,7 @@ All control endpoints accept `?profile=<name>`; the CLI uses `--browser-profile`
 
 ## Chrome extension relay (use your existing Chrome)
 
-SkyKoi can also drive **your existing Chrome tabs** (no separate “SkyKoi” Chrome instance) via a local CDP relay + a Chrome extension.
+SKYKOI can also drive **your existing Chrome tabs** (no separate “SKYKOI” Chrome instance) via a local CDP relay + a Chrome extension.
 
 Full guide: [Chrome extension](/tools/chrome-extension)
 
@@ -227,7 +227,7 @@ Flow:
 
 - The Gateway runs locally (same machine) or a node host runs on the browser machine.
 - A local **relay server** listens at a loopback `cdpUrl` (default: `http://127.0.0.1:18792`).
-- You click the **SkyKoi Browser Relay** extension icon on a tab to attach (it does not auto-attach).
+- You click the **SKYKOI Browser Relay** extension icon on a tab to attach (it does not auto-attach).
 - The agent controls that tab via the normal `browser` tool, by selecting the right profile.
 
 If the Gateway runs elsewhere, run a node host on the browser machine so the Gateway can proxy browser actions.
@@ -245,22 +245,22 @@ Chrome extension relay takeover requires host browser control, so either:
 1. Load the extension (dev/unpacked):
 
 ```bash
-SkyKoi browser extension install
+SKYKOI browser extension install
 ```
 
 - Chrome → `chrome://extensions` → enable “Developer mode”
-- “Load unpacked” → select the directory printed by `SkyKoi browser extension path`
+- “Load unpacked” → select the directory printed by `SKYKOI browser extension path`
 - Pin the extension, then click it on the tab you want to control (badge shows `ON`).
 
 2. Use it:
 
-- CLI: `SkyKoi browser --browser-profile chrome tabs`
+- CLI: `SKYKOI browser --browser-profile chrome tabs`
 - Agent tool: `browser` with `profile="chrome"`
 
 Optional: if you want a different name or relay port, create your own profile:
 
 ```bash
-SkyKoi browser create-profile \
+SKYKOI browser create-profile \
   --name my-chrome \
   --driver extension \
   --cdp-url http://127.0.0.1:18792 \
@@ -280,7 +280,7 @@ Notes:
 
 ## Browser selection
 
-When launching locally, SkyKoi picks the first available:
+When launching locally, SKYKOI picks the first available:
 
 1. Chrome
 2. Brave
@@ -319,12 +319,12 @@ All endpoints accept `?profile=<name>`.
 
 Some features (navigate/act/AI snapshot/role snapshot, element screenshots, PDF) require
 Playwright. If Playwright isn’t installed, those endpoints return a clear 501
-error. ARIA snapshots and basic screenshots still work for SkyKoi-managed Chrome.
+error. ARIA snapshots and basic screenshots still work for SKYKOI-managed Chrome.
 For the Chrome extension relay driver, ARIA snapshots and screenshots require Playwright.
 
 If you see `Playwright is not available in this gateway build`, install the full
 Playwright package (not `playwright-core`) and restart the gateway, or reinstall
-SkyKoi with browser support.
+SKYKOI with browser support.
 
 #### Docker Playwright install
 
@@ -332,7 +332,7 @@ If your Gateway runs in Docker, avoid `npx playwright` (npm override conflicts).
 Use the bundled CLI instead:
 
 ```bash
-docker compose run --rm SkyKoi-cli \
+docker compose run --rm SKYKOI-cli \
   node /app/node_modules/playwright-core/cli.js install chromium
 ```
 
@@ -360,79 +360,79 @@ All commands also accept `--json` for machine-readable output (stable payloads).
 
 Basics:
 
-- `SkyKoi browser status`
-- `SkyKoi browser start`
-- `SkyKoi browser stop`
-- `SkyKoi browser tabs`
-- `SkyKoi browser tab`
-- `SkyKoi browser tab new`
-- `SkyKoi browser tab select 2`
-- `SkyKoi browser tab close 2`
-- `SkyKoi browser open https://example.com`
-- `SkyKoi browser focus abcd1234`
-- `SkyKoi browser close abcd1234`
+- `SKYKOI browser status`
+- `SKYKOI browser start`
+- `SKYKOI browser stop`
+- `SKYKOI browser tabs`
+- `SKYKOI browser tab`
+- `SKYKOI browser tab new`
+- `SKYKOI browser tab select 2`
+- `SKYKOI browser tab close 2`
+- `SKYKOI browser open https://example.com`
+- `SKYKOI browser focus abcd1234`
+- `SKYKOI browser close abcd1234`
 
 Inspection:
 
-- `SkyKoi browser screenshot`
-- `SkyKoi browser screenshot --full-page`
-- `SkyKoi browser screenshot --ref 12`
-- `SkyKoi browser screenshot --ref e12`
-- `SkyKoi browser snapshot`
-- `SkyKoi browser snapshot --format aria --limit 200`
-- `SkyKoi browser snapshot --interactive --compact --depth 6`
-- `SkyKoi browser snapshot --efficient`
-- `SkyKoi browser snapshot --labels`
-- `SkyKoi browser snapshot --selector "#main" --interactive`
-- `SkyKoi browser snapshot --frame "iframe#main" --interactive`
-- `SkyKoi browser console --level error`
-- `SkyKoi browser errors --clear`
-- `SkyKoi browser requests --filter api --clear`
-- `SkyKoi browser pdf`
-- `SkyKoi browser responsebody "**/api" --max-chars 5000`
+- `SKYKOI browser screenshot`
+- `SKYKOI browser screenshot --full-page`
+- `SKYKOI browser screenshot --ref 12`
+- `SKYKOI browser screenshot --ref e12`
+- `SKYKOI browser snapshot`
+- `SKYKOI browser snapshot --format aria --limit 200`
+- `SKYKOI browser snapshot --interactive --compact --depth 6`
+- `SKYKOI browser snapshot --efficient`
+- `SKYKOI browser snapshot --labels`
+- `SKYKOI browser snapshot --selector "#main" --interactive`
+- `SKYKOI browser snapshot --frame "iframe#main" --interactive`
+- `SKYKOI browser console --level error`
+- `SKYKOI browser errors --clear`
+- `SKYKOI browser requests --filter api --clear`
+- `SKYKOI browser pdf`
+- `SKYKOI browser responsebody "**/api" --max-chars 5000`
 
 Actions:
 
-- `SkyKoi browser navigate https://example.com`
-- `SkyKoi browser resize 1280 720`
-- `SkyKoi browser click 12 --double`
-- `SkyKoi browser click e12 --double`
-- `SkyKoi browser type 23 "hello" --submit`
-- `SkyKoi browser press Enter`
-- `SkyKoi browser hover 44`
-- `SkyKoi browser scrollintoview e12`
-- `SkyKoi browser drag 10 11`
-- `SkyKoi browser select 9 OptionA OptionB`
-- `SkyKoi browser download e12 /tmp/report.pdf`
-- `SkyKoi browser waitfordownload /tmp/report.pdf`
-- `SkyKoi browser upload /tmp/file.pdf`
-- `SkyKoi browser fill --fields '[{"ref":"1","type":"text","value":"Ada"}]'`
-- `SkyKoi browser dialog --accept`
-- `SkyKoi browser wait --text "Done"`
-- `SkyKoi browser wait "#main" --url "**/dash" --load networkidle --fn "window.ready===true"`
-- `SkyKoi browser evaluate --fn '(el) => el.textContent' --ref 7`
-- `SkyKoi browser highlight e12`
-- `SkyKoi browser trace start`
-- `SkyKoi browser trace stop`
+- `SKYKOI browser navigate https://example.com`
+- `SKYKOI browser resize 1280 720`
+- `SKYKOI browser click 12 --double`
+- `SKYKOI browser click e12 --double`
+- `SKYKOI browser type 23 "hello" --submit`
+- `SKYKOI browser press Enter`
+- `SKYKOI browser hover 44`
+- `SKYKOI browser scrollintoview e12`
+- `SKYKOI browser drag 10 11`
+- `SKYKOI browser select 9 OptionA OptionB`
+- `SKYKOI browser download e12 /tmp/report.pdf`
+- `SKYKOI browser waitfordownload /tmp/report.pdf`
+- `SKYKOI browser upload /tmp/file.pdf`
+- `SKYKOI browser fill --fields '[{"ref":"1","type":"text","value":"Ada"}]'`
+- `SKYKOI browser dialog --accept`
+- `SKYKOI browser wait --text "Done"`
+- `SKYKOI browser wait "#main" --url "**/dash" --load networkidle --fn "window.ready===true"`
+- `SKYKOI browser evaluate --fn '(el) => el.textContent' --ref 7`
+- `SKYKOI browser highlight e12`
+- `SKYKOI browser trace start`
+- `SKYKOI browser trace stop`
 
 State:
 
-- `SkyKoi browser cookies`
-- `SkyKoi browser cookies set session abc123 --url "https://example.com"`
-- `SkyKoi browser cookies clear`
-- `SkyKoi browser storage local get`
-- `SkyKoi browser storage local set theme dark`
-- `SkyKoi browser storage session clear`
-- `SkyKoi browser set offline on`
-- `SkyKoi browser set headers --json '{"X-Debug":"1"}'`
-- `SkyKoi browser set credentials user pass`
-- `SkyKoi browser set credentials --clear`
-- `SkyKoi browser set geo 37.7749 -122.4194 --origin "https://example.com"`
-- `SkyKoi browser set geo --clear`
-- `SkyKoi browser set media dark`
-- `SkyKoi browser set timezone America/New_York`
-- `SkyKoi browser set locale en-US`
-- `SkyKoi browser set device "iPhone 14"`
+- `SKYKOI browser cookies`
+- `SKYKOI browser cookies set session abc123 --url "https://example.com"`
+- `SKYKOI browser cookies clear`
+- `SKYKOI browser storage local get`
+- `SKYKOI browser storage local set theme dark`
+- `SKYKOI browser storage session clear`
+- `SKYKOI browser set offline on`
+- `SKYKOI browser set headers --json '{"X-Debug":"1"}'`
+- `SKYKOI browser set credentials user pass`
+- `SKYKOI browser set credentials --clear`
+- `SKYKOI browser set geo 37.7749 -122.4194 --origin "https://example.com"`
+- `SKYKOI browser set geo --clear`
+- `SKYKOI browser set media dark`
+- `SKYKOI browser set timezone America/New_York`
+- `SKYKOI browser set locale en-US`
+- `SKYKOI browser set device "iPhone 14"`
 
 Notes:
 
@@ -443,7 +443,7 @@ Notes:
   - `--format ai` (default when Playwright is installed): returns an AI snapshot with numeric refs (`aria-ref="<n>"`).
   - `--format aria`: returns the accessibility tree (no refs; inspection only).
   - `--efficient` (or `--mode efficient`): compact role snapshot preset (interactive + compact + depth + lower maxChars).
-  - Config default (tool/CLI only): set `browser.snapshotDefaults.mode: "efficient"` to use efficient snapshots when the caller does not pass a mode (see [Gateway configuration](/gateway/configuration#browser-SkyKoi-managed-browser)).
+  - Config default (tool/CLI only): set `browser.snapshotDefaults.mode: "efficient"` to use efficient snapshots when the caller does not pass a mode (see [Gateway configuration](/gateway/configuration#browser-SKYKOI-managed-browser)).
   - Role snapshot options (`--interactive`, `--compact`, `--depth`, `--selector`) force a role-based snapshot with refs like `ref=e12`.
   - `--frame "<iframe selector>"` scopes role snapshots to an iframe (pairs with role refs like `e12`).
   - `--interactive` outputs a flat, easy-to-pick list of interactive elements (best for driving actions).
@@ -453,16 +453,16 @@ Notes:
 
 ## Snapshots and refs
 
-SkyKoi supports two “snapshot” styles:
+SKYKOI supports two “snapshot” styles:
 
-- **AI snapshot (numeric refs)**: `SkyKoi browser snapshot` (default; `--format ai`)
+- **AI snapshot (numeric refs)**: `SKYKOI browser snapshot` (default; `--format ai`)
   - Output: a text snapshot that includes numeric refs.
-  - Actions: `SkyKoi browser click 12`, `SkyKoi browser type 23 "hello"`.
+  - Actions: `SKYKOI browser click 12`, `SKYKOI browser type 23 "hello"`.
   - Internally, the ref is resolved via Playwright’s `aria-ref`.
 
-- **Role snapshot (role refs like `e12`)**: `SkyKoi browser snapshot --interactive` (or `--compact`, `--depth`, `--selector`, `--frame`)
+- **Role snapshot (role refs like `e12`)**: `SKYKOI browser snapshot --interactive` (or `--compact`, `--depth`, `--selector`, `--frame`)
   - Output: a role-based list/tree with `[ref=e12]` (and optional `[nth=1]`).
-  - Actions: `SkyKoi browser click e12`, `SkyKoi browser highlight e12`.
+  - Actions: `SKYKOI browser click e12`, `SKYKOI browser highlight e12`.
   - Internally, the ref is resolved via `getByRole(...)` (plus `nth()` for duplicates).
   - Add `--labels` to include a viewport screenshot with overlayed `e12` labels.
 
@@ -476,18 +476,18 @@ Ref behavior:
 You can wait on more than just time/text:
 
 - Wait for URL (globs supported by Playwright):
-  - `SkyKoi browser wait --url "**/dash"`
+  - `SKYKOI browser wait --url "**/dash"`
 - Wait for load state:
-  - `SkyKoi browser wait --load networkidle`
+  - `SKYKOI browser wait --load networkidle`
 - Wait for a JS predicate:
-  - `SkyKoi browser wait --fn "window.ready===true"`
+  - `SKYKOI browser wait --fn "window.ready===true"`
 - Wait for a selector to become visible:
-  - `SkyKoi browser wait "#main"`
+  - `SKYKOI browser wait "#main"`
 
 These can be combined:
 
 ```bash
-SkyKoi browser wait "#main" \
+SKYKOI browser wait "#main" \
   --url "**/dash" \
   --load networkidle \
   --fn "window.ready===true" \
@@ -498,16 +498,16 @@ SkyKoi browser wait "#main" \
 
 When an action fails (e.g. “not visible”, “strict mode violation”, “covered”):
 
-1. `SkyKoi browser snapshot --interactive`
+1. `SKYKOI browser snapshot --interactive`
 2. Use `click <ref>` / `type <ref>` (prefer role refs in interactive mode)
-3. If it still fails: `SkyKoi browser highlight <ref>` to see what Playwright is targeting
+3. If it still fails: `SKYKOI browser highlight <ref>` to see what Playwright is targeting
 4. If the page behaves oddly:
-   - `SkyKoi browser errors --clear`
-   - `SkyKoi browser requests --filter api --clear`
+   - `SKYKOI browser errors --clear`
+   - `SKYKOI browser requests --filter api --clear`
 5. For deep debugging: record a trace:
-   - `SkyKoi browser trace start`
+   - `SKYKOI browser trace start`
    - reproduce the issue
-   - `SkyKoi browser trace stop` (prints `TRACE:<path>`)
+   - `SKYKOI browser trace stop` (prints `TRACE:<path>`)
 
 ## JSON output
 
@@ -516,10 +516,10 @@ When an action fails (e.g. “not visible”, “strict mode violation”, “co
 Examples:
 
 ```bash
-SkyKoi browser status --json
-SkyKoi browser snapshot --interactive --json
-SkyKoi browser requests --filter api --json
-SkyKoi browser cookies --json
+SKYKOI browser status --json
+SKYKOI browser snapshot --interactive --json
+SKYKOI browser requests --filter api --json
+SKYKOI browser cookies --json
 ```
 
 Role snapshots in JSON include `refs` plus a small `stats` block (lines/chars/refs/interactive) so tools can reason about payload size and density.
@@ -542,8 +542,8 @@ These are useful for “make the site behave like X” workflows:
 
 ## Security & privacy
 
-- The SkyKoi browser profile may contain logged-in sessions; treat it as sensitive.
-- `browser act kind=evaluate` / `SkyKoi browser evaluate` and `wait --fn`
+- The SKYKOI browser profile may contain logged-in sessions; treat it as sensitive.
+- `browser act kind=evaluate` / `SKYKOI browser evaluate` and `wait --fn`
   execute arbitrary JavaScript in the page context. Prompt injection can steer
   this. Disable it with `browser.evaluateEnabled=false` if you do not need it.
 - For logins and anti-bot notes (X/Twitter, etc.), see [Browser login + X/Twitter posting](/tools/browser-login).
@@ -567,7 +567,7 @@ How it maps:
 - `browser act` uses the snapshot `ref` IDs to click/type/drag/select.
 - `browser screenshot` captures pixels (full page or element).
 - `browser` accepts:
-  - `profile` to choose a named browser profile (SkyKoi, chrome, or remote CDP).
+  - `profile` to choose a named browser profile (SKYKOI, chrome, or remote CDP).
   - `target` (`sandbox` | `host` | `node`) to select where the browser lives.
   - In sandboxed sessions, `target: "host"` requires `agents.defaults.sandbox.browser.allowHostControl=true`.
   - If `target` is omitted: sandboxed sessions default to `sandbox`, non-sandbox sessions default to `host`.