Create a Personal Access Token
Create a human-owned API key with the narrowest useful scope set and store it safely because the raw token is only shown once.
CLI In this interface
4 steps Steps
3 interfaces Available in
Use this path when
The CLI create command can also immediately switch the current profile to the newly issued PAT.
What you'll finish here
- Choose scopes deliberately.
- Copy the raw token immediately.
- Use PATs only for human-owned automation.
Where this happens
Same Task, Other Interfaces
Use the version that matches where you are working now. The subject matter stays the same; the delivery changes by surface.
Keep this boundary clear
- PATs belong to a human and never exceed the human role. They are not workspace-shared automation credentials.
Do the work
- 1. Run `./backlog.sh pat create` with a label and the narrowest set of repeated `--scope` flags you need.
- 2. Add `--use` if the current CLI profile should immediately start using the new PAT.
- 3. Capture the token output securely if you are not using `--use`.
- 4. Run `./backlog.sh status` afterward if you want to confirm the new auth mode.
Keep Going in Sessions and Personal Tokens
Stay in the same interface and move to the next closest task in this topic when needed.
CLI Sessions and Personal Tokens
List Personal Access Tokens
Review the current personal API keys before creating a new one or revoking an old one.
4 steps
CLI Sessions and Personal Tokens
Revoke a Personal Access Token
Revoke a human-owned API key by credential id when it is obsolete, leaked, or no longer appropriate for the workflow.
4 steps
Nearby Guides
These guides stay close to the current workflow so you can keep moving without restarting discovery.