Skip to main content
Access is for humans and operator tools that need to inspect or control a running machine after creation. Keep networking docs for ports, preview URLs, tokens, and WebSockets; use this section when the question is “how do I get into the machine?” Desktop environments are a build surface for browser, desktop app, and visual-agent workflows. See Desktop Environments when the question is “how does an agent use a GUI?”

​
Choose An Access Surface

​
Access And Lifecycle

Access surfaces attach to an existing machine. They do not replace the machine lifecycle APIs:
  1. Create or connect to a machine.
  2. Use commands, files, volumes, templates, and preview URLs for normal application behavior.
  3. Attach PTY or SSH when a person needs to inspect state, debug a failure, or operate an interactive tool.
  4. Destroy disposable machines, or use retention, hibernate, auto-resume, and volumes when state must survive.

​
Access From Agent Runs

Agent jobs and services expose backing machine IDs. Use normal machine access commands to inspect retained runs:
Use Agent Deployments when you want repeatable named agent jobs and services. Use Agent workspaces when you want Codex, Claude Code, Amp, or OpenCode running inside a machine you control.