Requests / revisions / results

What happens
after you ask?

A task starts a conversation. Ergod works with tools and files, returns a result, and takes the next change. Here are three examples you can inspect for yourself.

Collected and reviewed September 20, 2026. Sales and research ran in the live web app. The game comes from an earlier hosted-agent recording, with fresh gameplay verification.

01 / Work with data

Build it. Try it.
Ask for the next change.

Six synthetic orders become a self-contained sales explorer. The next request adds a paid-only shortcut and a CSV export. A reviewer finds a toggle bug, reports it in the same conversation, and checks the corrected file.

  1. First requestTurn a CSV into a chart and filterable table. Show totals for the visible rows. Open and test it in a browser.
  2. Useful revisionAdd a Paid only shortcut, export the visible rows, and show an explicit empty state.
  3. Review and correctionThe new toggle stuck on. A follow-up named the exact failure; version 3 fixed it.
Recorded interaction with the delivered version 3: all orders → paid orders → no matching orders → reset. This is a walkthrough of the result, not a recording of generation time.
Try version 3 ↗First buildVersion 2, with the observed bugOriginal CSV
What was independently checked?
  • All six orders total 10 units and $219.50.
  • Paid only shows four orders, eight units and $169.50. Turning it off restores all six.
  • Selecting pending after Paid only takes precedence: one order, one unit and $24.00.
  • Games + pending produces zero rows, $0.00 and an empty-state message.
  • The downloaded paid-only CSV contains exactly the four visible paid rows.
  • No document overflow at a 390px viewport.
  • Re-downloaded original HTML and CSV matched their pre-revision hashes.

See the actual correction in chat · Full verification record

Hunyuan 3 · live Ergod web app · September 20 · three turns. The first turn included browser checks and approval waits. Later versions were checked independently. The generated files are unedited; this is one reviewed example, not a promise that every first attempt succeeds.

02 / Research a question

An answer with
somewhere to look next.

“I am making a small, non-commercial weather widget for friends. Compare Open-Meteo and the US National Weather Service API using their current official documentation only.”

Ergod fetched the documentation, compared coverage and access requirements, and attached a brief with direct sources. A follow-up narrowed an overbroad coverage claim and improved a citation. A final request asked for a shorter answer in chat.

The live Ergod conversation: a follow-up asks for a short recommendation, and the answer includes official documentation links.
Actual conversation, captured September 20. Account navigation is outside the frame. The saved revised brief uses the more precise forecast-office coverage wording; the short chat answer still ends with the shorthand “US-only.”
Read the revised brief ↗Original briefReview notes
Sources and the review

The reviewer checked the claims against Open-Meteo's API documentation, service terms, data licence, and the NWS API documentation.

The revision distinguishes forecast-office coverage from a claim about every NWS data product. It also keeps free API access terms separate from the data's attribution licence. The recommendation applies to the example's non-commercial, worldwide-widget requirement and the documentation on the recording date.

Hunyuan 3 · live Ergod web app · September 20. Original and revised Markdown files are unedited. Source links make the answer reviewable; they do not remove the need to check it.

03 / Make something for friends

A raccoon. Falling fries.
One more request.

“Our server mascot is a raccoon. Make a tiny game where it catches falling fries.”
“Add a calmer mode and keep the high score between rounds. Keep raccoon-fries-v1.html untouched and make raccoon-fries-v2.html.”

The second file adds Normal and Calm choices. Later review caught a clipped phone layout and a missing touch-input step; two follow-ups corrected them. Move with the mouse or arrow keys; press Space to pause. It's a single-player game you can open in a browser.

Play the revised game ↗First versionCalm-mode revisionLayout revision
Version 2 gameplay, captured September 20. A real catch raises the score to 1. The playable link includes the later phone fixes.
Recording and verification boundaries

Versions 1 and 2 were generated September 18 with Qwen 3.7 Flash using the hosted agent and sandbox. Versions 3 and 4 were requested in the live web app with Hunyuan 3 on September 20. These examples do not test a production Discord conversation or multiplayer. The original agent staged some screenshots; those are not used here.

Fresh review exercised Calm mode, pointer movement, scoring, game over, restart, the Space pause overlay, and high-score persistence after reload. The six-second clip preserves elapsed time from sampled screenshots, without injecting game state. All four HTML outputs are unedited. See the capture notes for the checks on the phone revisions.

Exact requests and capture notes