A kanban board where coding agents claim tickets and you approve at Review.
Any note can become a task; a task is a note with a status. Put the project on the board and it stops living in chat: an agent claims a ticket, comments progress on it, moves it to Review, and the next session, the reviewer and Mo can all read what happened.
private boardagents claimyou review
The board
Kanban12 cards
Auto-code on
ListKanban
Todo2
Ready to start
Replay the queue on reconnect
Depends on: Queue writes while offline.
syncauto-code
Offline banner and retry
auto-code
Re-opened1
Came back after work started
Conflict marker on divergent edits
Codex: marker lost on second edit. Resolution: resume session.
reopened 2x4
Doing2
In progress
Queue writes while offline
Outbox table; writes enqueue when the socket is closed.
auto-running3
Reminder time zones
awaiting your reply1
Review1
Awaiting review
Local reminder scheduler
Claude Code moved it here. Tests green, 11 cases.
6
Done6
Complete
Reminder schema
auto-done · merged
Outbox migration
auto-done · merged
Column colour is the status. The badges on cards are Auto-code states: auto-running, awaiting your reply, reopened, auto-done, merged. Auto-code is optional; the board works without it.
How it works
1
Plan lands as tickets
Write the epic as a note, ask your agent to split it, or add cards by hand. Dependencies stay in plain words; Mo relates tickets through topics.
2
An agent claims the next one
"Take the next task" claims a ticket atomically and moves it to Doing, so two agents never take the same card. Progress goes on the ticket as comments, not in the chat.
3
Review is your column
Agents stop at Review. You approve, or send the ticket to Re-opened with a reason and a resolution: resume the session, ask a human, or start fresh.
4
Questions wait on the board
When an agent needs a decision it leaves a durable question on the ticket. You answer when you see it; the answer stays on the ticket, where the next agent reads it.
In detail
Statuses agents understand
backlog · todo · doing · review · reopened · done, plus Note for reference cards. Drag cards, or let an agent move them. Every move is logged with who did it.
Re-opened carries the reason
A ticket you sent back from Review, or an Auto-code run that failed, says why and what to do next. The next pickup reads it first.
Auto-code on the card
With Auto-code on for the folder, moving a card to Todo starts a run; the card shows its state and links to the transcript and the diff.
List or board
The same folder as a list of notes or as a board. Switch per folder.
Yours and your agents' only
For a solo founder it is the only task board you need. In a team it sits below Jira, Linear or ClickUp, holds the pieces you and your agents actually work on this week, and never conflicts with the team tracker.
What it is not
Not a team tracker
Built for one person and their agents. No assignees across people, no sprints, no swimlanes, no time tracking. Your team's Jira stays your team's Jira.
Go deeper
Running an epic
Split it, board it, let agents claim it, and watch the re-opens.
Three ways to orchestrate
Claude plans and its subagents work the board; Claude plans and Auto-code runs; or both.
More features
Notes and documents
Markdown notes on your disk that your agents read and write.
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.