docs(cli): the client runs on Bun, and refusals name their flag

changelog.mdx

@@ -7,6 +7,34 @@ description: "Stay up to date with the latest agentsfleet product updates, new f
   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="Sep 20, 2026" tags={["CLI", "Breaking changes"]}>
+  ## The command-line client runs on Bun
+
+  `agentsfleet` now runs on the Bun runtime. Install Bun 1.4 or later before you install the client. Install the client with `bun install --global @agentsfleet/cli`. If `bun` is not on your `PATH`, the command reports that it was not found.
+
+  ## Breaking changes
+
+  - **`--no-open` and `--no-input` belong to `login`** — write them after the command name, as `agentsfleet login --no-open`. Written before it, as `agentsfleet --no-open login`, they are now rejected as unknown flags. `--api` and `--json` are unchanged and still work in either position.
+  - **Bun 1.4 or later is required** — the client no longer runs on Node.js alone.
+  - **`--workspace-id` is now `--workspace`** — `agentsfleet list` and `agentsfleet workspace show` took `--workspace-id`, while the `agentsfleet schedule` subcommands took `--workspace`. One spelling now, matching `--fleet`. `agentsfleet list --workspace-id <id>` is rejected as an unknown flag; write `agentsfleet list --workspace <id>`.
+
+  ## What's new
+
+  - **`agentsfleet help <command>` reads the same as `agentsfleet <command> --help`** — both print the same body, for a command or a group.
+  - **An unrecognised command names a next step** — a near match is suggested, and a command matching nothing points at the command list for the group you were in, not the root.
+  - **Help fits an eighty-column terminal** — every line wraps at eighty characters, and options advertise the value they take, such as `--limit <n>` and `--api <url>`.
+
+  ## Bug fixes
+
+  - **A mistyped flag reports the flag, not your sign-in** — `agentsfleet list --limit 0` while signed out now says `must be ≥ 1` and exits `4`. It used to ask you to sign in first, and the flag was still wrong when you came back.
+  - **`agentsfleet doctor` exits non-zero when a check fails** — it reported success while naming an unreachable server.
+  - **A refused value names the bound it crossed, the flag it came from, and the value you passed** — `agentsfleet list --limit 0` reports `invalid --limit: must be ≥ 1 (got "0")`. Flags and arguments read the same way, so a wrong value buried in a long command is visible without re-reading the line you typed.
+  - **`--json` prints the error envelope and nothing else** — a rejected invocation used to print the help page above it, so reading the output as JSON failed on the first character. `agentsfleet --help --json` still prints help.
+  - **A dropped connection is retried, on every command** — a socket lost mid-request used to fail the command outright with `cannot reach agentsfleet API`. It is now sent again, up to three attempts with a growing pause, because a reply you never saw is usually a request that never ran. A server that answers — a `503`, a rate limit, a timeout the client declared — is unchanged: those still stop at one attempt for anything that writes.
+  - **What a retry can cost you, stated plainly** — if the connection drops *after* the server accepted the write, the second attempt is a second write. `agentsfleet secret create` reports `already exists` for the value it just stored (the vault holds what you sent; no `secret update` is needed), and `agentsfleet api-key create` can leave a key you never see the secret for — check `agentsfleet api-key list` if a create is interrupted. A rejected certificate or an unusable URL is never retried, and now says so in its own words instead of suggesting you check your network.
+
+</Update>
+
 <Update label="Sep 19, 2026" tags={["API", "What's new", "Bug fixes"]}>
   ## A reviewer fleet reviews without asking you first
 

cli/agentsfleet.mdx

@@ -54,10 +54,19 @@ Commands:
 | `-v`, `--version` | Prints the client version and exits. | `false` | Boolean |
 | `--api <API_URL>` | Sends requests to this API URL. | `https://api.agentsfleet.net` | URL beginning with `http://` or `https://` |
 | `--json` | Prints JSON when the command supports it. | `false` | Boolean |
-| `--no-input` | Returns an error instead of asking a question. | `false` | Boolean |
-| `--no-open` | Prints the login URL instead of opening a browser. | `false` | Boolean |
 | `-h`, `--help` | Prints help and exits. | `false` | Boolean |
 
+### Login options
+
+Write these after `login`. Only `agentsfleet login` reads them.
+
+| Option | Effect | Default | Unit or range |
+|---|---|---|---|
+| `--no-open` | Prints the login URL instead of opening a browser. | `false` | Boolean |
+| `--no-input` | Returns an error instead of asking a question. | `false` | Boolean |
+| `--force` | Signs in again even when this computer already holds a credential. | `false` | Boolean |
+| `--token-name <LABEL>` | Labels this sign-in on the approval page and in `agentsfleet auth status`. | The platform family name | Text |
+
 ### Account and diagnosis
 
 | Command | Effect |

