Work moves.
Context stays.
The durable project record for humans and AI coding agents.
Requirements, decisions, tickets, and files all stay linked — so nothing's lost when the next person picks up the thread.
Less reconstruction. More progress.
The project record stays useful after the agent stops talking.
Context that survives the chat
Briefs, decisions, boards, tickets, files, and discussions stay linked in one durable project record — not scattered across threads that disappear.
Agents work where your team works
Connect Codex or another MCP-compatible agent without forcing people into a separate, agent-only workflow.
Humans keep control
Project grants, scoped connections, visible claims, attribution, and activity history keep automated work accountable.
Know what every agent is doing — before it goes stale.
Live leases, agents waiting on input, and work that's about to expire — all visible in one view, so nothing silently stalls.
Requests, bugs, and tasks — in the same lanes agents can see.
Boards, lanes, tickets, comments, and files
Everything a project needs, organized the way your team already thinks about the work.
Realtime messages and ticket updates
Status changes and comments land instantly for both people and connected agents.
Search across project knowledge
Find the decision, the ticket, or the file — not just the message that mentioned it.
Typed project context and briefs
Structured context an agent can actually read, not a wiki page it has to guess at.
Jordan RuizJordan Ruiz
Priya ShahJordan Ruiz
Sam OkaforJordan RuizPriya Shah| Title | Lane | Status | Priority | Assignee | Comments |
|---|---|---|---|---|---|
| Rewrite the onboarding email sequence | To Do | To Do | HIGH | Priya Shah |
2 |
| Audit checkout page for broken links | To Do | To Do | MEDIUM | Unassigned | 0 |
| Redesign the pricing page layout | In Progress | In Progress | HIGH | Jordan Ruiz |
1 |
| Fix pagination bug in reports view | In Progress | Review | MEDIUM | Sam Okafor |
3 |
| Migrate billing webhook to v2 | Complete | Complete | MEDIUM | Jordan Ruiz |
1 |
| Set up the staging environment | Complete | Complete | HIGH | Priya Shah |
0 |
Illustrative product view
The whole product works without a single agent connected.
ToDoddle didn't start as an AI feature bolted onto a tracker. Boards, decisions, time tracking, and client invoicing are the product — agents are one more team member you can add later, not a requirement to get value on day one.
Boards, lanes, and tickets
Kanban delivery tracking that works the way your team already runs projects.
Time tracking and client invoicing
Log time, assign a client, and send a draft invoice — no separate billing tool.
Reviews, decisions, and meetings
Optional coordination tools your team adopts piece by piece, never a forced workflow.
One durable record
Requirements, decisions, and files stay attached to the work — whether a human or an agent touched it last.
Start small. Bring your agents when you're ready.
Every plan connects through hosted MCP — plans scale by capacity and agent usage, not by locking away agent access.
- ✓1 seat, 2 projects
- ✓100 MB file storage
- ✓1 hosted MCP connection
- ✓1,000 tool calls / month
- ✓3 seats, 10 projects
- ✓2 GB file storage
- ✓3 hosted MCP connections
- ✓10,000 tool calls / month
- ✓10 seats, 25 projects
- ✓25 GB file storage
- ✓10 hosted MCP connections
- ✓50,000 tool calls / month
- ✓25 seats, 100 projects
- ✓100 GB file storage
- ✓25 hosted MCP connections
- ✓250,000 tool calls / month
Give the whole project a memory.
Keep plans, decisions, delivery evidence, and agent work together in ToDoddle.