# Coding Agents

Configure available coding agents and check tenant-specific runtime readiness.

## Where to find it

Open **Account > Assistant > Coding Agents**.

Address: `/account/assistant?panel=coding`, `/account/coding-agents`, `/account/coding-agents/:agentId`. Open the saved resource from the product rather than typing this address.

## Create a coding agent

Open the new-agent action to show **New coding agent**. Choose a template, then review **Agent name**, **Model**, **Permission**, and **Budget (USD)**. Permission choices are **Accept edits**, **Plan**, and **Default**; they control the coding runner's behavior, not general tenant or cloud access.

Use **Advanced setup** only when you need a specific **Agent key**, **Workspace path**, or **Instruction path** instead of the generated defaults. Choose **Create Coding Agent**, then find the new entry in **Configured coding agents**. Use **Search agents** to locate an existing configuration before creating another.

## Recheck and test readiness

**Recheck** evaluates runtime configuration. **Test** performs a provider-backed launch check; runtime checks passing alone do not prove the provider can run. **Ready** also requires a successful provider test for this tenant within the last 24 hours. Resolve the displayed credential, runtime, or budget blocker before testing again.

Open the agent's name for [configuration, instructions, tools, and task launch](/docs/coding-agent-details). An agent or test in another tenant is not evidence for this one.

## Remove an agent

**Remove** is available for eligible customer-managed configurations. Topline-managed entries show **Managed by Topline**. Removing a configuration does not delete prior task history, source changes, artifacts, or deployed output. Resolve active work first and check the remaining list.

## Related guides

- [Coding agent details](/docs/coding-agent-details)
- [Task Monitor](/docs/task-monitor)
- [Usage and limits](/docs/usage)