T3CCH/CHARLIE

CHARLIE - Semantic Memory & Cost Discipline for Claude Code

CHARLIE is the memory layer Claude Code's built-in Auto Memory isn't. Claude Code (v2.1.59+) writes flat per-repo markdown notes and prefix-loads the first 200 lines every session; CHARLIE banks typed, priority-weighted knowledge (mistakes, decisions, patterns, conventions) in PostgreSQL+pgvector and recalls it by semantic relevance — across projects, across machines, automatically injected before related work so the same mistake never happens twice.

Where it goes beyond anything native:

• Semantic code search — search_code("where do we retry failed embeds") over a live-indexed codebase. Claude Code only has grep and LSP symbol navigation; there is no first-party vector search.
• Automatic mistake capture — failed tool calls are hook-banked (PostToolUseFailure → auto-bank) without the model deciding to remember. Native Auto Memory only saves what Claude chooses to note at session end.
• Cross-machine shared state — one Postgres knowledge base serves every machine and every Claude Code instance. Auto Memory is machine-local with no sync.
• Longitudinal cost & ROI — /usage is single-machine and approximate; CHARLIE's dashboard tracks token/dollar savings and per-session cost over months, with active waste-blocking (redirecting grep/Read to indexed equivalents) rather than just measurement.

CHARLIE is built to save you time and money with AI. Reusing recalled patterns instead of re-explaining them, capping per-session spend with hard budgets, and bypassing redundant tool calls all add up. The dashboard's /savings page tracks the token and dollar savings over time so you can see the ROI.

Runs as a Docker-based FastMCP server with PostgreSQL+pgvector database, file watcher, scheduler, and web dashboard. The project will change how your claude environment works. So please either deploy on a fresh system or back up your claude files first before using this.

[![Buy Me A