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

How to turn repeated instructions into project notes with CTX Handoff Mod

Save the preferences, corrections and facts you keep repeating into a notes file loaded into every new chat.

Who it is forA developer who keeps re-teaching Claude the same project conventions across new conversations.

The problemA new conversation forgets instructions you already gave, so you repeat them every session.

The outcomePreferences, corrections and facts are kept in one Markdown notes file per project, and an instruction repeated three times becomes a line in your repo.

What you need first

  • Claude Code 2.1.287 or later (the README says it is tested up to 2.1.302)
  • A Claude subscription sign-in, or an API key, Bedrock or Vertex setup with the cache refresh turned off
  • Access to the Claude Code plugin commands in a terminal

Steps

  1. Run claude plugin install ctx-handoff@ctx-handoff-mod if it is not installed yet
  2. Give Claude a preference or correction in normal conversation, as you would anyway
  3. Open /handoff panel to view memories, rules and the latest notes update
  4. Delete any memory you do not want; note that it returns only if you bring it up again in a new part of the conversation
  5. Check the Markdown notes file in ~/.claude/projects/ for your project

Prompt for your agent

Using Claude Code with ctx-handoff-mod, record a repeated instruction for <project path> and then inspect the notes file under ~/.claude/projects/ for that project. Expected output: a Markdown notes file containing the instruction. Verify that the entry appears in the file and in the panel.

Caveat. Notes are updated from the new part of the conversation by a model the README names, so review the panel output before relying on the notes.

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