Mo indexes the notes you allow and gives each agent only what its task needs.
Mo, the agent inside Morion, reads the notes you allow and builds what an agent needs to find the right slice of a project fast: a summary and keywords per note, a catalog per folder, topic documents per project. When an agent picks up a ticket, Mo hands it a work packet with the decisions, lessons and specs that matter. It indexes notes, not source code.
projectstopicswork packets
What Mo keeps for each note and project
Left: what Mo computed for one note, all editable. Right: the project's catalog and topics. Your edits to an overview stay; Mo only refreshes its own section.
How it works
1
Choose the folders Mo indexes
AI access in each folder’s settings decides whether Mo indexes it, and folders and notes hidden from AI are always skipped. Your journal stays your journal. When indexing runs on a provider key, a per-workspace cap limits what it may spend.
2
Mo reads and summarises
Each note gets a summary and keywords; each folder a catalog paragraph; each project a directory and topic documents with an overview you can edit by hand.
3
A ticket arrives with its context
An agent that picks up a ticket calls one tool and gets the ticket, the comments that matter, the project brief, related decisions, lessons, specs, rules and topics. It can claim the ticket in the same call.
4
Ask Mo uses the same index
Questions run over the same evidence, so an answer cites the notes Mo indexed, with a status on every claim.
In detail
Summary and keywords per note
Editable. Agents filter on them before reading the body; the Meta Data panel shows who computed what and how confident Mo is.
Projects and catalogs
Every folder belongs to a project. Moving a folder between projects re-indexes it. The catalog is one paragraph an agent reads before opening anything.
Topics that maintain themselves
Topic documents are created, merged and retired as the notebook changes. Human text outside Mo's section is never touched.
Where Mo looks first
Each folder has a Role in project: general, lessons, architecture, specs or rules. In the project settings you can also tell Mo which folders or notes to check first for which kind of work; work packets and answers follow it.
Runs on the login you already have
Indexing, topics and retrieval run on your Claude Code login, or on your Codex login on macOS, with no API key. On Pro they can also run on OpenRouter or a local Ollama; pick the models in Settings, Smart Indexing, Indexing Models.
What it is not
Not a code indexer
Morion indexes the knowledge about your codebase: architecture notes, decisions, lessons, specs. The code stays in the repo, where the agent reads it as usual.
Go deeper
A large codebase without drowning the agent
Keep the knowledge about the code in Morion so a ticket arrives with the relevant slice.
Mo Assistant
Ask over the same index and get cited answers.
More features
Notes and documents
Markdown notes on your disk that your agents read and write.
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.
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.