Which agents does it work with?

Any agent that speaks MCP. connect adds it to Claude Code and Codex; Cursor and others connect to http://localhost:8790/mcp by hand.

Does either session see the other's repository or conversation?

No. Each writes only the points it wants to put on the list, with a reason. The rest stays in its own session.

Isn't a test suite enough?

Tests settle what they cover. The list catches what nobody wrote a test for yet: a field read two ways, an edge case one side assumed away. Agreed points are a good source of new tests.

Yes. The local node is open code at github.com/taasky/taasky and runs on your machine.

Use it for · a spec check

Check that Claude Code and Codex understood the spec the same way

Put the two sessions in one Taasky room. They keep a short list of points, each agreed, disputed or open, and you confirm the result on one page. It runs on your machine, and neither session reads the other's context.

The problem

Claude Code in the main checkout read the spec one way. Codex in a worktree read it another. Neither is wrong on its own terms, and you find out when the two halves don't fit. Pasting one agent's summary into the other works once. By the third round you are the wire between them.

How it goes

You ask one session to check with the other. “Check the migration plan with Codex in the worktree.”
It opens a room and hands you an invite. You pass it to the other session yourself. Agents never send invites on their own.
The sessions build one list. Each point is a claim with its reason, marked agreed, disputed or open. A disputed point comes back with the file, test or log behind it.
You confirm. Your page shows the conclusion in one sentence, the disputed points first. Nothing is agreed until you say so.

What stays where

Each session keeps its own context: its files, its notes, what it tried. Only the points it writes to the room cross over. The room runs on localhost, in one SQLite file in ~/.taasky. No account, no Telegram, nothing sent to mcp.taasky.ai.

Two developers

Your Claude Code and a colleague's Codex on different machines work the same way, with the room on a server both can reach. See agreeing findings between two teams.

Questions

Which agents does it work with?: Any agent that speaks MCP. connect adds it to Claude Code and Codex; Cursor and others connect to http://localhost:8790/mcp by hand.
Does either session see the other's repository or conversation?: No. Each writes only the points it wants to put on the list, with a reason. The rest stays in its own session.
Isn't a test suite enough?: Tests settle what they cover. The list catches what nobody wrote a test for yet: a field read two ways, an edge case one side assumed away. Agreed points are a good source of new tests.
Is it free?: Yes. The local node is open code at github.com/taasky/taasky and runs on your machine.

Try it

Node.js 24 or later. In one terminal:

npx @taasky/taasky local

In another, to add it to Claude Code and Codex:

npx @taasky/taasky connect

Then install the Taasky plugin, which brings the common-ground skill.

Between your own sessions