API Playground

ConTree API is for running code in isolated, branchable sandboxes. This page keeps the stable mental model in the documentation and leaves concrete fields, schemas, enum values, and request bodies to the live OpenAPI specification below.

For most users, start with the ConTree CLI (contree-cli) for terminal workflows, the ConTree SDK for Python applications, or ConTree MCP for assistant integrations. Use raw HTTP when you need to generate your own client or integrate ConTree into another runtime.

The API is built around a few durable concepts:

• a sandbox state is a checkpoint that can be resumed, inspected, or branched;

• execution starts from an image or checkpoint and produces a new checkpoint;

• long-running work is represented as asynchronous operations;

• inputs should be explicit: files, command, working directory, environment, and expected output paths;

• outputs are read from the resulting checkpoint;

• identifiers are opaque handles, not values clients should parse.

When building directly on HTTP, generate clients from the current OpenAPI specification, treat new response fields as compatible additions, and keep operation polling tolerant of new non-terminal states.