Use cases
What people grow in the first week
An artifact can be a page, report, walkthrough, internal app, dashboard or scheduled job. These guides show the workflow and its limits.
PR walkthroughs your agent keeps at a URL
Attach a living walkthrough to a pull request. Keep context, changed files, test steps and known limits readable after the agent session closes.
Internal tools nobody would staff, built by your agent
Turn a small operational backlog into working internal tools with a URL, Postgres, login, schedules and an optional custom domain.
Send customers a working prototype, not a deck
Build a scoped customer prototype, share it with the right access boundary, collect comments in place and keep the same URL through revisions.
Reports and write-ups live at their own address
Publish an agent-built report when it exists, share a lasting URL, collect comments and keep its files available beyond the original session.
Dashboards that read your data and stay up
Build an agent-made dashboard with a lasting URL, Postgres, login, refresh jobs and controlled sharing. Learn the setup and limits.
Scheduled jobs and small automations that keep running
Build a small scheduled job with a visible app, Postgres state, login and a lasting URL. See the prompt, setup, proof checks and limits.