Update an Automation
Change automation metadata, team boundaries, scopes, or suspension state without recreating the automation.
The CLI update command handles the same automation maintenance work from the terminal.
- Edit the correct automation.
- Narrow scopes safely.
- Suspend access without deleting context.
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 update command with the automation id.
- 2. Add only the flags that describe the actual change: `--name`, `--description`, repeated `--team-id`, repeated `--scope`, `--suspend`, or `--unsuspend`.
- 3. Use `--clear-description` when the description should be removed.
- 4. Confirm the output and then re-list automations if you want a fresh inventory view.
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.
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.
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.
List Automations
Review the current workspace automations before you create, update, or rotate one.
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.