We're starting to show our work

Most of what we change about Comb happens quietly. A bug gets fixed, a statement that used to fail now imports correctly, a new way to track your spending shows up in the sidebar — and unless you happen to notice, there's no way to know any of it happened, or why.

We don't think that's good enough for something that holds your financial data. So this is a new, permanent place on Comb where we'll explain what changed and why, every time something meaningful ships.

Why we built it

A lot of what we fix starts with someone actually using Comb and hitting something broken — a statement that wouldn't import, a number that looked wrong. That's not a failure we want to hide in a commit log only engineers read. It's proof the product gets better because real people are using it, and we think that deserves to be visible.

• —What changed, described the way you'd explain it to a friend — not engineering shorthand.
• —Why we built it, including when it came from something a customer actually ran into.
• —What it actually means for you, which is usually: nothing you need to do, it just works better now.

If we can't explain why a change makes Comb better for you, we probably shouldn't have shipped it.

What this means for you

Nothing changes about how you use Comb. When something ships that's worth telling you about, you'll find it here — in plain English, written by the people building it.