Ai Agents on Multivergence.com

Forkable State Gives AI Agents a Real Way to Try Before They Commit

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

Agents have started trying things before they commit. A coding agent sketches three plans for a refactor and keeps the one whose tests pass. A travel agent holds a train, a flight and a coach until the fares and the delays are in. A planner runs a few sequences of tool calls and takes the first that works. People do this too, of course. What’s new is that software is doing it hundreds of times an hour, and it needs somewhere to keep the alternatives while it decides.

How a Coding Agent Tries Three Fixes at Once and Ships the One That Passes

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

A bug report comes in: Median([1 2 3 4]) returns 3, and it should return 2.5. A coding agent can usually think of more than one fix. The usual move is to pick the one it likes best, apply it, run the tests, and start over if they fail. Each failed attempt has to be undone by hand, and the working copy spends the whole time half changed.

With Multivergence the agent drafts all three fixes at once, each in its own branch, and lets the evidence pick. This case study walks through examples/fixes in the repository. The patches in it are real Go functions and the test suite really runs on them. Every number below is from its recorded output.

How an On-Call Agent Narrows Down an Outage With Weighted Hypotheses

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

At 14:02 an alert fires: checkout’s p99 latency is 4.8 seconds, against a normal 300 ms. Whoever is on call, a person or an agent, starts with a handful of suspects. The connection pool could be exhausted. The release that went out at 13:58 could be bad. A cache node could be failing, or the payment provider could be slow. Each suspect comes with its own fix, and picking the wrong fix costs time during an outage.