Claude Code's run of the AI Travel Planner

A Hono + React app on a reused Worker with D1. It has a chat workspace with itinerary, map and explore views, a seven-section admin console, and a global daily cost cap. The agent tested in production against real OpenAI, Places and email, and reports reading real verification emails through a disposable inbox.

Run length Agent claim: Reported by the agent in its own build report. Not independently verified.

1h 25m

of 8h allowed · started 22:28 UTC, Nov 5, 2026

Requirements tracked Agent claim: Reported by the agent in its own build report. Not independently verified.

73

71 marked Verified by the agent

Checks reported passing Agent claim: Reported by the agent in its own build report. Not independently verified.

278

across 4 suites of different scope

Approvals Observed: Observed by The Build Hypothesis during the recorded run.

Ran through without asking for further input during the run.

Timeline

  • Commit
  • Problem
  • Fix
  • Deploy
  • Start / end
View the timeline as a table

Claude Code, started 22:28 UTC

OffsetTimeEventTypeSource
+0 min22:28 UTCRun startedStartAgent claim: Reported by the agent in its own build report. Not independently verified.
+2 min22:30 UTC ≈Found the existing DB binding pointed at a missing database, so created a new D1 databaseProblemAgent claim: Reported by the agent in its own build report. Not independently verified.
+42 min23:10 UTCImplement AI Travel Planner on Cloudflare Workers and D1CommitGit record: Taken from the public repository's commit history.
+50 min23:18 UTCClose guest quota gap, handle over-long trips, add browser journeysCommitGit record: Taken from the public repository's commit history.
+54 min23:22 UTCAllow the zone-injected Cloudflare Web Analytics beacon in the CSPFixGit record: Taken from the public repository's commit history.
+1h 4m23:31 UTCFix source badge on stops without a place; add README and production checksFixGit record: Taken from the public repository's commit history.
+1h 9m23:37 UTCOnly open the map when the traveler asksFixGit record: Taken from the public repository's commit history.
+1h 15m23:43 UTCStop rejecting correct Places matches because of bad model coordinatesFixGit record: Taken from the public repository's commit history.
+1h 25m23:53 UTCBuild report generatedEndAgent claim: Reported by the agent in its own build report. Not independently verified.
+1h 26m23:53 UTCAdd build report artifacts and a test for the daily cleanup jobCommitGit record: Taken from the public repository's commit history.

5,125 seconds, measured until the report was generated. The final commit and build check came after.

Tests the agent reported

  • 236 passed · 0 failedUnit and integration (Vitest in workerd, real D1, mocked external APIs)6 files
  • 9 passed · 0 failed · 1 skippedProduction browser tests (Playwright, real OpenAI, Places and email)
  • 13 passed · 0 failedProduction admin bootstrap activation
  • 20 passed · 0 failedProduction walkthrough (spec §14.5)20 of 20 steps

The agent split the spec into 73 requirements.

Deployment & cost

Deployment Agent claim: Reported by the agent in its own build report. Not independently verified.
Deployed through GitHub-connected Workers Builds, with the build verified for the deployed commit.
Interventions Agent claim: Reported by the agent in its own build report. Not independently verified.
None reported ("No human interventions occurred.")
Estimated API spend while testing in production Agent claim: Reported by the agent in its own build report. Not independently verified.
$4.94Estimated from list prices for the agent's own production testing (67 LLM requests and 146 billable Places requests). About 99% of it is Places. This reflects how much the agent tested, not how efficient the app is.
Public demo
The experiment deployment calls billable AI and Places APIs, so it is not linked publicly. A demo link will be added here if a public version is published.

Highlights Agent claim: Reported by the agent in its own build report. Not independently verified.

  • AI edits are applied on the server as a list of operations, so unrelated itinerary content can't change
  • Itinerary stops carry source badges (verified place or AI suggestion) and warnings for overlaps and closed venues
  • Map with numbered, day-colored pins, and dashed pins for unverified locations
  • Admin console with Overview charts, Users, Trips, Usage and costs, Operations, Administrators and an Audit log
  • Per-owner, per-address and daily limits, plus a global daily estimated-cost cap
  • Replaced the default admin password in production about two minutes after the first deploy

Gaps it admitted Agent claim: Reported by the agent in its own build report. Not independently verified.

  • Schedule practicality is Partial (depends on the model and was not systematically assessed)
  • Accessibility marked Implemented but Unverified (no screen-reader test or automated audit)
  • Long-distance drag reorder failed under Playwright, and touch drag was not implemented
  • Some failure paths, rate limits and the cost cap were tested only with mocks

Stack & Cloudflare services

Stack

  • TypeScript
  • Cloudflare Workers
  • Hono
  • Zod
  • React 19
  • React Router
  • Vite
  • Tailwind CSS 4
  • Leaflet + OpenStreetMap
  • Vitest
  • Playwright

Cloudflare

  • Workers
  • D1
  • Workers Static Assets
  • Email Service
  • Cron Triggers
  • Workers Builds
  • Observability

Notes

Notes from the build report

  • The first full test run had 209 tests with 4 failures. One was a real bug: D1 counted cascaded rows, so deleting an admin who had a session falsely reported “last administrator”. It was fixed before the final run of 236 tests.
  • Testing against the real OpenAI and Places APIs exposed bugs the mocks missed: a closed venue marked as verified, an invented start date, a duplicate replacement stop and back-to-back stops. The agent reports fixing all of them.
  • A push was rejected because the repository owner had committed in the meantime. The agent rebased rather than overwriting. GitHub later rejected one push three times with a server-side error, and it went through unchanged about five minutes later.

Context for viewers

The repository’s history also contains an earlier implementation from 4 November that was reverted before this run. It is outside the reported run, and the agent’s report says it built from scratch without reading that code. Commits in the repo are attributed to the owner’s git identity, not to the agent.

The other runs