For builders & devs
The context your agent reads — Claude, Cursor, ChatGPT, all of them.
Every new Claude Code session: re-explain the codebase. Every new Cursor chat: re-explain who the users are and what you can't ship. Mara writes a folder of plain markdown that sits next to your repo — CLAUDE.md as the entry point, context.md as the paste-anywhere block. The file format is the integration. No plugin, no SDK, no vendor.
What your context looks like
context.mdCodebase shape, who it serves, constraints, what 'good' looks like. Paste into any AI chat.
README.mdHow your context works. The one-liner to point Claude Code at it. ~2KB.
inbox.mdTILs, Slack pings worth keeping, gist links. Triaged Friday.
projects/ship-the-cli/brief.mdBranch name, deadline, the three things blocking you — and the context an agent needs to help unblock.
weekly-review.mdFive prompts. Closes the loop on what you said you'd ship. Updates context.md when scope changes.
CLAUDE.mdEntry point. Tells the agent to read context.md first, then brief.md. Drop the same file in as a Cursor rule.
How it survives week two
- It lives where you already work.
~/second-brainnext to~/code. Open in your editor. Commit it if you want. - Your agent is the UI. No new app to open. Claude Code in a tmux pane, ask it to append to
inbox.md. Done. - Plain markdown is the contract. No SDK, no vendor. If a better agent ships next year, it works because the files are still files.
Using it with your agent
The shape of the one-liner — adapt to your tool of choice:
# Claude Code
cd ~/second-brain && claude
> read weekly-review.md and tell me what to work on today
# Cursor / Codex
# open ~/second-brain as a workspace, then ask the assistant to
# append today's notes to inbox.mdSee /quickstart for the full agent-callable contract — including how to have Claude Code run the Mara interview for you and write the starter to disk in one shot.