AI-friendly Markdown
Make notes usable by Claude, Codex, and Cursor.
Claude, Codex, and Cursor do not need Raven to become a chat box. They need notes they can read, cite, and update without breaking things. Plain Markdown files give them something to read. Raven Companion gives them a safer path for writes.
Last updated by Thomas Sivilay.
Notes that file-based tools can read.
Claude, Codex, Cursor, and local MCP clients work better when notes are plain text on disk. Raven includes Companion, a local CLI/MCP helper that lets agents use Raven-aware tools instead of writing directly to the file system.
Checklist for the notes.
Three patterns that work.
Start with the folder.
A folder of Markdown files is the foundation. Finder, git, ripgrep, and your editor can all reach the same files. Nothing needs to be installed or configured for reads.
Use Companion for Raven-aware edits.
Raven includes Companion, a bundled CLI/MCP helper. It can search notes, create or append content, update tasks, and edit with hash-guarded writes when you grant edit access.
Keep destructive tools out.
Companion does not expose delete, move, archive, task deletion, direct retagging, or structural table edits. If an assistant needs those, it should ask you.
A clear note beats a chat transcript.
A project brief with the decision and supporting links gives Claude fewer guesses to make than a loose chat history.
Raven keeps the notes on disk.
Raven stores every note as a Markdown file on disk. Companion sits on top and handles Raven-aware reads and writes. Read access and write access are separate permissions you control in Raven Settings.
A vault local agents can read without exports.
Raven gives you a native Mac, iPhone, and iPad notes app around a folder of Markdown files, plus Companion tools for local AI clients.
$14 lifetime through July 31. Apple handles refunds through Report a Problem.