Leave notes for your agent
A note for your agent is a piece of work you leave in kelve, on the lines it’s about. Your agent picks it up in your own session, the next time you message it.
How it goes
- You leave it. Select lines, Note, then For Claude Code (your agent’s name), then Keep. The choice shows where it goes on your agent’s list, and the note says “Waiting for your next message to it”.
- Your agent is told. The next time you message it, it learns notes are waiting.
- It does them, in your files, as it does anything you ask. You watch it, and stop it as you would.
- It marks each done, with a line on what it did, then shows you what it changed. The note says Done, with that line under it, and See what Claude Code changed.
A note can ask your agent to find something out. What it finds comes back as a note with the work, in the project’s .kelve/notes/. You and the people you work with read it in kelve.
A note is done for the words it had. Change it after, in kelve or any editor, and it waits again. Your agent is given what it did before and what you added. It does only what’s new. Clear it for new notes forgets what was done.
kelve never starts your agent, never runs it on a schedule, and never keeps it going after it stops.
How your agent is told
Your agent is told through one hook in its settings. kelve adds the hook only with your yes. You give it when you set kelve up, or with Let Claude Code pick up your notes, and lessons in Settings, Your agent. kelve shows you the exact change first.
From the command line:
kelve hook install claudekelve hook remove claudeIn place of claude: codex, cursor, copilot, gemini, antigravity, kiro, droid, qwen, qoder or augment.
The hook adds one command, kelve moment, to your agent’s own settings, on its own events. It leaves the rest of the file as it was. kelve moment answers in a fraction of a second or says nothing. If kelve isn’t running, it prints nothing and starts nothing.
- As you send a message: one line when notes are waiting for the project you’re in, and nothing otherwise. Once for each version, it also says when a newer kelve is out.
- As your agent reads or edits a file, runs a command, or something fails: the lesson that helps then, if one fits.
- As its turn ends, for Claude Code and Qoder, or with your next message for other agents: your agent may have changed files and not shown them in kelve since. If so, the hook asks it to show you its work, if the work is finished and worth showing. Your agent decides. For Claude Code and Qoder, after a hard stretch it got past, the hook asks one question on what it learned.
| Agent | Where the hook goes | After |
|---|---|---|
| Claude Code | ~/.claude/settings.json | |
| Codex | ~/.codex/hooks.json | Trust it in /hooks |
| Cursor | ~/.cursor/hooks.json | |
| GitHub Copilot | ~/.copilot/hooks/kelve.json | |
| Gemini CLI | ~/.gemini/settings.json | Restart it |
| Antigravity | ~/.gemini/config/hooks.json | Restart it |
| Kiro | ~/.kiro/hooks/kelve.json | |
| Factory Droid | ~/.factory/hooks.json | Look it over in /hooks, or restart it |
| Qwen Code | ~/.qwen/settings.json | Restart it, or open /hooks |
| Qoder | ~/.qoder/settings.json | |
| Augment | ~/.augment/settings.json, and a script in ~/.augment/hooks/ |
Cursor, GitHub Copilot, Antigravity and Augment have no event for a message you send. So the hook gives them lessons only. They check for notes as kelve’s instructions ask. Antigravity can’t be given text as a tool runs, so kelve keeps a lesson until it next calls its model.
A newer kelve brings its hook up to date as it starts, where it’s already in, and changes nothing else.
Other agents
Agents without hooks, such as Cline, OpenCode and Amp, check for notes before each task. They ask for lessons when something fails. kelve’s tools ask them to do both. An agent without MCP reads them from the command line:
kelve noteskelve notes done <id> <version> "<what you did>"The id and version are as kelve notes gave them. A note changed since it was read isn’t marked done.
What your agent can read
Your agent reads only the notes you leave for it, in the project it’s working in, never your other notes. It treats a note as part of your work, not as orders from anyone else.