▲ 11 r/BDDevs

Meet Projectmem — an open-source agentic memory for your AI coding assistant.

Whether you're a programmer, web dev, researcher, AI coder, or vibe coder: if you work on projects big or small using AI, this can be a real productivity saver.

In the age of coding with AI, fast coding alone isn't enough. Having memory for your project is equally important.

Feel free to ask any questions you have about this tool, I'll try to answer every one of them. Thanks.

u/SatisfactionFar3936 — 4 days ago

▲ 1 r/VibeCodeDevs

projectmem — local memory + judgment for vibe coders. Open source. MIT. Just shipped on PH today

gm vibe coders 👋

I'm Ripon — solo builder, PhD student, been vibe coding side projects on Claude / Cursor / Codex / Antigravity for the past year. Today I'm launching the tool I wish existed from day one. It's called projectmem and it's live on Product Hunt right now.

why vibe coders need this more than anyone

Trad devs feel AI amnesia. We feel it 10x harder. Because we don't always architect first — we vibe, we ship, we patch, we move on. Two weeks later we open the same project and our agent has zero idea what we already tried, what we already fixed, what already broke. We re-explain everything. Burn 10K tokens. Watch it suggest the exact dead-end fix from last week.

That's the gap projectmem fills.

after and before using projectmem

what it actually does

projectmem is a local-first memory + judgment layer that lives inside your repo as plain text. It captures every bug, every failed attempt, every fix, every architectural decision your agent makes — and feeds it back in the next session so the AI actually remembers.

But the killer feature isn't memory. It's judgment at git commit time.

When you `git commit`, projectmem checks if you've tried a similar fix on this file before and failed. If you have, it warns you BEFORE the commit completes. Memory + judgment, at the exact moment it matters.

Features beyond memory

- 14 MCP tools — plugs into Claude, Cursor, Codex, Antigravity

- pre-commit warning (the killer one)

- `pjm score` — A+ to F grade for your project's "prevention score" with debugging hours saved, tokens saved, $ saved

- `pjm visualize` — 4-view D3 dashboard (story map, ROI, architecture map, event timeline)

- cross-project memory at `~/.projectmem/global/` — lessons from one vibe project auto-apply to the next if the stack matches

- 100% local. No cloud. No telemetry. No accounts.

- default-on secret redaction (OpenAI keys, GitHub PATs, AWS, JWT, etc.)

- MIT-licensed. Free forever.

reddit.com

u/SatisfactionFar3936 — 2 months ago

▲ 0 r/sideprojects

Built projectmem because I was tired of AI agents repeating yesterday's failed fixes

Quick story before the project details.

Few weeks ago I watched my AI coding agent confidently suggest the same broken CSS fix I'd rejected the previous Friday. Same contain: layout solution. No memory I'd already tried it. Every new chat was Groundhog Day. That was the breaking point. I'd been trying on a fix for months — this weekend I finally shipped it. It's called projectmem.

What it is:

A small Python package that gives AI coding agents (Claude, Cursor, Antigravity, Codex) persistent project memory through MCP. It captures development events — bugs, attempts with explicit outcomes, fixes, decisions — into plain-text files inside the repo. The agent reads it through 14 MCP tools at session start.

The thing I'm most proud of is the pre-commit hook. It checks your staged changes against memory and warns BEFORE the commit if a logged failed approach exists for that file. Memory plus judgment, at the moment of action. Most "AI memory" tools store and retrieve. Projectmem interrupts you at the right time.

Tech rundown:

Python 3.10+, ~600 LOC core
Deps: mcp, typer, watchdog. That's it.
Storage: append-only JSONL inside the repo, distilled into summary
58 unit tests, end-to-end verified across 4 MCP clients
100% local. No cloud, no telemetry, no accounts. MIT.
v0.1.3 on PyPI, also on the official MCP Registry

What I'd love feedback on:

The pre-commit precheck heuristics are simple right now (file-name match → surface failed attempts). What signals would make it smarter without becoming noisy?
For anyone running it: did the install + MCP wiring feel clean? What's the friction point?

Genuinely interested in what's working and what isn't for other makers.

u/SatisfactionFar3936 — 2 months ago