The bug that stayed silent even after we made it 200 times faster

Some bugs crash loudly. This one didn’t make a sound, which is exactly why it took three separate fixes to actually go away.

What happened

Forge is meant to work alongside other AI coding tools — open Claude Code in the same project folder, and Forge quietly hands it context about what you’re building, so you don’t have to re-explain your own project to a second assistant. At least, that’s the idea. In practice, a tester opened both side by side and got nothing. No error. No red text. Just silence, as if the two tools had never heard of each other.

The obvious fix that wasn’t enough

The first suspect was easy to find: every time a message was typed, Forge quietly ran a background check across the whole project — and it was doing that check one file at a time, spinning up a separate process for every single file. On a real project, that’s not one check, it’s two hundred. We fixed it properly, collapsing two hundred separate calls into one.

It should have been a clear win. It wasn’t. The two tools still weren’t talking.

The silent stopwatch

The real answer took longer to find, and it’s the part worth remembering. Even after the fix, that one remaining check still took around 24 seconds to run on a real project. Nothing wrong with that on its own — except the platform running it had its own safety limit of 5 seconds, and it enforced that limit by quietly killing anything that ran longer. No warning. No “timed out” message. The result was finished, correct, and ready — and it got thrown away one second before it would have arrived, every single time.

A performance fix can be completely correct and still lose to a stopwatch nobody told you was running.

There was a second, smaller problem hiding behind the first: this whole handoff only ever switched on when you created a brand-new project. Open a project you’d already been working on, and Forge never even tried. Months of existing projects had simply never been invited to the conversation.

The fix

Two changes, neither of them dramatic: the safety limit went from 5 seconds to 30, giving a real check room to actually finish. And the handoff now turns on every time a project opens, not just the moment it’s born.

Where that leaves things

The dramatic bugs — the crashes, the stack traces — are the easy ones. They tell you exactly where they are. This one didn’t: everything downstream looked fine, because nothing ever technically failed. It just quietly never happened. That’s the harder, more honest kind of bug to catch, and it’s also the kind that two hundred green tests will never show you.

We’re closer than we were before tonight, and closer in a way we can point to and explain — which, as always, is the only kind of closer worth writing about.