DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to pick up a Claude Code project where you stopped with Claude DB

Get Claude to recap your last decisions and open threads when you return to a repo.

Who it is forA developer who works on a repo in short sessions and loses the thread between chats.

The problemEach new Claude Code chat starts from zero, so you re-explain past decisions, dead ends and rules before any work can start.

The outcomeAt the start of a new chat, /catchup tells you where you stopped, using memory saved from earlier chats.

What you need first

  • Node 22.16 or newer
  • A git repository for your project
  • Claude Code installed and able to run hooks
  • Optional: a Postgres or MongoDB database if you want to share memory across machines

Steps

  1. npm install -g claude-db
  2. cd your-project
  3. claude-db install --project
  4. Restart Claude Code, then run claude-db flush and claude-db scan to load existing material.
  5. Start a new chat in the project and run /catchup.

Prompt for your agent

In the repo <repo-path> with claude-db installed, run /catchup in Claude Code and report the decisions, dead ends and open items it lists. Verify that each item matches a real earlier discussion or commit in the project before you rely on it.

Caveat. Memory only builds up from chats and scans after install, so the first chat in a new project will know little until you use it for a while.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page