Agent Guides · Advisory Hour Note

When a GenAI Coding Tool Surprises You

A quick field note on the “wait, that’s possible?” moments that make agentic coding feel less like autocomplete and more like a new creative surface.

By Eric Rhea Published: May 9, 2026 Status: Agent field note

Originally published as an Advisory Hour Substack note. Subscribe there for the latest essays, notes, and frontier work.

The note

Every now and then a genai coding tool just really surprises with what’s possible.

Browser screenshot of a locally running retro 3D scene with mossy stone walls, ladders, and pixelated game textures.
A local browser scene running at 127.0.0.1:5189 — the kind of generated artifact that makes the capability jump feel concrete.

Why this matters

The interesting part is not just that the tool can produce code. It is that the boundary of what feels reasonable to ask for keeps moving. A coding assistant can now help assemble a running visual prototype, expose it locally, and leave behind something you can inspect rather than merely imagine.

That changes the rhythm of software work. The first useful artifact can arrive earlier, and the human’s job shifts toward taste, direction, verification, and deciding which surprise deserves another iteration.

Operating pattern

Turn surprise into a repeatable loop

  • 1 · Capture the artifact
    When a coding tool produces a real “I did not expect that” result, save the page, screenshot, or repo state before the moment disappears into the scrollback.
  • 2 · Identify the lever
    Ask what made the jump possible: better scaffolding, clearer constraints, a stronger model, a local server, or a verification loop.
  • 3 · Fold it back into practice
    Turn the discovery into a prompt pattern, checklist, demo harness, or agent skill so the next build starts from the new floor.

Related thread