Claude Reforge

Claude Reforge

Built specifically for Claude Code.

Claude Code is stateless.
Claude Reforge isn't.

Every session, Claude starts from zero.

It doesn't know that you spent 3 hours on that timeout bug last week.
It doesn't know that webpack.config.js needs the alias or the build breaks.
It doesn't know that in *your* project, the obvious solution is wrong.

So it makes the same mistakes. Again. And again.

Until now.

Claude Reforge breaks that loop.

This is not RAG.
It does not retrieve knowledge.

It learns from what actually happened and uses that to guide decisions and prevent repeated failures.

This is not a prompt.
Not a config file.
Not documentation.

It's experience.

Without vs With

Quick Start

Restart Claude Code. That's it.

The moment it clicks

You're debugging something. Before Claude starts, it already knows:

Claude doesn't rediscover this.
It already knows what worked.

It compounds

Every fix becomes future context.
Every session adds to what Claude knows about your project.
Every error resolved makes the next one faster.

The more you use it, the less Claude has to guess.

How it works

Claude Reforge installs four hooks into Claude Code's lifecycle.
They run silently. You never interact with them directly.

The hook pipeline

Memory types

Retrieval

No embeddings. No API calls. No external dependencies.

Retrieval uses a composite score: BM25 keyword match × time decay × importance × outcome weight × reuse bonus × project affinity × folder affinity. Injection is deliberately capped: top 3 episodes + top 3 rules + max 1 prevention warning. Less is more — too much context hurts more than it helps.

Score factors:
- BM25 — keyword relevance between query and episode text
- Time decay — < 1w → 1.0 / < 1mo → 0.85 / < 3mo → 0.65 / < 6mo → 0.45 /…