Overview

The Checkpoints API treats git commits as workspace checkpoints. You can list the checkpoint history, create a new checkpoint by committing the current working tree, tag a checkpoint, and restore the workspace to a previous checkpoint. This is file-system checkpointing for local or VM-bound workspaces, distinct from run/job cursor state.

Base URL

All endpoints require authentication via a Bearer token in the Authorization header unless the route is otherwise noted. See Authentication for details.

Endpoints

List checkpoints

Query parameters: Response when inside a git repository:
Response when not inside a git repository:

Create checkpoint

Request body:
Response:
The endpoint stages all changes (git add -A) and creates a commit with the provided message. An empty message returns 400 Bad Request.

Tag checkpoint

Request body:
Response:

Restore checkpoint

Before restoring, any uncommitted work is stashed with the message pre-restore-<checkpointId>. The current branch is then reset hard to the target commit. Response:

Error codes