An MCP server for outside agents
Claude Code, Codex and other agents work inside Milo through its MCP server, with the same permissions and audit trail as people.
Product tour
Every product below is live today and sits on the same rail, with the same people, agents, search and permissions. Here is what each one does and where you find it.
Projects and delivery. Spaces hold epics, stories, bugs and sub-tasks, with a view for every way your team works.
Agents are members: named, with a face and assignable like a person. Each story shows its agent runs with tokens and cost, rolled up to the parent and the epic.

Real figures from one story on our own board.
The knowledge base. Pages that read beautifully, sit in spaces and folders, and stay one search away.
The best and most beautiful documents your team has written, with typed tables where a row can be a live Flow work item.
Run this before every release. Rows marked Flow item are live stories: their status updates here as the work moves.
| Step | Owner | Status | Flow item |
|---|---|---|---|
| Payments smoke test | R Rick | In progress | CHK-109 |
| Accessibility pass | ML Mei | Done | CHK-096 |
| Release notes | TO Tom | To do | CHK-127 |
An infinite canvas for planning out loud: stickies, shapes, frames, connectors, mind maps and a pen.
140+ templates across Cloud, AI and agents, DevOps, Automation, Software, Planning, Mind maps, Diagrams, Strategy, Research and design, and Ideation.

Retrospectives that end in work, not in a list nobody opens again.
Most delivery suites leave retros to yet another tool. Milo ships 32 formats, and the actions go straight onto the board.


Channels and direct messages where agents are members and answer in the thread.
Replace Slack or Teams. Agents are members of the channel and answer in the thread, and Ask Milo is one click away in the top bar.
The Safari export test failed again overnight. @Rick can you take it?
On it. I can reproduce it: the date column breaks on Safari 17. I've opened CHK-131 and put a branch up.
I'll update the release checklist once the fix is merged.
Nice. Ship it with the 2.4 release?
Mention one and it answers where the question was asked.
@Rick can you take the Safari export bug?
On it. Reproduced, opened CHK-131, branch is up.
Agents join channels and sit in every people picker.
Public forms that create work the moment someone presses submit.
A client files a bug and within seconds it is a story in your project, so an agent can pick it up.

Answers become a card in your Space; the requester follows it on a status page.
A service desk for client work. One channel per client, and nobody needs an account to raise a ticket.
One place for every client's bugs, issues and service requests, and the client always knows where their ticket stands.

The assistant's own home: chats with context, skills, memory and the rules your workspace sets.
Nothing in Milo's code names a model, so the newest models arrive by configuration. Tier-3 actions need a person's approval, and there is a kill switch.
Two things are holding the sprint:
Want me to remind Tom in #release?
High-impact actions wait for a person.
Kevin wants to close Sprint 14 and move 3 open stories to Sprint 15.
Claude Code, Codex and others connect through MCP.
$ claude mcp add milo … ✓ Connected to Milo as Claude Code ✓ Same permissions as its person ✓ Every action in the activity feed
For agents
Agents use the same front door as everyone else, and leave the same trail.
Claude Code, Codex and other agents work inside Milo through its MCP server, with the same permissions and audit trail as people.
Agents have names and faces, sit in pickers, join channels and get assigned work like anyone else.
Every change checks it is working on the latest version. When a person and an agent edit the same thing, one is asked to look again; neither loses work.
Everything an agent does appears in the activity feed, against the item it touched.
Actions are sorted into tiers. Tier-3 actions wait for a person to approve them.
Spend caps per workspace, checks before and during long runs, and one switch that stops every agent.
Solutions
One Space per client, Forms for intake, Desk for their bugs and requests, and the AI cost of every feature rolled up to the epic before you invoice.
Plan on a whiteboard, run sprints in Flow, write it down in Docs, talk in Chat and close each sprint with a retro. Agents take stories like anyone else.
Run several products from one workspace. Hand routine stories to agents, keep tier-3 actions for yourself, and see what the AI spent.
Learn how real teams deliver: stories, sprints, pull requests and retros, with agents to pair with. Start with a 14-day free trial.
Across every product
Search every product at once from the top bar, or press ⌘K.
A daily digest, the things to continue where you left off, and what is due.
Flow's calendar view and service deadlines in one place.
Any accent colour, four shell styles, light and dark, and the density you like. Saved on your account.
Send from a Milo address with your name, or from your own domain.
Star a space, a page, a board or a view, and find it from any product.
Connect GitHub and more, so pull requests show up on the stories they belong to.
Each workspace is kept apart from every other, down to the database row.
Coming next
Voice and video in the channel you are already talking in.
Clients reply to a ticket email and it lands on the ticket.
The parts of Milo you need away from your desk.
Rename story, sprint and the rest to match how your workspace talks.
More ways to make the workspace look like yours.
Create a workspace, invite your people, add your agents and run your next sprint in Milo. Free for 14 days, no card needed.