docs: whoami, per-fleet charges, and removable workspace library entries - #203
Merged
Merged
Conversation
`agentsfleet whoami` and `GET /v1/users/me` are new user surfaces, so the command reference, the API introduction and the changelog carry them. Two corrections travel with the entry. `agentsfleet auth status` was documented as showing the token's claims; a command-line credential has none, and the command shows the credential's source, its target and the server's verdict. And both login and `auth status` used to check a credential against `GET /v1/tenants/me/billing`, which needs `billing:read` — anyone signed in without that scope was told their credential had been rejected. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
A client that asks for /v1/users/me on a deployment without it gets a 404, and a 404 judges no credential — a path is matched before a credential is checked. The note says what each command does in that window and that every other command keeps working. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
… what it resumed M203_001. The ledger's arbiter gains the fleet, so two fleets sharing one event id can no longer accumulate into a single row; the continuation's narrative row keeps its predecessor whichever writer lands first; and a charge's `fleet_id` stops being documented as nullable. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Four pages for the removal verb. The library page gains the list and remove walk, what survives a removal and what does not, and the dashboard's Library page. The command-line reference gains both verbs and says plainly how `agentsfleet library` and `agentsfleet library list` differ — one is everything installable here, the other is only what this workspace owns. The error reference gains no code, because none was minted: a malformed entry_id is a plain 400, a cursor from the wrong collection is UZ-LIBRARY-001, and a database failure is UZ-LIBRARY-006. One new changelog entry. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
schedule add, rm and status are create, delete and show, matching every other collection on the surface. No alias survives either spelling, so the retired ones are gone from the reference rather than listed as deprecated. status keeps answering for the whole workspace and takes no identifier; the one-fleet read is fleet show, which the reference now carries. Every list prints name, then identifier, then what the thing is, then how long ago it arrived. The rendered samples move with it: the workspace list's bare asterisk is a STATUS column reading active, and the gallery leads with the name rather than the identifier. The gallery samples also say why TIER matters — two entries can share a name across the tiers — and name the badge the dashboard shows for the same thing. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
`library add` becomes `library create` and `library remove` becomes `library delete`, so the group stops spelling create and delete its own way. The reference pages describe what the CLI does, so every occurrence moves with it. The changelog does not. Two bullets under the Sep 19 entry name `agentsfleet library add`, and that is what shipped in 0.49.0 — editing them would put a command in the record that never existed on that date. The rename gets its own bullet under the unreleased entry instead, naming the break, because no alias is kept and a script pinning the old spelling needs an edit. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
`connector status` becomes `connector show`, because a single-resource read is called `show` everywhere else on this surface and the command's own help already said so. `auth status` goes. It overlapped `whoami` on identity and the target, and `doctor` on reachability, leaving one field of its own: where the live credential came from. That field moves to `whoami` rather than being lost, so the table gains a `whoami` row — the command was never documented here, which is why removing `auth status` would otherwise have left a hole. The Sep 16 entry naming `connector status` stays as written. That is what shipped. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…anch changelog.mdx entries from all three branches are re-applied in one pass after the merges, so this merge keeps main's copy. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…ned changelog branch Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…mbined changelog branch Resolves the account-and-diagnosis table in favour of m204: auth status is gone and whoami answers for it. The changelog entries for m200, m203 and m204 are re-applied here in plain language, in one pass. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Greptile review of #203: - the schedule option table still routed --cron, --message and --timezone to the removed add verb - fleets/library.mdx and fleets/authoring.mdx still said no command and no endpoint removed a workspace library entry - library:write was described as adding only - whoami's field list omitted the source field it gains on Sep 21 - /v1/users/me's refusal named UZ-AUTH-001, whose message sends the caller to an operator about API keys; the spec names no code for that 403, so the changelog now words it as the spec does Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
indykish
deleted the
chore/m200-m204-whoami-ledger-library-changelog
branch
September 22, 2026 09:57
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Combines three docs branches that were open against
mainwith no PR between them:chore/m200-whoami-changelog,chore/m203-ledger-key-and-lineage-changelog, andchore/m204-workspace-library-removal-changelog.What's here
agentsfleet whoami,GET /v1/users/me, the sign-in check that no longer needsbilling:readagentsfleet billinggroups by fleet and eventlibrary add→library create,connector status→connector show,auth statusfolded intowhoamiChangelog
The three
<Update>blocks were rewritten in plain language rather than merged as-is. Each one now leads with what changed for the reader, follows the fixed section order (Upgrading → What's new → API reference → Bug fixes), and keeps the load-bearing detail: endpoint paths, error codes (UZ-AUTH-001,UZ-LIBRARY-001,UZ-LIBRARY-006), scope names, and column names. Entries dated before these three are untouched.Merge resolutions
cli/agentsfleet.mdx, account and diagnosis table — resolved in favour of m204.agentsfleet auth statusis removed andwhoamianswers for it; the--token-namedescription now points atwhoamitoo.changelog.mdx— each merge keptmain's copy, and all three entries were re-applied together in the final commit so the dates stay ordered around the existing Sep 20 Bun entry.Verification
make lintpasses end to end: documentation checks, OpenAPI drift,mintlify validate, broken links, and markdown link check.🤖 Generated with Claude Code
The documentation changes appear safe to merge, with no outstanding correctness or repository-rule violations.
Summary
This PR updates the documentation for three product changes:
agentsfleet whoamiand the scope-freeGET /v1/users/meidentity check.Reviews (2) · Last reviewed commit: "docs: the library removal reads the same..."