Git-backed agent workspaces

Version every agent workspace like a repo.

Driftstone gives your product a Git system for agent work: repositories, branches, file contents, commits, merges, and sync operations behind a clean API.

repos/agent-work
repomainbranchmergesync

agent.json

initial files

environment.json

committed

01

Repo primitives

Create repositories, list them, and resolve them under the authenticated organization.

02

Branch control

List, inspect, create, and delete branches around agent-generated work.

03

Upload surface

Create signed upload URLs for main branch files and complete uploads once storage succeeds.

Why Driftstone

Agent work should not disappear into one-off folders.

Driftstone turns generated files and workspace updates into named Git operations your product can reason about, review, and publish.

Create repos

Start an org-scoped repository with a stable slug and main branch metadata.

Manage branches

Create branches from the repository main head or create branch records for later uploads.

Upload files

Request signed URLs for main branch files, upload bytes, and mark uploads complete.

Clean up

Delete repositories or branches and let background jobs remove the stored files.

Workflow

Keep agent output on a reviewable path.

Driftstone is built around explicit Git movements: create, branch, write, merge, and sync. That gives teams a stable control plane for work that agents produce across many users.

01

Create a tracked workspace

An agent or product flow starts with /v1/repos and gets a real repository record instead of a loose file bundle.

02

Work on an isolated branch

A branch can start from the repository main head or wait for its first uploaded directory.

03

Upload main files

Upload URLs target main branch files under an identifier and expire after 15 minutes.

04

Complete the upload

Completing an upload sets the repository main head identifier for future branches.

API surface

A compact Git API for products and agents.

The endpoints stay narrow on purpose. Callers get the Git operations they need without taking responsibility for repo storage, organization resolution, or commit plumbing.

Bearer keys
Org-scoped repos
Commit metadata
Health checks
repo create
curl -X POST https://api.driftstone.ai/v1/repos \
  -H "Authorization: Bearer dk-..." \
  -d '{"name":"agent-work"}'

driftstone: repo created
main: ready for upload
branches: ready for review
upload request
POST /v1/repos/agent-work/uploads

{
  "identifier": "ver-1234abcd",
  "files": [
    {
      "name": "README.md",
      "hash": "64-character-sha256-or-client-hash"
    }
  ]
}
Method
POST/v1/reposCreate a repository.
GET/v1/reposList repositories for an organization.
GET/v1/repos/{repo}Get repository metadata.
DELETE/v1/repos/{repo}Delete a repository.
POST/v1/repos/{repo}/uploadsCreate signed upload URLs.
POST/v1/repos/{repo}/uploads/{upload}/completeComplete an upload.
GET/v1/repos/{repo}/branchesList branches for a repository.
POST/v1/repos/{repo}/branchesCreate a branch.
DELETE/v1/repos/{repo}/branches/{branch}Delete a branch.

Frequently asked questions

What is Driftstone?

Driftstone is the Git system inside this folder: a repository API for creating repos, uploading main files, branching work, and cleaning up repository state.

Driftstone API

Build agent work on Git primitives from the start.

Repos, branches, contents, merges, and sync operations give the rest of Harnesslayer a stable system of record for agent workspace changes.