Observed arrival · 2026-11-22
A disposable stage for every coding-agent task
Forkstage offers isolated copies of an application stack where coding agents can reproduce bugs and run tests.
○Open
⊠Login
$Paid
†Ads
✦Pretty
●Pro
◎Niche
◉Human
⚑Risk
ƒJS
- For
- Teams running coding agents against multi-service applications
- Worth noticing
- The forkstage.yaml recipe names services, ports, seeds, and tests; a bake runs migrations and seeds before saving a warm snapshot.
Field notes
The setup is expressed in forkstage.yaml: the example names app, database, queue, and worker services, plus seeds and tests. The page says one bake runs migrations and seeds before saving a snapshot; subsequent task forks are separate, and a sample proof lists commands, exit codes, and test output. It also says proof records remain for 30 days after a fork is destroyed.
Observed signals
Read the marks
Editorial observations of this landing page, not a rating.
○OpenPublic substance visible
⊠LoginAccess appeared gated
✦PrettyNotable craft visible
●ProPolished or operationally mature
◎NicheUnusually specific use
One card from the complete issue