Why Crumb exists.

Claude forgets. Crumb remembers. And Crumb gets it done. That's the whole reason this exists.

Here's the trap nobody warns you about. You've got a vision. You open up an AI and start building. And somewhere around hour three you're lost in dev hell, twelve half-built features deep, the AI forgot what you decided this morning, and you're vibe-coding in circles with nothing to show for it. That's not a you problem. That's every AI tool handing you a blank terminal and wishing you luck.

Paul von Rieter is a photographer and the founder of The Editorial Edit. He's been using Claude Code since it launched. Not occasionally. Every day. Building real software. Client tools, automation systems, apps with actual users. And every time he came back to a project after a few days off, he'd lost the thread. Context evaporated. The AI re-walked ground it had already covered. Real time burned re-explaining the project for the fifth time.

Every project starts the same way now: at New Project, Crumb hands you Starters, a gallery of 100 project briefs, a logo to a full app. Pick one, answer a few questions up front so there are no wrong assumptions later, and Crumb seeds the plan before you've typed a line of code.

Crumb onboards you, too. The built-in Tutor watches your session and teaches you as you work: short, lesson-style tips right when they're useful, not a manual you'll never open. It shows you how to think in systems and architecture instead of duct-taping prompts together and hoping. And it puts the power in arm's reach: prompts, pointers, and one-click buttons that auto-populate your session and wire real skills straight into your project. You stop guessing. You start building.

And it never forgets. When you close a session, Crumb runs a 7-layer audit and writes five artifacts: a verbatim session log, raw transcript, terminal scrollback, an AI-written restart guide, and a Ledger entry. Every decision, every dead end, every rule you set. Day 40 starts knowing everything from days 1 through 39. No more re-explaining your project for the fifth time.

Crumb also shows you the wall before you hit it. Live usage meters. A native notification when a long task finishes while you're in the kitchen. The Counter, which shows every parallel session and whether it's working, waiting, or done. The Baker, which builds a project plan and rejects stub completions. The things Paul was wishing for every day before he built them himself.

And if you're watching the bill, there's Scrooge mode: a top-right toggle that refuses to overpay. Chores go to fast, cheap models. Judgment calls go mid-tier. The hard stuff goes to the frontier expert, with a second model checking the work so quality holds. It typically saves somewhere around 70%, sometimes more, which means the same subscription stretches across a lot more building.

The name is literal. Hansel and Gretel dropped crumbs through the forest so they could find their way back. You've been leaving a trail of crumbs this whole time. Half ideas, dead sessions, scattered context, almost-features. Crumb picks them up and makes something of them.

Crumb is not VC-funded. It's not backed by a growth fund with an exit timeline. It's an independent macOS app built by the people who use it, priced to stay sustainable without being predatory, and committed to not changing what makes it good.

The Editorial Edit is the company behind Crumb. Founded by photographers, for the people who create things. The original product line is focused on photography workflow. Crumb is the first tool that's useful for everyone who wants to build software without becoming a software developer first.

If you have a question, use info@theeditorialedit.com. Paul reads it.