Why a travel planner?
A travel planner sounds simple until you write the spec. This one asks for a conversational AI that edits structured
itineraries without trashing unrelated days. It also needs real place data rather than invented opening hours, guest
sessions that migrate into accounts, email verification, an admin console with its own identity system, and per-request
cost accounting for every LLM and Google Places call. All of it has to be deployed through a CI pipeline the agent
didn’t build.
That makes it a good first test. Polished screenshots are easy to produce, and you can’t fake the integrations.
How the runs were set up
Each agent got its own GitHub repository, holding the license and spec v1.7 before the run started. Each had its own
Cloudflare Worker, connected to its repository through Workers Builds, and the same runtime model (gpt-4o-mini) set
by the administrator. The runs took place one after another on 5 November 2026 and were screen-recorded.
What we know so far
The runs are recorded and the repositories are public. Each agent left a BUILD_REPORT.md and a machine-readable
BUILD_RESULTS.json. What follows on this page comes from those artifacts and the git history, and is labeled that
way. Agent claims are not verified results. The independent evaluation, with hands-on testing of each deployed
app, comes next and will be published alongside the episode.