Your AI forgets.
Hydrate remembers.
Claude Code starts each session with a blank mind. Hydrate captures what was built, decided, and named — then quietly injects it into the next session. No prompt engineering. No screenshots of previous chats. Just context that works.
From the 2026-04-17 benchmark run. $67 of real API spend. Every number is reproducible.
The difference is execution, not intelligence.
Models don't get smarter with Hydrate. They get context. That's usually enough.
$ claude "add a dark mode toggle"
Haiku: What should the default
colour scheme be?
Haiku: What do you mean by
"toggle" — a button? switch?
Haiku: Which pages should be
affected?
[ nothing written ] $ claude "add a dark mode toggle"
Haiku: edits src/styles/globals.css
Haiku: edits src/components/Nav.tsx
Haiku: Done. Toggle wired to
prefers-color-scheme. Persists in
localStorage. Icon updates on
change. It pays off differently for every model.
Hydrate isn't a uniform speed-up. Each model has a different failure mode without context. Hydrate removes all four — at different costs, with different value propositions.
Three quiet pieces.
Hooks
Hydrate installs two Claude Code hooks — UserPromptSubmit and Stop.
They're invisible to you. They capture each session's prompt, decisions, and output.
Facts
Between sessions, an extractor pulls concrete facts — "pricing tiers are Free/Pro/Team", "accent colour is #89b4fa" — and stores them scoped to your project.
Dashboard
A local dashboard at localhost:8089/dashboard shows your spend, cache ratio,
and facts per project. Nothing ever leaves your machine — Free, Pro, or Team.
Start free. Pay only when you need the rest.
Pro
Unlimited active projects plus per-project backup / restore.
Join Pro waitlist →Team
Shared project memory across teammates. Hybrid mode shines here.
Join Team waitlist →Enterprise with SSO, self-host, org-scoped facts — contact sales.
Install in 30 seconds.
No account. No telemetry. The Free tier never touches the network.