Archive
2026
- Why the Project Is Called CodeInstances
- Why Replay Matters for AI Agents That Take a Different Path Every Run
- What a Code Instance Is and Why Program Runs Should Be Kept Like Code
- The CodeInstances File Format Is Open JSON With a SHA-256 ID
- How to Upgrade a Dependency With CodeInstances Replaying Real Runs
- How to Replay the AI Agent Run That Did Something Odd Last Night
- How to Develop Against a Metered or Rate Limited API With CodeInstances
- How CodeInstances Was Tested Before Its First Release
- How CodeInstances Keeps the Failing Run of a Flaky CI Test
- How a Bug Report Can Arrive as a Runnable CodeInstances File
- CodeInstances Shrinks a Failing Run to the Answer That Breaks It and Keeps It as a Test
- CodeInstances Now Compares Two Runs and Shows Where the Failing One Went Wrong
- CodeInstances Launches as an Open Source Tool That Keeps Program Runs and Replays Them
- CodeInstances Groups Failing Runs by Fingerprint So Repeats of One Bug Show as One
- CodeInstances Forks a Run at Any Step, to Run On Live or Try a What-If Answer
- CodeInstances Adds a Self-Hosted Store, Push and Pull by ID, and Bug Reports That Reproduce