Skip to content

Review an Agent's instructions and assigned resources as the job changes. Check recent conversations and usage before changing a schedule or access grant. Revoking a person's or application's role must be treated separately from removing a connection assignment.

Reuse and transition

A reusable Agent definition can become a Marketplace template when private state, credentials, and privileged bindings are excluded. A remix receives its own configuration and requires its own setup. Publishing a definition does not share the live Agent.

If the work requires an application backend, identify selected Agent source and prepare a brief for a user-directed Project. An Agent association does not create a Project or transfer its authority. Review schedules, API consumers, and retained results before archiving or deleting an Agent.

Example: replace a specialist

Before retiring an older review Agent, identify its schedules, people, and application consumers. Configure and verify the replacement with a representative report, then update each intended consumer through its authorized workflow.

Do not assume a new Agent with the same name inherits grants, connections, or conversations. Check Access and Schedules before removing the old resource.

Retire recurring work explicitly

Inspect the Agent's schedules and application consumers before archiving or deleting it. After restoring an archived Agent, review its schedules before deliberately resuming them; restoration is not a request to replay missed work. Keep any deliverables you need accessible through their own resource controls.