How it works

Describe. Watch. Close.
Pick up tomorrow.

The real Crumb flow. What a session looks like, what happens when you close, what Resume actually does, and how Starters, the Tutor, Scrooge mode, the Counter, notifications, and the Baker fit in.

The manifesto

From the Crumb manifesto

Crumb onboards you. It teaches you to actually work in the terminal the right way, the way real builders do. 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 and features straight into your project.

You stop guessing. You start building.

Step 01

Describe

Tell Claude what you want. The way you'd tell a smart friend. No code, no jargon, no syntax. Crumb teaches you to think in systems and architecture instead of duct-taping prompts together and hoping.

"Build me a client intake form for my photography business" is a complete prompt. So is "I need an invoice tracker that emails me when clients are late." You don't need to specify a stack. You don't need to know what a stack is.

Don't have a prompt ready? At New Project, open Starters, a gallery of 100 fully-built project prompts, logo to a full app. Pick one and it asks the right questions first, so there are no wrong assumptions baked in, then seeds the plan before you type anything.

Built for the creative. The person with the idea, not the computer science degree.

What do you want to build?
Build me a client intake form for my photography business. It should collect name, email, shoot date, location, and any special requests. When someone submits it I want an email notification.
Send to Claude
Step 02

Watch

Claude writes the code, runs it, catches its own mistakes. The Tutor watches alongside you and hands you short, lesson-style tips right when they're useful, teaching you as you go instead of handing you a manual you'll never open.

Prompts, pointers, and one-click buttons are in arm's reach too. They auto-populate your session and wire real skills straight into your project. You stop guessing. You start building.

Crumb tracks the context level in real time. When it gets high, you know it's time to wrap cleanly instead of letting the AI forget what you decided this morning. That's what pulls you out of the spiral.

No more re-explaining your project for the fifth time.

Context Level
35%
src/IntakeForm.tsx . created
src/api/submit.ts . created
src/email/notify.ts . created
package.json . updating...
npm install ▸
added 12 packages in 1.8s
Step 03

Preserve and Resume

When you're done, close the session. One click runs a 7-layer audit and writes five artifacts to your Mac: a verbatim session log, the raw terminal transcript, full scrollback, an AI-written restart guide, and a Ledger entry. Nothing is sent anywhere.

Resume opens a fresh Claude session already briefed from those artifacts. It doesn't continue the old conversation. It starts clean, with context, which keeps the AI sharp. Day 40 starts knowing everything from days 1 through 39.

The trail is always there. Crumb never forgets even when Claude does.

Preserve . photography-intake
Session log written
Raw transcript saved
Terminal scrollback captured
AI restart guide generated
Ledger entry added
7-layer audit passed. All artifacts on your Mac. Nothing sent anywhere.
The Baker

Plan. Build. Verify.

The Baker interviews you at the start of a project, generates a linear flow-chart build plan with milestones, and watches for real evidence of completion at each gate. It rejects stubs and fake outputs.

You stop wondering "did it actually do that?" The Baker catches the AI when it lies about being done. Free tier includes manual-check mode. Automatic evidence-gating requires a paid plan.

The Baker . photography-intake
Form fields + validation
Email on submit
Confirmation page . checking
Deploy
The Counter + Notifications

Run parallel. Stay in control.

Running more than one session at a time? The Counter (Cmd+Shift+B) shows every session, its state, its context level, and its branch. You know who is working, who is stuck, who is waiting for you, without switching windows.

Native macOS notifications handle the async parts. When Claude finishes a long task while you're elsewhere, Crumb pings you. When it needs input, it pings you again. Local only. Nothing leaves your Mac.

The Counter . Cmd+Shift+B
client-portal
feature/auth-flow · ctx 74%
Needs you
invoice-tool
main · ctx 22%
Working
portfolio-site
feature/gallery · ctx 41%
Resting
Scrooge mode (Nerd)

Refuses to overpay.

A toggle at the top right, off by default. Flip it on and Crumb stops routing everything to the priciest model by habit. Instead it splits the work across three tiers, each piece of work going to the cheapest model that can actually handle it:

  • Helpers — fast, cheap models for the busywork: formatting, boilerplate, small edits.
  • Checkers — a mid-tier model for judgment calls, and for reviewing what the helpers did.
  • Expert — the frontier model, reserved for architecture calls and the genuinely hard stuff.

Typically around 70% cheaper, we've seen a range of 60–85% depending on the work. On a subscription plan, that stretches the same weekly limits across roughly 3 to 5 times the work. It's routing, not magic, and not a guaranteed number. Included in the 3-day trial and on every paid plan; free tier doesn't include Nerd mode.

Scrooge mode
Helper Rename 12 component props
Checker Review the intake form validation logic
Expert Decide the auth architecture
Est. savings this session: ~70%. Typical range, not a guarantee.
Demo video

A 90-second walkthrough is on the way.

Static screenshots tell the story for now. Video will show a real session, not a demo environment.

The closer

Pick up your crumbs.

Build the thing.

Free to start. No card required for the free tier. No spiral.

Get Crumb