Skip to main content
A session is a durable conversation with a deployed agent. Each turn appends input and streamed runtime events to the session, allowing clients to resume a conversation without rebuilding its history locally.

​
Agent playground

Open a project in the dashboard and choose Agent playground. Select the agent and environment independently, then create a new session or resume a previous playground session. Playground sessions stay in the playground list. Sessions started through an API appear under Sessions, where their durable turn history can be inspected. See Playground and debugging for target selection and the debug inspector.

​
CLI

Start a session against the development agent:
The session command always uses the current project’s bound Development deployment. It does not select between local and remote runtimes. Projects with multiple agents may select another member of the bound project. The environment remains Development:
Add --verbose to stream non-message lifecycle, runtime, tool, egress, usage, and turn events. Assistant message text continues to stream normally:
Or manage the durable session lifecycle explicitly:
Follow the durable event log directly. With --json, each event is one NDJSON record suitable for a coding agent or log processor:
Project scripts resolve the opencomputer binary from the installed @opencomputer/cli package. For a one-off invocation outside those scripts, select the scoped package explicitly:
Use --keep on supported commands when the session should remain active after the command exits.

​
Input sources

Inside an agent, useInput().source identifies how the current work arrived. This lets the same agent distinguish direct work from delegated subagent work without defining another session type.