Repository navigation
Conversation
Projects can now have several tokens, each with a name, linked projects, permissions, an expiration and a last-used date. Tokens are hashed and shown only once, so the docs no longer say to copy the token from the project settings or to regenerate it. - Add Account & access → Project tokens: where tokens are managed and by whom, permission presets, expiration, rotation without downtime, multi-project tokens and ARGOS_PROJECT, legacy tokens, and the API/MCP endpoints. - Point every "Settings → Authentication → Project token" mention to creating a token, and replace the Regenerate section of Run Argos in CI. - Say which permissions the CLI read commands, baseline download and media commands need, and that a multi-project token needs ARGOS_PROJECT. - Transfer: tokens linked only to the project move with it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
argos-ci/argos-javascript#411 adds `argos project token` and `argos account project-token` (list, create, revoke), and lets `finalize`, `skip`, `deploy` and `baseline download` take `--project` for a token linked to several projects. - CLI reference: add both command groups, with their defaults (every permission, no expiration) and the roles they need; drop "baseline download has no --project flag"; say what --project does for a multi-project token. - Project tokens: mention the CLI next to the API, and that ARGOS_PROJECT naming another project fails with a 401 for a single-project token. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
argos-ci/argos#2747 (749192a65) changed what the docs describe: - Creating a token through the API or the CLI without `permissions` now grants `builds:write` and `deployments:write`, not every permission. The CLI examples drop the now-redundant `--permissions`. - `expireAt` is required on the REST create endpoints (`null` for a token that never expires). The CLI still sends `null` by default. - The Upload from CI preset lets CI upload builds and deployments, but not media, instead of covering everything CI needs. - A token linked to a single project ignores ARGOS_PROJECT instead of rejecting a mismatched one with a 401. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
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
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.
Important
Merge once argos-ci/argos#2747 is deployed. Until then, these docs describe a UI and API that don't exist in production yet.
The CLI parts (
argos project token,argos account project-token,--projectonbaseline download) andARGOS_PROJECTfor multi-project tokens also need argos-ci/argos-javascript#411 released. If the SDK release lags behind the deploy, hold this PR until it ships.Documents the project tokens shipped by argos-ci/argos#2747 (Linear ARG-519). A project can have several tokens, each hashed and shown once, with permissions and an optional expiration, so the old "copy it from Settings → Authentication → Project token" and "Regenerate token" instructions are wrong.
New page: Account & access → Project tokens
media:write) andargos baseline download(projects:read+builds:write). Also the 403 message.ARGOS_PROJECT=owner/project; a single-project token ignores it. Transfer behavior.GET/POST /projects/{owner}/{project}/tokens,DELETE …/tokens/{tokenId}, andGET/POST/DELETE /accounts/{accountSlug}/project-tokens, with the role each one requires. The create endpoints requireexpireAt(nullfor never), and defaultpermissionstobuilds:write+deployments:write. The same operations are MCP tools.Registered in
docs/SUMMARY.mdand in the Account & access README.Updated mentions
ARGOS_TOKENnow links to the new page and says to create the token in Settings → Authentication and copy it right away.ARGOS_PROJECTis added to the env var table.baseline downloadneeds Read projects + Upload builds and takes--projectfor a multi-project token. A project token identifies its project only when it is linked to a single project. Newproject token list|create|revokeandaccount project-token list|create|revokesections, from feat: support project tokens linked to several projects, and rotate them from the CLI argos-javascript#411. Without flags, the CLI creates an upload-only token that never expires, so the docs say to pass--expires-in.To check before merging
ARGOS_PROJECTor the token commands. Add one if you want it once feat: support project tokens linked to several projects, and rotate them from the CLI argos-javascript#411 is released.🤖 Generated with Claude Code