Memory Pruner
An agent memory cleaner app idea: a cleaner for stale notes in your coding agent memory. Weekend build with Node.js, Claude API, simple-git and Commander, for developers who use claude code or cursor on long-running projects.
Why now
beacon.sh launched as open-source self-improving memory for AI coding agents, which means more projects will pile up agent-written notes that drift out of date. The mcp package is also up 70% on PyPI, so more agents read from shared memory files that nobody reviews. From the signals of the week of 9 Nov 2026.
The spec
Scans the memory and rules files your coding agent accumulates and finds entries that contradict the current code, duplicate each other or refer to files that no longer exist. It proposes a pruned version you can accept entry by entry.
Build time
WeekendAPIs or integrations · Level 3 of 5Audience
Developers who use Claude Code or Cursor on long-running projects.
Stack
- Node.js
- Claude API
- simple-git
- Commander
Fun factor
Watching a bloated rules file shrink to half its size feels like clearing a desk.
Core features
- Scan a repo for agent memory and rules files
- Detect references to deleted files and renamed functions
- Find duplicate or conflicting entries
- Accept or reject each proposed change as a diff
AI features
- Compares each memory entry with the current code and judges whether it is still true
- Merges near-duplicate entries into one clear rule while keeping the original meaning
Stretch goals
- Git hook that warns when memory drifts after a large change
- Support for several agent file formats at once
- Staleness score shown in a README badge
First version
A CLI that reads one memory file, checks file paths mentioned in it against the repo and lists stale lines.
Build plan
4 milestones, in the order you would build them. Saved ideas get this plan with checkboxes and notes.
The build prompt
Paste this into ChatGPT, Claude, Codex, or Cursor, then build the first version before anything else.
# Build Memory Pruner You are a senior full-stack engineer pairing with me on a side project. Build a working first version of the product described below. Read the whole brief before writing any code, then follow "How to work" at the end. ## The idea **Memory Pruner.** Scans the memory and rules files your coding agent accumulates and finds entries that contradict the current code, duplicate each other or refer to files that no longer exist. It proposes a pruned version you can accept entry by entry. **Why now:** beacon.sh launched as open-source self-improving memory for AI coding agents, which means more projects will pile up agent-written notes that drift out of date. The mcp package is also up 70% on PyPI, so more agents read from shared memory files that nobody reviews. **Who it is for:** Developers who use Claude Code or Cursor on long-running projects **What makes it fun:** Watching a bloated rules file shrink to half its size feels like clearing a desk. ## Scope - **Build time:** Weekend. Size every decision to ship a working first version inside this window. - **Technical ambition:** Level 3 of 5, "APIs or integrations". The product leans on third-party APIs. Wrap each integration in its own module, handle its failures and rate limits, and cache what is safe to cache. - **First version only.** Ship the core features below end to end. Stretch goals are listed so you can design around them, not build them. ## Core features (each must work end to end in the first version) 1. Scan a repo for agent memory and rules files 2. Detect references to deleted files and renamed functions 3. Find duplicate or conflicting entries 4. Accept or reject each proposed change as a diff ## AI features - Compares each memory entry with the current code and judges whether it is still true - Merges near-duplicate entries into one clear rule while keeping the original meaning How to build them: - Put every model call behind one server-side module with a typed interface, so the provider can change without touching the UI. - Read API keys from environment variables only, and document each one in `.env.example`. - Write prompts as versioned constants with clear instructions and an example of the expected output; parse and validate responses before using them. - Handle timeouts, rate limits, and malformed output with a graceful fallback the user can understand. Stream responses where a wait would exceed a couple of seconds. - Never let a feature depend on the model being perfect. Show the result, let the user edit or retry. ## Stretch goals (later, not in the first version) - Git hook that warns when memory drifts after a large change - Support for several agent file formats at once - Staleness score shown in a README badge Leave clean seams for these (a module boundary, a nullable column, a feature flag), but do not implement them unless I ask. ## Tech stack Use exactly: Node.js, Claude, Simple-git, Commander. Stay on current stable versions, follow each tool's official conventions, and add a library only when the standard library or the chosen stack cannot do the job cleanly. If part of this stack is a poor fit for a specific requirement, say so and propose the smallest change. ## Owner's notes Written by me, the project owner. Treat these as requirements and preferences that override the generated material above when they conflict. The first version should be exactly this, and no bigger: A CLI that reads one memory file, checks file paths mentioned in it against the repo and lists stale lines. ## Build plan (with saved progress) 0 of 4 steps complete. Resume at step 1: Find memory files. Before you start it, check what is already implemented so you do not repeat finished work. 1. **Find memory files** [not started] Locate known agent memory and rules files in a repo. 2. **Check references** [not started] Verify every mentioned path and symbol still exists. 3. **Judge entries** [not started] Ask the model which entries conflict with current code. 4. **Write the diff** [not started] Output a proposed cleaned file the user can apply or reject. ## Definition of done for the first version - [ ] Scan a repo for agent memory and rules files works end to end, with real data, not a placeholder. - [ ] Detect references to deleted files and renamed functions works end to end, with real data, not a placeholder. - [ ] Find duplicate or conflicting entries works end to end, with real data, not a placeholder. - [ ] Accept or reject each proposed change as a diff works end to end, with real data, not a placeholder. - [ ] Every screen handles loading, empty, and error states. - [ ] Typecheck, lint, and any tests pass, and the main user flow was exercised by hand. - [ ] A README explains setup, environment variables, and how to run it locally. ## Quality bar - Responsive from a phone to a desktop, keyboard-accessible, semantic HTML, visible focus states, labelled inputs, and sensible contrast. - Loading, empty, and error states for every screen that reads or writes data. Errors say what happened and what to do next. - Validate on the server, never trust the client, and keep secrets in environment variables with a committed `.env.example`. - Type-safe end to end. No `any` without a comment explaining why. - Small, readable modules named after what they do. No premature abstraction, no dead code, no TODOs left for later without a note. - Sensible defaults over settings. If a choice is not in this brief, pick the simplest option that keeps the product coherent and say what you chose. ## How to work 1. **Read, then restate.** Summarize the product in three sentences and list your assumptions. Ask only the questions that block implementation. For everything else, decide and note the decision. 2. **Plan before code.** List the files and modules you will create, in build order, mapped to the core features. If a build plan is included above, use it instead: resume at the first step not marked done and check what already exists before touching it. 3. **Set up.** If a project already exists, inspect its code, instructions, and conventions first and build on them. Otherwise scaffold the stack above with linting, formatting, a typecheck script, `.env.example`, and a README stub. 4. **Model the data first.** Define the types, schema, and any migrations before the UI, so the shape of the product is settled early. 5. **Build in vertical slices.** Finish one core feature end to end (data, logic, UI) before starting the next. Keep the app runnable after every slice and commit each slice with a message that says what changed and why. 6. **Then the interface.** Apply the quality bar above to each screen as it lands, not as a final pass. 7. **Verify.** Run typecheck, lint, and tests. Exercise the main user flow by hand. Check each item in the definition of done and each acceptance criterion. 8. **Report.** Tell me what works, what you tested and how, what is not done, every setup step I must complete myself, and the three most useful next steps. Never claim a service, test, or flow was verified when it was not. If you can edit and run the project, start implementing right after the short plan. If you cannot, give me concrete code and the exact commands to run for the next step. Rules: keep the product name and the scope as written, do not invent features, prefer boring and proven choices, and stop to ask me when a decision would be expensive to reverse.
How to use
- Copy the prompt above.
- Open ChatGPT, Claude, or your AI editor and paste it into a new conversation.
- Build milestone one, run it, then move to the next. Add stretch goals only after the first version works.
Want ideas built around you instead? Generate four from your own interests, time, and stack.
FAQ
Frequently asked questions
Answers on what Memory Pruner is, how to build it, and where example ideas come from.
Similar to Memory Pruner
More developer tools ideas, then a few from other categories.
Ready to generate yours?
Four ideas per round, shaped by your interests, skill level, and how much time you have.