Skip to content

Latest commit

 

History

History
51 lines (33 loc) · 1.84 KB

File metadata and controls

51 lines (33 loc) · 1.84 KB

Launch Copy

X / Threads

I got tired of re-explaining the same repo to every new AI coding agent session.

Deja Vu is a 3-file, repo-local memory layer any capable coding agent can follow.

No vector DB. No SaaS. No embeddings. No daemon.

Memory should feel like recognition, not replay.

LinkedIn

Every new AI coding agent session starts with the same tax: explain the repo, explain the decisions, explain the constraints, explain what not to break.

Deja Vu is a 3-file memory system for AI coding agents:

  • AGENTS.md
  • memory/summary.md
  • memory/impressions.jsonl

It is repo-local, human-readable, git-friendly, and does not require a vector database, SaaS memory platform, embeddings, daemon, or npm install.

The goal is not to store more. The goal is to help agents recall less, better.

GitHub Release Intro

Deja Vu v0.6.0 reframes the project around the adoption path that matters most: a 3-file, repo-local memory system for any capable AI coding agent.

This release adds a copy-first starter kit, per-agent prompts, clearer compatibility and comparison docs, a visual recall flow, launch copy, and an optional deja-vu init/doctor/explain CLI that serves the file-first protocol without making npm required.

Hacker News Titles

  • Show HN: Deja Vu, a 3-file memory system for AI coding agents
  • Show HN: Repo-local memory for Codex, Claude Code, Cursor, and Windsurf
  • Show HN: Stop re-explaining your repo to every new coding agent chat
  • Show HN: Deja Vu stores less so coding agents recall better

Taglines

  • A 3-file memory system for any AI coding agent.
  • Repo-local memory for coding agents.
  • Long-term project memory that fits in a pull request.
  • Stop re-explaining your repo to every new agent chat.
  • Memory should feel like recognition, not replay.
  • Store less, recall better.
  • Your repo should carry its own agent memory.