1. Pass or store the correct workspace id.
2. Run `./backlog.sh admin agents list --workspace-id ws_123`.
3. Review the binding ids and profile ids.
4. Continue to agent creation or update only after you know which agent record you are dealing with.

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 for an access token.

Review the current workspace automations before you create, update, or rotate one.

Create the workspace automation boundary, issue the automation secret, and store that secret safely because it is only shown once.

Change automation metadata, team boundaries, scopes, or suspension state without recreating the automation.

Issue a new automation secret when the old one should no longer be trusted, then replace it everywhere the old secret was used.

Create a named visible agent under an existing installation so activity, assignees, and attribution can point to a meaningful product actor.

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.

Create a named visible agent under an existing installation so activity, assignees, and attribution can point to a meaningful product actor.

Change a visible agent name, team scope, role, or suspension state without recreating the binding.