Skip to content

A disposable copy of production for every coding-agent task

Bake your stack once. Then every task, agent and pull request gets its own complete copy in about 100 ms, with a public address. Use it, prove it, throw it away.
Terminal window
npm install -g forkstage # once
forkstage login # once per machine: GitHub in the browser
forkstage init # in a repository: writes forkstage.yaml
forkstage bake # builds, seeds and snapshots the stack (about a minute)
forkstage up # a fork in about 100 ms, with https://<id>.forkstage.run

Then forkstage test, forkstage sh, forkstage exec -- <command>, and forkstage down when done. The proof of what ran stays in the dashboard.

Stack

One repository’s forkstage.yaml: its services, ports, seed data, ready check and tests.

Bake and snapshot

Starting the stack once, running migrations and seeds, and freezing it warm. Forks come from the newest snapshot.

Environment, or fork

A running copy made from a snapshot in its own microVM. Short id, public address, destroyed when the task ends.

Proof

The record of one fork: every command, its exit code and output tail, every test run, timings. Kept 30 days.