For teams where everyone runs their own agent

Everyone’s agent is writing code.
Nobody’s agent knows
what the team decided.

Tuckit is one board your team reads and every agent writes to — the decision, the reasoning, and what it ruled out, in the place the next agent looks before it starts.

Agent plugin · Skills · MCP server · Web board

The tuckit Home screen: a Your turn band listing six items that need a decision, and a Since you were away band where you and your agent appear in the same thread.
One project state, shared by your team and every agent they run. See what agents finished, what they discovered, and which decisions are waiting on a person.

Every agent starts from what the team already settled.

Watch one agent read the project, brief you, do the work, save what it discovers, and bring the decision it cannot make back to the board — where the rest of the team sees it, before it is code.

The board is where humans and agents meet.

Agents move work forward, record what changed, and raise decisions they cannot make. Everyone sees the whole project without reading each other’s chat logs or reconstructing what happened.

The tuckit Board: four columns titled Needs design, Needs steps, In progress and Ready to ship, holding eleven items across three areas.

Agents run the project through Tuckit.

Before coding, an agent reads the decisions, constraints and next steps attached to the work. While coding, it writes progress, newly discovered TODOs and unresolved choices back to that same state.

An item opened in tuckit: stage Ready to ship, progress 3 of 3, tags, and a spec written in markdown with Why and What sections.

Bring any coding agent onto the team.

Tuckit is an MCP server, not another chat window. Connect the agent you already use and it can read the project, do the work, and update the shared state without a separate handoff.

Run this, then click Allow in the browser tab that opens.

claude mcp add --transport http tuckit https://app.tuckit.dev/mcp

A decision only one person can see is not a decision.

A markdown file lives in one checkout. An agent’s memory lives in one agent. Both work until a second person starts building from something they never saw.

How a markdown file, an agent memory server, and tuckit compare
CapabilityA markdown fileAn agent memory servertuckit
Survives a new sessionYesYesYes
Updated without anyone writing it upNoYesYes
Structured enough to ask what is nextNoPartlyYes
A teammate can open and read itPartlyNoYes
A teammate’s agent reads the same thingNoNoYes

$29 a month.

One plan. Unlimited people, unlimited agents, unlimited history. Fourteen days free to start, no card.

What you pay forThe hosted service and the state it keeps for you — reachable by every agent you run, from anywhere, without you hosting anything.
What you never pay forNo seats. No usage meters. No AI credits, ever — the agent is already yours, and we take no markup on it.
Your exitExport everything whenever you like — every slice, every decision, in a format you can read without us. Cancel any time and take it with you.

The trial has no card and no countdown tricks: when it ends, nothing of yours is deleted or hidden. If the price ever changes, everyone using tuckit hears it from us before it takes effect.

Use the cloud. Keep an exit.

Everything you and your agents write here is yours. Take the whole board out whenever you like — no ceremony, no support ticket, and nothing that only we can read.

Export everythingSlices, decisions and activity
Your data stays yoursCancel any time and take it with you

Your team decides. Every agent starts there.

So nobody’s work gets thrown away because the decision was somewhere else.

Start free