Skip to content

Commit 2967aa3

Browse files
committed
format
1 parent 8df192a commit 2967aa3

File tree

1 file changed

+13
-13
lines changed

1 file changed

+13
-13
lines changed

docs/rfds/acp-agent-registry.mdx

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -23,19 +23,19 @@ Every editor builds bespoke manifests or scrapes GitHub, leading to duplication
2323

2424
Each agent advertises itself via `agent.json` stored under `<id>/` in the registry repo. JSONC keeps things close to ACP’s JSON-centric schemas while remaining human-friendly during authoring. Fields (required unless noted):
2525

26-
| Field | Description |
27-
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
28-
| `id` | Lowercase slug, unique across registry (also the folder name). |
29-
| `name` | Human-readable label. |
30-
| `version` | Agent release version surfaced to users. |
31-
| `schema_version` | Semver of the manifest schema. Allows future breaking changes. |
32-
| `description` | Description of the agent's functionality and purpose. |
33-
| `homepage` | URL for docs/marketing. |
34-
| `repository` | Source repository URL. |
35-
| `authors` | Array of author/organization names (mirrors `authors` in the TOML example). |
36-
| `license` | Licence (string). |
37-
| `capabilities` | Array of ACP method names implemented (e.g. `["terminal/new","files/read"]`). |
38-
| `auth` | Array of auth options for authentication. This is the trickiest part of the schema. |
26+
| Field | Description |
27+
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
28+
| `id` | Lowercase slug, unique across registry (also the folder name). |
29+
| `name` | Human-readable label. |
30+
| `version` | Agent release version surfaced to users. |
31+
| `schema_version` | Semver of the manifest schema. Allows future breaking changes. |
32+
| `description` | Description of the agent's functionality and purpose. |
33+
| `homepage` | URL for docs/marketing. |
34+
| `repository` | Source repository URL. |
35+
| `authors` | Array of author/organization names (mirrors `authors` in the TOML example). |
36+
| `license` | Licence (string). |
37+
| `capabilities` | Array of ACP method names implemented (e.g. `["terminal/new","files/read"]`). |
38+
| `auth` | Array of auth options for authentication. This is the trickiest part of the schema. |
3939
| `distribution` | Object mapping target platforms to download/execution info. Each target key follows `<os>-<arch>` format (e.g., `darwin-aarch64`, `linux-x86_64`, `windows-x86_64`). Each target specifies `archive` (download URL), `cmd` (executable path), optional `args` (array of command-line arguments), and optional `env` (object of environment variables). |
4040

4141
Example skeleton:

0 commit comments

Comments
 (0)