diff --git a/.gitleaks.toml b/.gitleaks.toml
index b6ceba7..3262059 100644
--- a/.gitleaks.toml
+++ b/.gitleaks.toml
@@ -1,4 +1,4 @@
-title = "Zombie Docs Gitleaks Config"
+title = "Agent Docs Gitleaks Config"
 
 [allowlist]
   description = "Allow placeholder tokens used in documentation examples"
diff --git a/.mlc-config.json b/.mlc-config.json
index 3b6b461..fec8ad1 100644
--- a/.mlc-config.json
+++ b/.mlc-config.json
@@ -2,8 +2,8 @@
   "ignorePatterns": [
     { "pattern": "^/" },
     { "pattern": "^https://discord.gg" },
-    { "pattern": "^https://usezombie.com" },
-    { "pattern": "^https://app.usezombie.com" },
+    { "pattern": "^https://agentsfleet.net" },
+    { "pattern": "^https://app.agentsfleet.net" },
     { "pattern": "^mailto:" }
   ],
   "retryOn429": true,
diff --git a/AGENTS.md b/AGENTS.md
index 56e4d9f..c25be30 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -2,7 +2,7 @@
 
 ## About this project
 
-- This is the usezombie documentation site built on [Mintlify](https://mintlify.com)
+- This is the agentsfleet documentation site built on [Mintlify](https://mintlify.com)
 - Pages are MDX files with YAML frontmatter
 - Configuration lives in `docs.json`
 - Run `mint dev` to preview locally on port 3000
@@ -12,7 +12,7 @@
 
 ## Terminology
 
-- Use "agent" (lowercase) for the product noun — the always-on agent process. "zombie" is legacy terminology; do not use it in new prose (brand/code tokens like `usezombie`, `zombiectl`, `zombied`, `zmb_`, `zombie_id`, and `/zombies/` paths stay)
+- Use "agent" (lowercase) for the product noun — the always-on agent process. "agent" is legacy terminology; do not use it in new prose (brand/code tokens like `agentsfleet`, `agentsfleet`, `agentsfleetd`, `zmb_`, `agent_id`, and `/agents/` paths stay)
 - Use "workspace" not "project"
 - Use "skill" for a named capability an agent can invoke (agentmail, slack, github, ...)
 - Use "trigger" for how an agent receives events (today: webhook)
@@ -25,9 +25,9 @@
 - Use "runner" for the execution-plane process that sandboxes and runs an agent — not "executor"
 - Use "agent" not "bot" or "AI"
 - Use "PR" not "pull request" (except on first mention per page)
-- Use `zombiectl` in code formatting when referring to CLI commands
-- Use `zombied` in code formatting when referring to server processes
-- Use "Dashboard" (capitalized in headings, lowercase "dashboard" in body prose) for the web app at `app.usezombie.com`. The earlier aspirational name for this surface is retired — do not reintroduce it.
+- Use `agentsfleet` in code formatting when referring to CLI commands
+- Use `agentsfleetd` in code formatting when referring to server processes
+- Use "Dashboard" (capitalized in headings, lowercase "dashboard" in body prose) for the web app at `app.agentsfleet.net`. The earlier aspirational name for this surface is retired — do not reintroduce it.
 
 Forbidden terminology: `spec`, `stage`, `gate loop`, `scorecard`. These refer to a v1 product surface that has been removed. Do not introduce them into new pages. (`run`/`runs` are now the v2 execution unit — see Terminology above.)
 
@@ -51,10 +51,10 @@ Forbidden terminology: `spec`, `stage`, `gate loop`, `scorecard`. These refer to
 
 ## When closing out a feature PR in the lead repo (companion docs flow)
 
-A landing PR in any lead repo (`usezombie`, `zombiectl`, the website, the app) almost always drifts the docs site. Before the lead-repo PR flips ready-for-review:
+A landing PR in any lead repo (`agentsfleet`, `agentsfleet`, the website, the app) almost always drifts the docs site. Before the lead-repo PR flips ready-for-review:
 
 1. **Review the lead PR's changed files.** Every public-surface change is a candidate doc edit — HTTP request/response shape, CLI subcommand or flag, frontmatter schema, error code, env var, default value, response field, pricing / billing copy, dashboard flow.
-2. **Identify the `.mdx` pages that drift.** Grep this docs repo for the old field name, old YAML shape, old subcommand, old copy. Common candidates: `quickstart.mdx`, `cli/*.mdx`, `zombies/*.mdx` (especially `authoring.mdx`, `webhooks.mdx`, `install.mdx`, `running.mdx`), `api-reference/*.mdx`, `billing/*.mdx`, `snippets/rates.mdx`, `concepts/*.mdx`.
+2. **Identify the `.mdx` pages that drift.** Grep this docs repo for the old field name, old YAML shape, old subcommand, old copy. Common candidates: `quickstart.mdx`, `cli/*.mdx`, `agents/*.mdx` (especially `authoring.mdx`, `webhooks.mdx`, `install.mdx`, `running.mdx`), `api-reference/*.mdx`, `billing/*.mdx`, `snippets/rates.mdx`, `concepts/*.mdx`.
 3. **Update the relevant pages.** Fix examples, tables, and prose. Preserve load-bearing detail (`UZ-XXX-NNN` error codes, endpoint paths, env var names, schema column names, money amounts). Don't rewrite past entries; only touch pages that no longer describe what shipped.
 4. **Add a `changelog.mdx` `<Update>` block** at the top, after the leading `<Tip>`. Section order is fixed: Upgrading → What's new → API reference → Bug fixes → CLI. Voice rules: lead with the change, no marketing words, no milestone IDs / spec filenames / `RULE XXX` references. Date label `MMM DD, YYYY`, no semver prefix. Two entries on the same date get distinct titles (no disambiguator suffix needed) or a merged block.
 5. **All four steps land on a dedicated docs-repo branch** — `chore/m{N}-{slug}-changelog` off `main`. Do not commit docs changes on the lead-repo feature branch (it's a separate repository) and do not commit on `main` directly. Open the docs PR alongside the lead PR so reviewers can cross-link the two.
@@ -63,10 +63,10 @@ The rule applies to every milestone PR, not just trigger/CLI ones — schema mig
 
 ## Design system colors
 
-{/* SYNC SOURCE: ~/Projects/usezombie/ui/packages/design-system/src/tokens.css
+{/* SYNC SOURCE: ~/Projects/agentsfleet/ui/packages/design-system/src/tokens.css
      When touching colors in this repo (docs.json, logos, custom CSS), always
      verify values against the canonical design-system tokens first.
-     Run: grep -E "^  --(pulse|bg|surface|text|success|warn|error|info|evidence)" ~/Projects/usezombie/ui/packages/design-system/src/tokens.css
+     Run: grep -E "^  --(pulse|bg|surface|text|success|warn|error|info|evidence)" ~/Projects/agentsfleet/ui/packages/design-system/src/tokens.css
 
      Heritage `--z-orange` palette retired in M64 (Operational Restraint
      rollout). Anything still referencing `#d96b2b` / `--z-orange` is stale. */}
diff --git a/Makefile b/Makefile
index 7479127..ac517ff 100644
--- a/Makefile
+++ b/Makefile
@@ -2,7 +2,7 @@ SHELL := /bin/bash
 
 .PHONY: dev lint test _lint-openapi-drift
 
-OPENAPI_URL ?= https://raw.githubusercontent.com/usezombie/usezombie/main/public/openapi.json
+OPENAPI_URL ?= https://raw.githubusercontent.com/agentsfleet/agentsfleet/main/public/openapi.json
 
 dev:
 	npx mintlify dev
diff --git a/README.md b/README.md
index c8d030e..608c8a9 100644
--- a/README.md
+++ b/README.md
@@ -3,7 +3,7 @@
 <picture>
   <source media="(prefers-color-scheme: dark)" srcset="logo/dark.svg" />
   <source media="(prefers-color-scheme: light)" srcset="logo/light.svg" />
-  <img src="logo/dark.svg" width="200" alt="usezombie" />
+  <img src="logo/dark.svg" width="200" alt="agentsfleet" />
 </picture>
 
 **Your deploy failed. The agent already knows why.**
@@ -12,8 +12,8 @@ A long-lived runtime that owns one operational outcome end to end.
 Wakes on your events. Runs against a durable, replayable log.
 Posts evidenced answers — never chats.
 
-[![Docs](https://img.shields.io/badge/usezombie-Docs-5EEAD4?style=for-the-badge)](https://docs.usezombie.com)
-[![Get early access](https://img.shields.io/badge/usezombie-Get_early_access-5EEAD4?style=for-the-badge)](https://usezombie.com)
+[![Docs](https://img.shields.io/badge/agentsfleet-Docs-5EEAD4?style=for-the-badge)](https://docs.agentsfleet.net)
+[![Get early access](https://img.shields.io/badge/agentsfleet-Get_early_access-5EEAD4?style=for-the-badge)](https://agentsfleet.net)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg?style=for-the-badge)](https://opensource.org/licenses/MIT)
 
 </div>
@@ -37,4 +37,4 @@ Changes pushed to the default branch are deployed automatically via the [Mintlif
 
 ## License
 
-MIT — Copyright (c) 2026 usezombie
+MIT — Copyright (c) 2026 agentsfleet
diff --git a/zombies/authoring.mdx b/agents/authoring.mdx
similarity index 80%
rename from zombies/authoring.mdx
rename to agents/authoring.mdx
index 3553dad..420b999 100644
--- a/zombies/authoring.mdx
+++ b/agents/authoring.mdx
@@ -13,7 +13,7 @@ my-agent/
 └── TRIGGER.md    # machine-readable config + deployment metadata
 ```
 
-`zombiectl install <template>` scaffolds both. This page is the reference for authoring your own.
+`agentsfleet install <template>` scaffolds both. This page is the reference for authoring your own.
 
 ## `SKILL.md` — agent instructions
 
@@ -28,7 +28,7 @@ description: Diagnoses platform health from fly.io and upstash, posts to Slack.
 version: 0.1.0                     # required, semver
 when_to_use: ...                   # optional
 tags: [platform-ops, diagnostics]  # optional
-author: usezombie                  # optional
+author: agentsfleet                  # optional
 model: claude-sonnet-4-6           # optional, hint
 ---
 ```
@@ -87,7 +87,7 @@ always frame as "leading hypothesis" and let the human decide.
 ---
 name: platform-ops-agent   # top level — must match SKILL.md `name:`
 
-x-usezombie:                # all runtime config nests under this key
+x-agentsfleet:                # all runtime config nests under this key
   triggers:                 # array, 1–8 entries; one agent can wake on many sources
     - type: api             # operator chats via /steer; events arrive as event_type: chat
   tools:
@@ -120,22 +120,22 @@ x-usezombie:                # all runtime config nests under this key
 | Field | Required | Purpose |
 |---|---|---|
 | `name` | yes | Identity. Must equal `SKILL.md` `name:`. |
-| `x-usezombie` | yes | Runtime config block. Required subkeys below. |
+| `x-agentsfleet` | yes | Runtime config block. Required subkeys below. |
 
-Top-level keys other than `name`/`x-*` are accepted silently. Runtime keys (`tools`, `credentials`, `network`, `budget`, `trigger`) **must not** appear at the top level — they belong inside `x-usezombie:`.
+Top-level keys other than `name`/`x-*` are accepted silently. Runtime keys (`tools`, `credentials`, `network`, `budget`, `trigger`) **must not** appear at the top level — they belong inside `x-agentsfleet:`.
 
-### `x-usezombie:` subkeys
+### `x-agentsfleet:` subkeys
 
 Validation under this block is rigid: an unknown subkey is rejected with a typo hint. All listed subkeys are required unless marked optional.
 
 | Subkey | Required | Purpose |
 |---|---|---|
-| `triggers[]` | yes | Array of 1–8 trigger entries. The singular `trigger:` shape is rejected at install (`ERR_ZOMBIE_INVALID_CONFIG: use "triggers:" (array)`). Entries are unique on the `(type, source)` tuple; at most one `cron` entry. |
+| `triggers[]` | yes | Array of 1–8 trigger entries. The singular `trigger:` shape is rejected at install (`ERR_AGENTSFLEET_INVALID_CONFIG: use "triggers:" (array)`). Entries are unique on the `(type, source)` tuple; at most one `cron` entry. |
 | `triggers[].type` | yes | One of `webhook` \| `cron` \| `api`. See the table below. |
-| `triggers[].source` | per type | Required for `webhook`. Carries the upstream label (e.g. `github`, `slack`, `linear`) and selects the per-trigger URL `…/v1/webhooks/{zombie_id}/{source}` — see [Webhooks](/zombies/webhooks). |
+| `triggers[].source` | per type | Required for `webhook`. Carries the upstream label (e.g. `github`, `slack`, `linear`) and selects the per-trigger URL `…/v1/webhooks/{agent_id}/{source}` — see [Webhooks](/agents/webhooks). |
 | `triggers[].events` | optional | Per-webhook event whitelist (1–16 entries, ≤64 chars each). Omit to accept every event the source delivers. |
 | `triggers[].signature.secret_ref` | optional | Vault key whose value verifies webhook signatures (first-class providers). |
-| `tools` | yes | Non-empty list of tool names from the [Tools catalogue](/zombies/tools). |
+| `tools` | yes | Non-empty list of tool names from the [Tools catalogue](/agents/tools). |
 | `credentials` | optional | Vault key names the agent reads at event time. |
 | `network.allow` | yes | Outbound hostname allowlist enforced by the sandbox. |
 | `budget.daily_dollars` | yes | Rolling 24-hour dollar ceiling. |
@@ -145,11 +145,11 @@ Validation under this block is rigid: an unknown subkey is rejected with a typo
 
 | YAML value | Wakes from | Use when | Companion fields |
 |---|---|---|---|
-| `webhook` | An external HTTP `POST` to `https://api.usezombie.com/v1/webhooks/{zombie_id}/{source}` with a signed body. | Most production agents — anything driven by a third-party event (GitHub, Slack, Linear, Jira, etc.). | `source` (label, also selects the URL) + `events` (optional whitelist) + `signature` (HMAC config). See [Webhooks](/zombies/webhooks). |
+| `webhook` | An external HTTP `POST` to `https://api.agentsfleet.net/v1/webhooks/{agent_id}/{source}` with a signed body. | Most production agents — anything driven by a third-party event (GitHub, Slack, Linear, Jira, etc.). | `source` (label, also selects the URL) + `events` (optional whitelist) + `signature` (HMAC config). See [Webhooks](/agents/webhooks). |
 | `cron` | A self-scheduled timer the agent sets via the `cron_add` tool. | Periodic health checks, drift sweeps, scheduled cleanups. | None at the trigger level — schedules live inside the reasoning loop. At most one `cron` entry per agent. |
-| `api` | A `zombiectl steer` invocation or a `POST /v1/.../zombies/{id}/messages` API call. | Steerable, operator-driven agents — manual investigation, on-demand workflows, the install-time smoke test. | None. |
+| `api` | A `agentsfleet steer` invocation or a `POST /v1/.../agents/{id}/messages` API call. | Steerable, operator-driven agents — manual investigation, on-demand workflows, the install-time smoke test. | None. |
 
-An agent can declare up to eight triggers and wake on any of them — e.g. one webhook from GitHub plus a cron sweep every 30 minutes. Any agent can also be steered via `zombiectl steer` regardless of declared triggers — steer always works. The `api` type is for agents whose *primary* surface is steer (no inbound webhook).
+An agent can declare up to eight triggers and wake on any of them — e.g. one webhook from GitHub plus a cron sweep every 30 minutes. Any agent can also be steered via `agentsfleet steer` regardless of declared triggers — steer always works. The `api` type is for agents whose *primary* surface is steer (no inbound webhook).
 
 <Note>**Long-run continuations are not a trigger type.** When a run exhausts its context, the runtime re-enqueues the same event with `actor=continuation:<original_actor>` automatically. You don't declare this in `TRIGGER.md`; it happens regardless of which trigger type woke the original run. See [Context lifecycle](/concepts/context-lifecycle).</Note>
 
@@ -157,11 +157,11 @@ An agent can declare up to eight triggers and wake on any of them — e.g. one w
 
 The `tools:` list is the explicit allowlist of tools the agent may invoke. A compromised or jailbroken agent cannot reach outside this list.
 
-23 tools are user-callable today, grouped by category — network (`http_request`, `web_search`, `web_fetch`), memory (`memory_store`/`recall`/`list`/`forget`), cron (`cron_add`/`list`/`remove`/`update`/`run`/`runs`), agent orchestration (`delegate`, `spawn`, `schedule`), browser, git, file edits, and stateless utilities. **See [Tools catalogue](/zombies/tools) for every tool with its purpose and use cases.**
+23 tools are user-callable today, grouped by category — network (`http_request`, `web_search`, `web_fetch`), memory (`memory_store`/`recall`/`list`/`forget`), cron (`cron_add`/`list`/`remove`/`update`/`run`/`runs`), agent orchestration (`delegate`, `spawn`, `schedule`), browser, git, file edits, and stateless utilities. **See [Tools catalogue](/agents/tools) for every tool with its purpose and use cases.**
 
 ### Credentials
 
-Each entry under `credentials:` is a **bare vault key name** referencing a JSON-shaped secret in the workspace vault (e.g. `github` carrying `{api_token, webhook_secret}`, `slack` carrying `{bot_token}`). Names like `github`, `slack`, `linear`, `jira` are credential references — **not** tool names. The tool bridge resolves the named credential at `http_request` time and substitutes its fields into outbound calls; the agent sees the response, never the raw secret. Add and rotate via [Credentials](/zombies/credentials).
+Each entry under `credentials:` is a **bare vault key name** referencing a JSON-shaped secret in the workspace vault (e.g. `github` carrying `{api_token, webhook_secret}`, `slack` carrying `{bot_token}`). Names like `github`, `slack`, `linear`, `jira` are credential references — **not** tool names. The tool bridge resolves the named credential at `http_request` time and substitutes its fields into outbound calls; the agent sees the response, never the raw secret. Add and rotate via [Credentials](/agents/credentials).
 
 ### Network allowlist
 
@@ -180,17 +180,17 @@ A breach terminates the in-flight event cleanly and records a `budget_breach` en
 
 | Symptom | Cause | Fix |
 |---|---|---|
-| `RuntimeKeysOutsideBlock` at install | `tools:`, `credentials:`, etc. at the top of TRIGGER.md | Indent them under `x-usezombie:`. |
-| `UnknownRuntimeKey` at install | Typo in a runtime subkey (e.g. `crendentials:` instead of `credentials:`) | Fix the spelling, or remove the key. Validation under `x-usezombie:` is strict. |
+| `RuntimeKeysOutsideBlock` at install | `tools:`, `credentials:`, etc. at the top of TRIGGER.md | Indent them under `x-agentsfleet:`. |
+| `UnknownRuntimeKey` at install | Typo in a runtime subkey (e.g. `crendentials:` instead of `credentials:`) | Fix the spelling, or remove the key. Validation under `x-agentsfleet:` is strict. |
 | `name_mismatch` at install | SKILL.md and TRIGGER.md disagree on `name:` | One identity per bundle. Make both top-level `name:` values equal. |
 | `MissingRequiredField` for SKILL.md | `name`, `description`, or `version` missing from SKILL.md frontmatter | All three are required at the top level. |
 
 ## Validation
 
-`zombiectl install --from <dir>` reads both files and posts them to the server, which runs the same parser the runtime uses. Errors are returned with the field at fault.
+`agentsfleet install --from <dir>` reads both files and posts them to the server, which runs the same parser the runtime uses. Errors are returned with the field at fault.
 
 ```bash
-zombiectl install --from ./my-agent
+agentsfleet install --from ./my-agent
 ```
 
 ```
@@ -202,10 +202,10 @@ zombiectl install --from ./my-agent
 ## Next
 
 <CardGroup cols={2}>
-  <Card title="Bundled templates" icon="layer-group" href="/zombies/templates">
+  <Card title="Bundled templates" icon="layer-group" href="/agents/templates">
     See the anatomy of the flagship `platform-ops` sample.
   </Card>
-  <Card title="Webhooks" icon="webhook" href="/zombies/webhooks">
+  <Card title="Webhooks" icon="webhook" href="/agents/webhooks">
     Authentication modes and approval gates in depth.
   </Card>
 </CardGroup>
diff --git a/zombies/credentials.mdx b/agents/credentials.mdx
similarity index 77%
rename from zombies/credentials.mdx
rename to agents/credentials.mdx
index 383b9fc..13b9900 100644
--- a/zombies/credentials.mdx
+++ b/agents/credentials.mdx
@@ -11,12 +11,12 @@ The **workspace vault** is the answer. Secrets live in a dedicated, encrypted va
 
 ## Adding a credential
 
-`zombiectl credential add <name> --data=@-` stores a JSON-shaped secret in the current workspace's vault. The name is what you reference from `TRIGGER.md`.
+`agentsfleet credential add <name> --data=@-` stores a JSON-shaped secret in the current workspace's vault. The name is what you reference from `TRIGGER.md`.
 
 Always pipe the JSON on stdin (`--data=@-`) so secrets never appear in shell history or process argv:
 
 ```bash
-zombiectl credential add github --data=@- <<'JSON'
+agentsfleet credential add github --data=@- <<'JSON'
 {
   "api_token": "ghp_...",
   "webhook_secret": "<32-byte hex>"
@@ -24,13 +24,13 @@ zombiectl credential add github --data=@- <<'JSON'
 JSON
 ```
 
-If you keep secrets in 1Password, use `op inject` to resolve them at the moment of the call — the rendered JSON exists only on the in-memory pipe between `op` and `zombiectl`:
+If you keep secrets in 1Password, use `op inject` to resolve them at the moment of the call — the rendered JSON exists only on the in-memory pipe between `op` and `agentsfleet`:
 
 ```bash
-cat <<'JSON' | op inject | zombiectl credential add github --data=@-
+cat <<'JSON' | op inject | agentsfleet credential add github --data=@-
 {
-  "api_token":      "{{ op://Personal/usezombie-github/api_token }}",
-  "webhook_secret": "{{ op://Personal/usezombie-github/webhook_secret }}"
+  "api_token":      "{{ op://Personal/agentsfleet-github/api_token }}",
+  "webhook_secret": "{{ op://Personal/agentsfleet-github/webhook_secret }}"
 }
 JSON
 ```
@@ -51,10 +51,10 @@ Exit codes:
 
 ## Listing credentials
 
-`zombiectl credential list` returns the names and creation timestamps of every credential in the current workspace. **Values are never returned.** This is by design — once stored, a secret is only ever used by the firewall.
+`agentsfleet credential list` returns the names and creation timestamps of every credential in the current workspace. **Values are never returned.** This is by design — once stored, a secret is only ever used by the firewall.
 
 ```bash
-zombiectl credential list
+agentsfleet credential list
 ```
 
 ```
@@ -73,7 +73,7 @@ An agent declares the credentials it needs as a **list of bare key names** in it
 ---
 name: platform-ops-agent
 
-x-usezombie:
+x-agentsfleet:
   triggers:
     - type: webhook
       source: github
@@ -90,14 +90,14 @@ x-usezombie:
 
 At event delivery time the tool bridge fetches each named secret from the vault and substitutes it into the outbound HTTP call. The agent never sees the resolved value.
 
-If an agent references a credential that is not present in the vault when `zombiectl install --from <path>` is called, install fails with a clear error listing the missing names.
+If an agent references a credential that is not present in the vault when `agentsfleet install --from <path>` is called, install fails with a clear error listing the missing names.
 
 ## Rotation
 
 Rotating a credential is a single command — no re-install is needed. The next event handled by any agent using that credential picks up the new value.
 
 ```bash
-zombiectl credential add github --data=@- --force <<'JSON'
+agentsfleet credential add github --data=@- --force <<'JSON'
 { "api_token": "ghp_...new...", "webhook_secret": "<new>" }
 JSON
 ```
@@ -107,10 +107,10 @@ JSON
 ## Deletion
 
 ```bash
-zombiectl credential delete <name>
+agentsfleet credential delete <name>
 ```
 
-`zombiectl credential show <name>` prints metadata (creation timestamp, last-rotated) but **never the value**. The vault is one-way: write at the boundary, read only by the firewall.
+`agentsfleet credential show <name>` prints metadata (creation timestamp, last-rotated) but **never the value**. The vault is one-way: write at the boundary, read only by the firewall.
 
 ## What the agent can and cannot see
 
diff --git a/agents/install.mdx b/agents/install.mdx
new file mode 100644
index 0000000..890bbf2
--- /dev/null
+++ b/agents/install.mdx
@@ -0,0 +1,53 @@
+---
+title: "Installing an agent"
+description: "What `agentsfleet install --from <path>` does and how to invoke it."
+---
+
+`agentsfleet install --from <path>` is how you bring an agent up. It reads `SKILL.md` and `TRIGGER.md` from the directory you point at, validates them, and uploads to your active workspace. **Install is the deploy** — there's no separate `up` step.
+
+```bash
+agentsfleet install --from ~/.config/agentsfleet/samples/platform-ops
+```
+
+```
+✓ platform-ops-agent is live.
+  Agent ID: 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71
+  Webhook URLs (register on the upstream provider):
+    github: https://api.agentsfleet.net/v1/webhooks/0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71/github
+```
+
+One URL is printed per declared `webhook` trigger in `TRIGGER.md`, keyed by `triggers[].source`. The host-agent install skill consumes this map and registers each URL on the upstream provider via the user's own `gh` (or equivalent) CLI — no paste-into-GitHub step. See [Quickstart](/quickstart) for the guided flow, or [Webhooks](/agents/webhooks) if you maintain the upstream hook by hand.
+
+Re-running against the same workspace is safe — running it twice has the same effect as running it once. Your edits to `SKILL.md` / `TRIGGER.md` replace the previous version on the next event.
+
+## Two ways to invoke
+
+Most users don't run `agentsfleet install --from` directly. They drive the install from a host agent (Claude Code, Amp, Codex CLI, OpenCode) via the `/agentsfleet-install-platform-ops` slash command. Add the skills with `npx skills add agentsfleet/skills`, which symlinks `/agentsfleet-*` into every supported host's skill directory it detects. Then invoke the slash command in your host agent:
+
+```
+/agentsfleet-install-platform-ops
+```
+
+<Tip>
+  **No global install?** `curl -fsSL https://agentsfleet.dev | bash` installs `agentsfleet` and the skill together in one command (requires Node — it runs npm under the hood). Run `curl -fsSL https://agentsfleet.dev` without `| bash` to read it first.
+</Tip>
+
+The slash command asks three gating questions (Slack channel, production branch glob, optional cron schedule), registers the webhook via your existing `gh` CLI, and prints a per-trigger registration summary at the end. See [Quickstart](/quickstart) for the full walkthrough.
+
+Power users and scripted setups call `agentsfleet install --from <path>` directly — the same flow as the slash command, minus the gating questions and the auto-registration.
+
+For the self-managed provider posture, see [`agentsfleet tenant provider`](/cli/agentsfleet#tenant-provider).
+
+## Exit codes
+
+| Code | Meaning |
+|---|---|
+| `0` | Installed (or updated). |
+| `1` | No workspace selected, or API error. |
+| `2` | Missing `--from`, invalid path, or schema rejection. |
+
+## See also
+
+- [Templates](/agents/templates) — the catalogue of pre-built agents you can install.
+- [Authoring an agent](/agents/authoring) — the `SKILL.md` and `TRIGGER.md` reference for writing your own.
+- [Starting, observing, and stopping](/agents/running) — what to do after install.
diff --git a/agents/overview.mdx b/agents/overview.mdx
new file mode 100644
index 0000000..740f66b
--- /dev/null
+++ b/agents/overview.mdx
@@ -0,0 +1,69 @@
+---
+title: "Agents"
+description: "What an agent is, the lifecycle it moves through, and how it relates to your workspace."
+---
+
+## Overview
+
+An **agent** is a preconfigured, always-on agent process in your workspace. You describe it once — its trigger, the skills it can use, the credentials it needs, the budget it is allowed to consume — and the platform keeps it alive, receiving events and invoking the agent, until you kill it.
+
+Everything in this section of the docs is about working with agents: how to install one from a template, how to start and stop it, how to attach credentials, how webhooks reach it, and how to author the `SKILL.md` and `TRIGGER.md` files that define its behavior.
+
+## Lifecycle
+
+An agent moves through five observable states.
+
+```mermaid
+flowchart LR
+    Install[agentsfleet install --from path] --> Alive[Alive<br/>webhook live]
+    Alive -->|event arrives| Processing[Processing<br/>agent reasoning]
+    Processing -->|run exits| Alive
+    Alive -->|agentsfleet stop| Stopped[Stopped<br/>paused]
+    Stopped -->|agentsfleet resume| Alive
+    Alive -->|agentsfleet kill| Killed[Killed<br/>terminal]
+    Stopped -->|agentsfleet kill| Killed
+    Killed -->|agentsfleet delete| Deleted([deleted — hard-removed])
+```
+
+1. **Alive.** `agentsfleet install --from <path>` reads the local `SKILL.md` + `TRIGGER.md`, validates the schema, uploads to your workspace, provisions the webhook URL, and starts the event loop. Install is the deploy — there is no separate `up` step.
+2. **Processing.** When a signed event arrives (webhook, cron, or steer), the platform opens a **run**: the agent reads the event, reasons, invokes the tools listed in `TRIGGER.md`, and produces a result. The activity stream is the durable record — replay any time with `agentsfleet logs <agent_id>` (or `events --actor 'webhook:*'` for filtered history).
+3. **Stopped.** `agentsfleet stop <agent_id>` halts the running session — new events stop dispatching, the in-flight run finishes cleanly. Reversible with `agentsfleet resume`. Use this for "pause while I debug upstream"; reach for `kill` only when you mean *terminal*.
+4. **Killed.** `agentsfleet kill <agent_id>` marks the agent terminal. The row, history, and webhook URL persist but no new events are processed. State is checkpointed; nothing on the event stream is lost. Re-install with the same `SKILL.md` produces a **new** `agent_id`.
+5. **Deleted.** `agentsfleet delete <agent_id>` hard-removes the agent. The row, its `agent_id`, and its webhook URL are gone — the webhook URL starts returning `UZ-WH-001` for any new POSTs. The activity-stream history is retained for the workspace's retention window per [Observability](/cli/agentsfleet#observability); replays after delete reference the prior `agent_id` as a historical record only. You must `kill` the agent before `delete` will accept it.
+
+You can inspect state at any time:
+
+```bash
+agentsfleet status                     # every agent in the active workspace
+agentsfleet logs 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71              # tail one agent's recent activity
+agentsfleet steer 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71 "morning health check"   # manual trigger
+```
+
+## Workspace scoping
+
+Every agent belongs to exactly one **workspace**. The workspace is the boundary for:
+
+- **Credentials** — the vault that agents read from when they invoke skills. See [Credentials](/agents/credentials).
+- **Access control** — teammates invited to a workspace can see, start, and kill its agents; they cannot see agents in other workspaces.
+- **Webhook namespace** — every agent in a workspace gets one unique URL per declared trigger under `https://api.agentsfleet.net/v1/webhooks/{agent_id}/{source}` (one entry per `triggers[].source` in `TRIGGER.md`).
+
+Billing is **not** workspace-scoped — every workspace draws on the same tenant-level billing. See [Billing](/billing/plans) for the model.
+
+`agentsfleet workspace add [name]` creates a new workspace and sets it as active. Switch between existing ones with `agentsfleet workspace use <id>` (run `agentsfleet workspace list` first to see the IDs). The dashboard's active-workspace selection is independent — switching there does not affect the CLI and vice versa.
+
+## What's next
+
+<CardGroup cols={2}>
+  <Card title="Install an agent" icon="download" href="/agents/install">
+    Scaffold an agent from a bundled template.
+  </Card>
+  <Card title="Start, stop, observe" icon="circle-play" href="/agents/running">
+    The `install`, `status`, `events`, `steer`, and `kill` commands.
+  </Card>
+  <Card title="Workspace credentials" icon="key" href="/agents/credentials">
+    Add secrets to the vault without the agent ever seeing them.
+  </Card>
+  <Card title="Authoring an agent" icon="file-code" href="/agents/authoring">
+    How `SKILL.md` and `TRIGGER.md` combine to define an agent.
+  </Card>
+</CardGroup>
diff --git a/zombies/running.mdx b/agents/running.mdx
similarity index 52%
rename from zombies/running.mdx
rename to agents/running.mdx
index 23b751e..755e390 100644
--- a/zombies/running.mdx
+++ b/agents/running.mdx
@@ -5,36 +5,36 @@ description: "The lifecycle commands — install, status, logs, events, steer, s
 
 ## Overview
 
-A small set of verbs cover the live lifecycle: `install --from <path>` brings an agent up, `status` shows what's running, `logs` (or `events` for filtered history) replays the activity stream, `steer` triggers a manual run, and `stop` / `resume` / `kill` / `delete` walk the irreversibility ladder. Each operates on the current workspace; set it with `zombiectl workspace use` or check with `zombiectl workspace show`.
+A small set of verbs cover the live lifecycle: `install --from <path>` brings an agent up, `status` shows what's running, `logs` (or `events` for filtered history) replays the activity stream, `steer` triggers a manual run, and `stop` / `resume` / `kill` / `delete` walk the irreversibility ladder. Each operates on the current workspace; set it with `agentsfleet workspace use` or check with `agentsfleet workspace show`.
 
 ```bash
-zombiectl install --from ~/.config/usezombie/samples/platform-ops
-zombiectl status                               # every agent in the workspace
-zombiectl logs zmb_2041                        # tail one agent's recent activity
-zombiectl steer zmb_2041 "morning health check"
-zombiectl stop zmb_2041                        # pause; resumable
-zombiectl kill zmb_2041                        # terminal
-zombiectl delete zmb_2041                      # hard-delete (kill first)
+agentsfleet install --from ~/.config/agentsfleet/samples/platform-ops
+agentsfleet status                               # every agent in the workspace
+agentsfleet logs 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71                        # tail one agent's recent activity
+agentsfleet steer 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71 "morning health check"
+agentsfleet stop 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71                        # pause; resumable
+agentsfleet kill 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71                        # terminal
+agentsfleet delete 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71                      # hard-delete (kill first)
 ```
 
-## `zombiectl install --from <path>`
+## `agentsfleet install --from <path>`
 
 Reads `SKILL.md` and `TRIGGER.md` from the directory you point at, validates them, and uploads to the active workspace. **Install is the deploy** — there is no separate `up` step.
 
 ```bash
-zombiectl install --from ~/.config/usezombie/samples/platform-ops
+agentsfleet install --from ~/.config/agentsfleet/samples/platform-ops
 ```
 
 ```
 ✓ platform-ops-agent is live.
-  Zombie ID: zmb_2041
+  Agent ID: 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71
   Webhook URLs (register on the upstream provider):
-    github: https://api.usezombie.com/v1/webhooks/zmb_2041/github
+    github: https://api.agentsfleet.net/v1/webhooks/0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71/github
 ```
 
 One URL is printed per declared `webhook` trigger, keyed by `triggers[].source`. The host-agent install skill registers each URL on the upstream provider via your existing `gh` (or equivalent) CLI — there is no separate paste step. To rotate the workspace-level signing secret, see [Quickstart → Verify the registered webhook](/quickstart#verify-the-registered-webhook).
 
-Re-running `zombiectl install --from <same-path>` against a workspace that already has the same agent is idempotent: the new `SKILL.md` / `TRIGGER.md` replace the previous version on the next event.
+Re-running `agentsfleet install --from <same-path>` against a workspace that already has the same agent is idempotent: the new `SKILL.md` / `TRIGGER.md` replace the previous version on the next event.
 
 Exit codes:
 
@@ -42,35 +42,35 @@ Exit codes:
 - `1` — no workspace selected, or API error.
 - `2` — missing `--from`, invalid path, or schema rejection.
 
-## `zombiectl status`
+## `agentsfleet status`
 
 Lists every agent in the active workspace with its state, last event, and budget consumed.
 
 ```bash
-zombiectl status
+agentsfleet status
 ```
 
 ```
-Zombies (workspace: ws_abc123)
-──────────────────────────────────────────────────────────────────
-ID         Name                  Status  Events  Budget
-zmb_2041   platform-ops-agent   alive   42      $1.23
+Agents (workspace: 0198a7b0-3c2d-7f14-9a08-1b6e4d2f8c50)
+────────────────────────────────────────────────────────────────────────────────
+ID                                    Name                  Status  Events  Budget
+0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71  platform-ops-agent   alive   42      $1.23
 ```
 
 Pass `--json` for a machine-readable shape suitable for scripting:
 
 ```bash
-zombiectl status --json
+agentsfleet status --json
 ```
 
-## `zombiectl logs <zombie_id>`
+## `agentsfleet logs <agent_id>`
 
 Print the agent's recent activity stream. Every webhook receipt, cron fire, steer message, tool call, and run exit lands here, tagged with what triggered it (`webhook:github`, `cron:*`, `steer:<user>`, `continuation:<original_actor>`).
 
 ```bash
-zombiectl logs zmb_2041
-zombiectl logs zmb_2041 --limit 50 --cursor <next_cursor>
-zombiectl logs zmb_2041 --json
+agentsfleet logs 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71
+agentsfleet logs 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71 --limit 50 --cursor <next_cursor>
+agentsfleet logs 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71 --json
 ```
 
 | Flag | Default | Purpose |
@@ -79,14 +79,14 @@ zombiectl logs zmb_2041 --json
 | `--cursor <cursor>` | *(none)* | Pagination cursor returned as `next_cursor` in a previous response. |
 | `--json` | off | Emit the raw `{ items, next_cursor }` envelope. |
 
-## `zombiectl events <zombie_id>` — filtered history
+## `agentsfleet events <agent_id>` — filtered history
 
 Richer filter surface than `logs`. Use this when you need to slice by actor or time window:
 
 ```bash
-zombiectl events zmb_2041 --actor 'webhook:*' --since 2h
-zombiectl events zmb_2041 --actor 'steer:*' --since 7d --limit 100
-zombiectl events zmb_2041 --json | jq 'select(.error)'
+agentsfleet events 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71 --actor 'webhook:*' --since 2h
+agentsfleet events 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71 --actor 'steer:*' --since 7d --limit 100
+agentsfleet events 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71 --json | jq 'select(.error)'
 ```
 
 | Flag | Default | Purpose |
@@ -99,12 +99,12 @@ zombiectl events zmb_2041 --json | jq 'select(.error)'
 
 There's no streaming-tail flag today. Poll `events --since 30s` from a script if you need near-live behaviour.
 
-## `zombiectl steer <zombie_id> "<message>"`
+## `agentsfleet steer <agent_id> "<message>"`
 
 Posts a steer message — a manual trigger that runs the same reasoning loop as a webhook event. Useful before you have a webhook wired up, or for one-off investigation.
 
 ```bash
-zombiectl steer zmb_2041 "morning health check — anything red?"
+agentsfleet steer 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71 "morning health check — anything red?"
 ```
 
 The reply streams back live; the result is also persisted to the activity stream for replay.
@@ -115,19 +115,19 @@ Four verbs control the agent's lifecycle, in increasing order of irreversibility
 
 | Verb | What it does | Reversible? |
 |---|---|---|
-| `stop <zombie_id>` | Halt the running session. New events stop dispatching; the in-flight run finishes cleanly. | Yes — `zombiectl resume`. |
-| `resume <zombie_id>` | Bring a `stopped` (or auto-paused) agent back to active. | — |
-| `kill <zombie_id>` | Mark terminal. The agent won't process events again, but its row, history, and webhook URL persist. | No, but a killed agent can be `delete`d after. |
-| `delete <zombie_id>` | Hard-delete. Removes the agent row and its webhook URL. **Must `kill` first.** | No. |
+| `stop <agent_id>` | Halt the running session. New events stop dispatching; the in-flight run finishes cleanly. | Yes — `agentsfleet resume`. |
+| `resume <agent_id>` | Bring a `stopped` (or auto-paused) agent back to active. | — |
+| `kill <agent_id>` | Mark terminal. The agent won't process events again, but its row, history, and webhook URL persist. | No, but a killed agent can be `delete`d after. |
+| `delete <agent_id>` | Hard-delete. Removes the agent row and its webhook URL. **Must `kill` first.** | No. |
 
 ```bash
-zombiectl stop   zmb_2041   # pause; resumable
-zombiectl resume zmb_2041   # back to active
-zombiectl kill   zmb_2041   # terminal; webhook still 200s but routes nowhere new
-zombiectl delete zmb_2041   # hard-delete; webhook URL starts returning UZ-WH-001
+agentsfleet stop   0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71   # pause; resumable
+agentsfleet resume 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71   # back to active
+agentsfleet kill   0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71   # terminal; webhook still 200s but routes nowhere new
+agentsfleet delete 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71   # hard-delete; webhook URL starts returning UZ-WH-001
 ```
 
-State is checkpointed at every transition — nothing on the activity stream is lost until the final `delete`. After delete, recreating with the same `SKILL.md` produces a **new** `zombie_id` and a **new** webhook URL; any upstream wiring needs to be updated.
+State is checkpointed at every transition — nothing on the activity stream is lost until the final `delete`. After delete, recreating with the same `SKILL.md` produces a **new** `agent_id` and a **new** webhook URL; any upstream wiring needs to be updated.
 
 ## Exit codes
 
@@ -135,6 +135,6 @@ State is checkpointed at every transition — nothing on the activity stream is
 |------|---------|
 | `0` | Success. |
 | `1` | Workspace not selected, network error, or server rejected the call. |
-| `2` | Invalid or missing argument (missing `--from`, missing `<zombie_id>`, etc.). |
+| `2` | Invalid or missing argument (missing `--from`, missing `<agent_id>`, etc.). |
 
-See the [CLI reference](/cli/zombiectl) for the full command matrix.
+See the [CLI reference](/cli/agentsfleet) for the full command matrix.
diff --git a/zombies/templates.mdx b/agents/templates.mdx
similarity index 76%
rename from zombies/templates.mdx
rename to agents/templates.mdx
index 71ae7fa..15a93f4 100644
--- a/zombies/templates.mdx
+++ b/agents/templates.mdx
@@ -6,10 +6,10 @@ description: "The shipped sample directory — pre-built agents you can install
 A **template** is a directory with a valid `SKILL.md` and `TRIGGER.md`. Pick one, install it, get a working agent.
 
 ```bash
-zombiectl install --from <path>
+agentsfleet install --from <path>
 ```
 
-The `zombiectl` package ships sample directories under `~/.config/usezombie/samples/`.
+The `agentsfleet` package ships sample directories under `~/.config/agentsfleet/samples/`.
 
 ## Catalogue
 
@@ -27,15 +27,15 @@ More samples land as new flagships ship.
 
 ## Writing your own
 
-A template is just a directory with `SKILL.md` and `TRIGGER.md`. See [Authoring an agent](/zombies/authoring) for the file references; install with:
+A template is just a directory with `SKILL.md` and `TRIGGER.md`. See [Authoring an agent](/agents/authoring) for the file references; install with:
 
 ```bash
-zombiectl install --from .
+agentsfleet install --from .
 ```
 
 ## Sharing
 
-Templates are markdown — commit `my-agent/` to git, clone it on a new machine, `zombiectl install --from .`. Credentials never live in the template; they live in the workspace vault. Template-safe to share publicly; credentials are not.
+Templates are markdown — commit `my-agent/` to git, clone it on a new machine, `agentsfleet install --from .`. Credentials never live in the template; they live in the workspace vault. Template-safe to share publicly; credentials are not.
 
 <Note>
   A hosted template marketplace (community-contributed agents, one-click install) is on the roadmap. For now, git is the distribution mechanism.
diff --git a/zombies/tools.mdx b/agents/tools.mdx
similarity index 87%
rename from zombies/tools.mdx
rename to agents/tools.mdx
index 0eff6ae..3ca19f3 100644
--- a/zombies/tools.mdx
+++ b/agents/tools.mdx
@@ -3,10 +3,10 @@ title: "Tools catalogue"
 description: "Every tool an agent can declare in `TRIGGER.md`, what it does, and when to reach for it."
 ---
 
-A **tool** is a named verb the agent inside a run may invoke. Tools are declared in `TRIGGER.md` under `x-usezombie.tools:` — anything not on the list is unreachable, even if the model tries to call it. This page is the canonical catalogue.
+A **tool** is a named verb the agent inside a run may invoke. Tools are declared in `TRIGGER.md` under `x-agentsfleet.tools:` — anything not on the list is unreachable, even if the model tries to call it. This page is the canonical catalogue.
 
 ```yaml
-x-usezombie:
+x-agentsfleet:
   tools:
     - http_request
     - memory_recall
@@ -14,7 +14,7 @@ x-usezombie:
     - cron_add
 ```
 
-23 tools are user-callable today. They group into nine categories below. For the file format, validation rules, and frontmatter, see [Authoring an agent](/zombies/authoring).
+23 tools are user-callable today. They group into nine categories below. For the file format, validation rules, and frontmatter, see [Authoring an agent](/agents/authoring).
 
 ## Network
 
@@ -39,7 +39,7 @@ Cross-run durable state. See [Memory](/memory) for the four-category model and k
 | `memory_store` | Upsert a distilled fact (key + category + body + tags). | End of every run where the agent learned something worth keeping. |
 | `memory_recall` | Exact-key lookup; returns the entry or empty. | Start of every run, before reasoning. |
 | `memory_list` | Filter entries by category, tags, recency. | When the agent doesn't know the exact key (e.g. "show me all open tickets"). |
-| `memory_forget` | Delete an entry. | Correcting stale facts; fed by `zombiectl steer` corrections. |
+| `memory_forget` | Delete an entry. | Correcting stale facts; fed by `agentsfleet steer` corrections. |
 
 ## Cron
 
@@ -110,12 +110,12 @@ Pure-function helpers — no side effects, no network, no state.
 
 ## How tools, credentials, and the network allowlist combine
 
-Tools are the *what* (verbs the agent may invoke). Credentials are the *what-with* (named secrets the tool bridge substitutes into outbound calls — see [Credentials](/zombies/credentials)). The network allowlist is the *to-where* (hostnames the sandbox firewall lets traffic reach).
+Tools are the *what* (verbs the agent may invoke). Credentials are the *what-with* (named secrets the tool bridge substitutes into outbound calls — see [Credentials](/agents/credentials)). The network allowlist is the *to-where* (hostnames the sandbox firewall lets traffic reach).
 
 A working `http_request` to Slack needs all three:
 
 ```yaml
-x-usezombie:
+x-agentsfleet:
   tools:
     - http_request                    # the verb
   credentials:
@@ -129,11 +129,11 @@ Drop any one and the call fails: missing tool → agent can't even try; missing
 
 ## Validation
 
-`zombiectl install --from <path>` accepts the `tools:` list as-is — there's no catalogue check at install time. Unknown names surface later, when the runner builds tools for a run: each unrecognized name gets logged as `UZ-TOOL-005` (Unknown tool) and silently skipped. The agent runs with the remaining tools.
+`agentsfleet install --from <path>` accepts the `tools:` list as-is — there's no catalogue check at install time. Unknown names surface later, when the runner builds tools for a run: each unrecognized name gets logged as `UZ-TOOL-005` (Unknown tool) and silently skipped. The agent runs with the remaining tools.
 
 The practical consequences:
 
-- **Typos pass install.** Declaring `http_requesst:` (typo) won't fail `zombiectl install --from`. Catch this by tailing `zombiectl logs <zombie_id>` after the first event and looking for the skip warning, or by spotting tool calls in the activity stream that don't match what your `SKILL.md` prose expects.
+- **Typos pass install.** Declaring `http_requesst:` (typo) won't fail `agentsfleet install --from`. Catch this by tailing `agentsfleet logs <agent_id>` after the first event and looking for the skip warning, or by spotting tool calls in the activity stream that don't match what your `SKILL.md` prose expects.
 - **Disabled tools are also silently dropped.** Setting `enabled: false` on a tool entry skips it without a warning.
 - **`UZ-TOOL-005` is a log warning, not a wire response.** It won't appear as an HTTP error to a webhook caller; it's a server-side observability signal.
 
@@ -141,7 +141,7 @@ When the agent tries to invoke a tool not in the agent's resolved `tools:` set,
 
 ## See also
 
-- [Authoring an agent](/zombies/authoring) — full `TRIGGER.md` schema.
+- [Authoring an agent](/agents/authoring) — full `TRIGGER.md` schema.
 - [Memory](/memory) — the four memory categories and how recall/store fit a run.
-- [Credentials](/zombies/credentials) — adding the secrets the tool bridge substitutes.
-- [Webhooks](/zombies/webhooks) — wiring an external system to your agent.
+- [Credentials](/agents/credentials) — adding the secrets the tool bridge substitutes.
+- [Webhooks](/agents/webhooks) — wiring an external system to your agent.
diff --git a/zombies/troubleshooting.mdx b/agents/troubleshooting.mdx
similarity index 66%
rename from zombies/troubleshooting.mdx
rename to agents/troubleshooting.mdx
index 0dde36a..6eb8535 100644
--- a/zombies/troubleshooting.mdx
+++ b/agents/troubleshooting.mdx
@@ -9,32 +9,32 @@ An agent that's misbehaving falls into one of six failure shapes. Find the sympt
 
 | Symptom | Most likely cause | Start here |
 |---|---|---|
-| `zombiectl install --from` exits non-zero | Frontmatter validation failed | [§1 Install rejected](#1-install-rejected) |
+| `agentsfleet install --from` exits non-zero | Frontmatter validation failed | [§1 Install rejected](#1-install-rejected) |
 | Upstream says it sent the webhook, agent didn't wake | Signature mismatch or wrong URL | [§2 Webhook delivered but agent silent](#2-webhook-delivered-but-agent-silent) |
 | Agent woke, run failed before producing output | Credential, network, or tool error | [§3 Run opens then fails](#3-run-opens-then-fails) |
 | Run produces a result but it's wrong | `SKILL.md` prose or memory issue | [§4 Run completes but output is wrong](#4-run-completes-but-output-is-wrong) |
 | Run terminates with `budget_breach` | `daily_dollars` / `monthly_dollars` ceiling hit | [§5 Budget breach](#5-budget-breach) |
-| `zombiectl` itself is broken (auth, network) | Local config or platform reachability | [§6 zombiectl can't reach the platform](#6-zombiectl-cant-reach-the-platform) |
+| `agentsfleet` itself is broken (auth, network) | Local config or platform reachability | [§6 agentsfleet can't reach the platform](#6-agentsfleet-cant-reach-the-platform) |
 
 ## 1. Install rejected
 
-`zombiectl install --from <path>` exited with code `2`. The platform parsed your `SKILL.md` + `TRIGGER.md` and rejected them.
+`agentsfleet install --from <path>` exited with code `2`. The platform parsed your `SKILL.md` + `TRIGGER.md` and rejected them.
 
 ```bash
-zombiectl install --from ./my-agent --json 2>&1 | tail -5
+agentsfleet install --from ./my-agent --json 2>&1 | tail -5
 ```
 
 The `--json` output carries the wire error code:
 
 | Wire code | Cause | Fix |
 |---|---|---|
-| `UZ-ZMB-008` | `TRIGGER.md` config_json fails schema validation | Re-read [Authoring](/zombies/authoring) §`x-usezombie:` subkeys. Common: a runtime key (`tools`, `credentials`, `network`) at the top level instead of nested under `x-usezombie:`. |
-| `UZ-ZMB-011` | `SKILL.md` and `TRIGGER.md` disagree on top-level `name:` | Make both files' `name:` value identical. |
-| `UZ-VAULT-001` | Credential `data` body is empty / not a JSON object | The error is from a prior `credential add` call, not from `install` itself. Re-run `zombiectl credential add <name> --data=@-` with a non-empty JSON object. |
+| `UZ-AGT-008` | `TRIGGER.md` config_json fails schema validation | Re-read [Authoring](/agents/authoring) §`x-agentsfleet:` subkeys. Common: a runtime key (`tools`, `credentials`, `network`) at the top level instead of nested under `x-agentsfleet:`. |
+| `UZ-AGT-011` | `SKILL.md` and `TRIGGER.md` disagree on top-level `name:` | Make both files' `name:` value identical. |
+| `UZ-VAULT-001` | Credential `data` body is empty / not a JSON object | The error is from a prior `credential add` call, not from `install` itself. Re-run `agentsfleet credential add <name> --data=@-` with a non-empty JSON object. |
 
 For other codes, check [Error codes](/api-reference/error-codes) and grep for the `UZ-` prefix.
 
-**Local validation tip:** the parser the platform uses is the same one `zombiectl install --from` runs — there's no separate lint command. To catch schema errors before committing, run `zombiectl install --from <path> --json` and read the structured error output. Note the call still uploads on success; there is no `--validate-only` flag.
+**Local validation tip:** the parser the platform uses is the same one `agentsfleet install --from` runs — there's no separate lint command. To catch schema errors before committing, run `agentsfleet install --from <path> --json` and read the structured error output. Note the call still uploads on success; there is no `--validate-only` flag.
 
 ## 2. Webhook delivered but agent silent
 
@@ -44,7 +44,7 @@ The upstream provider says it fired the webhook, your activity stream shows noth
 
 ```bash
 # All webhook-actor events in the last hour, including rejected ones
-zombiectl events <zombie_id> --actor 'webhook:*' --since 1h --json
+agentsfleet events <agent_id> --actor 'webhook:*' --since 1h --json
 ```
 
 Three things to look for in the output:
@@ -61,12 +61,12 @@ If the upstream itself shows a non-2xx response, the body carries one of:
 
 | Wire code | HTTP | What to check |
 |---|---|---|
-| `UZ-WH-001` | 404 | URL is wrong. The path is `https://api.usezombie.com/v1/webhooks/{zombie_id}/{source}` — verify the ID matches `zombiectl status`. |
+| `UZ-WH-001` | 404 | URL is wrong. The path is `https://api.agentsfleet.net/v1/webhooks/{agent_id}/{source}` — verify the ID matches `agentsfleet status`. |
 | `UZ-WH-002` | 400 | Request body is malformed JSON or empty. |
-| `UZ-WH-003` | 403 | Agent is paused or killed. `zombiectl status` will show the state; re-install with `zombiectl install --from <path>`. |
+| `UZ-WH-003` | 403 | Agent is paused or killed. `agentsfleet status` will show the state; re-install with `agentsfleet install --from <path>`. |
 | `UZ-WH-010` | 401 | HMAC signature verification failed. The shared secret in your vault doesn't match the one configured at the upstream. Rotate per [Quickstart → Verify the registered webhook](/quickstart#verify-the-registered-webhook). |
 | `UZ-WH-011` | 401 | Replay-window violation — request timestamp is older than 5 minutes. Sender clock skew is the usual culprit. |
-| `UZ-WH-020` | 401 | No webhook credential configured for this agent's source. The `secret_ref` in `TRIGGER.md` either isn't set or points at a vault key that doesn't exist. Run `zombiectl credential list` to confirm; add with `zombiectl credential add <source> --data=@-`. |
+| `UZ-WH-020` | 401 | No webhook credential configured for this agent's source. The `secret_ref` in `TRIGGER.md` either isn't set or points at a vault key that doesn't exist. Run `agentsfleet credential list` to confirm; add with `agentsfleet credential add <source> --data=@-`. |
 | `UZ-WH-030` | 413 | Payload exceeds the 1 MiB ingest limit. The upstream is sending too much; filter or trim the event body before forwarding. |
 
 ### Common signature config mistakes
@@ -74,7 +74,7 @@ If the upstream itself shows a non-2xx response, the body carries one of:
 ```yaml
 # WRONG — secret_ref references a vault key that doesn't exist
 signature:
-  secret_ref: github_secret    # but you ran: zombiectl credential add github
+  secret_ref: github_secret    # but you ran: agentsfleet credential add github
                                #              ^^^^^^ — name is "github", not "github_secret"
 
 # RIGHT
@@ -82,7 +82,7 @@ signature:
   secret_ref: github
 ```
 
-For first-class providers (`github`, `slack`, `linear`), don't set `header` and `prefix` manually — the registry fills those. See [Webhooks → Natively normalized providers](/zombies/webhooks#natively-normalized-providers).
+For first-class providers (`github`, `slack`, `linear`), don't set `header` and `prefix` manually — the registry fills those. See [Webhooks → Natively normalized providers](/agents/webhooks#natively-normalized-providers).
 
 ## 3. Run opens then fails
 
@@ -91,18 +91,18 @@ The webhook landed and a run opened, but it terminated before producing output.
 ### Diagnostic
 
 ```bash
-zombiectl events <zombie_id> --since 1h --json | jq 'select(.error)'
+agentsfleet events <agent_id> --since 1h --json | jq 'select(.error)'
 ```
 
 | Wire code | Cause | Fix |
 |---|---|---|
-| `UZ-ZMB-003` | A required vault credential is absent | The credential name in `TRIGGER.md` `credentials:` doesn't exist in the workspace vault. `zombiectl credential list` to confirm; `zombiectl credential add <name> --data=@-` to add. |
-| `UZ-ZMB-002` | Agent timeout | The model didn't return within the per-event ceiling. Often a sign the prompt is too large or the model is overwhelmed. Tighten `SKILL.md` or check `tool_window` in [Context lifecycle](/concepts/context-lifecycle). |
+| `UZ-AGT-003` | A required vault credential is absent | The credential name in `TRIGGER.md` `credentials:` doesn't exist in the workspace vault. `agentsfleet credential list` to confirm; `agentsfleet credential add <name> --data=@-` to add. |
+| `UZ-AGT-002` | Agent timeout | The model didn't return within the per-event ceiling. Often a sign the prompt is too large or the model is overwhelmed. Tighten `SKILL.md` or check `tool_window` in [Context lifecycle](/concepts/context-lifecycle). |
 | `UZ-MEM-003` | Memory backend unavailable | Transient. Re-trigger; if persistent, file an issue. |
 | `UZ-MEM-001` | Memory scope denied | The agent tried to read another agent's memory. Check the `key` derivation in `SKILL.md` — keys are agent-scoped. |
 
 <Note>
-**Tool-related failures don't surface as wire codes.** When a `tools:` entry has a typo, the runner logs `UZ-TOOL-005` at warn level and silently skips it. When the agent tries to invoke a tool that isn't in its resolved set, NullClaw returns a "no such tool" message in the activity stream rather than emitting `UZ-TOOL-004` to a caller. Both `UZ-TOOL-*` codes exist in the registry (see [Error codes → Tool](/api-reference/error-codes#tool)) but in v2 today the diagnostic signal is the activity-stream entry, not a wire response. Audit `zombiectl logs <zombie_id>` for the actual error text. See [Tools catalogue → Validation](/zombies/tools#validation).
+**Tool-related failures don't surface as wire codes.** When a `tools:` entry has a typo, the runner logs `UZ-TOOL-005` at warn level and silently skips it. When the agent tries to invoke a tool that isn't in its resolved set, NullClaw returns a "no such tool" message in the activity stream rather than emitting `UZ-TOOL-004` to a caller. Both `UZ-TOOL-*` codes exist in the registry (see [Error codes → Tool](/api-reference/error-codes#tool)) but in v2 today the diagnostic signal is the activity-stream entry, not a wire response. Audit `agentsfleet logs <agent_id>` for the actual error text. See [Tools catalogue → Validation](/agents/tools#validation).
 </Note>
 
 ### Network allowlist drops
@@ -117,7 +117,7 @@ The hardest class of failure. Run exits cleanly, the diagnosis posts to Slack, b
 
 ```bash
 # Full event with the agent's tool calls and reasoning trail
-zombiectl events <zombie_id> --since 30m --json | jq 'select(.actor | startswith("webhook:") or startswith("steer:"))'
+agentsfleet events <agent_id> --since 30m --json | jq 'select(.actor | startswith("webhook:") or startswith("steer:"))'
 ```
 
 The model's tool-call trail tells you what it actually did. Compare against what your `SKILL.md` told it to do:
@@ -132,58 +132,58 @@ The model's tool-call trail tells you what it actually did. Compare against what
 
 ### Iterating on prose
 
-`SKILL.md` is a prompt. The fastest debug loop is `zombiectl steer`:
+`SKILL.md` is a prompt. The fastest debug loop is `agentsfleet steer`:
 
 ```bash
-zombiectl steer <zombie_id> "<the same input that triggered the bug>"
+agentsfleet steer <agent_id> "<the same input that triggered the bug>"
 ```
 
-Edit `SKILL.md`, `zombiectl install --from .`, re-steer. The next event uses the new prose — no redeploy.
+Edit `SKILL.md`, `agentsfleet install --from .`, re-steer. The next event uses the new prose — no redeploy.
 
 ## 5. Budget breach
 
-Run terminated with `UZ-ZMB-001`. The `daily_dollars` or `monthly_dollars` ceiling in `TRIGGER.md` was hit.
+Run terminated with `UZ-AGT-001`. The `daily_dollars` or `monthly_dollars` ceiling in `TRIGGER.md` was hit.
 
 ```bash
-zombiectl status --json | jq '.[] | select(.zombie_id == "<id>") | {state, budget}'
+agentsfleet status --json | jq '.[] | select(.agent_id == "<id>") | {state, budget}'
 ```
 
 Two layers of cap exist independently:
 
 1. **Per-agent** (`TRIGGER.md` `budget.daily_dollars` / `monthly_dollars`) — terminates this agent's runs until the rolling window resets. Raise the value, re-install.
-2. **Tenant wallet** — every workspace's runs debit the same pool. When it hits zero, all runs across all workspaces stop. Top up at `app.usezombie.com/billing`. See [Billing → Budgets](/billing/budgets).
+2. **Tenant wallet** — every workspace's runs debit the same pool. When it hits zero, all runs across all workspaces stop. Top up at `app.agentsfleet.net/billing`. See [Billing → Budgets](/billing/budgets).
 
 If you're hitting the per-agent cap repeatedly on legitimate traffic, the agent's per-run cost is higher than you sized for. Audit the activity stream for unusually long runs (high `tokens` or `wall_ms` fields), and consider tightening `SKILL.md` or splitting the work across multiple smaller agents.
 
-## 6. zombiectl can't reach the platform
+## 6. agentsfleet can't reach the platform
 
 Anything that affects every command — login fails, `status` returns errors, `install` 401s.
 
 ### Diagnostic
 
 ```bash
-zombiectl doctor
+agentsfleet doctor
 ```
 
 Three checks run; all must pass:
 
 | Check | Failure means |
 |---|---|
-| `server_reachable` | API is unreachable from your machine. Check your network. The base URL is `https://api.usezombie.com` (override with `--api` or `ZOMBIE_API_URL`). |
-| `workspace_selected` | Local config has no `current_workspace_id`. Run `zombiectl workspace add [name]` (creates + activates) or `workspace use <id>` (activates an existing one). |
-| `workspace_binding_valid` | Auth token doesn't have access to the selected workspace. Either the token expired (re-run `zombiectl login`) or the workspace was deleted on the server. |
+| `server_reachable` | API is unreachable from your machine. Check your network. The base URL is `https://api.agentsfleet.net` (override with `--api` or `AGENTSFLEET_API_URL`). |
+| `workspace_selected` | Local config has no `current_workspace_id`. Run `agentsfleet workspace add [name]` (creates + activates) or `workspace use <id>` (activates an existing one). |
+| `workspace_binding_valid` | Auth token doesn't have access to the selected workspace. Either the token expired (re-run `agentsfleet login`) or the workspace was deleted on the server. |
 
 Pass `--json` for the structured envelope: `{ ok: bool, api_url: string, checks: [{ name, ok, detail }] }`.
 
 ### Auth resolution order
 
-If `zombiectl` keeps acting unauthenticated, your token might be coming from somewhere unexpected. Resolution order, highest priority first:
+If `agentsfleet` keeps acting unauthenticated, your token might be coming from somewhere unexpected. Resolution order, highest priority first:
 
 1. `--token <value>` flag
-2. `ZOMBIE_TOKEN` environment variable
-3. Stored credentials at `~/.config/zombiectl/credentials` (written by `zombiectl login`)
+2. `AGENTSFLEET_TOKEN` environment variable
+3. Stored credentials at `~/.config/agentsfleet/credentials` (written by `agentsfleet login`)
 
-Unset `ZOMBIE_TOKEN` if you've been running CI scripts that exported it; otherwise it overrides whatever `zombiectl login` wrote.
+Unset `AGENTSFLEET_TOKEN` if you've been running CI scripts that exported it; otherwise it overrides whatever `agentsfleet login` wrote.
 
 ## When to escalate
 
@@ -191,17 +191,17 @@ Two paths, depending on whether you want a fix or a faster sanity-check.
 
 **Fast: ask in [Discord](https://discord.gg/H9hH2nqQjh).** Best for "is this a known issue?", "is this expected?", or anything where you need a human eye in minutes rather than hours. Design partners and the core team hang out there.
 
-**Durable: file an issue at [github.com/usezombie/usezombie/issues](https://github.com/usezombie/usezombie/issues).** Best when the problem is reproducible, blocks shipping, or hits any of:
+**Durable: file an issue at [github.com/agentsfleet/agentsfleet/issues](https://github.com/agentsfleet/agentsfleet/issues).** Best when the problem is reproducible, blocks shipping, or hits any of:
 
 - Diagnostic returns no error but the symptom persists across multiple triggers.
 - A `UZ-INTERNAL-*` or `UZ-AUTH-004` (auth service unavailable) keeps firing.
-- `zombiectl doctor` passes but operations still fail.
+- `agentsfleet doctor` passes but operations still fail.
 
 Either way, include the `request_id` from the `--json` error envelope, the wire code, and a recent timestamp — those uniquely identify the request server-side.
 
 ## See also
 
 - [Error codes](/api-reference/error-codes) — full registry of `UZ-*` codes.
-- [Webhooks](/zombies/webhooks) — signature config reference.
-- [Authoring](/zombies/authoring) — `SKILL.md` / `TRIGGER.md` schema.
+- [Webhooks](/agents/webhooks) — signature config reference.
+- [Authoring](/agents/authoring) — `SKILL.md` / `TRIGGER.md` schema.
 - [Context lifecycle](/concepts/context-lifecycle) — when long runs get continued or escalated.
diff --git a/zombies/webhooks.mdx b/agents/webhooks.mdx
similarity index 70%
rename from zombies/webhooks.mdx
rename to agents/webhooks.mdx
index 01f6c6a..bf7e2d2 100644
--- a/zombies/webhooks.mdx
+++ b/agents/webhooks.mdx
@@ -6,10 +6,10 @@ description: "How external systems deliver events to your agent, and how the pla
 Every webhook trigger declared in `TRIGGER.md` gets a unique, stable URL keyed by `source`:
 
 ```
-https://api.usezombie.com/v1/webhooks/{zombie_id}/{source}
+https://api.agentsfleet.net/v1/webhooks/{agent_id}/{source}
 ```
 
-External systems POST to this URL. The platform verifies the signature and delivers the event to the agent. No tunneling, no ngrok, no custom servers on your side. `zombiectl install --from` prints the full set of URLs (one per declared webhook trigger) at install time.
+External systems POST to this URL. The platform verifies the signature and delivers the event to the agent. No tunneling, no ngrok, no custom servers on your side. `agentsfleet install --from` prints the full set of URLs (one per declared webhook trigger) at install time.
 
 <Tip>
   **Most users don't wire webhooks by hand.** The `platform-ops` install skill registers each declared webhook automatically via your existing `gh` CLI — no paste-into-GitHub step. Use [Quickstart](/quickstart) for the full guided flow. The reference below is for custom webhooks — your own provider, an internal service, etc.
@@ -23,7 +23,7 @@ An agent declares its webhooks in `TRIGGER.md` under the `triggers:` array (1–
 ---
 name: my-agent
 
-x-usezombie:
+x-agentsfleet:
   triggers:
     - type: webhook
       source: github
@@ -35,9 +35,9 @@ x-usezombie:
 ---
 ```
 
-`source` is a label that appears in the activity stream (`github`, `slack`, `linear`, etc.) and selects the per-trigger inbound URL — `https://api.usezombie.com/v1/webhooks/{zombie_id}/{source}`. `events` is an optional whitelist of upstream event names (1–16 entries, ≤64 chars each); omit it to accept every event the source delivers. The `signature` block tells the platform how to verify the request.
+`source` is a label that appears in the activity stream (`github`, `slack`, `linear`, etc.) and selects the per-trigger inbound URL — `https://api.agentsfleet.net/v1/webhooks/{agent_id}/{source}`. `events` is an optional whitelist of upstream event names (1–16 entries, ≤64 chars each); omit it to accept every event the source delivers. The `signature` block tells the platform how to verify the request.
 
-The singular `trigger:` shape is rejected at install (`ERR_ZOMBIE_INVALID_CONFIG: use "triggers:" (array)`); always declare the array form, even for a single webhook.
+The singular `trigger:` shape is rejected at install (`ERR_AGENTSFLEET_INVALID_CONFIG: use "triggers:" (array)`); always declare the array form, even for a single webhook.
 
 ## Authentication
 
@@ -79,10 +79,10 @@ triggers:
 
 The parser rejects an unknown `source` that supplies only `secret_ref` with no `header` — explicit configuration is required outside the registry.
 
-`secret_ref` always names a credential in the workspace vault carrying the upstream's signing secret. See [Credentials](/zombies/credentials).
+`secret_ref` always names a credential in the workspace vault carrying the upstream's signing secret. See [Credentials](/agents/credentials).
 
 <Note>
-  **Payload normalization is automatic for named sources.** When `source` is `github`, `slack`, or `linear`, `POST /v1/webhooks/{zombie_id}/{source}` runs the provider-specific normalizer (event-type extraction, payload shape coercion) before the agent sees the event — no flag, no separate URL. Pick a different `source` label (e.g. `source: github_raw`) with an explicit `signature` block to bypass normalization and receive the raw payload. Clerk-shaped (Svix) webhooks are the one exception: they use a distinct route, `POST /v1/webhooks/svix/{zombie_id}`, to accommodate Svix's multi-signature rotation scheme.
+  **Payload normalization is automatic for named sources.** When `source` is `github`, `slack`, or `linear`, `POST /v1/webhooks/{agent_id}/{source}` runs the provider-specific normalizer (event-type extraction, payload shape coercion) before the agent sees the event — no flag, no separate URL. Pick a different `source` label (e.g. `source: github_raw`) with an explicit `signature` block to bypass normalization and receive the raw payload. Clerk-shaped (Svix) webhooks are the one exception: they use a distinct route, `POST /v1/webhooks/svix/{agent_id}`, to accommodate Svix's multi-signature rotation scheme.
 </Note>
 
 ## Sending an event
@@ -90,7 +90,7 @@ The parser rejects an unknown `source` that supplies only `secret_ref` with no `
 Once the agent is installed, your provider POSTs to its URL with a signed body:
 
 ```bash
-curl -X POST https://api.usezombie.com/v1/webhooks/zmb_2041/github \
+curl -X POST https://api.agentsfleet.net/v1/webhooks/0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71/github \
   -H "x-hub-signature-256: sha256=<computed-hmac>" \
   -H "Content-Type: application/json" \
   -d '{
@@ -103,7 +103,7 @@ curl -X POST https://api.usezombie.com/v1/webhooks/zmb_2041/github \
 The platform verifies the signature, enqueues the event, and returns `202 Accepted`:
 
 ```json
-{ "accepted": true, "request_id": "req_01JQ7K..." }
+{ "accepted": true, "request_id": "0198a7b7-4e9c-7a18-b3d6-5f2c8a4e1b73" }
 ```
 
 Delivery is **at-least-once** — your provider may retry on transient failure, so the same event can arrive twice. Include a unique `event_id` in the body so the agent can dedupe.
@@ -114,7 +114,7 @@ Delivery is **at-least-once** — your provider may retry on transient failure,
 |--------|-------|
 | `401` | Missing, malformed, or mis-signed signature header. |
 | `404` | Agent ID does not exist. |
-| `410` | Agent was killed; re-install with `zombiectl install --from <path>`. |
+| `410` | Agent was killed; re-install with `agentsfleet install --from <path>`. |
 | `429` | Rate limit hit; back off per `Retry-After`. |
 | `503` | Budget breached, or platform applying backpressure; safe to retry after the period resets. |
 
@@ -122,13 +122,13 @@ Delivery is **at-least-once** — your provider may retry on transient failure,
 
 Some agent actions — sending money, merging a PR, posting to a public channel — should not happen without a human in the loop. The **approval gate** lets an agent pause mid-run, emit an approval request, and wait for a human to click approve or deny in the dashboard.
 
-For programmatic decisions (e.g. an internal tool calling back into usezombie), POST the decision to:
+For programmatic decisions (e.g. an internal tool calling back into agentsfleet), POST the decision to:
 
 ```bash
-curl -X POST https://api.usezombie.com/v1/webhooks/zmb_2041/approval \
+curl -X POST https://api.agentsfleet.net/v1/webhooks/0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71/approval \
   -H "Authorization: Bearer $APPROVAL_TOKEN" \
   -H "Content-Type: application/json" \
-  -d '{ "approval_id": "apr_01JQ...", "decision": "approve" }'
+  -d '{ "approval_id": "0198a7b9-5a3f-7e24-9b18-4c7d2a8f5e63", "decision": "approve" }'
 ```
 
 The approval token is auto-provisioned for the agent at install time.
@@ -138,7 +138,7 @@ The approval token is auto-provisioned for the agent at install time.
 Every accepted and rejected webhook appears in the activity stream:
 
 ```bash
-zombiectl logs zmb_2041
+agentsfleet logs 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71
 ```
 
 Rejected requests carry a reason code (`webhook_rejected: signature_mismatch`, etc.) so you can tell a noisy upstream from a real auth bug.
@@ -148,9 +148,9 @@ Rejected requests carry a reason code (`webhook_rejected: signature_mismatch`, e
 Some upstreams (a few SaaS form-postbacks, a few legacy systems) can't attach a signature header. For those, the platform accepts a path-embedded secret:
 
 ```
-https://api.usezombie.com/v1/webhooks/{zombie_id}/{url_secret}
+https://api.agentsfleet.net/v1/webhooks/{agent_id}/{url_secret}
 ```
 
 The `url_secret` is matched in constant time. Reserved segments (`approval`, `grant-approval`, `svix`) cannot be used as secret values. Prefer HMAC where the upstream supports it — the URL-embedded form is a fallback.
 
-**Path resolution order.** The trailing segment is resolved against declared `triggers[].source` values *first*, then falls back to a `url_secret` lookup. So `POST /v1/webhooks/zmb_2041/github` routes to the `github` source when the agent declares one, and only searches `url_secret` values for a constant-time match on the literal string `github` when no such source is declared. Practical consequence: avoid choosing a `url_secret` value that collides with any `triggers[].source` on the same agent — the source wins and the secret will never match.
+**Path resolution order.** The trailing segment is resolved against declared `triggers[].source` values *first*, then falls back to a `url_secret` lookup. So `POST /v1/webhooks/0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71/github` routes to the `github` source when the agent declares one, and only searches `url_secret` values for a constant-time match on the literal string `github` when no such source is declared. Practical consequence: avoid choosing a `url_secret` value that collides with any `triggers[].source` on the same agent — the source wins and the secret will never match.
diff --git a/api-reference/error-codes.mdx b/api-reference/error-codes.mdx
index 5ef5a9f..12b0aa5 100644
--- a/api-reference/error-codes.mdx
+++ b/api-reference/error-codes.mdx
@@ -1,6 +1,6 @@
 ---
 title: 'Error Codes'
-description: 'All error responses from zombied use RFC 7807 (application/problem+json). This page lists every error code, its HTTP status, and common causes.'
+description: 'All error responses from agentsfleetd use RFC 7807 (application/problem+json). This page lists every error code, its HTTP status, and common causes.'
 ---
 
 ## Response format
@@ -9,11 +9,11 @@ Every `4xx` and `5xx` response uses `Content-Type: application/problem+json`:
 
 ```json
 {
-  "docs_uri": "https://docs.usezombie.com/api-reference/error-codes#UZ-ZMB-009",
-  "title": "Zombie not found",
-  "detail": "No zombie with id 'abc123' in this workspace.",
-  "error_code": "UZ-ZMB-009",
-  "request_id": "req_a1b2c3d4e5f6"
+  "docs_uri": "https://docs.agentsfleet.net/api-reference/error-codes#UZ-AGT-009",
+  "title": "Agent not found",
+  "detail": "No agent with id '0198a7ba-2c1d-7f08-8a45-3e9b6d2f1c70' in this workspace.",
+  "error_code": "UZ-AGT-009",
+  "request_id": "0198a7b5-3c8d-7e41-9a2b-6f1d4c7e8a05"
 }
 ```
 
@@ -110,42 +110,42 @@ Every `4xx` and `5xx` response uses `Content-Type: application/problem+json`:
 | `UZ-WH-003` | 403 | Agent paused | Agent exists but is not active |
 | `UZ-WH-010` | 401 | Invalid webhook signature | HMAC or Svix signature verification failed. Verify the `secret_ref` vault entry matches the signing secret configured with the provider. |
 | `UZ-WH-011` | 401 | Stale webhook timestamp | Webhook timestamp is older than 5 minutes (replay protection). Ensure the sender clock is not skewed. |
-| `UZ-WH-020` | 401 | Webhook credential not configured | No webhook credential is configured for this agent's source. Run `zombiectl credential add <source> --data=@-` with `{ "webhook_secret": "..." }` in the agent's workspace, then resend. |
+| `UZ-WH-020` | 401 | Webhook credential not configured | No webhook credential is configured for this agent's source. Run `agentsfleet credential add <source> --data=@-` with `{ "webhook_secret": "..." }` in the agent's workspace, then resend. |
 | `UZ-WH-030` | 413 | Webhook payload too large | Webhook body exceeds the 1 MiB ingest limit. Reduce the payload at the source or filter fields before forwarding. |
 
 ## Tool
 
 | Code | HTTP | Title | Common Causes |
 |---|---|---|---|
-| `UZ-TOOL-004` | 400 | Tool not attached | The tool isn't in this agent's `tools:` list. Add it to `TRIGGER.md` `x-usezombie.tools:` and re-install. |
-| `UZ-TOOL-005` | 400 | Unknown tool | Tool name not recognized — typo against the [Tools catalogue](/zombies/tools) is the usual cause. |
+| `UZ-TOOL-004` | 400 | Tool not attached | The tool isn't in this agent's `tools:` list. Add it to `TRIGGER.md` `x-agentsfleet.tools:` and re-install. |
+| `UZ-TOOL-005` | 400 | Unknown tool | Tool name not recognized — typo against the [Tools catalogue](/agents/tools) is the usual cause. |
 
 <Note>
-**Registered, not always emitted.** The two `UZ-TOOL-*` codes are registered in the platform's error registry but, in v2 today, the user-facing failure path for a missing or misspelled tool is a NullClaw-level "no such tool" message in the activity stream rather than one of these wire codes. Treat the codes as authoritative for *meaning* if you do see them, but don't expect them as the primary signal — audit `zombiectl logs <zombie_id>` for the actual error text.
+**Registered, not always emitted.** The two `UZ-TOOL-*` codes are registered in the platform's error registry but, in v2 today, the user-facing failure path for a missing or misspelled tool is a NullClaw-level "no such tool" message in the activity stream rather than one of these wire codes. Treat the codes as authoritative for *meaning* if you do see them, but don't expect them as the primary signal — audit `agentsfleet logs <agent_id>` for the actual error text.
 </Note>
 
 ## Agent
 
 | Code | HTTP | Title | Common Causes |
 |---|---|---|---|
-| `UZ-ZMB-001` | 402 | Agent budget exceeded | Daily dollar budget hit. Raise `budget.daily_dollars` in `TRIGGER.md`. |
-| `UZ-ZMB-002` | 500 | Agent agent timeout | Agent timed out processing an event. Check the activity stream. |
-| `UZ-ZMB-003` | 424 | Agent credential missing | A required vault credential is absent. Add it with `zombiectl credential add <name>`. |
-| `UZ-ZMB-004` | 500 | Agent claim failed | Agent could not be claimed from the database. Verify the `zombie_id` exists and status is `active`. |
-| `UZ-ZMB-005` | 500 | Agent checkpoint failed | Session checkpoint write to Postgres failed. |
-| `UZ-ZMB-006` | 409 | Agent name already exists | Name taken. Kill the existing agent first, then re-install. |
-| `UZ-ZMB-008` | 400 | Invalid agent config | `TRIGGER.md` config_json fails schema validation. Verify trigger, tools, credentials, and budget fields. |
-| `UZ-ZMB-009` | 404 | Agent not found | No agent with this ID in the workspace. |
-| `UZ-ZMB-010` | 409 | Agent already stopped or killed | This agent is already stopped or killed. Re-install before issuing another stop. |
-| `UZ-ZMB-011` | 400 | SKILL.md and TRIGGER.md disagree on `name:` | Top-level `name:` must match across both files. One identity per agent bundle. |
+| `UZ-AGT-001` | 402 | Agent budget exceeded | Daily dollar budget hit. Raise `budget.daily_dollars` in `TRIGGER.md`. |
+| `UZ-AGT-002` | 500 | Agent agent timeout | Agent timed out processing an event. Check the activity stream. |
+| `UZ-AGT-003` | 424 | Agent credential missing | A required vault credential is absent. Add it with `agentsfleet credential add <name>`. |
+| `UZ-AGT-004` | 500 | Agent claim failed | Agent could not be claimed from the database. Verify the `agent_id` exists and status is `active`. |
+| `UZ-AGT-005` | 500 | Agent checkpoint failed | Session checkpoint write to Postgres failed. |
+| `UZ-AGT-006` | 409 | Agent name already exists | Name taken. Kill the existing agent first, then re-install. |
+| `UZ-AGT-008` | 400 | Invalid agent config | `TRIGGER.md` config_json fails schema validation. Verify trigger, tools, credentials, and budget fields. |
+| `UZ-AGT-009` | 404 | Agent not found | No agent with this ID in the workspace. |
+| `UZ-AGT-010` | 409 | Agent already stopped or killed | This agent is already stopped or killed. Re-install before issuing another stop. |
+| `UZ-AGT-011` | 400 | SKILL.md and TRIGGER.md disagree on `name:` | Top-level `name:` must match across both files. One identity per agent bundle. |
 
-<Note>`UZ-ZMB-007` is retired; oversized credential bodies now return [`UZ-VAULT-002`](#vault).</Note>
+<Note>`UZ-AGT-007` is retired; oversized credential bodies now return [`UZ-VAULT-002`](#vault).</Note>
 
 ## Integration grants
 
 | Code | HTTP | Title | Common Causes |
 |---|---|---|---|
-| `UZ-GRANT-001` | 403 | No integration grant for service | This agent has no approved grant for the target service. Request one with `POST /v1/zombies/{id}/integration-requests`. |
+| `UZ-GRANT-001` | 403 | No integration grant for service | This agent has no approved grant for the target service. Request one with `POST /v1/agents/{id}/integration-requests`. |
 | `UZ-GRANT-002` | 403 | Integration grant pending approval | A grant request for this service is pending human approval. Approve in Slack, Discord, or the dashboard. |
 | `UZ-GRANT-003` | 403 | Integration grant denied | The grant for this service was denied or revoked by the workspace owner. Re-request via the host agent. |
 
@@ -169,7 +169,7 @@ Every `4xx` and `5xx` response uses `Content-Type: application/problem+json`:
 
 ## Credentials
 
-These fire on the inference path — when the runner needs to call the model and can't resolve a usable LLM provider key. Not the same as workspace vault credentials your agent uses for `http_request` (those are [`UZ-VAULT-*`](#vault) and [`UZ-ZMB-003`](#agent)).
+These fire on the inference path — when the runner needs to call the model and can't resolve a usable LLM provider key. Not the same as workspace vault credentials your agent uses for `http_request` (those are [`UZ-VAULT-*`](#vault) and [`UZ-AGT-003`](#agent)).
 
 | Code | HTTP | Title | Common Causes |
 |---|---|---|---|
@@ -187,8 +187,8 @@ These fire on the inference path — when the runner needs to call the model and
 
 | Code | HTTP | Title | Common Causes |
 |---|---|---|---|
-| `UZ-MEM-001` | 403 | Memory scope denied | Cross-agent memory access attempted. Memory operations are scoped per `zombie_id`. |
-| `UZ-MEM-002` | 404 | Agent not found for memory op | The `zombie_id` on the memory call does not exist in the workspace. |
+| `UZ-MEM-001` | 403 | Memory scope denied | Cross-agent memory access attempted. Memory operations are scoped per `agent_id`. |
+| `UZ-MEM-002` | 404 | Agent not found for memory op | The `agent_id` on the memory call does not exist in the workspace. |
 | `UZ-MEM-003` | 503 | Memory backend unavailable | Memory store is unreachable. Retry the trigger; if persistent, file an issue. |
 
 ## Relay
@@ -201,7 +201,7 @@ These fire on the inference path — when the runner needs to call the model and
 
 | Code | HTTP | Title | Common Causes |
 |---|---|---|---|
-| `UZ-STARTUP-001` | 500 | Environment check failed | Required environment variables are missing. Run 'zombied doctor' to see which ones. |
+| `UZ-STARTUP-001` | 500 | Environment check failed | Required environment variables are missing. Run 'agentsfleetd doctor' to see which ones. |
 | `UZ-STARTUP-002` | 500 | Config load failed | Configuration failed to load. Check that all required env vars are set. |
 | `UZ-STARTUP-003` | 500 | Database connect failed | Database is unreachable. Check that DATABASE_URL is set and the database accepts connections. |
 | `UZ-STARTUP-004` | 500 | Redis connect failed | Redis is unreachable. Check that REDIS_URL_API is set. |
@@ -226,4 +226,4 @@ These fire on the inference path — when the runner needs to call the model and
 |---|---|---|---|
 | `UZ-SLACK-001` | 403 | Slack OAuth state invalid | OAuth state parameter mismatch — possible CSRF attempt. |
 | `UZ-SLACK-002` | 502 | Slack token exchange failed | Could not exchange OAuth code for bot token. Verify SLACK_CLIENT_SECRET is set. |
-| `UZ-SLACK-003` | 401 | Slack bot token expired | The Slack bot token has been revoked or expired. Reinstall usezombie to Slack. |
+| `UZ-SLACK-003` | 401 | Slack bot token expired | The Slack bot token has been revoked or expired. Reinstall agentsfleet to Slack. |
diff --git a/api-reference/introduction.mdx b/api-reference/introduction.mdx
index 742ed10..01bc395 100644
--- a/api-reference/introduction.mdx
+++ b/api-reference/introduction.mdx
@@ -1,12 +1,12 @@
 ---
 title: 'API Reference'
-description: 'usezombie Control Plane API — deploy, observe, and control agents programmatically.'
+description: 'agentsfleet Control Plane API — deploy, observe, and control agents programmatically.'
 ---
 
 ## Base URL
 
 ```
-https://api.usezombie.com
+https://api.agentsfleet.net
 ```
 
 ## Authentication
@@ -14,14 +14,14 @@ https://api.usezombie.com
 All API endpoints require a Bearer token in the `Authorization` header, except health checks and the initial auth session creation.
 
 ```bash
-curl https://api.usezombie.com/v1/workspaces/ws_abc/zombies \
-  -H "Authorization: Bearer $ZOMBIE_TOKEN"
+curl https://api.agentsfleet.net/v1/workspaces/0198a7b0-3c2d-7f14-9a08-1b6e4d2f8c50/agents \
+  -H "Authorization: Bearer $AGENTSFLEET_TOKEN"
 ```
 
 Two kinds of bearer token are accepted:
 
-- **Tenant API key (`zmb_t_…`)** — long-lived, for programmatic and service-to-service callers (CI, cron, integrations, scripts). Create one in the dashboard under **Settings → API keys**; the raw value is shown once. This is the right credential for calling the API directly.
-- **User JWT** — short-lived (~15 min), for an interactive human. Mint one with `zombiectl login`, a browser device flow with terminal-side verification. It can't be obtained by a bare API client — the flow needs the dashboard's browser leg — so for unattended access use a tenant API key.
+- **Tenant API key (`agt_t…`)** — long-lived, for programmatic and service-to-service callers (CI, cron, integrations, scripts). Create one in the dashboard under **Settings → API keys**; the raw value is shown once. This is the right credential for calling the API directly.
+- **User JWT** — short-lived (~15 min), for an interactive human. Mint one with `agentsfleet login`, a browser device flow with terminal-side verification. It can't be obtained by a bare API client — the flow needs the dashboard's browser leg — so for unattended access use a tenant API key.
 
 ## Errors
 
@@ -29,11 +29,11 @@ All errors use RFC 7807 problem detail (`Content-Type: application/problem+json`
 
 ```json
 {
-  "docs_uri": "https://docs.usezombie.com/api-reference/error-codes#UZ-WORKSPACE-001",
+  "docs_uri": "https://docs.agentsfleet.net/api-reference/error-codes#UZ-WORKSPACE-001",
   "title": "Workspace not found",
   "detail": "No workspace with the given ID exists.",
   "error_code": "UZ-WORKSPACE-001",
-  "request_id": "req_01JQ7K..."
+  "request_id": "0198a7b6-1f2a-7d53-8c94-2b7e5a1f9d40"
 }
 ```
 
@@ -43,7 +43,7 @@ Error codes follow the `UZ-<DOMAIN>-NNN` scheme in the `error_code` field. Every
 
 - **IDs** are UUIDv7.
 - **Timestamps** are Unix milliseconds.
-- **State transitions** are partial updates on the parent resource (e.g., `PATCH /v1/workspaces/{workspace_id}/zombies/{zombie_id}` with body `{status: "stopped"}`). Sub-resources (e.g., `/messages`, `/events`, `/events/stream`) handle data-flow operations.
+- **State transitions** are partial updates on the parent resource (e.g., `PATCH /v1/workspaces/{workspace_id}/agents/{agent_id}` with body `{status: "stopped"}`). Sub-resources (e.g., `/messages`, `/events`, `/events/stream`) handle data-flow operations.
 - **Streaming endpoints** (activity stream) return Server-Sent Events.
 
 ## Rate limits
@@ -53,7 +53,7 @@ API rate limits are per-workspace. If you hit a rate limit, the response include
 <Card
   title="OpenAPI Spec"
   icon="code"
-  href="https://raw.githubusercontent.com/usezombie/usezombie/main/public/openapi.json"
+  href="https://raw.githubusercontent.com/agentsfleet/agentsfleet/main/public/openapi.json"
 >
   View the full OpenAPI 3.1 specification
 </Card>
diff --git a/billing/budgets.mdx b/billing/budgets.mdx
index 1c6ebce..cb1f172 100644
--- a/billing/budgets.mdx
+++ b/billing/budgets.mdx
@@ -3,10 +3,10 @@ title: "Budgets and cost control"
 description: "Per-agent dollar ceilings, tenant-wide spend caps, and how debits work."
 ---
 
-usezombie enforces budgets at two levels: per-agent ceilings declared in `TRIGGER.md`, and a tenant-wide balance that every run debits against.
+agentsfleet enforces budgets at two levels: per-agent ceilings declared in `TRIGGER.md`, and a tenant-wide balance that every run debits against.
 
 <Note>
-  **Free until July 31, 2026.** During the launch trial, hosted execution is free — the tenant-wallet mechanics below apply **after** the trial. See [pricing](https://usezombie.com/pricing).
+  **Free until July 31, 2026.** During the launch trial, hosted execution is free — the tenant-wallet mechanics below apply **after** the trial. See [pricing](https://agentsfleet.net/pricing).
 </Note>
 
 ## Per-agent ceilings (`daily_dollars` / `monthly_dollars`)
@@ -32,18 +32,18 @@ Separately, your tenant has a single wallet (the $5 free credit at signup, toppe
 
 - The wallet is **tenant-scoped**, not workspace-scoped. All workspaces under your tenant share the same pool.
 - When the wallet hits **zero**, runs across all workspaces stop until the tenant tops up.
-- The wallet balance is visible in the dashboard header and via `zombiectl billing show`.
+- The wallet balance is visible in the dashboard header and via `agentsfleet billing show`.
 
-Set a monthly spend cap on your tenant from the billing page at [app.usezombie.com/billing](https://app.usezombie.com/billing).
+Set a monthly spend cap on your tenant from the billing page at [app.agentsfleet.net/billing](https://app.agentsfleet.net/billing).
 
-<Note>A `zombiectl billing budget set` CLI command is planned for a future release.</Note>
+<Note>A `agentsfleet billing budget set` CLI command is planned for a future release.</Note>
 
 ## Run cancellation
 
 Cancel an in-flight run at any time via CLI or API:
 
 ```bash
-zombiectl kill <zombie_id>
+agentsfleet kill <agent_id>
 ```
 
 Cancelling stops the run at the next lease renewal. The run time already elapsed is metered and debited — cancelling doesn't refund the work done so far. See [Credit deduction timing](#credit-deduction-timing) below for the full rule.
diff --git a/billing/plans.mdx b/billing/plans.mdx
index a2db1d3..889e321 100644
--- a/billing/plans.mdx
+++ b/billing/plans.mdx
@@ -3,10 +3,10 @@ title: "Plans"
 description: "One credit-based model — the starter credit and how per-second run billing works."
 ---
 
-usezombie has a single credit-based model. Every tenant gets the full platform — always-on agent hosting, the tool bridge, activity stream, webhook ingestion, kill switch — and pays from one shared credit wallet. There are no tiers to choose between or upgrade to.
+agentsfleet has a single credit-based model. Every tenant gets the full platform — always-on agent hosting, the tool bridge, activity stream, webhook ingestion, kill switch — and pays from one shared credit wallet. There are no tiers to choose between or upgrade to.
 
 <Note>
-  **Free until July 31, 2026.** During the launch trial, hosted execution — every event receipt and run — is free. The billing details below describe charging **after** the trial. See [pricing](https://usezombie.com/pricing).
+  **Free until July 31, 2026.** During the launch trial, hosted execution — every event receipt and run — is free. The billing details below describe charging **after** the trial. See [pricing](https://agentsfleet.net/pricing).
 </Note>
 
 ## Starter credit
@@ -29,4 +29,4 @@ Run time is metered by the second: each background lease renewal debits the elap
 
 ## Topping up
 
-When the wallet runs low, top up at [app.usezombie.com/billing](https://app.usezombie.com/billing). Top-ups and payment-method updates happen via the dashboard, not the CLI — the CLI surface is `zombiectl billing show` for read-only balance and charge history. Top-ups apply to the tenant, not an individual workspace — the wallet follows the tenant.
+When the wallet runs low, top up at [app.agentsfleet.net/billing](https://app.agentsfleet.net/billing). Top-ups and payment-method updates happen via the dashboard, not the CLI — the CLI surface is `agentsfleet billing show` for read-only balance and charge history. Top-ups apply to the tenant, not an individual workspace — the wallet follows the tenant.
diff --git a/changelog.mdx b/changelog.mdx
index 412a11b..2c1bc3f 100644
--- a/changelog.mdx
+++ b/changelog.mdx
@@ -1,6 +1,6 @@
 ---
 title: "Changelog"
-description: "Stay up to date with the latest usezombie product updates, new features, platform improvements, and bug fixes."
+description: "Stay up to date with the latest agentsfleet product updates, new features, platform improvements, and bug fixes."
 ---
 
 import { STARTER_CREDIT, EVENT_RATE } from "/snippets/rates.mdx";
@@ -19,9 +19,43 @@ export const STAGE_PLATFORM_M66 = "$0.001";
 export const STAGE_SELF_MANAGED_M66 = "$0.0001";
 
 <Tip>
-  usezombie is in **stealth-mode testing** and pre-production. APIs and agent behavior may change between releases without long deprecation windows. Email [usezombie@agentmail.to](mailto:usezombie@agentmail.to) if you want a hand calibrating an agent or to join as a design partner.
+  agentsfleet is in **stealth-mode testing** and pre-production. APIs and agent behavior may change between releases without long deprecation windows. Email [agentsfleet@agentmail.to](mailto:agentsfleet@agentmail.to) if you want a hand calibrating an agent or to join as a design partner.
 </Tip>
 
+<Update label="Jun 15, 2026" tags={["Breaking", "What's new", "API", "CLI"]}>
+  ## The product is now agentsfleet
+
+  usezombie is now **agentsfleet**. Every operator-facing name moved together: the CLI is `agentsfleet`, the API answers on `api.agentsfleet.net`, the dashboard on `app.agentsfleet.net`, and the install one-liner lives at `agentsfleet.dev`. The durable, event-woken worker the API exposes is now uniformly an **agent** across routes, wire fields, error codes, and config — existing data is untouched, the surfaces around it were renamed.
+
+  ## Upgrading
+
+  A hard cutover with no compatibility shims — the CLI and server must move together.
+
+  - **Reinstall the CLI** — `zombiectl` is now `agentsfleet`. Reinstall from `https://agentsfleet.dev`, or `npm i -g @agentsfleet/cli` in place of `@usezombie/zombiectl`. Config moves from `~/.config/zombiectl` to `~/.config/agentsfleet`, and the CLI re-asks telemetry consent once on first run.
+  - **Repoint API hosts** — `api.usezombie.com` becomes `api.agentsfleet.net` (dev: `api-dev.agentsfleet.net`). Any pinned base URL must change.
+  - **Rename environment variables** — every `ZOMBIE_*` variable is now `AGENTSFLEET_*`. The old names are no longer read; a process started with a legacy `ZOMBIE_*` value logs a loud diagnostic and ignores it.
+  - **Update routes and wire fields** — `…/zombies/{zombie_id}/…` is now `…/agents/{agent_id}/…`, and the `zombie_id` field is `agent_id`. The `/agents` collection replaces `/zombies`.
+  - **Re-read entity error codes** — `UZ-ZMB-*` codes are now `UZ-AGT-*` (a 404 on a missing agent is `UZ-AGT-009`). `UZ-AUTH-*` codes are unchanged.
+  - **Re-mint raw tokens** — prefixes are now role-symmetric: agent keys start `agt_a` (was `zmb_a`), tenant API keys `agt_t` (was `zmb_t`), runner tokens `agt_r` (was `zmb_r`). Tokens minted under the old prefixes no longer validate.
+
+  ## What's new
+
+  - **One brand, end to end** — README, dashboard, CLI, container images (`ghcr.io/agentsfleet/agentsfleetd`), and runner metrics (`agentsfleet_runner_*`) all read agentsfleet.
+  - **Agent keys are their own credential** — a workspace-scoped key (`agt_a…`) carries its own `agent_key_id`, distinct from the `agent_id` it acts against, managed under `/v1/workspaces/{workspace_id}/agent-keys` and `agentsfleet agent-key …`.
+
+  ## API reference
+
+  ```http
+  GET /v1/workspaces/{workspace_id}/agents/{agent_id}
+  → 200 { "agent_id": "…", "agent_slug": "…", … }
+  → 404 { "error_code": "UZ-AGT-009", … }
+  ```
+
+  ## CLI
+
+  - **`agentsfleet`** replaces `zombiectl`; subcommand shapes are unchanged. `agentsfleet agent-key add|list|delete` manages workspace agent keys.
+</Update>
+
 <Update label="Jun 12, 2026" tags={["What's new", "Breaking", "API"]}>
   ## Scratch memories now expire on their own
 
@@ -1047,7 +1081,7 @@ export const STAGE_SELF_MANAGED_M66 = "$0.0001";
   2. **SKILL.md** — frontmatter needs `name:`, `description:`, `version:`. Match `name:` to TRIGGER.md.
   3. **`zombiectl install --from <dir>`** — re-run until field-level errors clear.
 
-  See [Authoring skills](/zombies/authoring) for the canonical shape.
+  See [Authoring skills](/agents/authoring) for the canonical shape.
 
   ## What's new
 
@@ -1287,7 +1321,7 @@ export const STAGE_SELF_MANAGED_M66 = "$0.0001";
   ## What's new
 
   - **New quickstart** — sign up → dashboard → create agent → copy webhook → `curl` trigger → verify credit debit. One page, end-to-end.
-  - **New CLI reference** at [`/cli/zombiectl`](/cli/zombiectl).
+  - **New CLI reference** at [`/cli/agentsfleet`](/cli/agentsfleet).
   - **Self-hosting section** under `/operator` — _(removed in M51 prep when self-host was deferred to v3; see [`usezombie/usezombie:docs/architecture/`](https://github.com/usezombie/usezombie/tree/main/docs/architecture) for the canonical reference)_.
   - **Concepts page** — four nouns (tenant, workspace, agent, skill) + tenant-scoped credit model.
   - **Billing pages** — rewritten around single-wallet, multi-workspace.
@@ -1374,15 +1408,15 @@ export const STAGE_SELF_MANAGED_M66 = "$0.0001";
 <Update label="Apr 19, 2026" tags={["Improvements", "CLI"]}>
   ## Agent lifecycle is the unified product model
 
-  The CLI and API now speak one language: `zombiectl install → up → status → logs → kill`. `zombiectl --help` is shorter, the API surface is tighter, and the docs, product, and code all describe the same thing. See [Agents](/zombies/overview).
+  The CLI and API now speak one language: `zombiectl install → up → status → logs → kill`. `zombiectl --help` is shorter, the API surface is tighter, and the docs, product, and code all describe the same thing. See [Agents](/agents/overview).
 </Update>
 
 <Update label="Apr 18, 2026" tags={["Docs"]}>
   ## Docs reshaped around the agent lifecycle
 
-  A new [Agents](/zombies/overview) section walks through installing a template, adding credentials, running, observing, and killing an agent. Pages describing the legacy v1 pipeline have been retired; the old `/specs/*` and `/runs/*` URLs now 404.
+  A new [Agents](/agents/overview) section walks through installing a template, adding credentials, running, observing, and killing an agent. Pages describing the legacy v1 pipeline have been retired; the old `/specs/*` and `/runs/*` URLs now 404.
 
-  New pages: [overview](/zombies/overview), [install](/zombies/install), [running](/zombies/running), [credentials](/zombies/credentials), [webhooks](/zombies/webhooks), [skills](/zombies/authoring), [templates](/zombies/templates).
+  New pages: [overview](/agents/overview), [install](/agents/install), [running](/agents/running), [credentials](/agents/credentials), [webhooks](/agents/webhooks), [skills](/agents/authoring), [templates](/agents/templates).
 </Update>
 
 <Update label="Apr 18, 2026" tags={["New", "API", "Security"]}>
@@ -1398,7 +1432,7 @@ export const STAGE_SELF_MANAGED_M66 = "$0.0001";
 
   Every per-agent webhook flows through one fail-closed middleware that handles URL-embedded secrets, Bearer tokens, HMAC signatures, and Svix multi-signature rotation with constant-time comparisons.
 
-  Seven providers ship first-class: **agentmail**, **Grafana**, **Slack**, **GitHub**, **Linear**, **Jira**, and **Clerk** (via Svix). Onboarding takes one field in `TRIGGER.md`; secrets are workspace-vaulted and rotate without an agent redeploy. See [Webhooks](/zombies/webhooks).
+  Seven providers ship first-class: **agentmail**, **Grafana**, **Slack**, **GitHub**, **Linear**, **Jira**, and **Clerk** (via Svix). Onboarding takes one field in `TRIGGER.md`; secrets are workspace-vaulted and rotate without an agent redeploy. See [Webhooks](/agents/webhooks).
 </Update>
 
 <Update label="Apr 16, 2026" tags={["New", "API", "UI"]}>
diff --git a/cli/zombiectl.mdx b/cli/agentsfleet.mdx
similarity index 50%
rename from cli/zombiectl.mdx
rename to cli/agentsfleet.mdx
index dd2391a..bb00160 100644
--- a/cli/zombiectl.mdx
+++ b/cli/agentsfleet.mdx
@@ -1,6 +1,6 @@
 ---
 title: "Command reference"
-description: "Complete zombiectl command reference."
+description: "Complete agentsfleet command reference."
 ---
 
 ## Overview
@@ -22,63 +22,63 @@ Every command accepts the [global flags](/cli/flags). Every command that returns
 
 ## Authentication
 
-### `zombiectl login`
+### `agentsfleet login`
 
 Authenticate via a Clerk-backed browser device flow with terminal-side verification. Opens your default browser to the approval page; on Approve, the page displays a 6-digit verification code which you type back into the CLI to complete login. The verification code binds the browser approver to the terminal user — phishing the URL alone is not enough to mint a credential.
 
 ```bash
-zombiectl login
+agentsfleet login
 ```
 
 ```bash
 # Label this device for visibility in `auth status` and on the approval page
-zombiectl login --token-name "kishore-macbook"
+agentsfleet login --token-name "kishore-macbook"
 ```
 
 ```bash
 # Non-interactive (CI, scripts): supply a token instead of the browser flow
-ZOMBIE_TOKEN="$MY_TOKEN" zombiectl login
+AGENTSFLEET_TOKEN="$MY_TOKEN" agentsfleet login
 # …or pipe it so it never lands in shell history
-printf '%s' "$MY_TOKEN" | zombiectl login
+printf '%s' "$MY_TOKEN" | agentsfleet login
 ```
 
-After the token persists, `login` also fetches `GET /v1/tenants/me/workspaces` and writes the first workspace into local state as `current_workspace_id`. Signup auto-provisions a default workspace, so a fresh `npm i -g @usezombie/zombiectl && zombiectl login` is enough to reach `zombiectl doctor` green — `workspace add` is only needed if you want a second or custom-named workspace, or if the workspace fetch failed (login still exits 0 in that case).
+After the token persists, `login` also fetches `GET /v1/tenants/me/workspaces` and writes the first workspace into local state as `current_workspace_id`. Signup auto-provisions a default workspace, so a fresh `npm i -g @agentsfleet/cli && agentsfleet login` is enough to reach `agentsfleet doctor` green — `workspace add` is only needed if you want a second or custom-named workspace, or if the workspace fetch failed (login still exits 0 in that case).
 
 Flags:
 
-- `--token <token>` — authenticate non-interactively with a token directly, skipping the browser entirely; the token is validated against the server and persisted. Prefer the `ZOMBIE_TOKEN` env var or piping the token on stdin to keep it out of your shell history. `--token-name` is ignored for any non-browser token source — `--token`, the `ZOMBIE_TOKEN` env var, or piped stdin — since there's no browser session to label.
-- `--token-name <label>` — human-readable device label persisted alongside the token. Defaults to your platform family (`macos-cli`, `linux-cli`, `windows-cli`). Shows up on the dashboard approval page (so you know which terminal you're approving for) and in `zombiectl auth status`.
+- `--token <token>` — authenticate non-interactively with a token directly, skipping the browser entirely; the token is validated against the server and persisted. Prefer the `AGENTSFLEET_TOKEN` env var or piping the token on stdin to keep it out of your shell history. `--token-name` is ignored for any non-browser token source — `--token`, the `AGENTSFLEET_TOKEN` env var, or piped stdin — since there's no browser session to label.
+- `--token-name <label>` — human-readable device label persisted alongside the token. Defaults to your platform family (`macos-cli`, `linux-cli`, `windows-cli`). Shows up on the dashboard approval page (so you know which terminal you're approving for) and in `agentsfleet auth status`.
 - `--no-open` — print the auth URL instead of opening a browser automatically.
 - `--force` — skip the "you're already logged in as `<name>`, replace?" prompt.
-- `--no-input` — fail fast instead of prompting for the verification code. Supply a token non-interactively via `--token`, the `ZOMBIE_TOKEN` env var, or piped stdin.
+- `--no-input` — fail fast instead of prompting for the verification code. Supply a token non-interactively via `--token`, the `AGENTSFLEET_TOKEN` env var, or piped stdin.
 
-`zombiectl login` resolves a token in priority order — the `--token` flag, then the `ZOMBIE_TOKEN` environment variable, then a token piped on stdin — and falls back to the browser device flow only on an interactive terminal with none of those set. A non-interactive shell (`--no-input`, or no terminal) with no token exits immediately with an error instructing you to supply one via `--token`, `ZOMBIE_TOKEN`, or piped stdin — the verification code can't be entered without a terminal.
+`agentsfleet login` resolves a token in priority order — the `--token` flag, then the `AGENTSFLEET_TOKEN` environment variable, then a token piped on stdin — and falls back to the browser device flow only on an interactive terminal with none of those set. A non-interactive shell (`--no-input`, or no terminal) with no token exits immediately with an error instructing you to supply one via `--token`, `AGENTSFLEET_TOKEN`, or piped stdin — the verification code can't be entered without a terminal.
 
-The login session lives 5 minutes; an unfinished approval expires automatically. The verification code's 6-digit shape is checked locally before it's sent, so a typo just re-prompts. Wrong (but well-formed) code attempts cap at 5 per session — a sixth wrong code aborts the session and you re-run `zombiectl login`.
+The login session lives 5 minutes; an unfinished approval expires automatically. The verification code's 6-digit shape is checked locally before it's sent, so a typo just re-prompts. Wrong (but well-formed) code attempts cap at 5 per session — a sixth wrong code aborts the session and you re-run `agentsfleet login`.
 
-### `zombiectl logout`
+### `agentsfleet logout`
 
-Removes local credentials (`~/.config/zombiectl/credentials.json`) and aborts any in-flight `zombiectl login` flows you have pending.
+Removes local credentials (`~/.config/agentsfleet/credentials.json`) and aborts any in-flight `agentsfleet login` flows you have pending.
 
 ```bash
-zombiectl logout
+agentsfleet logout
 ```
 
-Does **NOT** revoke your active session token — JWTs are short-lived (~15 min) and expire on their own. Does **NOT** touch the `ZOMBIE_TOKEN` environment variable — if it's set, subsequent commands continue to use that token until you unset it.
+Does **NOT** revoke your active session token — JWTs are short-lived (~15 min) and expire on their own. Does **NOT** touch the `AGENTSFLEET_TOKEN` environment variable — if it's set, subsequent commands continue to use that token until you unset it.
 
-### `zombiectl auth status`
+### `agentsfleet auth status`
 
-Inspect the stored credential without re-authenticating. Resolves the token source (file vs `ZOMBIE_TOKEN` env vs none), decodes the JWT claims (`iss`, `aud`, `sub`, `metadata.tenant_id`, `metadata.role`, `exp`), surfaces the `token_name` label persisted at login, and probes `GET /v1/tenants/me/billing` to check the token is still accepted by the server.
+Inspect the stored credential without re-authenticating. Resolves the token source (file vs `AGENTSFLEET_TOKEN` env vs none), decodes the JWT claims (`iss`, `aud`, `sub`, `metadata.tenant_id`, `metadata.role`, `exp`), surfaces the `token_name` label persisted at login, and probes `GET /v1/tenants/me/billing` to check the token is still accepted by the server.
 
 ```bash
-zombiectl auth status
-zombiectl auth status --json
+agentsfleet auth status
+agentsfleet auth status --json
 ```
 
 Exit codes:
 
 - `0` — token valid, or server unreachable (transient API issues don't poison local state).
-- `1` — no credentials configured, or the server rejected the token (`UZ-AUTH-001` / `UZ-AUTH-002` / `TOKEN_EXPIRED`). Re-run `zombiectl login`.
+- `1` — no credentials configured, or the server rejected the token (`UZ-AUTH-001` / `UZ-AUTH-002` / `TOKEN_EXPIRED`). Re-run `agentsfleet login`.
 
 The probe result is one of `valid` (200 from the billing endpoint), `unauthorized` (server rejected), or `unreachable` (network / 5xx). `unreachable` is informational — the local token is unchanged.
 
@@ -86,22 +86,22 @@ The probe result is one of `valid` (200 from the billing endpoint), `unauthorize
 
 ## Agents
 
-### `zombiectl install --from <path>`
+### `agentsfleet install --from <path>`
 
-Reads `SKILL.md` and `TRIGGER.md` from `<path>`, validates them, and uploads to the active workspace. The two markdown files are the configuration; the `usezombie-install-platform-ops` host-agent skill is what generates them under `.usezombie/<zombie>/` in your repo. The `--from` flag is required — there are no bare-name template aliases.
+Reads `SKILL.md` and `TRIGGER.md` from `<path>`, validates them, and uploads to the active workspace. The two markdown files are the configuration; the `agentsfleet-install-platform-ops` host-agent skill is what generates them under `.agentsfleet/<agent>/` in your repo. The `--from` flag is required — there are no bare-name template aliases.
 
 ```bash
-zombiectl install --from ~/.config/usezombie/samples/platform-ops
+agentsfleet install --from ~/.config/agentsfleet/samples/platform-ops
 ```
 
-The `samples/` directory ships with `zombiectl` and contains the flagship `platform-ops` sample. The host-agent install skill (`/usezombie-install-platform-ops`) drives this command under the hood. See [Quickstart](/quickstart) and [Templates](/zombies/templates).
+The `samples/` directory ships with `agentsfleet` and contains the flagship `platform-ops` sample. The host-agent install skill (`/agentsfleet-install-platform-ops`) drives this command under the hood. See [Quickstart](/quickstart) and [Templates](/agents/templates).
 
-### `zombiectl list`
+### `agentsfleet list`
 
-List agents in the active workspace. Keyset-paginated over `(created_at, id)` — the dashboard `/zombies` page uses the same contract.
+List agents in the active workspace. Keyset-paginated over `(created_at, id)` — the dashboard `/agents` page uses the same contract.
 
 ```bash
-zombiectl list --limit 20
+agentsfleet list --limit 20
 ```
 
 | Flag | Default | Purpose |
@@ -113,12 +113,12 @@ zombiectl list --limit 20
 
 Human-readable output prints a table and, when more pages remain, a "Next" hint with the exact cursor to pass back.
 
-### `zombiectl status`
+### `agentsfleet status`
 
 List every agent in the current workspace with state, events processed, and budget consumed.
 
 ```bash
-zombiectl status
+agentsfleet status
 ```
 
 ### Agent lifecycle: `stop` / `resume` / `kill` / `delete`
@@ -127,28 +127,28 @@ Four verbs control an agent's lifecycle, in increasing order of irreversibility:
 
 | Verb | What it does | Reversible? |
 |---|---|---|
-| `stop <zombie_id>` | Halt the running session. New events stop dispatching; in-flight run finishes cleanly. | Yes — `zombiectl resume`. |
-| `resume <zombie_id>` | Resume from `stopped` or auto-paused state. | — |
-| `kill <zombie_id>` | Mark terminal. The agent won't process events again, but its row, history, and webhook URL persist. | No, but the agent can be `delete`d after. |
-| `delete <zombie_id>` | Hard-delete. Removes the agent row and its webhook URL. **Must `kill` first.** | No. |
+| `stop <agent_id>` | Halt the running session. New events stop dispatching; in-flight run finishes cleanly. | Yes — `agentsfleet resume`. |
+| `resume <agent_id>` | Resume from `stopped` or auto-paused state. | — |
+| `kill <agent_id>` | Mark terminal. The agent won't process events again, but its row, history, and webhook URL persist. | No, but the agent can be `delete`d after. |
+| `delete <agent_id>` | Hard-delete. Removes the agent row and its webhook URL. **Must `kill` first.** | No. |
 
 ```bash
-zombiectl stop   zmb_2041   # pause; resumable
-zombiectl resume zmb_2041   # back to active
-zombiectl kill   zmb_2041   # terminal; webhook still 200s but routes nowhere new
-zombiectl delete zmb_2041   # hard-delete; webhook URL starts returning UZ-WH-001
+agentsfleet stop   0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71   # pause; resumable
+agentsfleet resume 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71   # back to active
+agentsfleet kill   0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71   # terminal; webhook still 200s but routes nowhere new
+agentsfleet delete 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71   # hard-delete; webhook URL starts returning UZ-WH-001
 ```
 
 State is checkpointed at every transition — nothing on the activity stream is lost until the final `delete`.
 
-### `zombiectl logs <zombie_id>`
+### `agentsfleet logs <agent_id>`
 
 Print the agent's recent activity stream — newest-first, paginated.
 
 ```bash
-zombiectl logs zmb_2041
-zombiectl logs zmb_2041 --limit 50 --cursor <next_cursor>
-zombiectl logs zmb_2041 --json
+agentsfleet logs 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71
+agentsfleet logs 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71 --limit 50 --cursor <next_cursor>
+agentsfleet logs 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71 --json
 ```
 
 | Flag | Default | Purpose |
@@ -157,16 +157,16 @@ zombiectl logs zmb_2041 --json
 | `--cursor <cursor>` | *(none)* | Pagination cursor returned as `next_cursor` in a previous response. |
 | `--json` | off | Emit the raw `{ items, next_cursor }` envelope. |
 
-The agent ID may also be passed via `--zombie <id>` for scripting symmetry with `events`.
+The agent ID may also be passed via `--agent <id>` for scripting symmetry with `events`.
 
-### `zombiectl events <zombie_id>` — filtered history
+### `agentsfleet events <agent_id>` — filtered history
 
-Richer filter surface than `logs`. Use this when you need to slice by actor or time window — for example, when [troubleshooting](/zombies/troubleshooting) a specific webhook source.
+Richer filter surface than `logs`. Use this when you need to slice by actor or time window — for example, when [troubleshooting](/agents/troubleshooting) a specific webhook source.
 
 ```bash
-zombiectl events zmb_2041 --actor 'webhook:*' --since 2h
-zombiectl events zmb_2041 --actor 'steer:*' --since 7d --limit 100
-zombiectl events zmb_2041 --json | jq 'select(.error)'
+agentsfleet events 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71 --actor 'webhook:*' --since 2h
+agentsfleet events 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71 --actor 'steer:*' --since 7d --limit 100
+agentsfleet events 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71 --json | jq 'select(.error)'
 ```
 
 | Flag | Default | Purpose |
@@ -179,15 +179,15 @@ zombiectl events zmb_2041 --json | jq 'select(.error)'
 
 There is no `--follow`/streaming-tail flag today. To watch live, poll `events --since 30s` from a script.
 
-### `zombiectl steer <zombie_id> [message]`
+### `agentsfleet steer <agent_id> [message]`
 
 Post a steer message — a manual trigger that uses the same reasoning loop as a webhook event. Useful for ad-hoc investigation or before a webhook is wired up.
 
 ```bash
-zombiectl steer zmb_2041
-zombiectl steer zmb_2041 "morning health check — anything red?"
-echo "check the latest deploy event" | zombiectl steer zmb_2041
-printf "check the latest deploy event\ncheck memory usage\n" | zombiectl steer zmb_2041 --tty
+agentsfleet steer 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71
+agentsfleet steer 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71 "morning health check — anything red?"
+echo "check the latest deploy event" | agentsfleet steer 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71
+printf "check the latest deploy event\ncheck memory usage\n" | agentsfleet steer 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71 --tty
 ```
 
 | Flag | Default | Purpose |
@@ -195,9 +195,9 @@ printf "check the latest deploy event\ncheck memory usage\n" | zombiectl steer z
 | `--tty` | *(auto on TTY)* | Force the interactive REPL even when stdin is piped — each line is a separate turn; exits at end-of-file. |
 | `--json` | off | Emit the steer result as JSON. |
 
-When you invoke `zombiectl steer <zombie_id>` from a terminal (TTY) and omit the message, `zombiectl` opens a read-eval-print loop (REPL). Each submitted line posts one steer message, streams the reply, then returns to the prompt. Press `Ctrl-D` to exit cleanly, or `Ctrl-C` to cancel the active stream and exit.
+When you invoke `agentsfleet steer <agent_id>` from a terminal (TTY) and omit the message, `agentsfleet` opens a read-eval-print loop (REPL). Each submitted line posts one steer message, streams the reply, then returns to the prompt. Press `Ctrl-D` to exit cleanly, or `Ctrl-C` to cancel the active stream and exit.
 
-Explicit messages stay single-shot, even from a terminal. Piped input also stays single-shot by default so automation and agents can continue invoking the command once per turn. Add `--tty` to force the REPL over piped input; `zombiectl` exits when the pipe reaches end-of-file.
+Explicit messages stay single-shot, even from a terminal. Piped input also stays single-shot by default so automation and agents can continue invoking the command once per turn. Add `--tty` to force the REPL over piped input; `agentsfleet` exits when the pipe reaches end-of-file.
 
 The reply streams back live; the result also persists to the activity stream for replay.
 
@@ -205,87 +205,87 @@ The reply streams back live; the result also persists to the activity stream for
 
 ## Credentials
 
-### `zombiectl credential add <name> --data=@-`
+### `agentsfleet credential add <name> --data=@-`
 
 Store a JSON-shaped secret in the current workspace vault. The agent references it by name from `TRIGGER.md`.
 
 Always pipe JSON on stdin via `--data=@-`. Never pass it inline as `--data='{...}'` — that puts the secret in shell history and process argv:
 
 ```bash
-zombiectl credential add github --data=@- <<'JSON'
+agentsfleet credential add github --data=@- <<'JSON'
 { "api_token": "ghp_...", "webhook_secret": "<32-byte hex>" }
 JSON
 ```
 
 Default behaviour is skip-if-exists. Use `--force` to overwrite for rotation.
 
-See [Workspace credentials](/zombies/credentials) for the full vault model.
+See [Workspace credentials](/agents/credentials) for the full vault model.
 
-### `zombiectl credential show <name>`
+### `agentsfleet credential show <name>`
 
 Print metadata (created, last-rotated). **Values are never returned.**
 
-### `zombiectl credential delete <name>`
+### `agentsfleet credential delete <name>`
 
-Remove a credential from the workspace vault. Any agent still referencing it will fail with `UZ-ZMB-003` (credential missing) on the next event until you re-add it (or update `TRIGGER.md`). See [Error codes](/api-reference/error-codes).
+Remove a credential from the workspace vault. Any agent still referencing it will fail with `UZ-AGT-003` (credential missing) on the next event until you re-add it (or update `TRIGGER.md`). See [Error codes](/api-reference/error-codes).
 
-### `zombiectl credential list`
+### `agentsfleet credential list`
 
 List credential names and creation timestamps in the current workspace. Values are never returned.
 
 ```bash
-zombiectl credential list
+agentsfleet credential list
 ```
 
 ---
 
 ## Workspaces
 
-### `zombiectl workspace add [name]`
+### `agentsfleet workspace add [name]`
 
 Create a new workspace under the current tenant and set it as active. The optional positional `name` is a human label; if omitted, the server picks a default. There is no repo URL — workspaces are not bound to a specific GitHub repo at creation time.
 
 ```bash
-zombiectl workspace add                       # server-assigned name
-zombiectl workspace add my-platform-ops       # named workspace
+agentsfleet workspace add                       # server-assigned name
+agentsfleet workspace add my-platform-ops       # named workspace
 ```
 
-Returns the new `workspace_id` and persists it as `current_workspace_id` in `~/.config/zombiectl/workspaces.json`. Subsequent commands use it by default.
+Returns the new `workspace_id` and persists it as `current_workspace_id` in `~/.config/agentsfleet/workspaces.json`. Subsequent commands use it by default.
 
-### `zombiectl workspace list`
+### `agentsfleet workspace list`
 
 List all configured workspaces with an active marker.
 
 ```bash
-zombiectl workspace list
+agentsfleet workspace list
 ```
 
-### `zombiectl workspace use <id>`
+### `agentsfleet workspace use <id>`
 
-Set the active workspace persistently. Writes `current_workspace_id` to `~/.config/zombiectl/workspaces.json`; every subsequent command that accepts `--workspace-id` defaults to this value when the flag is omitted.
+Set the active workspace persistently. Writes `current_workspace_id` to `~/.config/agentsfleet/workspaces.json`; every subsequent command that accepts `--workspace-id` defaults to this value when the flag is omitted.
 
 ```bash
-zombiectl workspace use ws_abc123
+agentsfleet workspace use 0198a7b0-3c2d-7f14-9a08-1b6e4d2f8c50
 ```
 
-Errors out if the id isn't in the local list (run `zombiectl workspace list` first). The dashboard's own `active_workspace_id` cookie and the CLI config are independent — switching one does not affect the other. See [Workspaces overview](/workspaces/overview).
+Errors out if the id isn't in the local list (run `agentsfleet workspace list` first). The dashboard's own `active_workspace_id` cookie and the CLI config are independent — switching one does not affect the other. See [Workspaces overview](/workspaces/overview).
 
-### `zombiectl workspace show`
+### `agentsfleet workspace show`
 
 Show the active workspace (or a specific one via `--workspace-id`) — mirrors the dashboard **Settings** page.
 
 ```bash
-zombiectl workspace show
+agentsfleet workspace show
 ```
 
 Prints the workspace's `workspace_id`, `name`, `created_at`, and active marker. Use `--json` for scripting.
 
-### `zombiectl workspace delete <id>`
+### `agentsfleet workspace delete <id>`
 
-Delete a workspace and everything in it. Stops accepting new events immediately, lets in-flight runs finish, retains run history for 30 days. Cannot be undone — recreating a workspace produces a fresh `workspace_id` and fresh `zombie_id`s, so any upstream webhooks pointing at the old workspace's agents need to be re-wired.
+Delete a workspace and everything in it. Stops accepting new events immediately, lets in-flight runs finish, retains run history for 30 days. Cannot be undone — recreating a workspace produces a fresh `workspace_id` and fresh `agent_id`s, so any upstream webhooks pointing at the old workspace's agents need to be re-wired.
 
 ```bash
-zombiectl workspace delete ws_abc123
+agentsfleet workspace delete 0198a7b0-3c2d-7f14-9a08-1b6e4d2f8c50
 ```
 
 ---
@@ -294,30 +294,30 @@ zombiectl workspace delete ws_abc123
 
 External agents are API-key–authenticated callers (LangGraph, CrewAI, Composio, your own code) that drive a specific agent programmatically.
 
-### `zombiectl agent add`
+### `agentsfleet agent add`
 
 Mint an API key bound to one agent.
 
 ```bash
-zombiectl agent add --workspace ws_abc --zombie zm_xyz --name my-agent
+agentsfleet agent add --workspace 0198a7b0-3c2d-7f14-9a08-1b6e4d2f8c50 --agent 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71 --name my-agent
 ```
 
-The raw key (`zmb_…`) is returned **once**; store it in your secret manager.
+The raw key (`agt_a…`) is returned **once**; store it in your secret manager.
 
-### `zombiectl agent list`
+### `agentsfleet agent list`
 
 List every external agent key in a workspace.
 
 ```bash
-zombiectl agent list --workspace ws_abc
+agentsfleet agent list --workspace 0198a7b0-3c2d-7f14-9a08-1b6e4d2f8c50
 ```
 
-### `zombiectl agent delete <agent-id>`
+### `agentsfleet agent delete <agent-key-id>`
 
 Revoke an external agent key.
 
 ```bash
-zombiectl agent delete --workspace ws_abc ag_01JABC...
+agentsfleet agent delete --workspace 0198a7b0-3c2d-7f14-9a08-1b6e4d2f8c50 0198a7b4-6e1a-7c93-b052-8f3d2a1e7c46
 ```
 
 ---
@@ -326,35 +326,35 @@ zombiectl agent delete --workspace ws_abc ag_01JABC...
 
 Integration grants are per-agent permissions to reach a third-party service (Slack workspace, GitHub repo) that the agent requested interactively.
 
-### `zombiectl grant list --zombie <id>`
+### `agentsfleet grant list --agent <id>`
 
 List pending and approved grants for an agent.
 
 ```bash
-zombiectl grant list --zombie zm_01JABC...
+agentsfleet grant list --agent 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71
 ```
 
-### `zombiectl grant delete --zombie <id> <grant-id>`
+### `agentsfleet grant delete --agent <id> <grant-id>`
 
 Revoke a granted integration. Further attempts by the agent to reach that integration fail with `UZ-GRANT-003`.
 
 ```bash
-zombiectl grant delete --zombie zm_01JABC... gr_01JXYZ...
+agentsfleet grant delete --agent 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71 0198a7b4-2b5c-7d18-8f63-4e9a1c7d3b20
 ```
 
 ---
 
 ## Billing
 
-### `zombiectl billing show`
+### `agentsfleet billing show`
 
 Show the tenant's wallet balance and recent charges. Tenant-scoped (the wallet is tenant-level), not per-workspace.
 
 ```bash
-zombiectl billing show
-zombiectl billing show --limit 50
-zombiectl billing show --cursor <next_cursor>
-zombiectl billing show --json
+agentsfleet billing show
+agentsfleet billing show --limit 50
+agentsfleet billing show --cursor <next_cursor>
+agentsfleet billing show --json
 ```
 
 | Flag | Default | Purpose |
@@ -363,59 +363,59 @@ zombiectl billing show --json
 | `--cursor <cursor>` | *(none)* | Pagination cursor from a previous response. |
 | `--json` | off | Emit raw JSON for scripting. |
 
-For per-agent spend breakdowns, use `zombiectl logs <zombie_id> --json` and aggregate the `tokens` / `wall_ms` fields client-side. Top-ups and payment-method updates happen at [app.usezombie.com/billing](https://app.usezombie.com/billing).
+For per-agent spend breakdowns, use `agentsfleet logs <agent_id> --json` and aggregate the `tokens` / `wall_ms` fields client-side. Top-ups and payment-method updates happen at [app.agentsfleet.net/billing](https://app.agentsfleet.net/billing).
 
 ---
 
 ## Tenant provider
 
-By default your tenant runs on **platform-managed** inference — usezombie holds a Fireworks key for Kimi K2.6 and bills you for the tokens at retail rate, bundled into the run charge. You can flip the tenant to **self-managed** at any time: store your own provider credential (Anthropic, OpenAI, Fireworks, Together, Groq, Moonshot, OpenRouter) in the vault under a name you choose, then point the tenant at it. On self-managed runs the per-second run fee still applies, but there is no added per-token cost from usezombie — you pay your provider directly. See [pricing](https://agentsfleet.net/#pricing) for current rates.
+By default your tenant runs on **platform-managed** inference — agentsfleet holds a Fireworks key for Kimi K2.6 and bills you for the tokens at retail rate, bundled into the run charge. You can flip the tenant to **self-managed** at any time: store your own provider credential (Anthropic, OpenAI, Fireworks, Together, Groq, Moonshot, OpenRouter) in the vault under a name you choose, then point the tenant at it. On self-managed runs the per-second run fee still applies, but there is no added per-token cost from agentsfleet — you pay your provider directly. See [pricing](https://agentsfleet.net/#pricing) for current rates.
 
-### `zombiectl tenant provider show`
+### `agentsfleet tenant provider show`
 
 Print the active posture, model, context-cap, and (for self-managed) the credential name. `--json` for the structured shape.
 
 ```bash
-zombiectl tenant provider show
-zombiectl tenant provider show --json
+agentsfleet tenant provider show
+agentsfleet tenant provider show --json
 ```
 
-### `zombiectl tenant provider set`
+### `agentsfleet tenant provider set`
 
-Activate a self-managed credential for the tenant. The credential must already exist in the workspace vault (`zombiectl credential add <name>`). The command validates the credential structure, resolves the model's context cap from the `cap.json` endpoint, and pins both into the tenant's provider row.
+Activate a self-managed credential for the tenant. The credential must already exist in the workspace vault (`agentsfleet credential add <name>`). The command validates the credential structure, resolves the model's context cap from the `cap.json` endpoint, and pins both into the tenant's provider row.
 
 ```bash
 # 1. Store the provider credential
-zombiectl credential add account-fireworks --data='{"provider":"fireworks","api_key":"fw_…","model":"accounts/fireworks/models/kimi-k2.6"}'
+agentsfleet credential add account-fireworks --data='{"provider":"fireworks","api_key":"fw_…","model":"accounts/fireworks/models/kimi-k2.6"}'
 
 # 2. Activate it for the tenant
-zombiectl tenant provider set --credential account-fireworks
+agentsfleet tenant provider set --credential account-fireworks
 ```
 
 In-flight events finish under the snapshot they were claimed under; the next event's debits use the new posture.
 
-### `zombiectl tenant provider reset`
+### `agentsfleet tenant provider reset`
 
 Drop the explicit `tenant_providers` row and fall back to the platform-managed synth-default.
 
 ```bash
-zombiectl tenant provider reset
+agentsfleet tenant provider reset
 ```
 
-For the install-time vs trigger-time resolution flow, the frontmatter overlay sentinels, and the provider routing details, see [`docs/architecture/user_flow.md` §8.7](https://github.com/usezombie/usezombie/blob/main/docs/architecture/user_flow.md#87-model-and-context-cap-origin-platform-vs-self-managed) and [`docs/architecture/billing_and_provider_keys.md`](https://github.com/usezombie/usezombie/blob/main/docs/architecture/billing_and_provider_keys.md). The architecture is the canonical reference; this page is the command surface.
+For the install-time vs trigger-time resolution flow, the frontmatter overlay sentinels, and the provider routing details, see [`docs/architecture/user_flow.md` §8.7](https://github.com/agentsfleet/agentsfleet/blob/main/docs/architecture/user_flow.md#87-model-and-context-cap-origin-platform-vs-self-managed) and [`docs/architecture/billing_and_provider_keys.md`](https://github.com/agentsfleet/agentsfleet/blob/main/docs/architecture/billing_and_provider_keys.md). The architecture is the canonical reference; this page is the command surface.
 
 ---
 
 ## Diagnostics
 
-### `zombiectl doctor`
+### `agentsfleet doctor`
 
 Verify API connectivity, authentication, and local configuration. Does not require authentication.
 
 ```bash
-zombiectl doctor
+agentsfleet doctor
 ```
 
 ---
 
-See [`docs/architecture/`](https://github.com/usezombie/usezombie/tree/main/docs/architecture) for the full technical reference.
+See [`docs/architecture/`](https://github.com/agentsfleet/agentsfleet/tree/main/docs/architecture) for the full technical reference.
diff --git a/cli/configuration.mdx b/cli/configuration.mdx
index 3225534..5ef52f8 100644
--- a/cli/configuration.mdx
+++ b/cli/configuration.mdx
@@ -5,60 +5,60 @@ description: "Configuration precedence and environment variables."
 
 ## Auth precedence
 
-`zombiectl login` decides which token to **store**, highest priority first:
+`agentsfleet login` decides which token to **store**, highest priority first:
 
 1. **`--token <value>`** — login-only flag
-2. **`ZOMBIE_TOKEN`** environment variable
+2. **`AGENTSFLEET_TOKEN`** environment variable
 3. **Piped stdin** — token read from a pipe
 4. **Browser device flow** — interactive terminals only
 
 Every **other command** then resolves its token, and the order is TTY-aware:
 
-- **Interactive terminal** — `ZOMBIE_TOKEN` wins over stored credentials, so an env var you just exported overrides a possibly-stale file.
-- **Non-interactive (CI, cron, pipes)** — stored credentials (written by `zombiectl login` to `~/.config/zombiectl/credentials.json`) win, falling back to `ZOMBIE_TOKEN` only when no file exists.
+- **Interactive terminal** — `AGENTSFLEET_TOKEN` wins over stored credentials, so an env var you just exported overrides a possibly-stale file.
+- **Non-interactive (CI, cron, pipes)** — stored credentials (written by `agentsfleet login` to `~/.config/agentsfleet/credentials.json`) win, falling back to `AGENTSFLEET_TOKEN` only when no file exists.
 
-`--token` is not accepted on commands other than `login`; use the `ZOMBIE_TOKEN` env var for one-off overrides in scripts.
+`--token` is not accepted on commands other than `login`; use the `AGENTSFLEET_TOKEN` env var for one-off overrides in scripts.
 
 ## API URL precedence
 
 1. **CLI flag** -- `--api https://...`
-2. **Environment variable** -- `ZOMBIE_API_URL`
+2. **Environment variable** -- `AGENTSFLEET_API_URL`
 3. **`.env.local`** -- dev fallback file in the current directory
-4. **Built-in default** -- `https://api.usezombie.com`
+4. **Built-in default** -- `https://api.agentsfleet.net`
 
 ## Environment variables
 
 | Variable | Purpose | Default |
 |----------|---------|---------|
-| `ZOMBIE_API_URL` | API base URL | `https://api.usezombie.com` |
-| `ZOMBIE_TOKEN` | Auth token (for CI and scripts; user-bound, from `zombiectl login`) | *(from `zombiectl login`)* |
-| `ZOMBIE_API_KEY` | Service auth (machine-bound, from `zombiectl agent add`). Use this for service-to-service calls and external agents (LangGraph, CrewAI, Composio, your own code). | — |
-| `ZOMBIE_STATE_DIR` | Directory for local CLI state (credentials, telemetry, session). | `~/.config/zombiectl` |
+| `AGENTSFLEET_API_URL` | API base URL | `https://api.agentsfleet.net` |
+| `AGENTSFLEET_TOKEN` | Auth token (for CI and scripts; user-bound, from `agentsfleet login`) | *(from `agentsfleet login`)* |
+| `AGENTSFLEET_API_KEY` | Service auth (machine-bound, from `agentsfleet agent add`). Use this for service-to-service calls and external agents (LangGraph, CrewAI, Composio, your own code). | — |
+| `AGENTSFLEET_STATE_DIR` | Directory for local CLI state (credentials, telemetry, session). | `~/.config/agentsfleet` |
 | `NO_COLOR` | Set to `1` to disable color output. | — |
-| `ZOMBIE_TELEMETRY_DISABLED` | Set to `1` to opt out of anonymous analytics + tracing. | unset (telemetry on) |
+| `AGENTSFLEET_TELEMETRY_DISABLED` | Set to `1` to opt out of anonymous analytics + tracing. | unset (telemetry on) |
 | `DO_NOT_TRACK` | Set to `1` to opt out via the industry-standard signal ([consoledonottrack.com](https://consoledonottrack.com/)). | unset |
-| `ZOMBIE_TELEMETRY_POSTHOG_KEY` | Override the bundled PostHog project key (advanced; for self-hosted PostHog routing). | bundled `phc_*` key |
-| `ZOMBIE_TELEMETRY_POSTHOG_HOST` | Override the PostHog ingest host. | `https://us.i.posthog.com` |
-| `ZOMBIE_TELEMETRY_DEBUG` | Set to `1` to print span summaries to stderr for local development. | unset |
+| `AGENTSFLEET_TELEMETRY_POSTHOG_KEY` | Override the bundled PostHog project key (advanced; for self-hosted PostHog routing). | bundled `phc_*` key |
+| `AGENTSFLEET_TELEMETRY_POSTHOG_HOST` | Override the PostHog ingest host. | `https://us.i.posthog.com` |
+| `AGENTSFLEET_TELEMETRY_DEBUG` | Set to `1` to print span summaries to stderr for local development. | unset |
 
 ## Telemetry
 
-`zombiectl` collects anonymous usage data (command name, exit code, duration, OS, CLI version, detected AI agent if any) to improve the CLI. Identifiers are random UUIDs persisted in `$ZOMBIE_STATE_DIR/telemetry.json` (default `~/.config/zombiectl/telemetry.json`); no source paths, file contents, prompts, or credentials are ever sent.
+`agentsfleet` collects anonymous usage data (command name, exit code, duration, OS, CLI version, detected AI agent if any) to improve the CLI. Identifiers are random UUIDs persisted in `$AGENTSFLEET_STATE_DIR/telemetry.json` (default `~/.config/agentsfleet/telemetry.json`); no source paths, file contents, prompts, or credentials are ever sent.
 
 Telemetry is **on by default**. Opt out per-command, per-shell, or persistently:
 
 ```bash
 # One command
-ZOMBIE_TELEMETRY_DISABLED=1 zombiectl status
+AGENTSFLEET_TELEMETRY_DISABLED=1 agentsfleet status
 
 # Whole shell session
-export ZOMBIE_TELEMETRY_DISABLED=1
+export AGENTSFLEET_TELEMETRY_DISABLED=1
 
 # Industry-standard signal (same effect, honored by many CLIs)
 export DO_NOT_TRACK=1
 
-# Persistent — edit $ZOMBIE_STATE_DIR/telemetry.json:
-# (defaults to ~/.config/zombiectl/telemetry.json)
+# Persistent — edit $AGENTSFLEET_STATE_DIR/telemetry.json:
+# (defaults to ~/.config/agentsfleet/telemetry.json)
 #   { "consent": "denied", ... }
 ```
 
@@ -66,9 +66,9 @@ Either env variable forces consent to `denied` regardless of the persisted value
 
 ## CI usage
 
-In CI environments, set `ZOMBIE_TOKEN` from your secrets manager and use `--no-input` for non-interactive operation:
+In CI environments, set `AGENTSFLEET_TOKEN` from your secrets manager and use `--no-input` for non-interactive operation:
 
 ```bash
-export ZOMBIE_TOKEN="$ZOMBIE_SECRET"
-zombiectl status --no-input --json
+export AGENTSFLEET_TOKEN="$AGENTSFLEET_SECRET"
+agentsfleet status --no-input --json
 ```
diff --git a/cli/flags.mdx b/cli/flags.mdx
index da6f52b..48bdfe9 100644
--- a/cli/flags.mdx
+++ b/cli/flags.mdx
@@ -1,15 +1,15 @@
 ---
 title: "Global flags"
-description: "Flags available on all zombiectl commands."
+description: "Flags available on all agentsfleet commands."
 ---
 
 ## Global flags
 
-These flags can be passed to any `zombiectl` command.
+These flags can be passed to any `agentsfleet` command.
 
 | Flag | Description | Default |
 |------|-------------|---------|
-| `--api <url>` | API base URL | `https://api.usezombie.com` |
+| `--api <url>` | API base URL | `https://api.agentsfleet.net` |
 | `--json` | Machine-readable JSON output | `false` |
 | `--no-open` | Suppress browser auto-open (login) | `false` |
 | `--no-input` | Non-interactive mode | `false` |
@@ -28,8 +28,8 @@ When `--json` is enabled, error responses include structured error codes for pro
 ```json
 {
   "error": {
-    "code": "UZ-ZMB-008",
-    "message": "Invalid zombie config: TRIGGER.md config_json fails schema validation."
+    "code": "UZ-AGT-008",
+    "message": "Invalid agent config: TRIGGER.md config_json fails schema validation."
   }
 }
 ```
diff --git a/cli/install.mdx b/cli/install.mdx
index d73f28f..5712611 100644
--- a/cli/install.mdx
+++ b/cli/install.mdx
@@ -1,6 +1,6 @@
 ---
 title: "Install"
-description: "Install the zombiectl CLI."
+description: "Install the agentsfleet CLI."
 ---
 
 ## Install
@@ -14,37 +14,37 @@ description: "Install the zombiectl CLI."
     Run the following command in your terminal:
 
     ```bash
-    npm install -g @usezombie/zombiectl
+    npm install -g @agentsfleet/cli
     ```
 
     Use `npx` to run without a global install:
 
     ```bash
-    npx @usezombie/zombiectl --help
+    npx @agentsfleet/cli --help
     ```
   </Step>
 </Steps>
 
 ## Agent Skills
 
-The `usezombie-install-platform-ops` skill is the guided install UX driven from a host agent (Claude Code, Amp, Codex CLI, OpenCode). Add the skills with one command:
+The `agentsfleet-install-platform-ops` skill is the guided install UX driven from a host agent (Claude Code, Amp, Codex CLI, OpenCode). Add the skills with one command:
 
 ```bash
-npx skills add usezombie/skills
+npx skills add agentsfleet/skills
 ```
 
-This symlinks the `/usezombie-*` slash commands from the public [`usezombie/skills`](https://github.com/usezombie/skills) repo into every supported host's skill directory it detects on your machine — invoke `/usezombie-install-platform-ops` in your agent and you're set. Pass `--host=<claude|amp|codex|opencode>` to target a single host instead of every detected one.
+This symlinks the `/agentsfleet-*` slash commands from the public [`agentsfleet/skills`](https://github.com/agentsfleet/skills) repo into every supported host's skill directory it detects on your machine — invoke `/agentsfleet-install-platform-ops` in your agent and you're set. Pass `--host=<claude|amp|codex|opencode>` to target a single host instead of every detected one.
 
 <Tip>
-  **No global install?** `curl -fsSL https://usezombie.sh | bash` installs `zombiectl` and the skill together in one command (requires Node — it runs npm under the hood). Run `curl -fsSL https://usezombie.sh` without `| bash` to read it first.
+  **No global install?** `curl -fsSL https://agentsfleet.dev | bash` installs `agentsfleet` and the skill together in one command (requires Node — it runs npm under the hood). Run `curl -fsSL https://agentsfleet.dev` without `| bash` to read it first.
 </Tip>
 
-The skill drives `zombiectl install --from`, `zombiectl credential`, `zombiectl steer`, `zombiectl logs`, and the doctor preflight under the hood. See [Quickstart](/quickstart) for the end-to-end flow.
+The skill drives `agentsfleet install --from`, `agentsfleet credential`, `agentsfleet steer`, `agentsfleet logs`, and the doctor preflight under the hood. See [Quickstart](/quickstart) for the end-to-end flow.
 
 ## Verify installation
 
 ```bash
-zombiectl --version
+agentsfleet --version
 ```
 
 ## Check connectivity
@@ -52,7 +52,7 @@ zombiectl --version
 Run the built-in diagnostics command to verify API connectivity, auth status, and local configuration:
 
 ```bash
-zombiectl doctor
+agentsfleet doctor
 ```
 
 `doctor` runs three checks and exits non-zero if any fails. It does **not** require authentication and never short-circuits — every check runs and reports:
@@ -60,7 +60,7 @@ zombiectl doctor
 | Check | Verifies |
 |---|---|
 | `server_reachable` | `GET /healthz` against the configured API URL returns `{ "status": "ok" }` within 5s. |
-| `workspace_selected` | The local config has a `current_workspace_id`. Auto-populated by `zombiectl login` from your signup-provisioned default workspace; can also be set or replaced by `zombiectl workspace add` / `workspace use`. |
+| `workspace_selected` | The local config has a `current_workspace_id`. Auto-populated by `agentsfleet login` from your signup-provisioned default workspace; can also be set or replaced by `agentsfleet workspace add` / `workspace use`. |
 | `workspace_binding_valid` | The resolved auth token can read the selected workspace's agents — i.e. it is bound to the right tenant. Reports a failed check (rather than aborting) when no token is present. |
 
-Pass `--json` for the structured `{ ok, api_url, checks: [...] }` envelope. Run it before any install — host-agent skills depend on this preflight. For the tenant's inference posture and free-trial window, use [`zombiectl tenant provider show`](/cli/zombiectl#tenant-provider).
+Pass `--json` for the structured `{ ok, api_url, checks: [...] }` envelope. Run it before any install — host-agent skills depend on this preflight. For the tenant's inference posture and free-trial window, use [`agentsfleet tenant provider show`](/cli/agentsfleet#tenant-provider).
diff --git a/concepts.mdx b/concepts.mdx
index c34514b..a6642f9 100644
--- a/concepts.mdx
+++ b/concepts.mdx
@@ -4,16 +4,16 @@ description: "The four nouns, the tool bridge, and how a run works."
 ---
 
 <Tip>
-  This page introduces the operator-facing model. For the canonical technical reference — system topology, data flow, billing internals, security boundary, post-ship reflection — read [`docs/architecture/`](https://github.com/usezombie/usezombie/tree/main/docs/architecture) on GitHub.
+  This page introduces the operator-facing model. For the canonical technical reference — system topology, data flow, billing internals, security boundary, post-ship reflection — read [`docs/architecture/`](https://github.com/agentsfleet/agentsfleet/tree/main/docs/architecture) on GitHub.
 </Tip>
 
 ## The four nouns
 
-usezombie has four primary objects. Everything else is infrastructure.
+agentsfleet has four primary objects. Everything else is infrastructure.
 
 <CardGroup cols={2}>
   <Card title="Tenant" icon="building">
-    Your top-level billing and identity boundary. Created automatically on first Clerk sign-in. Carries your default Stripe customer — hosted execution is [free until July 31, 2026](https://usezombie.com/pricing).
+    Your top-level billing and identity boundary. Created automatically on first Clerk sign-in. Carries your default Stripe customer — hosted execution is [free until July 31, 2026](https://agentsfleet.net/pricing).
   </Card>
   <Card title="Workspace" icon="folder-tree">
     A container for agents and credentials. One tenant can have many workspaces (team, project, environment). Billing and identity live at the tenant — a workspace is purely an organizational boundary.
@@ -33,7 +33,7 @@ Tenant  (billing + identity, provider: anthropic)
 │
 ├── Workspace: "platform-ops"
 │   │
-│   ├── Zombie: platform-ops      (zmb_2041)
+│   ├── Agent: platform-ops      (0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71)
 │   │   ├── Tools:    http_request, memory_store, cron_add
 │   │   └── Triggers: webhook (GitHub Actions), cron, steer
 │   │
@@ -41,7 +41,7 @@ Tenant  (billing + identity, provider: anthropic)
 │
 └── Workspace: "support"
     │
-    └── Zombie: ticket-triage     (zmb_2042)
+    └── Agent: ticket-triage     (0198a7b3-1a4d-7b62-a3f9-5c8e2d1b7a04)
         ├── Tools:    http_request, memory_store
         └── Triggers: webhook (Zendesk), steer
 ```
@@ -50,9 +50,9 @@ Tenant  (billing + identity, provider: anthropic)
 
 Hosted execution — every event receipt and run — is **free until July 31, 2026**. No credit card to start.
 
-**You bring your provider and model.** Pick the provider (Anthropic, OpenAI, Fireworks, Together, Groq, Moonshot), attach the key, and pay them directly — usezombie marks up zero on inference. The runner resolves your credential at the tool bridge, so the agent never sees the raw key.
+**You bring your provider and model.** Pick the provider (Anthropic, OpenAI, Fireworks, Together, Groq, Moonshot), attach the key, and pay them directly — agentsfleet marks up zero on inference. The runner resolves your credential at the tool bridge, so the agent never sees the raw key.
 
-For the metered rates that apply after the trial, see [pricing on usezombie.com](https://usezombie.com/pricing).
+For the metered rates that apply after the trial, see [pricing on agentsfleet.net](https://agentsfleet.net/pricing).
 
 ## How a run works
 
@@ -79,9 +79,9 @@ A trigger lands on the event stream. A run opens. The agent calls tools allow-li
   <Accordion title="Trigger">
     What wakes an agent. Three sources, all feeding the same reasoning loop:
 
-    - **Webhook** — an external system (GitHub, Slack, your monitoring) POSTs to `https://api.usezombie.com/v1/webhooks/{zombie_id}/{source}` (one URL per declared trigger source).
+    - **Webhook** — an external system (GitHub, Slack, your monitoring) POSTs to `https://api.agentsfleet.net/v1/webhooks/{agent_id}/{source}` (one URL per declared trigger source).
     - **Cron** — the agent schedules its own future runs via the `cron_add` tool.
-    - **Steer** — a human invokes `zombiectl steer <zombie_id> "..."` for a manual run.
+    - **Steer** — a human invokes `agentsfleet steer <agent_id> "..."` for a manual run.
 
     `SKILL.md` decides what to do based on the event payload.
   </Accordion>
@@ -96,10 +96,10 @@ A trigger lands on the event stream. A run opens. The agent calls tools allow-li
   </Accordion>
 
   <Accordion title="Tool bridge">
-    The boundary between your secrets and the model. Credentials are stored encrypted in the workspace vault; the model itself only sees `${secrets.NAME.FIELD}` placeholders. When the agent invokes a tool, the **tool bridge** substitutes the real secret value outside the sandbox, makes the outbound call, and returns the response — never the secret. A prompt-injection attack recovers only the placeholder string. See [Workspace credentials](/zombies/credentials).
+    The boundary between your secrets and the model. Credentials are stored encrypted in the workspace vault; the model itself only sees `${secrets.NAME.FIELD}` placeholders. When the agent invokes a tool, the **tool bridge** substitutes the real secret value outside the sandbox, makes the outbound call, and returns the response — never the secret. A prompt-injection attack recovers only the placeholder string. See [Workspace credentials](/agents/credentials).
   </Accordion>
 
   <Accordion title="Budget">
-    Dollar ceilings on hosted execution (the platform compute that runs your agent — separate from your model provider's bill) declared in `TRIGGER.md`. `daily_dollars` caps spend over a rolling 24-hour window; `monthly_dollars` caps the calendar month. Hitting either ceiling stops new runs from opening. During the launch free trial (through July 31, 2026) hosted-execution runs are billed at **$0**, so a budget ceiling won't stop an agent for trial usage — these caps apply to the metered rate after the trial (see [pricing](https://usezombie.com/pricing)). Inference is on your model provider's bill, not on your usezombie invoice — your provider's own caps apply there.
+    Dollar ceilings on hosted execution (the platform compute that runs your agent — separate from your model provider's bill) declared in `TRIGGER.md`. `daily_dollars` caps spend over a rolling 24-hour window; `monthly_dollars` caps the calendar month. Hitting either ceiling stops new runs from opening. During the launch free trial (through July 31, 2026) hosted-execution runs are billed at **$0**, so a budget ceiling won't stop an agent for trial usage — these caps apply to the metered rate after the trial (see [pricing](https://agentsfleet.net/pricing)). Inference is on your model provider's bill, not on your agentsfleet invoice — your provider's own caps apply there.
   </Accordion>
 </AccordionGroup>
diff --git a/concepts/context-lifecycle.mdx b/concepts/context-lifecycle.mdx
index 2cf962a..32cacfd 100644
--- a/concepts/context-lifecycle.mdx
+++ b/concepts/context-lifecycle.mdx
@@ -23,7 +23,7 @@ A chain caps at **10 continuations**. The 11th attempt is refused, the originati
 
 ## Knobs you can tune
 
-Set these under `x-usezombie.context` in `TRIGGER.md`. Defaults work for almost every workload — leave them alone unless you have a specific reason.
+Set these under `x-agentsfleet.context` in `TRIGGER.md`. Defaults work for almost every workload — leave them alone unless you have a specific reason.
 
 | Knob | Default | When to touch it |
 |---|---|---|
@@ -51,4 +51,4 @@ Almost certainly not. The defaults are tuned for the flagship `platform-ops` age
 
 - [Memory](/memory) — the API the agent uses to checkpoint findings during a long run.
 - [Budgets](/billing/budgets) — `daily_dollars` and `monthly_dollars` ceilings.
-- [Authoring an agent](/zombies/authoring) — the full `TRIGGER.md` reference.
+- [Authoring an agent](/agents/authoring) — the full `TRIGGER.md` reference.
diff --git a/docs.json b/docs.json
index 274aad0..0e14eb0 100644
--- a/docs.json
+++ b/docs.json
@@ -1,7 +1,7 @@
 {
   "$schema": "https://mintlify.com/docs.json",
   "theme": "mint",
-  "name": "usezombie",
+  "name": "agentsfleet",
   "appearance": {
     "default": "dark"
   },
@@ -48,15 +48,15 @@
           {
             "group": "Agents",
             "pages": [
-              "zombies/overview",
-              "zombies/install",
-              "zombies/running",
-              "zombies/credentials",
-              "zombies/webhooks",
-              "zombies/authoring",
-              "zombies/tools",
-              "zombies/templates",
-              "zombies/troubleshooting"
+              "agents/overview",
+              "agents/install",
+              "agents/running",
+              "agents/credentials",
+              "agents/webhooks",
+              "agents/authoring",
+              "agents/tools",
+              "agents/templates",
+              "agents/troubleshooting"
             ]
           },
           {
@@ -77,7 +77,7 @@
             "group": "CLI reference",
             "pages": [
               "cli/install",
-              "cli/zombiectl",
+              "cli/agentsfleet",
               "cli/flags",
               "cli/configuration"
             ]
@@ -92,7 +92,7 @@
       },
       {
         "tab": "API reference",
-        "openapi": "https://raw.githubusercontent.com/usezombie/usezombie/main/public/openapi.json",
+        "openapi": "https://raw.githubusercontent.com/agentsfleet/agentsfleet/main/public/openapi.json",
         "groups": [
           {
             "group": "Overview",
@@ -158,7 +158,7 @@
             "pages": [
               "GET /v1/workspaces/{workspace_id}/agent-keys",
               "POST /v1/workspaces/{workspace_id}/agent-keys",
-              "DELETE /v1/workspaces/{workspace_id}/agent-keys/{agent_id}"
+              "DELETE /v1/workspaces/{workspace_id}/agent-keys/{agent_key_id}"
             ]
           },
           {
@@ -181,47 +181,47 @@
           {
             "group": "Agents",
             "pages": [
-              "GET /v1/workspaces/{workspace_id}/zombies",
-              "POST /v1/workspaces/{workspace_id}/zombies",
-              "PATCH /v1/workspaces/{workspace_id}/zombies/{zombie_id}",
-              "DELETE /v1/workspaces/{workspace_id}/zombies/{zombie_id}"
+              "GET /v1/workspaces/{workspace_id}/agents",
+              "POST /v1/workspaces/{workspace_id}/agents",
+              "PATCH /v1/workspaces/{workspace_id}/agents/{agent_id}",
+              "DELETE /v1/workspaces/{workspace_id}/agents/{agent_id}"
             ]
           },
           {
             "group": "Agent messages",
             "pages": [
-              "POST /v1/workspaces/{workspace_id}/zombies/{zombie_id}/messages"
+              "POST /v1/workspaces/{workspace_id}/agents/{agent_id}/messages"
             ]
           },
           {
             "group": "Agent memories",
             "pages": [
-              "GET /v1/workspaces/{workspace_id}/zombies/{zombie_id}/memories"
+              "GET /v1/workspaces/{workspace_id}/agents/{agent_id}/memories"
             ]
           },
           {
             "group": "Agent events",
             "pages": [
-              "GET /v1/workspaces/{workspace_id}/zombies/{zombie_id}/events",
-              "GET /v1/workspaces/{workspace_id}/zombies/{zombie_id}/events/stream"
+              "GET /v1/workspaces/{workspace_id}/agents/{agent_id}/events",
+              "GET /v1/workspaces/{workspace_id}/agents/{agent_id}/events/stream"
             ]
           },
           {
             "group": "Integration grants",
             "pages": [
-              "GET /v1/workspaces/{workspace_id}/zombies/{zombie_id}/integration-grants",
-              "POST /v1/workspaces/{workspace_id}/zombies/{zombie_id}/integration-requests",
-              "DELETE /v1/workspaces/{workspace_id}/zombies/{zombie_id}/integration-grants/{grant_id}"
+              "GET /v1/workspaces/{workspace_id}/agents/{agent_id}/integration-grants",
+              "POST /v1/workspaces/{workspace_id}/agents/{agent_id}/integration-requests",
+              "DELETE /v1/workspaces/{workspace_id}/agents/{agent_id}/integration-grants/{grant_id}"
             ]
           },
           {
             "group": "Webhooks",
             "pages": [
-              "POST /v1/webhooks/svix/{zombie_id}",
-              "POST /v1/webhooks/{zombie_id}",
-              "POST /v1/webhooks/{zombie_id}/approval",
-              "POST /v1/webhooks/{zombie_id}/github",
-              "POST /v1/webhooks/{zombie_id}/grant-approval"
+              "POST /v1/webhooks/svix/{agent_id}",
+              "POST /v1/webhooks/{agent_id}",
+              "POST /v1/webhooks/{agent_id}/approval",
+              "POST /v1/webhooks/{agent_id}/github",
+              "POST /v1/webhooks/{agent_id}/grant-approval"
             ]
           },
           {
@@ -239,17 +239,17 @@
       "anchors": [
         {
           "anchor": "Website",
-          "href": "https://usezombie.com",
+          "href": "https://agentsfleet.net",
           "icon": "globe"
         },
         {
           "anchor": "GitHub",
-          "href": "https://github.com/usezombie/usezombie",
+          "href": "https://github.com/agentsfleet/agentsfleet",
           "icon": "github"
         },
         {
           "anchor": "Contributing",
-          "href": "https://github.com/usezombie/usezombie#contributing",
+          "href": "https://github.com/agentsfleet/agentsfleet#contributing",
           "icon": "code-pull-request"
         }
       ]
@@ -267,13 +267,13 @@
       },
       {
         "label": "Talk to us",
-        "href": "https://usezombie.com/contact/sales"
+        "href": "https://agentsfleet.net/contact/sales"
       }
     ],
     "primary": {
       "type": "button",
       "label": "Get early access",
-      "href": "https://app.usezombie.com"
+      "href": "https://app.agentsfleet.net"
     }
   },
   "contextual": {
@@ -290,7 +290,7 @@
   },
   "footer": {
     "socials": {
-      "github": "https://github.com/usezombie",
+      "github": "https://github.com/agentsfleet",
       "discord": "https://discord.gg/H9hH2nqQjh"
     }
   },
diff --git a/favicon.svg b/favicon.svg
index 7e437d7..39d9aaa 100644
--- a/favicon.svg
+++ b/favicon.svg
@@ -2,7 +2,7 @@
 <!--
   agentsfleet brand-mark — the wake-pulse circle.
 
-  Identical geometry to the usezombie mark (the mark carries no text,
+  Identical geometry to the agentsfleet mark (the mark carries no text,
   so the rename does not alter it). Pure cyan-mint disc on the dark
   brand surface. Use as: favicon, GitHub avatar, docs site icon.
 -->
diff --git a/index.mdx b/index.mdx
index 39bb493..f6dcae8 100644
--- a/index.mdx
+++ b/index.mdx
@@ -1,34 +1,34 @@
 ---
 title: "Your deploy failed. The agent already knows why."
-description: "usezombie is an open runtime that owns operational outcomes — an agent wakes on your events, gathers evidence from your own systems, posts a diagnosis with proof, and keeps a replayable log of every move it made."
+description: "agentsfleet is an open runtime that owns operational outcomes — an agent wakes on your events, gathers evidence from your own systems, posts a diagnosis with proof, and keeps a replayable log of every move it made."
 ---
 
 <Warning>
-  **Stealth-mode testing.** usezombie is in private alpha — APIs and agent behavior may change without long deprecation windows. Want a hand calibrating an agent or to join as a design partner? Email [usezombie@agentmail.to](mailto:usezombie@agentmail.to).
+  **Stealth-mode testing.** agentsfleet is in private alpha — APIs and agent behavior may change without long deprecation windows. Want a hand calibrating an agent or to join as a design partner? Email [agentsfleet@agentmail.to](mailto:agentsfleet@agentmail.to).
 </Warning>
 
 ## The 2am problem
 
 A deploy fails at 2am. Your on-call engineer is asleep, so someone guesses from a stack trace and ships a patch on hope. By morning the context is gone — no record of what was tried, evidence scattered across CI, logs, dashboards, and chat.
 
-usezombie owns the outcome instead. An **agent** is a durable runtime described in two markdown files — `SKILL.md` (the senior engineer's playbook in prose) plus `TRIGGER.md` (which tools the agent can reach and which events wake it). When a trigger fires, the agent gathers the evidence, reasons over it, posts an evidenced diagnosis to your Slack channel, and keeps a replayable log of every move it made.
+agentsfleet owns the outcome instead. An **agent** is a durable runtime described in two markdown files — `SKILL.md` (the senior engineer's playbook in prose) plus `TRIGGER.md` (which tools the agent can reach and which events wake it). When a trigger fires, the agent gathers the evidence, reasons over it, posts an evidenced diagnosis to your Slack channel, and keeps a replayable log of every move it made.
 
-The flagship `platform-ops` wakes on a GitHub Actions deploy failure, pulls workflow logs + your hosting provider's app state + your data-plane's health, and posts a one-paragraph diagnosis with a leading hypothesis. The same agent is reachable via `zombiectl steer` for a manual investigation. The runtime is open source, you bring your own model and pay your provider directly, and the agent never sees your raw keys — only `${secrets.NAME.FIELD}` placeholders, swapped for real values outside the sandbox.
+The flagship `platform-ops` wakes on a GitHub Actions deploy failure, pulls workflow logs + your hosting provider's app state + your data-plane's health, and posts a one-paragraph diagnosis with a leading hypothesis. The same agent is reachable via `agentsfleet steer` for a manual investigation. The runtime is open source, you bring your own model and pay your provider directly, and the agent never sees your raw keys — only `${secrets.NAME.FIELD}` placeholders, swapped for real values outside the sandbox.
 
 ## Get started
 
 `platform-ops` goes from a cold machine to a real diagnosis in Slack in about ten minutes. Install the CLI, add the host skills, and sign in:
 
 ```bash
-npm install -g @usezombie/zombiectl
-npx skills add usezombie/skills
-zombiectl login
+npm install -g @agentsfleet/cli
+npx skills add agentsfleet/skills
+agentsfleet login
 ```
 
 Then invoke the install skill inside your agent — Claude Code, Amp, Codex CLI, or OpenCode:
 
 ```
-/usezombie-install-platform-ops
+/agentsfleet-install-platform-ops
 ```
 
 The skill registers the GitHub webhook and writes `SKILL.md` + `TRIGGER.md` into your repo. From there, behaviour iterates on prose, not redeploys.
@@ -43,13 +43,13 @@ The skill registers the GitHub webhook and writes `SKILL.md` + `TRIGGER.md` into
   <Card title="Concepts" icon="book" href="/concepts">
     Tenants, workspaces, agents, tools — the four nouns.
   </Card>
-  <Card title="Authoring an agent" icon="file-code" href="/zombies/authoring">
+  <Card title="Authoring an agent" icon="file-code" href="/agents/authoring">
     Write your own `SKILL.md` + `TRIGGER.md`.
   </Card>
-  <Card title="CLI reference" icon="rectangle-terminal" href="/cli/zombiectl">
-    Every `zombiectl` command, with examples.
+  <Card title="CLI reference" icon="rectangle-terminal" href="/cli/agentsfleet">
+    Every `agentsfleet` command, with examples.
   </Card>
-  <Card title="GitHub" icon="github" href="https://github.com/usezombie/usezombie">
+  <Card title="GitHub" icon="github" href="https://github.com/agentsfleet/agentsfleet">
     Source, issues, design partners welcome.
   </Card>
 </Columns>
diff --git a/logo/mark-glow.svg b/logo/mark-glow.svg
index 7fb9035..ac88cdb 100644
--- a/logo/mark-glow.svg
+++ b/logo/mark-glow.svg
@@ -2,7 +2,7 @@
 <!--
   agentsfleet brand-mark with the wake-pulse glow ring.
 
-  Same disc as usezombie-mark.svg with the pulse-glow halo rendered
+  Same disc as agentsfleet-mark.svg with the pulse-glow halo rendered
   as a soft radial gradient — a static representation of the live
   wake-pulse animation that runs on the live website / app. Use this
   variant when the mark is rendered larger than ~32px and a static
diff --git a/memory.mdx b/memory.mdx
index 7f41000..82d45c5 100644
--- a/memory.mdx
+++ b/memory.mdx
@@ -82,14 +82,14 @@ Frontmatter is structured metadata; the body is the distilled prose the agent wr
 To remove or fix a fact, the agent itself calls `memory_forget(key)` followed by `memory_store(...)` with the corrected entry — typically driven from a steer message:
 
 ```bash
-zombiectl steer zmb_2041 "forget customer_bob_chen_acme; Bob is now on the Enterprise plan"
+agentsfleet steer 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71 "forget customer_bob_chen_acme; Bob is now on the Enterprise plan"
 ```
 
 The next event uses the corrected memory.
 
 ## Isolation
 
-Every memory operation is scoped by `zombie_id`. Agent A cannot read Agent B's memory. The memory store is a separate Postgres database, not a shared filesystem — even an agent with shell or file tools can't reach it through the wrong protocol.
+Every memory operation is scoped by `agent_id`. Agent A cannot read Agent B's memory. The memory store is a separate Postgres database, not a shared filesystem — even an agent with shell or file tools can't reach it through the wrong protocol.
 
 ## Common questions
 
diff --git a/quickstart.mdx b/quickstart.mdx
index a35b7a6..c4a13da 100644
--- a/quickstart.mdx
+++ b/quickstart.mdx
@@ -1,6 +1,6 @@
 ---
 title: Quickstart
-description: "Install zombiectl, run /usezombie-install-platform-ops, see a real diagnosis in Slack."
+description: "Install agentsfleet, run /agentsfleet-install-platform-ops, see a real diagnosis in Slack."
 ---
 
 This walks through installing the flagship `platform-ops` agent on one of your repositories. Total time: about ten minutes from a cold machine. At the end, a deploy failure on the repo lands an evidenced diagnosis in your Slack channel.
@@ -18,56 +18,56 @@ This walks through installing the flagship `platform-ops` agent on one of your r
   Pick one. The rest of this page assumes you have a working session in front of you.
 </Step>
 
-<Step title="Install zombiectl and skills">
+<Step title="Install agentsfleet and skills">
   ```bash
-  npm install -g @usezombie/zombiectl
-  npx skills add usezombie/skills
+  npm install -g @agentsfleet/cli
+  npx skills add agentsfleet/skills
   ```
 
   Verify:
 
   ```bash
-  zombiectl --version
+  agentsfleet --version
   ```
 
-  `zombiectl` is the only binary you install on your machine; it ships the skill samples under `~/.config/usezombie/samples/` so the install skill can drive `zombiectl install --from` against a known-good source. `npx skills add usezombie/skills` then symlinks the `/usezombie-*` host skills from the public [`usezombie/skills`](https://github.com/usezombie/skills) repo into every supported agent it detects — so `/usezombie-install-platform-ops` is ready to invoke in the next step.
+  `agentsfleet` is the only binary you install on your machine; it ships the skill samples under `~/.config/agentsfleet/samples/` so the install skill can drive `agentsfleet install --from` against a known-good source. `npx skills add agentsfleet/skills` then symlinks the `/agentsfleet-*` host skills from the public [`agentsfleet/skills`](https://github.com/agentsfleet/skills) repo into every supported agent it detects — so `/agentsfleet-install-platform-ops` is ready to invoke in the next step.
 </Step>
 
 <Step title="Sign in">
   ```bash
-  zombiectl login
+  agentsfleet login
   ```
 
-  Opens a Clerk-backed approval page in your browser. After you click **Approve**, the page shows a 6-digit verification code — type it back into the CLI to complete login. The code binds the browser approver to the terminal you're typing from. Hosted execution (event receipts + runs) is **free until July 31, 2026** — no credit card to start; see [pricing](https://usezombie.com/pricing) for the metered rates after the trial. You bring your provider and model — pay them directly. usezombie marks up zero on inference.
+  Opens a Clerk-backed approval page in your browser. After you click **Approve**, the page shows a 6-digit verification code — type it back into the CLI to complete login. The code binds the browser approver to the terminal you're typing from. Hosted execution (event receipts + runs) is **free until July 31, 2026** — no credit card to start; see [pricing](https://agentsfleet.net/pricing) for the metered rates after the trial. You bring your provider and model — pay them directly. agentsfleet marks up zero on inference.
 
   Login also fetches your tenant's workspaces and selects the first one as active locally. Signup auto-provisions a default workspace, so your CLI is ready to install agents immediately — no `workspace add` required.
 
-  <Tip>Pass `--token-name "your-device-label"` to label this install so it's easy to recognize on the approval page and in `zombiectl auth status` later. Defaults to your platform family otherwise.</Tip>
+  <Tip>Pass `--token-name "your-device-label"` to label this install so it's easy to recognize on the approval page and in `agentsfleet auth status` later. Defaults to your platform family otherwise.</Tip>
 
   <Note>
-    **No terminal — CI, or an agent driving the CLI?** Skip the browser entirely: supply a token via the `--token <token>` flag, the `ZOMBIE_TOKEN` environment variable, or piped on stdin — resolved in that order (prefer the env var or stdin to keep it out of shell history). Add `--no-input` to fail fast instead of waiting for the code — a no-TTY shell with no token exits with an error. Full precedence in [`zombiectl login`](/cli/zombiectl#zombiectl-login).
+    **No terminal — CI, or an agent driving the CLI?** Skip the browser entirely: supply a token via the `--token <token>` flag, the `AGENTSFLEET_TOKEN` environment variable, or piped on stdin — resolved in that order (prefer the env var or stdin to keep it out of shell history). Add `--no-input` to fail fast instead of waiting for the code — a no-TTY shell with no token exits with an error. Full precedence in [`agentsfleet login`](/cli/agentsfleet#agentsfleet-login).
   </Note>
 </Step>
 
 <Step title="(Optional) Create a named workspace">
   ```bash
-  zombiectl workspace add platform-ops
+  agentsfleet workspace add platform-ops
   ```
 
-  Skip this step if the signup-provisioned default workspace is fine. Run it only when you want a second workspace or a custom name. Workspaces are the boundary for credentials, access control, and webhook namespaces — every agent lives in exactly one. Switch later with `zombiectl workspace use <id>`. See [Command reference → workspaces](/cli/zombiectl#workspaces).
+  Skip this step if the signup-provisioned default workspace is fine. Run it only when you want a second workspace or a custom name. Workspaces are the boundary for credentials, access control, and webhook namespaces — every agent lives in exactly one. Switch later with `agentsfleet workspace use <id>`. See [Command reference → workspaces](/cli/agentsfleet#workspaces).
 </Step>
 
 <Step title="Run the install skill">
-  The `npx skills add usezombie/skills` in Step 2 already added the `/usezombie-install-platform-ops` skill to your agent. Invoke it:
+  The `npx skills add agentsfleet/skills` in Step 2 already added the `/agentsfleet-install-platform-ops` skill to your agent. Invoke it:
 
   ```
-  /usezombie-install-platform-ops
+  /agentsfleet-install-platform-ops
   ```
 
-  The skill drives `zombiectl install --from ~/.config/usezombie/samples/platform-ops` under the hood. Power users can run that directly; everyone else gets the guided flow.
+  The skill drives `agentsfleet install --from ~/.config/agentsfleet/samples/platform-ops` under the hood. Power users can run that directly; everyone else gets the guided flow.
 
   <Tip>
-    **Fresh machine?** `curl -fsSL https://usezombie.sh | bash` installs `zombiectl` and the skill in one shot (it runs npm under the hood) — a one-command replacement for Step 2. You still need `zombiectl login` (Step 3) before the skill works. Run `curl -fsSL https://usezombie.sh` without `| bash` to read it first.
+    **Fresh machine?** `curl -fsSL https://agentsfleet.dev | bash` installs `agentsfleet` and the skill in one shot (it runs npm under the hood) — a one-command replacement for Step 2. You still need `agentsfleet login` (Step 3) before the skill works. Run `curl -fsSL https://agentsfleet.dev` without `| bash` to read it first.
   </Tip>
 
   The skill asks three gating questions:
@@ -76,7 +76,7 @@ This walks through installing the flagship `platform-ops` agent on one of your r
   - **Production branch glob** — which branches count as production (default `main`).
   - **Cron schedule** (optional) — for periodic health checks (e.g. `*/30 * * * *`). Leave blank for webhook-only.
 
-  It writes `.usezombie/platform-ops/SKILL.md` and `.usezombie/platform-ops/TRIGGER.md` into the current repo. Re-running against the same workspace is idempotent; existing files are diffed and updated.
+  It writes `.agentsfleet/platform-ops/SKILL.md` and `.agentsfleet/platform-ops/TRIGGER.md` into the current repo. Re-running against the same workspace is idempotent; existing files are diffed and updated.
 </Step>
 
 <Step title="Verify the registered webhook">
@@ -85,12 +85,12 @@ This walks through installing the flagship `platform-ops` agent on one of your r
   After install, the skill prints a summary line per registered hook:
 
   ```
-  ✓ github · https://api.usezombie.com/v1/webhooks/zmb_2041/github
+  ✓ github · https://api.agentsfleet.net/v1/webhooks/0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71/github
     hook_id=489182  events=[workflow_run]  active=true
     HMAC self-verify: ok
   ```
 
-  The agent filters incoming payloads for `conclusion=failure` on a production-branch workflow — the rule lives in the generated `.usezombie/platform-ops/SKILL.md` and is editable. See [Authoring](/zombies/authoring) to widen or narrow it.
+  The agent filters incoming payloads for `conclusion=failure` on a production-branch workflow — the rule lives in the generated `.agentsfleet/platform-ops/SKILL.md` and is editable. See [Authoring](/agents/authoring) to widen or narrow it.
 
   If `gh` is not authenticated for `admin:repo_hook` scope, the skill stops with the exact recovery command (`gh auth refresh -s admin:repo_hook`). If the hook already exists at the same URL, the skill matches on `config.url` and advances — re-running the install is idempotent.
 
@@ -101,28 +101,28 @@ This walks through installing the flagship `platform-ops` agent on one of your r
   <Warning>
     **Rotating the webhook secret.** The signing secret lives in the workspace vault under the `github` credential — there is no user-visible copy printed at install. To rotate, replace the credential then update every registered hook with `gh`. Two steps:
 
-    **1. Rotate the workspace `github` credential.** Generate a new webhook secret (e.g. `openssl rand -hex 32`), store it in 1Password, then pipe the credential JSON through `op inject` so the secret never appears in shell history or argv. Run `op signin` first — if the 1Password session is stale, `op inject` fails before `zombiectl` runs and the workspace vault is left untouched (don't proceed to step 2 in that case, or your GitHub webhooks will be set to a secret the server never stored):
+    **1. Rotate the workspace `github` credential.** Generate a new webhook secret (e.g. `openssl rand -hex 32`), store it in 1Password, then pipe the credential JSON through `op inject` so the secret never appears in shell history or argv. Run `op signin` first — if the 1Password session is stale, `op inject` fails before `agentsfleet` runs and the workspace vault is left untouched (don't proceed to step 2 in that case, or your GitHub webhooks will be set to a secret the server never stored):
 
     ```bash
-    cat <<'JSON' | op inject | zombiectl credential add github --data=@- --force
+    cat <<'JSON' | op inject | agentsfleet credential add github --data=@- --force
     {
-      "api_token":      "{{ op://Personal/usezombie-github/api_token }}",
-      "webhook_secret": "{{ op://Personal/usezombie-github/webhook_secret }}"
+      "api_token":      "{{ op://Personal/agentsfleet-github/api_token }}",
+      "webhook_secret": "{{ op://Personal/agentsfleet-github/webhook_secret }}"
     }
     JSON
     ```
 
-    `op inject` substitutes each `{{ op://... }}` reference with the resolved secret and pipes the rendered JSON to `zombiectl`. `--data=@-` reads from stdin; `--force` overwrites the existing credential. If you don't use 1Password, the literal-JSON form below works the same — just keep it on stdin, never inline:
+    `op inject` substitutes each `{{ op://... }}` reference with the resolved secret and pipes the rendered JSON to `agentsfleet`. `--data=@-` reads from stdin; `--force` overwrites the existing credential. If you don't use 1Password, the literal-JSON form below works the same — just keep it on stdin, never inline:
 
     ```bash
-    cat <<'JSON' | zombiectl credential add github --data=@- --force
+    cat <<'JSON' | agentsfleet credential add github --data=@- --force
     { "api_token": "ghp_...", "webhook_secret": "<new-secret>" }
     JSON
     ```
 
-    See [Credentials](/zombies/credentials) for the full schema.
+    See [Credentials](/agents/credentials) for the full schema.
 
-    **2. Update every registered hook.** Re-run `/usezombie-install-platform-ops` in each repo — the install skill detects the existing hook, calls `gh api -X PATCH repos/<owner>/<repo>/hooks/<hook_id>` with the new secret, and re-runs HMAC self-verify. The old secret stops working the moment step 1 completes, so do this immediately after.
+    **2. Update every registered hook.** Re-run `/agentsfleet-install-platform-ops` in each repo — the install skill detects the existing hook, calls `gh api -X PATCH repos/<owner>/<repo>/hooks/<hook_id>` with the new secret, and re-runs HMAC self-verify. The old secret stops working the moment step 1 completes, so do this immediately after.
   </Warning>
 </Step>
 
@@ -133,34 +133,34 @@ This walks through installing the flagship `platform-ops` agent on one of your r
   - The agent wakes, calls the tools `TRIGGER.md` allow-lists (`http_request` against your hosting provider, `memory_store` for findings), gathers evidence from the failed workflow.
   - An evidenced diagnosis posts to your Slack channel.
 
-  Tail it — replace `<zombie_id>` with the value the install step printed (e.g. `zmb_2041`):
+  Tail it — replace `<agent_id>` with the value the install step printed (e.g. `0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71`):
 
   ```bash
-  zombiectl logs zmb_2041
+  agentsfleet logs 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71
   ```
 
-  Need to slice by source or time window? `zombiectl events zmb_2041 --actor 'webhook:*' --since 30m`. Lost track of the ID? `zombiectl list` prints every agent in the active workspace. Or watch the same stream in the dashboard at `app.usezombie.com`.
+  Need to slice by source or time window? `agentsfleet events 0198a7b2-9e1f-7c3a-8b25-6d4f0a9e2c71 --actor 'webhook:*' --since 30m`. Lost track of the ID? `agentsfleet list` prints every agent in the active workspace. Or watch the same stream in the dashboard at `app.agentsfleet.net`.
 </Step>
 
 </Steps>
 
 ## What just happened
 
-The platform-ops agent installed `SKILL.md` (the prose system prompt — what to investigate, how to phrase a diagnosis) and `TRIGGER.md` (which tools the model can call) into your repo. From here, behaviour iterates on prose: edit the `.usezombie/platform-ops/SKILL.md` file, push, the next trigger runs the new behaviour. No redeploys, no DAG editor.
+The platform-ops agent installed `SKILL.md` (the prose system prompt — what to investigate, how to phrase a diagnosis) and `TRIGGER.md` (which tools the model can call) into your repo. From here, behaviour iterates on prose: edit the `.agentsfleet/platform-ops/SKILL.md` file, push, the next trigger runs the new behaviour. No redeploys, no DAG editor.
 
 ## Next steps
 
 <Columns cols={2}>
-  <Card title="Steer the agent manually" icon="message" href="/cli/zombiectl">
-    `zombiectl steer <zombie_id> "morning health check"` — same reasoning loop, manual trigger. Useful before you have a webhook firing.
+  <Card title="Steer the agent manually" icon="message" href="/cli/agentsfleet">
+    `agentsfleet steer <agent_id> "morning health check"` — same reasoning loop, manual trigger. Useful before you have a webhook firing.
   </Card>
   <Card title="Read SKILL.md / TRIGGER.md" icon="file-pen" href="/concepts">
-    The two markdown files in `.usezombie/platform-ops/` are the entire behaviour. Edit them like any other source file.
+    The two markdown files in `.agentsfleet/platform-ops/` are the entire behaviour. Edit them like any other source file.
   </Card>
   <Card title="Context lifecycle" icon="layer-group" href="/concepts/context-lifecycle">
     Why deep incidents keep reasoning past the model's context cap. Defaults work for 95% of cases.
   </Card>
-  <Card title="Authoring an agent" icon="file-code" href="/zombies/authoring">
+  <Card title="Authoring an agent" icon="file-code" href="/agents/authoring">
     The `SKILL.md` + `TRIGGER.md` reference for writing your own.
   </Card>
 </Columns>
diff --git a/scripts/test-spec.sh b/scripts/test-spec.sh
index a846ca8..013e2f5 100755
--- a/scripts/test-spec.sh
+++ b/scripts/test-spec.sh
@@ -1,6 +1,6 @@
 #!/usr/bin/env bash
 # M51_001 docs-site test specification — see
-# usezombie/usezombie:docs/v2/active/M51_001_*.md §Test Specification.
+# agentsfleet/agentsfleet:docs/v2/active/M51_001_*.md §Test Specification.
 #
 # Source-file checks. Mintlify "renders" iff the source file exists with
 # required content; "404s" iff the source file is absent (or hidden via
@@ -29,13 +29,13 @@ check() {
 echo "M51_001 docs-site spec tests"
 
 check "test_quickstart_page_renders" \
-  '[ -f quickstart.mdx ] && grep -q "platform-ops" quickstart.mdx && grep -q "usezombie-install-platform-ops" quickstart.mdx'
+  '[ -f quickstart.mdx ] && grep -q "platform-ops" quickstart.mdx && grep -q "agentsfleet-install-platform-ops" quickstart.mdx'
 
 check "test_concepts_context_lifecycle_renders" \
   '[ -f concepts/context-lifecycle.mdx ] && grep -q "tool_window" concepts/context-lifecycle.mdx && grep -q "memory_checkpoint_every" concepts/context-lifecycle.mdx'
 
 check "test_skills_index_renders" \
-  '[ -f skills/index.mdx ] && grep -q "usezombie-install-platform-ops" skills/index.mdx'
+  '[ -f skills/index.mdx ] && grep -q "agentsfleet-install-platform-ops" skills/index.mdx'
 
 check "test_concepts_v2_rewritten" \
   '! grep -E -i "AI-generated PRs|automated PR delivery|validated pull request" concepts.mdx'
@@ -47,7 +47,7 @@ check "test_no_self_host_page_in_v2" \
   '[ ! -f self-host.mdx ]'
 
 # Operator/ directory removed entirely (v1 self-host content was stale; v3 docs
-# will be authored fresh from usezombie/usezombie:docs/architecture/). Source
+# will be authored fresh from agentsfleet/agentsfleet:docs/architecture/). Source
 # absent → every /operator/* URL 404s.
 check "test_no_operator_pages_render" \
   '[ ! -d operator ]'
@@ -56,7 +56,7 @@ check "test_no_privacy_telemetry_page_in_v2" \
   '[ ! -f privacy/cli-telemetry.mdx ]'
 
 check "test_homelab_pages_404" \
-  '[ ! -f integrations/lead-collector.mdx ] && [ ! -f launch/homelab-zombie.mdx ]'
+  '[ ! -f integrations/lead-collector.mdx ] && [ ! -f launch/homelab-agent.mdx ]'
 
 # Cross-tab API entry resolution. Each `<METHOD> /<path>` entry in docs.json's
 # "API reference" tab must exist in the upstream openapi.json. Defers to the
@@ -71,37 +71,37 @@ check "test_api_tab_routes_resolve_in_openapi" \
 # changelog/ directory is excluded — historical Update entries reflect the
 # product as it was when the entry was written and are intentionally stale.
 
-# v1 sample names. Only platform-ops ships in usezombie/usezombie:samples/.
+# v1 sample names. Only platform-ops ships in agentsfleet/agentsfleet:samples/.
 # Re-introducing `slack-bug-fixer` or `homelab` in a current page sends
-# operators down `zombiectl install <name>` paths that fail with
+# operators down `agentsfleet install <name>` paths that fail with
 # MISSING_ARGUMENT.
 check "test_no_v1_sample_names_in_current_docs" \
   '! grep -rEl --include="*.mdx" --exclude-dir=changelog "slack-bug-fixer|slack_bug_fixer|\bhomelab\b|lead[_-]collector|lead[_-]scorer|homebox|pr-reviewer|pr_reviewer" . | grep -v "^./changelog.mdx$" | grep -q .'
 
-# `zombiectl up` does not exist in zombiectl/src/program/routes.js. Install IS
+# `agentsfleet up` does not exist in agentsfleet/src/program/routes.js. Install IS
 # the deploy in v2. Re-introducing it in a user-visible page sends operators
 # down a "command not found" rabbit hole.
-check "test_no_zombiectl_up_in_current_docs" \
-  '! grep -rEl --include="*.mdx" "zombiectl up\b" . | grep -v "^./changelog.mdx$" | grep -q .'
+check "test_no_agentsfleet_up_in_current_docs" \
+  '! grep -rEl --include="*.mdx" "agentsfleet up\b" . | grep -v "^./changelog.mdx$" | grep -q .'
 
-# Top-level CLI verb is `zombiectl login`, not `zombiectl auth login`. Verified
-# against zombiectl/src/program/routes.js (the `login` route entry).
-check "test_no_zombiectl_auth_login_in_current_docs" \
-  '! grep -rEl --include="*.mdx" "zombiectl auth login" . | grep -v "^./changelog.mdx$" | grep -q .'
+# Top-level CLI verb is `agentsfleet login`, not `agentsfleet auth login`. Verified
+# against agentsfleet/src/program/routes.js (the `login` route entry).
+check "test_no_agentsfleet_auth_login_in_current_docs" \
+  '! grep -rEl --include="*.mdx" "agentsfleet auth login" . | grep -v "^./changelog.mdx$" | grep -q .'
 
-# Webhook URL canonical form is api.usezombie.com, per usezombie/usezombie:
-# samples/platform-ops/README.md and skills/usezombie-install-platform-ops/
-# SKILL.md. Re-introducing hooks.usezombie.com sends webhooks to a domain that
+# Webhook URL canonical form is api.agentsfleet.net, per agentsfleet/agentsfleet:
+# samples/platform-ops/README.md and skills/agentsfleet-install-platform-ops/
+# SKILL.md. Re-introducing hooks.agentsfleet.net sends webhooks to a domain that
 # does not resolve.
 check "test_webhook_url_canonical_subdomain" \
-  '! grep -rE --include="*.mdx" "hooks\\.usezombie\\.com" . | grep -v "^./changelog.mdx" | grep -q .'
+  '! grep -rE --include="*.mdx" "hooks\\.agentsfleet\\.com" . | grep -v "^./changelog.mdx" | grep -q .'
 
 # Memory entries land in memory.memory_entries per schema/013_memory_entries.
-# sql:29 in usezombie/usezombie. core.zombie_memories never existed.
+# sql:29 in agentsfleet/agentsfleet. core.agent_memories never existed.
 check "test_memory_table_canonical_name" \
-  '! grep -rE --include="*.mdx" "core\\.zombie_memories|zombie_memories" . | grep -q .'
+  '! grep -rE --include="*.mdx" "core\\.agent_memories|agent_memories" . | grep -q .'
 
-# Real credential CLI shape per zombiectl/src/commands/zombie_credential.js
+# Real credential CLI shape per agentsfleet/src/commands/agent_credential.js
 # is `--data='<json>'` or `--data=@-` (stdin). Stale flags: `--value=`,
 # `--api-token`, `--bot-token`, `--host` for credential add. Each would fail
 # with parseFlags rejecting the unknown flag.
diff --git a/snippets/contact.mdx b/snippets/contact.mdx
index 9e1fe69..aa99133 100644
--- a/snippets/contact.mdx
+++ b/snippets/contact.mdx
@@ -1,10 +1,10 @@
 {/*
   Single canonical contact email for the docs site. Mirrors SUPPORT_EMAIL
   in src/config/contact.zig, ui/packages/website/src/lib/contact.ts,
-  ui/packages/app/lib/contact.ts, and zombiectl/src/lib/contact.js —
+  ui/packages/app/lib/contact.ts, and agentsfleet/src/lib/contact.js —
   cross-tier parity rule says the identifier matches across every
   runtime, so a future address rotation lands as a coordinated bump
   in all five places.
 */}
 
-export const SUPPORT_EMAIL = "usezombie@agentmail.to";
+export const SUPPORT_EMAIL = "agentsfleet@agentmail.to";
diff --git a/snippets/rates.mdx b/snippets/rates.mdx
index 676638f..bee7c4d 100644
--- a/snippets/rates.mdx
+++ b/snippets/rates.mdx
@@ -1,5 +1,5 @@
 {/*
-  Single source of truth for usezombie pricing strings on the docs site.
+  Single source of truth for agentsfleet pricing strings on the docs site.
 
   Mirrors the canonical Zig + TS + JS rate constants identifier-for-identifier
   (cross-tier parity rule):
@@ -7,7 +7,7 @@
                                               RUN_NANOS_PER_SEC
     - ui/packages/website/src/lib/rates.ts  — same names, bigint nanos values
     - ui/packages/app/lib/types.ts          — same names, JS Number nanos values
-    - zombiectl/src/constants/billing.js    — same names, JS Number nanos values
+    - cli/src/constants/billing.js    — same names, JS Number nanos values
 
   The keys below are the display strings keyed by role name. Bumping a rate
   requires a paired PR across the lead repo's rate constants AND this snippet —
diff --git a/style.css b/style.css
index 34c8286..77a5cf8 100644
--- a/style.css
+++ b/style.css
@@ -1,5 +1,5 @@
 /*
- * usezombie Mintlify overrides — Operational Restraint.
+ * agentsfleet Mintlify overrides — Operational Restraint.
  *
  * Mintlify's docs.json owns the bulk of the theming (colors, fonts,
  * code-block syntax theme). This file owns only the bits the schema
@@ -7,7 +7,7 @@
  * convention for cloud-build custom CSS pickup.
  *
  * Source-of-truth tokens live in
- * ~/Projects/usezombie/ui/packages/design-system/src/tokens.css.
+ * ~/Projects/agentsfleet/ui/packages/design-system/src/tokens.css.
  * Hex literals here are mirrored from there — change upstream first,
  * land here in the same release window.
  */
@@ -45,8 +45,8 @@
  * Selector targets the navbar primary button by its href; this is
  * stable against Mintlify's class-name churn between minor releases.
  */
-a[href="https://app.usezombie.com"],
-a[href="https://app.usezombie.com"] *,
+a[href="https://app.agentsfleet.net"],
+a[href="https://app.agentsfleet.net"] *,
 [data-mintlify-primary-button] {
   color: #0a0d0e;
 }
diff --git a/workspaces/managing.mdx b/workspaces/managing.mdx
index 85276be..a10e7cb 100644
--- a/workspaces/managing.mdx
+++ b/workspaces/managing.mdx
@@ -6,7 +6,7 @@ description: "Create, list, and remove workspaces."
 ## Add a workspace
 
 ```bash
-zombiectl workspace add [name]
+agentsfleet workspace add [name]
 ```
 
 The optional positional `name` is a human label; if omitted, the server picks a default. There is no repo URL — workspaces are tenant-scoped containers for credentials, agents, and webhook namespaces. Repos enter the picture later, when you configure per-agent webhooks (see [Quickstart](/quickstart)).
@@ -14,48 +14,48 @@ The optional positional `name` is a human label; if omitted, the server picks a
 For example:
 
 ```bash
-zombiectl workspace add platform-ops
+agentsfleet workspace add platform-ops
 ```
 
-The command creates the workspace, returns its `workspace_id`, and persists it as the active workspace in `~/.config/zombiectl/workspaces.json`.
+The command creates the workspace, returns its `workspace_id`, and persists it as the active workspace in `~/.config/agentsfleet/workspaces.json`.
 
 ## List workspaces
 
 ```bash
-zombiectl workspace list
+agentsfleet workspace list
 ```
 
 Lists every workspace under your tenant that the local CLI knows about, with the active marker.
 
 ```
-   WORKSPACE          NAME
-*  ws_01J8XV9R2M      platform-ops
-   ws_01J8XVKA3M      stripe-recon
-   ws_01J8XVKB7N      sentry-triage
+   WORKSPACE                               NAME
+*  0198a7b0-3c2d-7f14-9a08-1b6e4d2f8c50    platform-ops
+   0198a7b1-5d3e-7a29-b410-2c7f5e1a9d63    stripe-recon
+   0198a7b1-8f4a-7c1d-9e52-3a8b6d2f0c91    sentry-triage
 ```
 
-The leading `*` marks the active workspace (the one set by `zombiectl workspace use`). Add `--json` for the raw `{ items, current_workspace_id }` envelope.
+The leading `*` marks the active workspace (the one set by `agentsfleet workspace use`). Add `--json` for the raw `{ items, current_workspace_id }` envelope.
 
 ## Switch the active workspace
 
 ```bash
-zombiectl workspace use <workspace-id>
+agentsfleet workspace use <workspace-id>
 ```
 
-Makes the workspace active for subsequent CLI commands — `zombiectl install --from`, `zombiectl list`, `zombiectl status`, `zombiectl logs`, `zombiectl events`, `zombiectl steer`, and anything else that accepts a `--workspace-id` flag defaults to this value when the flag is omitted.
+Makes the workspace active for subsequent CLI commands — `agentsfleet install --from`, `agentsfleet list`, `agentsfleet status`, `agentsfleet logs`, `agentsfleet events`, `agentsfleet steer`, and anything else that accepts a `--workspace-id` flag defaults to this value when the flag is omitted.
 
-The choice is persisted to `~/.config/zombiectl/workspaces.json` (`current_workspace_id` field), so it survives across shells and sessions.
+The choice is persisted to `~/.config/agentsfleet/workspaces.json` (`current_workspace_id` field), so it survives across shells and sessions.
 
-Errors out if the id isn't in your local list — run `zombiectl workspace list` first to see what's available.
+Errors out if the id isn't in your local list — run `agentsfleet workspace list` first to see what's available.
 
 <Tip>
-  The dashboard at [app.usezombie.com](https://app.usezombie.com) has its own workspace switcher backed by a cookie. The CLI config and the dashboard cookie are independent — switching one does **not** affect the other. Useful when you want the CLI pointed at staging while the browser watches production.
+  The dashboard at [app.agentsfleet.net](https://app.agentsfleet.net) has its own workspace switcher backed by a cookie. The CLI config and the dashboard cookie are independent — switching one does **not** affect the other. Useful when you want the CLI pointed at staging while the browser watches production.
 </Tip>
 
 ## Show the active workspace
 
 ```bash
-zombiectl workspace show
+agentsfleet workspace show
 ```
 
 Prints the active workspace's `workspace_id`, `name`, `created_at`, and active marker. Pass `--workspace-id <id>` to inspect a specific workspace without changing the active one. Add `--json` for scripting.
@@ -65,7 +65,7 @@ This mirrors the dashboard **Settings** page.
 ## Delete a workspace
 
 ```bash
-zombiectl workspace delete <workspace-id>
+agentsfleet workspace delete <workspace-id>
 ```
 
 Deleting a workspace:
@@ -75,5 +75,5 @@ Deleting a workspace:
 - Retains run history for 30 days.
 
 <Warning>
-  This action cannot be undone. You'll need to recreate the workspace, re-add its credentials, and re-install its agents. Webhook URLs change because each new agent gets a fresh `zombie_id`, so any upstream webhook configurations will need to be updated too.
+  This action cannot be undone. You'll need to recreate the workspace, re-add its credentials, and re-install its agents. Webhook URLs change because each new agent gets a fresh `agent_id`, so any upstream webhook configurations will need to be updated too.
 </Warning>
diff --git a/workspaces/overview.mdx b/workspaces/overview.mdx
index 2197f98..4da6451 100644
--- a/workspaces/overview.mdx
+++ b/workspaces/overview.mdx
@@ -3,7 +3,7 @@ title: "Workspaces"
 description: "What a workspace is and how it relates to your tenant."
 ---
 
-A **workspace** is a tenant-scoped container for agents, their credentials, and their webhooks. Workspaces are not bound to a GitHub repo — repos enter the picture per-agent, when you wire an upstream webhook to a `zombie_id` (see [Webhooks](/zombies/webhooks)). Multiple workspaces under one tenant let you separate environments (staging vs. production) or domains (platform-ops vs. customer-success) without splitting billing, which stays at the tenant level.
+A **workspace** is a tenant-scoped container for agents, their credentials, and their webhooks. Workspaces are not bound to a GitHub repo — repos enter the picture per-agent, when you wire an upstream webhook to a `agent_id` (see [Webhooks](/agents/webhooks)). Multiple workspaces under one tenant let you separate environments (staging vs. production) or domains (platform-ops vs. customer-success) without splitting billing, which stays at the tenant level.
 
 ## What a workspace contains
 
@@ -11,7 +11,7 @@ Each workspace has its own:
 
 - **Agents** — the configured agents that live and run here.
 - **Credentials** — the vault keys agents in this workspace can read. Workspace-scoped on purpose: credentials do not leak across workspaces.
-- **Webhook namespace** — every agent in a workspace gets its own unique URL under `https://api.usezombie.com/v1/webhooks/{zombie_id}/{source}`.
+- **Webhook namespace** — every agent in a workspace gets its own unique URL under `https://api.agentsfleet.net/v1/webhooks/{agent_id}/{source}`.
 - **Access control** — teammates invited to a workspace can see, start, and kill its agents; they cannot see agents in other workspaces.
 
 ## What a workspace does NOT contain
@@ -31,7 +31,7 @@ A tenant gets unlimited workspaces and unlimited agents per workspace — there
 
 ## Workspace lifecycle
 
-1. **Create** — `zombiectl workspace add [name]` provisions a new workspace under your tenant and sets it active. Workspaces are not bound to a specific GitHub repo at creation time — repo bindings happen later via per-agent webhook configuration (see [Quickstart](/quickstart)).
+1. **Create** — `agentsfleet workspace add [name]` provisions a new workspace under your tenant and sets it active. Workspaces are not bound to a specific GitHub repo at creation time — repo bindings happen later via per-agent webhook configuration (see [Quickstart](/quickstart)).
 2. **Active** — agents can be installed, deployed, and triggered.
 3. **Paused** — `POST /v1/workspaces/{workspace_id}/pause` via the API (no CLI subcommand yet). New runs rejected; in-flight runs complete.
-4. **Deleted** — `zombiectl workspace delete <workspace-id>`. Run history retained 30 days. Webhook URLs are gone — any upstream pointing at an agent in this workspace starts hitting `UZ-WH-001` (agent not found).
+4. **Deleted** — `agentsfleet workspace delete <workspace-id>`. Run history retained 30 days. Webhook URLs are gone — any upstream pointing at an agent in this workspace starts hitting `UZ-WH-001` (agent not found).
diff --git a/zombies/install.mdx b/zombies/install.mdx
deleted file mode 100644
index 3d4a15e..0000000
--- a/zombies/install.mdx
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: "Installing an agent"
-description: "What `zombiectl install --from <path>` does and how to invoke it."
----
-
-`zombiectl install --from <path>` is how you bring an agent up. It reads `SKILL.md` and `TRIGGER.md` from the directory you point at, validates them, and uploads to your active workspace. **Install is the deploy** — there's no separate `up` step.
-
-```bash
-zombiectl install --from ~/.config/usezombie/samples/platform-ops
-```
-
-```
-✓ platform-ops-agent is live.
-  Zombie ID: zmb_2041
-  Webhook URLs (register on the upstream provider):
-    github: https://api.usezombie.com/v1/webhooks/zmb_2041/github
-```
-
-One URL is printed per declared `webhook` trigger in `TRIGGER.md`, keyed by `triggers[].source`. The host-agent install skill consumes this map and registers each URL on the upstream provider via the user's own `gh` (or equivalent) CLI — no paste-into-GitHub step. See [Quickstart](/quickstart) for the guided flow, or [Webhooks](/zombies/webhooks) if you maintain the upstream hook by hand.
-
-Re-running against the same workspace is safe — running it twice has the same effect as running it once. Your edits to `SKILL.md` / `TRIGGER.md` replace the previous version on the next event.
-
-## Two ways to invoke
-
-Most users don't run `zombiectl install --from` directly. They drive the install from a host agent (Claude Code, Amp, Codex CLI, OpenCode) via the `/usezombie-install-platform-ops` slash command. Add the skills with `npx skills add usezombie/skills`, which symlinks `/usezombie-*` into every supported host's skill directory it detects. Then invoke the slash command in your host agent:
-
-```
-/usezombie-install-platform-ops
-```
-
-<Tip>
-  **No global install?** `curl -fsSL https://usezombie.sh | bash` installs `zombiectl` and the skill together in one command (requires Node — it runs npm under the hood). Run `curl -fsSL https://usezombie.sh` without `| bash` to read it first.
-</Tip>
-
-The slash command asks three gating questions (Slack channel, production branch glob, optional cron schedule), registers the webhook via your existing `gh` CLI, and prints a per-trigger registration summary at the end. See [Quickstart](/quickstart) for the full walkthrough.
-
-Power users and scripted setups call `zombiectl install --from <path>` directly — the same flow as the slash command, minus the gating questions and the auto-registration.
-
-For the self-managed provider posture, see [`zombiectl tenant provider`](/cli/zombiectl#tenant-provider).
-
-## Exit codes
-
-| Code | Meaning |
-|---|---|
-| `0` | Installed (or updated). |
-| `1` | No workspace selected, or API error. |
-| `2` | Missing `--from`, invalid path, or schema rejection. |
-
-## See also
-
-- [Templates](/zombies/templates) — the catalogue of pre-built agents you can install.
-- [Authoring an agent](/zombies/authoring) — the `SKILL.md` and `TRIGGER.md` reference for writing your own.
-- [Starting, observing, and stopping](/zombies/running) — what to do after install.
diff --git a/zombies/overview.mdx b/zombies/overview.mdx
deleted file mode 100644
index 4dc9bf6..0000000
--- a/zombies/overview.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-title: "Agents"
-description: "What an agent is, the lifecycle it moves through, and how it relates to your workspace."
----
-
-## Overview
-
-An **agent** is a preconfigured, always-on agent process in your workspace. You describe it once — its trigger, the skills it can use, the credentials it needs, the budget it is allowed to consume — and the platform keeps it alive, receiving events and invoking the agent, until you kill it.
-
-Everything in this section of the docs is about working with agents: how to install one from a template, how to start and stop it, how to attach credentials, how webhooks reach it, and how to author the `SKILL.md` and `TRIGGER.md` files that define its behavior.
-
-## Lifecycle
-
-An agent moves through five observable states.
-
-```mermaid
-flowchart LR
-    Install[zombiectl install --from path] --> Alive[Alive<br/>webhook live]
-    Alive -->|event arrives| Processing[Processing<br/>agent reasoning]
-    Processing -->|run exits| Alive
-    Alive -->|zombiectl stop| Stopped[Stopped<br/>paused]
-    Stopped -->|zombiectl resume| Alive
-    Alive -->|zombiectl kill| Killed[Killed<br/>terminal]
-    Stopped -->|zombiectl kill| Killed
-    Killed -->|zombiectl delete| Deleted([deleted — hard-removed])
-```
-
-1. **Alive.** `zombiectl install --from <path>` reads the local `SKILL.md` + `TRIGGER.md`, validates the schema, uploads to your workspace, provisions the webhook URL, and starts the event loop. Install is the deploy — there is no separate `up` step.
-2. **Processing.** When a signed event arrives (webhook, cron, or steer), the platform opens a **run**: the agent reads the event, reasons, invokes the tools listed in `TRIGGER.md`, and produces a result. The activity stream is the durable record — replay any time with `zombiectl logs <zombie_id>` (or `events --actor 'webhook:*'` for filtered history).
-3. **Stopped.** `zombiectl stop <zombie_id>` halts the running session — new events stop dispatching, the in-flight run finishes cleanly. Reversible with `zombiectl resume`. Use this for "pause while I debug upstream"; reach for `kill` only when you mean *terminal*.
-4. **Killed.** `zombiectl kill <zombie_id>` marks the agent terminal. The row, history, and webhook URL persist but no new events are processed. State is checkpointed; nothing on the event stream is lost. Re-install with the same `SKILL.md` produces a **new** `zombie_id`.
-5. **Deleted.** `zombiectl delete <zombie_id>` hard-removes the agent. The row, its `zombie_id`, and its webhook URL are gone — the webhook URL starts returning `UZ-WH-001` for any new POSTs. The activity-stream history is retained for the workspace's retention window per [Observability](/cli/zombiectl#observability); replays after delete reference the prior `zombie_id` as a historical record only. You must `kill` the agent before `delete` will accept it.
-
-You can inspect state at any time:
-
-```bash
-zombiectl status                     # every agent in the active workspace
-zombiectl logs zmb_2041              # tail one agent's recent activity
-zombiectl steer zmb_2041 "morning health check"   # manual trigger
-```
-
-## Workspace scoping
-
-Every agent belongs to exactly one **workspace**. The workspace is the boundary for:
-
-- **Credentials** — the vault that agents read from when they invoke skills. See [Credentials](/zombies/credentials).
-- **Access control** — teammates invited to a workspace can see, start, and kill its agents; they cannot see agents in other workspaces.
-- **Webhook namespace** — every agent in a workspace gets one unique URL per declared trigger under `https://api.usezombie.com/v1/webhooks/{zombie_id}/{source}` (one entry per `triggers[].source` in `TRIGGER.md`).
-
-Billing is **not** workspace-scoped — every workspace draws on the same tenant-level billing. See [Billing](/billing/plans) for the model.
-
-`zombiectl workspace add [name]` creates a new workspace and sets it as active. Switch between existing ones with `zombiectl workspace use <id>` (run `zombiectl workspace list` first to see the IDs). The dashboard's active-workspace selection is independent — switching there does not affect the CLI and vice versa.
-
-## What's next
-
-<CardGroup cols={2}>
-  <Card title="Install an agent" icon="download" href="/zombies/install">
-    Scaffold an agent from a bundled template.
-  </Card>
-  <Card title="Start, stop, observe" icon="circle-play" href="/zombies/running">
-    The `install`, `status`, `events`, `steer`, and `kill` commands.
-  </Card>
-  <Card title="Workspace credentials" icon="key" href="/zombies/credentials">
-    Add secrets to the vault without the agent ever seeing them.
-  </Card>
-  <Card title="Authoring an agent" icon="file-code" href="/zombies/authoring">
-    How `SKILL.md` and `TRIGGER.md` combine to define an agent.
-  </Card>
-</CardGroup>