From b059447961cd4026060fdf9b47042a6a16858c1e Mon Sep 17 00:00:00 2001 From: Kishore Kumar Date: Mon, 15 Jun 2026 18:58:07 +0530 Subject: [PATCH 1/4] =?UTF-8?q?docs(m92-004):=20changelog=20=E2=80=94=20an?= =?UTF-8?q?nounce=20the=20agentsfleet=20rebrand=20+=20breaking=20changes?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Add the Jun 15 for the usezombie->agentsfleet cutover shipping in M92_004: CLI zombiectl->agentsfleet, host api.agentsfleet.net, env ZOMBIE_*->AGENTSFLEET_*, routes /zombies->/agents + zombie_id->agent_id, error codes UZ-ZMB-*->UZ-AGT-*, token prefixes agt_a/agt_t/agt_r, npm @agentsfleet/cli. Also flip the changelog's own current-product refs (frontmatter description, the stealth , support mail) to agentsfleet; historical entries are left as-is (they document zombie-era releases accurately). The broader docs prose rebrand (error-codes/cli/billing/README, ~37 files) is the deferred follow-up, not bundled here. Co-Authored-By: Claude Opus 4.8 (1M context) --- changelog.mdx | 38 ++++++++++++++++++++++++++++++++++++-- 1 file changed, 36 insertions(+), 2 deletions(-) diff --git a/changelog.mdx b/changelog.mdx index 412a11b..76dfa71 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"; - 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. + + ## 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`, tenant API keys `agt_t`, runner tokens `agt_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 + + ``` + 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. + + ## Scratch memories now expire on their own From 2a7b68dcd8fe6080bb09939f03d274914b2189c4 Mon Sep 17 00:00:00 2001 From: Kishore Kumar Date: Mon, 15 Jun 2026 19:04:37 +0530 Subject: [PATCH 2/4] docs(m92-004): rebrand docs prose usezombie->agentsfleet (textual cutover) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Flip the user-facing docs to the shipped brand across 37 files: zombiectl-> agentsfleet, hosts *.usezombie.com->*.agentsfleet.net, usezombie.sh-> agentsfleet.dev, @usezombie/zombiectl->@agentsfleet/cli, ZOMBIE_*->AGENTSFLEET_*, UZ-ZMB-*->UZ-AGT-*, /zombies->/agents, zombie_id->agent_id, core.zombie-> core.agent, x-usezombie->x-agentsfleet, and the zombie->agent entity noun. Ordered compound-first so usezombie never degrades to useagent, zombiectl to agentctl, or zombied to agentd (degradation check clean). changelog.mdx historical entries keep their zombie-era refs — they document past releases accurately (per Indy + the changelog history-append rule). Without this, post-merge the live docs would document a product that no longer exists: every zombiectl / api.usezombie.com / ZOMBIE_* is a dead instruction after the hard cutover. Co-Authored-By: Claude Opus 4.8 (1M context) --- .gitleaks.toml | 2 +- .mlc-config.json | 4 +- AGENTS.md | 18 +-- Makefile | 2 +- README.md | 8 +- api-reference/error-codes.mdx | 52 ++++---- api-reference/introduction.mdx | 16 +-- billing/budgets.mdx | 12 +- billing/plans.mdx | 6 +- cli/configuration.mdx | 46 +++---- cli/flags.mdx | 10 +- cli/install.mdx | 24 ++-- cli/zombiectl.mdx | 216 ++++++++++++++++----------------- concepts.mdx | 22 ++-- concepts/context-lifecycle.mdx | 4 +- docs.json | 68 +++++------ favicon.svg | 2 +- index.mdx | 24 ++-- logo/dark.svg | 2 +- logo/mark-glow.svg | 2 +- memory.mdx | 4 +- quickstart.mdx | 70 +++++------ scripts/test-spec.sh | 42 +++---- snippets/contact.mdx | 4 +- snippets/rates.mdx | 4 +- style.css | 8 +- workspaces/managing.mdx | 26 ++-- workspaces/overview.mdx | 8 +- zombies/authoring.mdx | 40 +++--- zombies/credentials.mdx | 26 ++-- zombies/install.mdx | 28 ++--- zombies/overview.mdx | 42 +++---- zombies/running.mdx | 76 ++++++------ zombies/templates.mdx | 10 +- zombies/tools.mdx | 22 ++-- zombies/troubleshooting.mdx | 76 ++++++------ zombies/webhooks.mdx | 26 ++-- 37 files changed, 526 insertions(+), 526 deletions(-) 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` `` block** at the top, after the leading ``. 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 @@ - usezombie + agentsfleet **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) @@ -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/api-reference/error-codes.mdx b/api-reference/error-codes.mdx index 5ef5a9f..cfd5e5a 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,10 +9,10 @@ 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", + "docs_uri": "https://docs.agentsfleet.net/api-reference/error-codes#UZ-AGT-009", + "title": "Agent not found", + "detail": "No agent with id 'abc123' in this workspace.", + "error_code": "UZ-AGT-009", "request_id": "req_a1b2c3d4e5f6" } ``` @@ -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 --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 --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. | -**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 ` 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 ` for the actual error text. ## 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 `. | -| `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 `. | +| `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. | -`UZ-ZMB-007` is retired; oversized credential bodies now return [`UZ-VAULT-002`](#vault). +`UZ-AGT-007` is retired; oversized credential bodies now return [`UZ-VAULT-002`](#vault). ## 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..c1edadf 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/ws_abc/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. +- **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,7 +29,7 @@ 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", @@ -43,7 +43,7 @@ Error codes follow the `UZ--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 View the full OpenAPI 3.1 specification 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. - **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). ## 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). -A `zombiectl billing budget set` CLI command is planned for a future release. +A `agentsfleet billing budget set` CLI command is planned for a future release. ## Run cancellation Cancel an in-flight run at any time via CLI or API: ```bash -zombiectl kill +agentsfleet kill ``` 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. - **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). ## 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/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 `** — 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 ` | API base URL | `https://api.usezombie.com` | +| `--api ` | 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 ``` ## 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=` 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=` to target a single host instead of every detected one. - **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. -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/cli/zombiectl.mdx b/cli/zombiectl.mdx index dd2391a..a57c677 100644 --- a/cli/zombiectl.mdx +++ b/cli/zombiectl.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 ` — 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