Rotate an Automation Secret
Issue a new automation secret when the old one should no longer be trusted, then replace it everywhere the old secret was used.
The CLI rotate command can also store the new secret as the active token when the next step stays in the terminal.
- Rotate intentionally.
- Copy the new secret immediately.
- Replace the old secret everywhere.
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.
Do the work
- 1. Run the rotate command with the automation id.
- 2. Add `--credential-label` if the new secret should have a specific label.
- 3. Add `--use` when the CLI profile should immediately switch to the new secret.
- 4. Replace the old secret in every external system that still holds it.
Keep Going in Automation and Agents
Stay in the same interface and move to the next closest task in this topic when needed.
Exchange an Automation Secret
Exchange an automation secret for an access token.
List Automations
Review the current workspace automations before you create, update, or rotate one.
Create an Automation
Create the workspace automation boundary, issue the automation secret, and store that secret safely because it is only shown once.
Update an Automation
Change automation metadata, team boundaries, scopes, or suspension state without recreating the automation.
List Visible Agents
Review the current visible agent bindings before creating a new agent or editing an existing one.
Create a Visible Agent
Create a named visible agent under an existing installation so activity, assignees, and attribution can point to a meaningful product actor.
Update a Visible Agent
Change a visible agent name, team scope, role, or suspension state without recreating the binding.
Nearby Guides
These guides stay close to the current workflow so you can keep moving without restarting discovery.