Clawback captures what matters from your AI builds while it's still fresh: the prompts that worked, the decisions you made, the fixes you'll never think to write down. Stored on your machine, owned by you, waiting patiently for the day you need it.
Claude gives you three places to build: Chat, Code, Design. You start in one, jump to another, and every idea spawns two more. After a weekend of that — where on earth is everything? Where did you do it? How many ideas were there? Where are the results of your work?
Yesterday you built something brilliant. The prompt was perfect, the fix was clever, the whole thing just worked. Today? Gone. It's somewhere in forty chat threads, one of which is helpfully titled "Untitled."
And here's the trap: you don't know when you'll need it back. Sometimes it's tomorrow, when the client wants "the same thing again but blue." Sometimes it's in a year, when a new project needs exactly the solution you already invented and can no longer find. The knowledge doesn't expire. Your memory of where you put it does.
Every session you don't capture is work you'll do twice. Time to claw it back.
Three steps, no manual required
{{ s.n }}{{ s.label }}
{{ s.title }}
{{ s.body }}
{{ s.tail }}
A memory for the machine age
Clawback traces it all, maps it all, retains it all — every build across Chat, Code, and Design, filed logically and adaptably. Create your own categories; file under client, project, or staff name. The prompts that worked, the architecture decisions, the gotchas, the "never do this again" notes. Everything searchable, everything structured, all on your own computer — or backed up to your own cloud.
It does one job and does it properly. No bloat, no dashboard soup, no feature you'll never touch.
Small. Solid. Yours.
Memory sold separately. This is the memory.
{{ f.tag }}
{{ f.title }}
{{ f.body }}
→{{ f.benefit }}
Claude has a context window. You have Clawback.
One of you will remember this conversation. Make sure it's you.
Made for people who build with AI
Developers keeping track of prompts and patterns across projects. Consultants who solve the same class of problem for different clients. Tinkerers with forty experiments and no map. Anyone who has ever typed "what was that prompt I used" into a search bar and felt the cold silence of the void.
And if you bill for your time, ClawBack has a quieter job: making sure the work you did actually reaches the invoice. Not to make more money — to stop losing the money you already earned.
If you build with AI more than once a week, Clawback pays for itself the first time it saves you a rebuild — or the first invoice it rescues.
Every tool you own costs you money. This one finds it.
{{ quoteTyped }}
— Every ClawBack user, ever. Probably.
The Catch
We don't bother with small print. Monthly. Annually. Or forget all that and go Life.
Monthly
$4/month
Dip a claw in. Cancel whenever — but when you end, the library closes. Your data stays yours either way.
Upgrades for life, on every plan. And a feedback loop that actually loops: suggest it; we evaluate it — a suggestion-to-shipped process that doesn't take a decade. Let's face it: none of us knows what 2030 holds, and that's {{ daysTo2030 }} days away.
→ Every upgrade, forever
→ One-click backup & restore
→ Your own cloud database, your keys
→ Open, portable data format
→ Works offline, forever
→ No account, no telemetry, no spying
→ Exportable timeline
→ Timesheet management genius
DONATE AN ORGAN
For those who know what a lost month of work actually costs. Name your own price — pay ANYTHING you like above the minimums, monthly, annually, or for life. Your generosity funds the roadmap; your name goes on the donor list (organ optional).
Minimums apply: $4/mo · $24/yr · $11 life. Ceilings don't.
STARSHIP ENTERPRISE
A site licence for the whole crew — even Scotty. Every seat, every department, every machine — one payment, one number, and nobody ever files an expense claim for memory again. Set phasers to stunning.
Collective network AI library database. ClawBack 'Zoo Manager', with ClawBack 'Ranger' departments. We have not thought of everything.
Contact and we'll send a landing party
Every plan: local-first, no account, your data in an open format. The claw remembers regardless.
How the machine works
Builds from Claude's three modes flow into one registry. No magic — a scraper, a JSON file, and a dashboard that reads it.
01Where builds are made — the three modes
claude-chat
Conversations & artifacts
One-off tools, documents, prototypes made in chat. The build lives in the conversation.
home → claude.ai/chat/… link
claude-code
Repos on your machine
Apps, scripts, automations built in the terminal. Leaves evidence: CLAUDE.md · .claude/ · git
home → ~/<folder>/ on disk
claude-design
Design files
Dashboards, UI, brands, posters as .dc.html design projects.
home → Design project / export
02Where builds land — the source of truth
~/ your machine
≈67 registered builds — folders on disk, chat links, and design files, side by side
pdf_factory/NZLL-Web-App/etoro-ikbr-bot/clawd/claude.ai/chat/…ClawBack.dc.html+ 60 more
scan · scrape · verify
03The data build — a Claude Code mission
clawback scraper
runs in Claude Code · replaces guesses with facts
step 1 — scan
Walk ~/, find every build folder; skip vendor dirs.
Every build filed by category and colour-tagged by its mode — Chat · Code · Design. Nothing lost, nothing rebuilt twice.
localStorage ⇄
Your manual corrections — status, category, origin, notes — persist in the browser, keyed by id.
why ids are sacred: change an id → its corrections are orphaned.
Legendbuilt in Chatbuilt in Codebuilt in Designflow: modes → disk → scraper → clawback-data.json → dashboard
Fair questions, straight answers
{{ q.q }}
{{ q.a }}
You'll need it tomorrow. Or in a year. Save it today.
The work you did yesterday is already fading. Clawback catches it while it's fresh and holds it until the day it saves you, whether that's tomorrow morning or fourteen months from now. It costs less than the coffee you'll drink rebuilding one lost prompt.