# Operate Agents

> Inspect Agent identity, follow Resource bindings, and understand which revision a Run executes.

## Before you begin {#before-you-begin}

You need `agent:read` access to the namespace. For Run inspection, also request `run:read` and ledger access. Know whether the Agent uses fixed Resource CRNs or scoped selectors resolved from tenant, customer, or principal authority.

## Steps {#steps}

1. Open the Agent detail page and confirm its CRN, version, mode, and deployment identity.
2. Review the summary cards before inspecting lower-level tables.
3. Follow linked Resource bindings to inspect Drivers, operations, Credentials, dependencies, and Policy.
4. Review the Tool catalog offered by the deployment.
5. Open a recent Run and compare its pinned deployment and Resource snapshot with the current Agent.
6. Use **Deploy new version** only when changing immutable behavior or deployment configuration.

## Verify {#verify}

A valid Agent has a resolvable canonical CRN, a complete binding snapshot, a bounded Tool catalog, positive limits, and a current Worker deployment. Existing Runs must continue to report the exact revision accepted at their boundary even after a newer Agent is deployed.

## Next steps {#next-steps}

Read [Run operations](/docs/runs/operate.md) for safe-point controls and durable history, or [Channel operations](/docs/channels/operate.md) for ingress routing.