Cross-Project Agent Memory Vault

Let coding agents remember rules, decisions and last week across clients

Problem

Developers working with coding agents and chat assistants across several client projects say the real cost isn't the work but the context: re-explaining past decisions, rules that apply to one client but not another, and what an agent did last week and why. Switching tools makes it worse because each keeps its own memory.

Solution

A local-first context vault that keeps a versioned record of rules and decisions per client or project, injects it into different agent tools through a standard format, and appends a short session summary at the end. Project and client scoping keeps contexts from bleeding together.

Users

Freelance developers and small teams juggling multiple clients while using Claude Code, Cursor and similar coding agents daily

MVP

Rules and decision entries scoped by project/client; one-click export as prompt context or CLAUDE.md-style files; automatic session summary append; full-text search across projects; purely local storage with simple encryption

Revenue

One-time purchase for the local version; subscription for cloud sync and team sharing ($8-15 per seat per month)

Why now

Coding agents are now everyday tools but their memory is locked inside each product, making cross-tool context a fresh and unmet gap. Standardized rule-file formats let a solo developer plug in without platform partnerships