cli/flags.mdx

@@ -36,10 +36,12 @@ agentsfleet --version
 | `-v`, `--version` | Prints the client version and exits. | `false` | Boolean |
 | `--api <URL>` | Sends API requests to this base URL. | `https://api.agentsfleet.net` | URL beginning with `http://` or `https://` |
 | `--json` | Prints machine-readable JSON when the command supports it. | `false` | Boolean |
-| `--no-input` | Returns an error instead of asking for input. | `false` | Boolean |
-| `--no-open` | Prints the login URL instead of opening a browser. | `false` | Boolean |
 | `-h`, `--help` | Prints help and exits. | `false` | Boolean |
 
+`--no-open`, `--no-input`, `--force`, and `--token-name` belong to
+`agentsfleet login`. Write them after the command name. See
+[Command reference](/cli/agentsfleet#login-options).
+
 ## Errors
 
 The client returns exit code `0` after success. Authentication and unexpected failures return `1`.

cli/install.mdx

@@ -15,18 +15,19 @@ This installs the `agentsfleet` command-line client. You can then manage fleets
 
 ## Before you begin
 
-Install Node.js 24 or later. The package also supports Bun 1.3.14 or later.
+Install Bun 1.4 or later. The `agentsfleet` command runs on Bun.
 
 ## Steps
 
-1. Install the package from npm.
+1. Install the package.
 
    ```bash
-   npm install --global @agentsfleet/cli
+   bun install --global @agentsfleet/cli
    ```
 
    ```text
-   added <varies> packages in <varies>
+   installed @agentsfleet/cli with binaries:
+    - agentsfleet
    ```
 
 2. Show the client version.
@@ -55,20 +56,20 @@ The command checks the API, your selected workspace, and the workspace binding.
 
 ## Common problems
 
-If `agentsfleet` is not found, reopen the terminal. Also check that the npm global binary directory is in your `PATH`.
+If `agentsfleet` is not found, reopen the terminal. Also check that Bun's global binary directory, `~/.bun/bin`, is in your `PATH`.
 
-If installation reports an unsupported runtime, upgrade Node.js to version 24 or later.
+If the command reports that `bun` was not found, install Bun 1.4 or later and reopen the terminal.
 
 ## Remove or undo
 
 Removing the client does not delete remote fleets or workspace data.
 
 ```bash
-npm uninstall --global @agentsfleet/cli
+bun remove --global @agentsfleet/cli
 ```
 
 ```text
-removed <varies> packages in <varies>
+removed @agentsfleet/cli
 ```
 
 ## Related pages

docs.json

@@ -146,6 +146,12 @@
               "DELETE /v1/api-keys/{id}"
             ]
           },
+          {
+            "group": "Users",
+            "pages": [
+              "GET /v1/users/me"
+            ]
+          },
           {
             "group": "Tenants",
             "pages": [
@@ -272,8 +278,10 @@
               "GET /v1/workspaces/{workspace_id}/fleet-libraries",
               "POST /v1/admin/fleet-libraries",
               "POST /v1/workspaces/{workspace_id}/fleet-libraries",
+              "GET /v1/workspaces/{workspace_id}/library-entries",
               "PATCH /v1/admin/fleet-libraries/{id}",
-              "DELETE /v1/admin/fleet-libraries/{id}"
+              "DELETE /v1/admin/fleet-libraries/{id}",
+              "DELETE /v1/workspaces/{workspace_id}/library-entries/{entry_id}"
             ]
           },
           {

quickstart.mdx

@@ -19,7 +19,7 @@ If you need access, [join the waitlist](https://accounts.agentsfleet.net/waitlis
 
 Open the [dashboard](https://app.agentsfleet.net) to manage your workspace. For your profile and sign-in security, choose **Manage account** in the account menu. You can also open [account settings](https://app.agentsfleet.net/settings/account) directly.
 
-You need Node.js 24 or later. You also need an `agentsfleet` account and a GitHub repository that you can manage.
+You need Bun 1.4 or later. You also need an `agentsfleet` account and a GitHub repository that you can manage.
 
 Create a GitHub token that can read the repository and post comments. Keep the token ready for step 4.
 
@@ -28,11 +28,12 @@ Create a GitHub token that can read the repository and post comments. Keep the t
 1. Install the `agentsfleet` command-line interface.
 
    ```bash
-   npm install --global @agentsfleet/cli
+   bun install --global @agentsfleet/cli
    ```
 
    ```text
-   added <varies> packages in <varies>
+   installed @agentsfleet/cli with binaries:
+    - agentsfleet
    ```
 
 2. Check the installed version.