Who it is forA developer who stops mid-task and wants a teammate or a fresh chat to pick up the work without a long recap.
The problemWork in progress lives in one chat, so the next person or session has to rebuild the context by hand.
The outcomeA short note saved through /handoff that the next chat or teammate can read at the start of their session.
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
npm install -g claude-dbcd your-projectclaude-db install --project- Restart Claude Code.
- At the end of your session, run
/handoffand write a short note on what is done and what is next.
Prompt for your agent
In the repo <repo-path>, run /handoff in Claude Code at the end of the session and then start a new chat in the same project. Expected output is a short summary of the open work in the new chat. Verify that it names the same open task you wrote in the handoff.
Caveat. The note reaches a teammate only if they use the same Claude DB database, so a local SQLite store does not share it by default.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: 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