Handling Contract Changes Without Retrying Old Work
When acceptance changes the contract, sending the old packet back to a coder only makes the workflow repeat itself more confidently.
Continue reading// THE BLOG
AI Agents
Tracking Agent Work Outside the Chat Window
The second version of SkyeEngine Code could launch agents, route requests and show their replies. It still learned most of what it knew by watching rows appear in somebody else’s message database and guessing what those …
Continue readingHandling Partial Output After an Agent Crash
A crashed turn may leave useful text and changed files, but neither should quietly acquire the authority of a completed response.
Continue reading
Running a Multi-Agent Investigation in SkyeEngine Code
The first proper test of SkyeEngine Code was not building SkyeEngine Code. It was trying to understand why the first connection to an Ashes of the Unbound server could capture a different sky from the second. By then the …
Continue reading
I Was the Message Bus
The awkward part of using several coding agents was not opening several terminals. It was me sitting between them, copying one answer into another window and trying to remember which session had seen which piece of the …
Continue readingWhy I Stopped Routing Agent Work by Hand
Copying work between agent windows is routing, state tracking and failure recovery disguised as clipboard use.
Continue readingNo posts on this page match that filter.