Use case · Coding agents

A workspace for every coding task.

Give each task its own filesystem and database, fork them for sub-agents, and roll back when a change goes wrong. The agent pushes code and calls APIs with tokens it never sees.

Get started Talk to us

How it fits

Built from the primitives you already get.

Forkable workspaces

Each task gets its own filesystem. fs_fork hands a sub-agent its own copy in milliseconds; large files are shared, not copied.

Branch before you migrate

db_branch creates a branch of the app database. Run the migration and tests there, then promote or discard it.

Snapshot, then try

Take a restore point before a risky refactor. If the tests fail, restore the primitive and try another approach.

Tokens by reference

vault_use injects a Git or registry token into the outbound request and redacts it from the response. It never enters the context window.

Solutions

More use cases

Multi-agent systems

Queues, shared memory and forked workspaces for agents that work together.

Long-term memory

Typed memory that persists across sessions and keeps its history.

Agent platforms

An isolated group per customer, scaled to zero when idle.

Build

Local-first development.

Build and test on your machine with the open-source engine. No cloud account needed: every primitive runs locally, with the same API as the cloud.

$ curl -fsSL https://useprimitives.com/install.sh | sh

Install the CLI, then run primitives dev. Quickstart

Open source

Built in the open. Contribute freely.

The SDKs, the MCP server and the single-node engine are open source and actively maintained. Submit PRs, report issues, improve docs, or just star the repo to show support.

useprimitives/primitivesFork, star, or open a pull request