tada

An opinionated harness for building software with any agent.

  • Kanban project planning
  • Powerful documentation heuristics
  • Test analytics and insights
  • Agent-agnostic collaboration via MCP
  1. Planned

    You decide what's next

    Write a Story, break it into Tasks, and move it to In Progress. Moving the card is the hand-off.

  2. In Progress

    The agent works from the board

    It reads the board through MCP, picks up the Story that is In Progress, and moves each Task along as the work lands. Your open tab updates as it goes.

  3. Done

    The board shows what shipped

    The Story moves to Done, and the agent writes what actually shipped into its description. After 30 days in Done it is filed to the Changelog.

The board

One board, the same rules for both of you.

A board inside every card

A Story is one unit of work. Open it and you get another kanban board, with the same four columns, whose cards are that Story's Tasks. An agent moves Tasks the way you drag them.

Two editors, no lost edits

Every agent write checks whether the Story changed since the agent read it. If you both changed the same part, the write is refused and the refusal shows both versions.

Live, with no refresh

Whenever anything on a board is written, by you or by the agent, every open tab updates. You watch the work move across the board while it happens.

You can tell who changed what

Anything an agent creates, edits, or merges gets the 🤖 ai-generated tag. A Story's Activity Log lists its recent writes, newest first, each marked with how it arrived.

Private by default

Your board is private until you choose to make it public. Nobody else can open it or tell that it exists, and only you can change it, whether from the browser or through your agent.

What needs a look

Collapse the lanes and the board's dashboard takes their place. Needs attention names the Stories that are overdue, due in the next week, waiting on a Story that isn't done, or marked Done with Tasks still open.

What shipped, kept

The Changelog shows a year of shipped Stories, one square per day. Stories carry due dates, tags, and Markdown descriptions, set on the board or through MCP.

The method

The plan is the contract.

The board and MCP let an agent edit a plan. The skills are what make tada a way of working: two loops, each one feeding the board.

The build loop

  1. The agent reads the live board.
  2. It picks up the Story marked In Progress.
  3. It does the work and opens a pull request.
  4. It moves the ticket only when the work actually ships.

The board drives the work, and the work updates the board.

The audit → board loop

  1. A sweep of the whole codebase emits findings.
  2. Each finding has a durable id, tracked across runs.
  3. You file the ones worth doing. Re-running never re-files them.
  4. They feed straight into the build loop.

What the audit finds becomes Stories on the board.

Set up

Open your board, then give your agent the same one.

Step 1

Open your board

Boards are hosted, so there is nothing to install to use one. Sign in and you land on your board.

Open your board

Step 2

Register the MCP server

Add it to the project's .mcp.json. The agent working in that project gets a set of plan tools for that board.

{
  "mcpServers": {
    "tada": {
      "command": "npx",
      "args": [
        "tsx", "/path/to/tada/app/mcp/server.ts",
        "--project", "myproject",
        "--owner-email", "you@example.com",
        "--url", "https://app.tada-ai.app"
      ]
    }
  }
}

Boards are created for you today, not self-serve. There is no “new board” button yet, and the ready-to-paste config comes with your board. Read the quick start

Questions

Before you start.

The docs cover the rest.

Can I create a board myself?

Not yet. Boards are created for you today, and there is no “new board” button. Once you have one, everything on this page works.

Which agents does it work with?

tada ships a stdio MCP server, so it is for a coding agent that can load one. The quick start shows the setup for Claude Code, which reads .mcp.json from the project root.

What happens when the agent and I edit the same Story?

If you changed different parts, the agent's write goes through, and its reply notes that someone else was editing. If you both changed the same part, the agent's write is refused and the refusal shows both versions. Neither edit is silently lost.

Who can see my board?

A board is private until you make it public. Nobody else can open a private board, or tell that it exists. Anyone can read a public board, signed in or not. The privacy page has the detail.

What does it cost?

tada takes no payments. It has no ads and sells no data.

Does this site track me?

No. This site runs no analytics and no scripts. The app counts page views with Vercel Web Analytics, which uses no cookies.

Put the plan where you can both see it.

Open your board, then give your agent the same one.