DocsAgent instructions
DocsStart
Agent instructions
The recommended prompt that tells an AI agent to use Memora as its long-term memory, and where to paste it in Claude Code, Cursor, Copilot, Codex, Gemini CLI and more.
Connecting an agent to Memora gives it the tools. These instructions tell it when to use them: search before answering, save what is worth keeping, and never store secrets. Paste them once per client and every agent shares the same habits.
Recommended instructions#
For a system prompt, project rules or custom instructions. The tool names match the Memora MCP tools.
From now on, use Memora as your second brain: a shared, long-term memory that you and my other AI agents read and write through the Memora MCP server.
Recall
- At the start of a task, search_memory for the topic, project, person or error you are working on, then read_memory the most relevant notes before you answer.
- Use search_by_tag (for example #decision, #todo) and get_neighbors to follow related notes.
- If a note answers the question, say so and use it instead of guessing.
Remember
- Save what is worth keeping: decisions and their reasons, my preferences, facts about my projects and people, fixes that worked, open todos.
- Update an existing note with patch_memory (append a dated line, add a tag) or save_memory; create_memory a new note only when nothing fits.
- Keep notes short Markdown: a clear title, a few bullet points, [[wikilinks]] to related notes and #tags such as #decision #todo #howto.
- Put notes in the right folder (for example Projects/<name>, People, Decisions, Journal).
Rules
- Search before creating, and update instead of duplicating.
- Never store secrets: passwords, API keys, tokens or private keys.
- Do not save small talk or anything I ask you not to remember.
- At the end of a longer session, append a two or three line summary to the project's note.Short version#
One paragraph for clients with a small instructions field.
Use Memora (MCP server "memora") as your long-term memory. Before answering, search_memory for the topic and read_memory the relevant notes. When you learn something worth keeping (a decision, a preference, a fact about me or my projects, a fix), save it with patch_memory or create_memory as short Markdown with [[wikilinks]] and #tags. Search before creating, update instead of duplicating, and never store secrets.Where to paste it#
| Client | Where to paste |
|---|---|
| Claude Code | CLAUDE.md in the project root, or ~/.claude/CLAUDE.md for every project |
| Cursor | A project rule in .cursor/rules/ (for example .cursor/rules/memora.mdc), or User Rules in settings |
| VS Code (GitHub Copilot) | .github/copilot-instructions.md in the repository |
| Codex | AGENTS.md in the repository root, or ~/.codex/AGENTS.md for every project |
| Gemini CLI | GEMINI.md in the project root, or ~/.gemini/GEMINI.md for every project |
| Windsurf | Rules: a workspace rule in .windsurf/rules/, or global rules in settings |
| ChatGPT | Custom instructions in settings, or the instructions of a project (the short version fits the field) |
| Claude apps (web, desktop, mobile) | Project instructions, or personal preferences in settings |
| Other MCP clients | The system prompt, rules file or custom instructions field |
Rules files such as CLAUDE.md, AGENTS.md and GEMINI.md are plain Markdown: paste the text as it is, under a heading such as ## Memory. The server must be registered under the name memora for the prompt to read naturally; if you used another name, change it in the first line.
Make it yours#
- Folders. Change
Projects/<name>, People, Decisions, Journalto the folders you already use. - Read-only agents. If a key has no
writescope, keep only the Recall and Rules parts. See Tools & permissions. - Privacy. Hide folders or notes from an agent with privacy rules instead of asking it not to look. See What each key sees.
- Tags. Keep a small, stable set (
#decision,#todo,#howto) sosearch_by_tagstays useful.
Check that it works#
Ask your agent "What do you remember about this project?" It should call search_memory and read_memory, and you will see the calls live in Activity in the web UI. Tell it a decision and ask it to remember it: a new or updated note appears in the vault, committed to git.
The same text is in the web app's Documentation page and in the console under /docs. The full tool list is in the MCP tool reference.