Stats
Links
Categories
Intelligent memory sidecar for Claude Code
Passively captures project decisions. Writes them where Claude reads them. Zero effort.
The Problem • Quick Start • How It Works • Architecture • Commands • Contributing
The Problem
Every time you start a new Claude Code session, it starts from scratch. It doesn't remember that:
- Your brand uses Inter for headings and #2563EB as the primary color
- Your API follows RESTful conventions with a /api/v1/ prefix
- You chose Drizzle over Prisma after careful evaluation
- Your React components use compound pattern with forwardRef
- That edge case in the payment flow that took you two hours to debug
There are many times when curated context can save significant time, frustration, and make Claude Code feel like magic. Take a website application project — the branding guide that defines colors, fonts, and layout may not always be defined upfront. Even if it was, it may not always be included in the context. It may change over time. If these details aren't in the context and you ask Claude Code to build a new page, it will often pick an entirely different theme, colors, fonts, and layout than what your application already uses.
You end up re-explaining the same decisions in every session. Over and over.
Where curated-context fits
Claude Code has a growing memory ecosystem. Each layer serves a different purpose:
| Layer | How it works | What it's good at |
|---|---|---|
| Built-in memory | You tell Claude "remember this" and it writes to CLAUDE.md | Explicit, intentional notes you want Claude to keep |
| claude-mem | Cross-session search over past conversations | Recalling what you discussed — finding prior work, decisions, and context from old sessions |
| curated-context (this plugin) | Passively extracts high-value information from every session | Automatically remembering project knowledge — design tokens, architecture choices, API patterns, conventions, and gotchas |
Built-in memory requires you to stop and say "remember this." claude-mem lets you search your history. curated-context fills the gap between them — it watches your conversations and silently captures the decisions that matter, so the next session starts with full context without you lifting a finger.
All three can run together. They complement each other.
Quick Start
# Add the marketplace
claude plugin marketplace add odmarkj/curated-context
# Install the plugin
claude plugin install curated-context
That's it. Two commands. No configuration needed. Works on the host and in devcontainers — the plugin auto-bootstraps into containers on first use.
How It Works
curated-context uses a 4-tier cascading pipeline designed to minimize API costs. Most sessions require zero API calls.
| Tier | Method | Cost | What It Captures |
|---|---|---|---|
| 1 | Memory Protocol | Free | Claude self-reports decisions to .claude/decisions.log |
| 2 | Structural Extraction | Free | CSS variables, dependencies, configs, API routes from file writes |
| 3 | Deterministic Triage | Free | Regex/keyword scoring filters ~75% of conversation noise |
| 4 | Claude via claude -p | Your Claude Code sub | Ambiguous conversational decisions (max 30 calls/hour) |