CodeInstances on SoftDevStudio.com

CodeInstances Adds a Self-Hosted Store, Push and Pull by ID, and Bug Reports

Sun, 18 Oct 2026 00:00:00 +0000

CodeInstances 0.5 moves a run from where it failed to where it gets fixed. codeinstances serve runs a small store of your own that keeps instances under their SHA-256 ids, push and pull move them by id or a 12-character prefix, and report writes a Markdown bug report that ends with the two commands that bring the exact run back. A GitHub Actions example pushes failing test runs and puts the report in the job summary. The release post has the details, and binaries are out for Linux, macOS and Windows.

CodeInstances Adds Diff, Comparing a Passing Run With a Failing One

Sun, 18 Oct 2026 00:00:00 +0000

CodeInstances shipped its second release the same day as its first. Version 0.2 adds the third verb on its plan, compare: codeinstances diff passing.instance failing.instance lines up two recorded runs and shows where they part ways. Binaries are out for Linux, macOS and Windows.

Calls are paired by method, URL and request body, then by method and URL alone, so a request sent with a different body shows as one changed call rather than one missing and one extra. Response bodies in JSON are compared member by member, down to a line like “at $.items: 12 items in a, 0 in b”. How each run ended and what it printed are compared too, and a fixed build run against the old one gets a note, not a difference. Each call now keeps how long it took, so the slowest changes show at a glance. That’s an addition to the open format, and older files still read.

CodeInstances Adds Group, Fingerprinting Failing Runs So Repeats of One Bug Collapse

Sun, 18 Oct 2026 00:00:00 +0000

CodeInstances 0.4 adds group, the next step on its plan. codeinstances group failures/ gives every failing run a fingerprint and puts the runs that fail the same way together, biggest group first, with when each was first and last seen. A pile of 40 red runs becomes the two or three bugs behind them. The release post has the details, and binaries are out for Linux, macOS and Windows.

A fingerprint is how the run ended, its error and the calls that failed. The error part reads Go panics and fatal errors, failed Go tests, Python tracebacks and Node.js and Java traces for their top frames. Then times, ids, numbers, ports and query values are blanked out so repeats match, while status codes stay. The ids carry a version, fp1, so a later change to the rules can’t be mistaken for the same bug.

CodeInstances Adds Shrink and Test, Narrowing a Failure Down and Keeping It as a Regression Test

Sun, 18 Oct 2026 00:00:00 +0000

CodeInstances reached its third release on its first day. Version 0.3 adds two commands from the same step of its plan. codeinstances shrink takes a failing run and a passing one and finds which of the failing answers cause the failure. codeinstances test replays a folder of recorded runs as regression tests. Binaries are out for Linux, macOS and Windows.

Shrink is delta debugging over recorded answers. It replays the program offline with the passing run’s answers swapped in for some of the failing ones, keeps narrowing, and stops when no single answer left can go without the failure going away. What’s left is written out as a small failing instance. Test then holds two rules: a run that passed must replay exactly, and a recorded failure must now exit 0 against the answers that broke it.

CodeInstances Forks a Run at Any Step

Sun, 18 Oct 2026 00:00:00 +0000

CodeInstances 0.6 adds fork. codeinstances fork -at 9 run.instance answers a kept run’s first eight calls from the recording and then lets the program carry on live from call nine, so an agent or job that went wrong late doesn’t have to spend the time and the calls to get back there. With -answer and -offline, call nine gets an answer you write instead, a 503 say, and nothing goes out: a what-if on a real run rather than a mock. The release post has the details, and binaries are out for Linux, macOS and Windows.

CodeInstances Launches, Keeping Program Runs as Files and Replaying Them Offline

Sun, 18 Oct 2026 00:00:00 +0000

CodeInstances, the studio’s fourteenth project, treats each run of a program as something you can keep. Code is versioned and reviewed; its runs are thrown away, so a CI test that fails once and passes on the rerun takes the bug with it. Version 0.1 came out on 18 October with the first two verbs, keep and replay, and binaries for Linux, macOS and Windows. It’s pure Go with no dependencies outside the standard library, open source under Apache 2.0.

CodeInstances Runs Kept Instances on Demand

Sun, 18 Oct 2026 00:00:00 +0000

CodeInstances 0.8 lets a store run what it keeps. Start it with serve -run, and anyone with the store’s token can have it replay a signed run, or fork one at a step, with codeinstances run, and get back how it went. A kept run works like a function in a function service: the request runs it, nobody sets the program up on a laptop, and every call is answered from the recording. The release post has the details, and binaries are out for Linux, macOS and Windows.

CodeInstances Signs Runs So Anyone Can Check Who Kept Them

Sun, 18 Oct 2026 00:00:00 +0000

CodeInstances 0.7 adds signing. Every kept run already carried a SHA-256 id that showed when a file had been edited, but not who made it, since anyone can edit a run and write a new id. Now codeinstances keygen makes an Ed25519 key pair, sign (or record -sign) vouches for a run with it, and verify -trust ci.pub exits 0 only when that key signed that exact run. The release post has the details, and binaries are out for Linux, macOS and Windows.