Markdown notes your coding agents can read and edit.
Specs, decisions, lessons, meeting notes, the architecture page you keep re-pasting into chat. In Morion they are plain Markdown notes in folders, in one SQLite file on your disk. You write them like any notes app; Claude Code, Codex and Cursor read and write them through MCP, with every change attributed.
Markdownone local fileread and written over MCP
The notes view
decisionreminders+Share with LLMCopy
Reminder architecture
Reminders are scheduled locally and mirrored to the server queue on sync. Decided: local first, server as backup. Push delivery stays out of scope until v2.
Open question: do queued deletes replay in order? See Queue writes while offline.
AIClaude Code· 12m ago
Implemented the local scheduler per this note. Replay order is still open; left a question on the ticket.
SavedEdited today, 14:02 · 2 versions
Folder sidebar, notes list and editor. The comment came in over MCP from Claude Code; the note was last edited from the app.
How it works
1
Write, import, or let an agent create the note
New note from the app, import from Markdown, text, Word or Apple Notes, or an agent calls the create tool from its session. Either way it is one Markdown body in one folder.
2
Agents find it the way you do
Full-text and semantic search work in the app and over MCP. A stable id, a summary and keywords let an agent filter before it reads the body.
3
Everyone writes to the same page
You edit in the app; agents append, update or comment through MCP. The activity feed shows who wrote what, in order: you, Claude Code, Codex, Mo.
4
It stays yours
One open SQLite database with Markdown bodies. Export to Markdown is one click and is never gated, during the trial or after it.
In detail
Plain Markdown, plain folders
Markdown bodies, nested folders, tags, pinned notes, revisions, trash and archive. Import from Markdown, text, Word and Apple Notes; export back to Markdown or copy the file itself.
Comments and attachments
Threads with replies on any note; files attached and readable by agents. Comments from an agent show an AI marker so you always know who said it.
Revisions with an author
Version history keeps checkpoints as you switch between notes and names the actor on each one: you, Claude Code, Codex.
Per-note AI access
Any note can be hidden from AI, or closed to agent edits and deletes, independent of its folder.
Yours, always
No Morion server holds your notes. Note content leaves your machine only when Mo or an agent sends the slice a task needs to the model you chose.
What it is not
Not a team wiki
One person’s notebook on one machine, read and written by that person’s agents. Your team’s Notion or Confluence stays where it is.
Go deeper
From CLAUDE.md to a memory that cites
What stays in the file, what moves to Morion, what changes on Monday.
A large codebase without drowning the agent
Keep the knowledge about the code in Morion so a ticket arrives with the relevant slice.
More features
Kanban tasks
A private board where agents claim tickets and you review.
MCP
Claude Code, Codex, Cursor and any client on one notebook, in parallel, locally.
Integrations
One-click setup for Claude Code, Codex, Cursor and more; the model sources Mo and Auto-code run on.
Permissions
Per-folder and per-note access for agents, tool categories, audit log.
Smart indexing
Every note summarised and grouped into topics; each ticket gets its context.
Mo Assistant
Ask what was decided and get the source note. Mo works the notebook while your agents work the code.
Auto-code
Move a ticket to Todo; Claude writes, Codex reviews, you merge with one click.