Skip to main content
A deployment is an immutable build of one agent. An alias gives a stable name to the deployment clients should run. Every project starts with two working environments: Sessions keep the deployment they started with. Publishing another version does not change the code underneath an existing session.

​
Deploy to production

From the project directory:
Every deploy first runs opencomputer doctor, a local static scan for invalid connection origins, misplaced tools, and missing secret declarations, and then prints the project it resolved and the cloud id each local agent deploys as. Run opencomputer doctor --json directly to get structured diagnostics, with the same resolution under resolution, before invoking a deployment agent. The CLI builds the current source, creates an immutable deployment, and moves the production alias to it. Development remains available for further work.

​
Select an agent and environment

Clients identify an agent with agent-id@alias:
The project dashboard’s environment selector changes which deployment you are inspecting. The playground has a separate agent selector when a project contains more than one agent.

​
Review history

Open the project’s Deployments page to inspect immutable versions, their aliases, and creation times. Use the deployment ID when correlating a session with logs or the debug inspector.