Execution

Give agents a real place to work.

Agent sessions combine model access, transcripts, sandbox volumes, compute hosts, browser/file/git tools, and run state so work can move beyond chat.

What a Hosted Session Gives the Agent

Use connected provider credentials or Codex access for the selected workspace.

Attach a sandbox volume or compute host so shell, file, browser, and git tools have a real place to operate.

Keep prompts, tool calls, outputs, approval pauses, and run status together.

Attach exactly the integrations, packages, repo access, and approval status tools the task needs.

Repo investigation	Ask the agent to inspect a repository and report concrete findings before granting write authority.
Patch and verify	Let an agent edit files and run tests in a sandbox volume, then review the branch push and gate PR creation with approval.
Integration check	Give read-only API capability first, then expand scope once the output is trustworthy.
Workflow draft	Ask an agent to propose a workflow definition, manual run shape, access rules, and expected outputs.

Need to expose tools to an external client?	Use MCP & API to connect Claude, Codex, Cursor, or another MCP caller through an Agent identity.
Need to make a working session repeatable?	Use Workflows after the task has a stable trigger, scope, approval point, and evidence to inspect.