Agent Studio
Product tour

Follow one card through Agent Studio

The stages of one card, from request to acceptance, shown with card DEMO-5 in the Agent Studio demo installation.

The demo uses invented projects and runs no agents. Where DEMO-5 has no record for a stage, the image shows what the product reports instead.

How work happens Getting started

From wish to acceptance

A card passes six stages. Review and the gate can send it back; an escalation stops it until a person decides.

Figure 1

One card from wish to acceptance

  1. Wish

    Backlog · Ready

    Request, project, agent and model

  2. Run

    In Progress

    Coding CLI in an isolated worktree

  3. Review

    Post Processing

    Automatic review grades the result

  4. Gate

    Card or batch gate

    Build and tests on the result revision

  5. Delivery

    develop

    Gated revision joins the integration branch

  6. Acceptance

    Human review → Accepted

    A person accepts or asks for a revision

  • Review → Run A finding can start a bounded rework round.
  • Gate → Ready A red gate can start a fix round with the failed tests.
  • → Escalated The card stops with a reason and waits for a person’s decision.
Lane names are the board labels of the product. Integration into develop and acceptance are recorded separately.

Start on the board

The board groups the cards of a project by lane. Open a card to see its request, runs, review and evidence in one place.

Agent Studio · recorded capture
Demo App board with the explorer on the left and three lane groups: Ready cards marked as held because no execution host is connected, an empty In Progress lane, two cards in Post Processing and two escalated cards.Demo App board with the explorer on the left and three lane groups: Ready cards marked as held because no execution host is connected, an empty In Progress lane, two cards in Post Processing and two escalated cards.

Demo App board. Ready cards are held because the demo has no execution host; In Progress is empty.

1. Write the wish

A card holds the request, the project, the coding agent, the model and the thinking level. DEMO-5 asks for a CSV export of reports.

Agent Studio · recorded capture
Card DEMO-5 “Add CSV export to reports”: the overview shows lane Human review, project Demo App, agent Claude Code with Opus 4.8 at medium thinking, owner and pipeline; the Task tab shows the request text.Card DEMO-5 “Add CSV export to reports”: the overview shows lane Human review, project Demo App, agent Claude Code with Opus 4.8 at medium thinking, owner and pipeline; the Task tab shows the request text.

DEMO-5 with lane, agent, model and pipeline on the left, the request on the right. The demo request text says that its content is invented.

2. Run the agent

A run starts the configured CLI in an isolated worktree. The Timeline records when the run started and finished. Activity shows what the run reported and attached.

Agent Studio · recorded capture
Timeline of DEMO-5 with prompt created, run started and run finished, each tagged with provenance pinned-demo-simulated; the Activity tab lists the reported screenshots, a delivery diff, notes, metrics and a capture log.Timeline of DEMO-5 with prompt created, run started and run finished, each tagged with provenance pinned-demo-simulated; the Activity tab lists the reported screenshots, a delivery diff, notes, metrics and a capture log.

The run events carry the provenance pinned-demo-simulated: the demo recorded them, no agent ran.

3. Read the review

Automatic review grades the result and names its findings. A finding can start a bounded rework round. DEMO-5 received grade B with one open finding.

Agent Studio · recorded capture
Code review of DEMO-5 with grade B and verdict concerns: one medium finding asks for an empty-table export assertion, one verified item covers CSV escaping and timezone formatting. The Result tab beside it shows Human review, grade B and a generated summary.Code review of DEMO-5 with grade B and verdict concerns: one medium finding asks for an empty-table export assertion, one verified item covers CSV escaping and timezone formatting. The Result tab beside it shows Human review, grade B and a generated summary.

Grade B with one open finding. The demo run wrote no status.md, so the Result tab shows the summary Agent Studio generated from the task record.

4. Pass the gate

Before integration, a gate runs build and tests on the result revision. A project can collect deliveries into a batch and test the combined candidate once.

Agent Studio · recorded capture
Batch verification panel for Demo App: 0 of 1 gate slots busy, no failed tests in the last 7 days, plan idle with no eligible cards, no waiting cards and no batches run yet.Batch verification panel for Demo App: 0 of 1 gate slots busy, no failed tests in the last 7 days, plan idle with no eligible cards, no waiting cards and no batches run yet.

The batch gate was switched on in the demo project for this capture. No card was eligible and no batch has run.

5. Inspect the delivery

Evidence collects screenshots and test results. Activity lists the delivered files. The delivery line in the card overview states whether the revision reached develop.

Agent Studio · recorded capture
Evidence tab of DEMO-5 with eight visual evidence screenshots and the note that no test evidence is assigned because the card has no commit; the Activity tab lists the attached files, including the delivery diff.Evidence tab of DEMO-5 with eight visual evidence screenshots and the note that no test evidence is assigned because the card has no commit; the Activity tab lists the attached files, including the delivery diff.

Eight screenshots, notes, metrics and a delivery diff are attached. No test evidence is assigned: the demo card has no commit.

6. Decide on acceptance

In Human review, a person accepts the result or asks for a specific revision. Integration and acceptance are recorded separately.

Agent Studio · recorded capture
Done and decide column of the Demo App board with the Human review lane: card DEMO-5 “Add CSV export to reports” with grade B, no code changes and no assigned test evidence.Done and decide column of the Demo App board with the Human review lane: card DEMO-5 “Add CSV export to reports” with grade B, no code changes and no assigned test evidence.

DEMO-5 waits in Human review. The image shows the waiting state; no acceptance was recorded.

Check readiness

The Environment view checks the server, execution hosts and projects. Each failing check states what it means and how to fix it.

Agent Studio · recorded capture
Environment view with server readiness: four failing and six attention checks, grouped by server, execution hosts and project, each with what it means and a remedy.Environment view with server readiness: four failing and six attention checks, grouped by server, execution hosts and project, each with what it means and a remedy.

Readiness checks in the demo with a remedy for each. The demo has no Git identity, no gate worker and no enrolled host.

See hosts and health

The same view lists why cards wait, the health of declared environments and the load and slots of each execution host.

Agent Studio · recorded capture
Environment view with application health and no declared environment, and two host cards: Local machine online and a configured remote host offline, without load or slot data.Environment view with application health and no declared environment, and two host cards: Local machine online and a configured remote host offline, without load or slot data.

The local machine is online; the configured remote host has never reported. No demo project declares an environment.

Exception: an escalated card

When automatic review has used its budget, the card stops in Escalated with its findings and a recommended option. DEMO-9 shows this case. It is not the normal path.

Agent Studio · recorded capture
Escalated card DEMO-9 with three open findings, actions Continue, Accept as-is and Abort, a delivery line without integration, and a decision with a recommended option.Escalated card DEMO-9 with three open findings, actions Continue, Accept as-is and Abort, a delivery line without integration, and a decision with a recommended option.

Exception view: DEMO-9 stopped in Escalated with three open findings and waits for a release decision.

About these images

Captured on 9 November 2026 from an unreleased develop build after v0.9.5, using the product’s fixed demo data. Light and dark captures follow the site theme. For the gate image, the batch gate was switched on in the demo project.