Agents do better work when they start with the story around the card. Mo reads your local notes, tasks, comments, and activity, then gives Claude Code, Codex, Cursor, or Auto-code exactly the context they need: related tickets, decisions, risks, open questions, and recent changes. Runs on your own LLM key.
The deal has not changed: your notes, tasks, comments, and attachments live in one local file on your own machine. Mo adds an AI layer that works on that data — no cloud workspace, no copy-pasting, no "let me re-explain my project."
You point Mo at any LLM you already use: OpenRouter, OpenAI, Anthropic, Groq, or a local Ollama. You control the bill, you control where the prompt goes. Mo has three jobs:
Your external agents through MCP keep working the same way regardless. Mo just makes them faster, more accurate, and less likely to wander.
All of these are useful because Mo sees the board, the notebook, and the activity stream together. It is not a chatbot bolted onto a doc.
"What did Codex change in the trainer project this week?" "Which Auto-code tickets are stuck?" "What risks did we record around Lichess?"
Mo answers from your notes, your activity, your kanban — without you reading 40 cards. Sessions are saved like any other chat, you can come back to them.
"Where did we decide the move-validation rule?" "Which sibling tickets touch this API?" "What did the previous agent leave in Review?"
Mo runs hybrid keyword + semantic search across your entire workspace and pulls exactly what you meant — without you fighting search syntax.
Tell Mo the rules for a folder once, in normal sentences:
"Claude can move cards from todo to review. Only I move anything to done. If a card sits in doing for more than two days, ask the owner what's blocking. Friday afternoon, draft a roll-up of what shipped this week."
Mo enforces those rules — nudges, catches drift, asks when unsure. You don't write code. You write what you want.
Mo keeps a per-folder Project Memory that updates as work happens: what's been decided, what's stuck, what just shipped, what the conventions are.
Humans get a one-page status. Agents reading the folder pick up the up-to-date story instead of starting from scratch every session.
Friday spec roll-up. Status email. "What's changed since Tuesday." Investor update from the active boards. Optimisation suggestions when Mo notices stale or duplicated content.
Mo writes the draft from real activity, you edit and ship. The cadence is yours — on a schedule or on demand.
Mo never deletes silently. Anything irreversible — delete a note, drop a folder, remove a tag — pops an approval card with the exact action and a one-line summary, and waits for your yes or no.
Edits, status moves, comments, drafts: those go through. Audit log records every action with the actor name "Mo", alongside Claude, Codex, Cursor, and you.
Mo doesn't try to be every AI in your workflow. Mo is the layer that knows your project, prepares context for the agents that do the work, and decides when to escalate to you.
When Claude Code, Codex, Cursor, or Auto-code picks up a ticket, Mo does not hand them a one-line spec. Mo bundles:
Every mo_stage inside an Auto-code workflow is Mo making a call after reading the ticket, the diff, the review, and the project context:
All three roles run on the same LLM key — OpenRouter, OpenAI, Anthropic, Groq, or local Ollama. Point at Ollama and nothing leaves your machine.
Mo isn't competing with Claude, Codex, or Cursor. They have different jobs.
A typical loop: you describe a task, Mo turns the surrounding project memory into a work packet, an agent works the card, Mo evaluates the result, and the board records what happened. You stay in the loop without staring at the loop.
Paid subscribers get every new Mo capability as it ships — at the early-adopter price.
Auto-code pauses when the workflow needs your call; Mo opens a chat with "here's the plan — go / no-go?" and your reply unblocks the next stage. After this lands, free open beta opens to everyone.
Mo asks structured "Ask Human" questions when stuck — choices, free text, deadlines. You answer in one click. Threaded into the activity panel, not buried in chat.
From any kanban card: "Open in Claude Code", "Open in Codex", "Open in Cursor", "Copy work prompt." The card becomes the dispatch point.
Mo remembers your preferences, naming conventions, and decisions across folders — not just per-project. Asks before storing anything controversial; you can edit memory anytime.
$8/mo billed annually ($96/yr), or $16/mo monthly. Bring any LLM key — OpenRouter, OpenAI, Anthropic, Groq, or local Ollama. Cancel anytime.
Single paid tier — everything we charge for, today and tomorrow, in one bundle.
Mo runs on the LLM provider you choose — OpenRouter, OpenAI, Anthropic, Groq, or a local Ollama. You bring the key, you pay your provider, you control where prompts go. Your data lives on your disk; Mo only sees the slice it needs for the current task.
Yes — point Mo at a local Ollama (or any OpenAI-compatible local endpoint). Mo treats it the same as cloud providers. Nothing leaves your machine. This is as offline as Mo gets.
Only what's relevant to the current job. If you ask Mo about your API folder, Mo reads recent activity and notes from that folder. Mo never holds your whole notebook. Folders you mark hidden from AI are invisible to Mo as well — same gates as MCP.
Not without your explicit approval. Anything irreversible pops an approval card showing the exact action; Mo waits for your yes or no. Reversible actions — edits, status moves, comments, drafts — go through directly, with audit log entries.
You control the bill — your LLM provider, your account, your budget caps. Point Mo at OpenRouter and you can cap spend at the provider level. Point at Ollama and the bill is your electricity.
No. Mo is opt-in per folder. You decide which projects Mo watches, which you keep manual, and which you hand entirely to your other AI clients via MCP. The paid tier just unlocks the option.
ChatGPT and Claude are general-purpose assistants. Mo is a specialised workspace assistant with built-in knowledge of your folders, kanban, activity, and rules. Mo is short on world knowledge and long on your project. Use Mo for "what's happening in my workspace" and use the others for "explain this concept" or "write this code."
Your notes, boards, Project Memory entries, and Auto-code workflows stay — they live in your local data file, untouched. Mo stops watching new activity, Auto-code stops running. Re-subscribe and both pick up where you left off.
Free is the whole notebook with full MCP. Paid ($8/mo billed annually) adds Mo, Auto-code, and unlimited boards — at the early-adopter rate.