AI agent preview environments you can actually click
Reading a diff tells you what changed. Clicking the app tells you whether it works. Every TaskShipyard run ends on a running application, not on a patch file.
Why AI agent preview environments matter more than diffs
When an agent writes a hundred files, reviewing line by line stops scaling — and it was never the part of review that caught the real problems anyway. The questions that matter are whether the screen renders, whether the endpoint answers, and whether the row lands in the database.
A preview environment answers all three in the time it takes to click.
What a preview environment contains
Not a screenshot service and not a static build. The run’s own machine keeps serving the whole stack it built the feature against.
- The frontend, on the branch that was just built
- The API, deployed to an isolated cloud stage for that seat
- A database with the run’s migrations applied and seeded
- The logs and screenshots the agent produced while testing
The seat is held until the work lands
A finished run keeps its machine. The seat stays parked on the feature it built, still serving the preview, so a reviewer who opens the link an hour later still finds a live app rather than a dead URL. When the work merges — or when you free the seat by hand — the machine goes back to the pool.
How previews fit into autonomous development
Autonomous development moves the human from writing to deciding. That trade only works if deciding is cheap: one link, one running app, one merge button. The preview environment is what makes the review a decision instead of an audit.
Questions we get asked
- How long does a preview stay up?
- Until the run’s work lands or you release the seat. The machine that built the feature is the machine that serves it, and it is not handed to another feature while it is holding one.
- Does the preview use production data?
- No. Each seat has a throwaway local database seeded from your migrations, and cloud resources deployed to a stage of its own.
- Can I share the preview link with someone else?
- Yes — it is a normal URL for the running app, and the pull request points at it.