All recorded work

Recorded on 25 September 2026

Chrono City: from brief to verified pull request

A five-era city scene looked ready after the first build. Browser QA found two unmet criteria, sent the work back and verified the fixes before the pull request was ready. This is the record of that run.

The prompt comes from Bijan Bowen, who uses it to test AI models. The screenshots are the QA agent's own captures from its running browser.

To the pull request
1 h 48 min
Agent runs
6
Criteria verified
11 of 11
Model spend
US$1.00

What was asked

Build an interactive city block that moves between 1945, 1965, 1985, 2005 and 2025. Visitors must be able to select each era and open period-aware details for scene objects.

What happened on the way

In the first delivery cycle, the year label switched to 1985 but the city did not render. QA reproduced the blank purple viewport three times. It also found empty descriptions in the info cards. Both findings went back to the developer agent before review.

The first build looked done. QA clicked through it anyway.

In an agent session, you are the QA person for your own automation. You open the browser, click every year, spot what is broken and write the follow-up prompt, round after round. Here the QA agent did that work and sent the build back before anyone was asked to review it.

Acceptance criterion 3

One of the five eras rendered nothing

QA screenshot: 1985 is selected and the viewport is an empty purple field
Cycle 1 · QA failed

“Selecting 1985 renders no city: the viewport is a flat purple film-grain field while the HUD reports 1985. Reproduced three times.”

QA screenshot: the 1985 era rendered as a neon downtown
Cycle 2 · QA verified

1985 renders its full neon skyline, whether it is picked on the slider or with the 3 key.

Acceptance criterion 6

The info cards were empty

QA screenshot: a building info card with no description
Cycle 1 · QA failed

“Clicking a building flies the camera in and opens the card, but the card contains no description.”

QA screenshot: a building info card describing a 1945 art-deco tower
Cycle 2 · QA verified

Every building, vehicle and pedestrian card carries period copy, and a new test fails if one is ever empty again.

From task to pull request in 1 h 48 min

Task created · 11:14Pull request ready · 13:02
  1. Architect
    11:14 · 11m 22s
    101.2k tokens
  2. Developer
    11:25 · 38m 1s
    21.4m tokens
  3. QA
    12:04 · 16m 50s
    4m tokens
    Sent back
  4. Developer
    12:21 · 14m 52s
    6.2m tokens
  5. QA
    12:36 · 21m 53s
    2.5m tokens
  6. Reviewer
    12:58 · 3m 56s
    443k tokens
Architect’s estimate
12m
Tokens used
34.7m
Model spend
US$1.00
Served from cache
97%

The architect estimated 12m tokens. The run used 34.7m: the developer checked its own renders, QA exercised every era in a real browser, and one rework round fixed what QA found. With 97% of those tokens served from cache, the whole task cost US$1.00.

All five eras, as QA captured them

  • QA screenshot of the 1945 era

    1945

  • QA screenshot of the 1965 era

    1965

  • QA screenshot of the 1985 era

    1985

  • QA screenshot of the 2005 era

    2005

  • QA screenshot of the 2025 era

    2025

It takes longer than a demo. That is the point: you get a pull request that has already been tested, not one you still have to test.

The outcome

The architect planned the work, the developer built it twice, QA ran twice and a reviewer checked the result. All 11 acceptance criteria passed in the second cycle. The pull request was ready 1 hour 48 minutes after the task was created.

The record

    • 1 task recorded in CoRoid

    Try it on your own repository

    Your own assistant can set CoRoid up. The onboarding walkthrough shows every step of a recorded setup, with its times.