Deploy an Arena project as an agent
EnterpriseDeploy an Arena project as a real agent from the project editor: an immutable, versioned PromptPack and a visible AgentRuntime.
Prerequisites
Section titled “Prerequisites”enterprise.enabled=truein your Helm values.- Editor access to the workspace. Deploy… is disabled without it.
- A project open in the editor, with a
deploy.configthat binds at least one Ready Provider. See Try a project’s dev agent to fix bindings.
Deploy
Section titled “Deploy”- Click Deploy… in the editor toolbar.
- Choose New deployment or Update a deployment. The dialog opens on Update a deployment when the project already has deployments.
- For New deployment, set Agent name and tick the Channels: WebSocket, A2A, REST or MCP. WebSocket is ticked by default. The name is a lowercase DNS label that no other agent in the workspace uses.
- For Update a deployment, pick the Deployment and a rollout: Switch now or Gradual. The dialog lists the providers the update repoints.
- Check Bindings. Click Change to edit them in place.
- Click Deploy.
The dialog shows Snapshot, Compile, Publish and Agent ready as each step finishes. A failed step shows its message and Back.
Verify
Section titled “Verify”The dialog shows <agent> is running <version>. Click Open the agent, or click Deployments in the editor toolbar to list what the project has deployed.
Troubleshooting
Section titled “Troubleshooting”Deploy is disabled and the dialog names a problem
Section titled “Deploy is disabled and the dialog names a problem”The line above Deploy says why: a name that is not a DNS label, a name already taken, no usable deploy block, or no provider binding that resolves. Fix the binding under Bindings.