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
The difficult rendering investigations in Ashes of the Unbound all began to follow the same choreography: load a state, apply a diagnostic mode, wait for the world to settle, capture a screenshot, write down what changed …
Continue reading
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 readingCopying work between agent windows is routing, state tracking and failure recovery disguised as clipboard use.
Continue readingSkyeEngine Code began as a practical complaint: I was spending too much time carrying messages between coding agents. The immediate trigger was the development workflow around Ashes of the Unbound. Rendering and …
Continue readingNo posts on this page match that filter.