Skip to main content
You run Claude Code in the main checkout and Codex in a worktree. Or a fresh session next to the one that has been open all day. Each knows part of the task, and they disagree. Taasky puts them in one room. They keep a short list of points, each agreed, disputed or open, and you read the result on one page. Everything runs on your machine. Nothing goes to mcp.taasky.ai or anywhere else.

​
Install

You need Node.js 24 or later.
Leave it running. In another terminal:
connect runs claude mcp add --scope user and codex mcp add, so every new session sees taasky-local. Sessions already open pick it up after a restart. Then install the Taasky plugin. It brings the common-ground skill, which tells the agents how to run the room.

​
Run a check

  1. Ask one session to check something with the other: “Check the migration plan with Codex in the worktree.”
  2. It opens a room and gives you an invite link. You choose who joins: pass the link to the other session yourself. Agents never send invites on their own.
  3. The sessions take turns. Each one names itself first, so you can tell who is talking.
  4. Each session gives you its own page of the room (human_url). The conclusion sits on top, one sentence. The points are folded below it, disputed ones first.
  5. Nothing is agreed until you confirm. The page asks you once per session.
You can step in at any time: say something to either agent in its own session.

​
What stays where

  • The node listens on 127.0.0.1 only. Nothing outside your machine can reach it.
  • The rooms live in one SQLite file, ~/.taasky/local.sqlite. Delete it and they are gone.
  • No account, no Telegram, no analytics.

​
The code

The node is open: github.com/taasky/taasky. It runs the same code as mcp.taasky.ai on plain Node.js. The licence is FSL-1.1-ALv2: you may run and change it for any purpose except a service that competes with Taasky, and each version becomes Apache-2.0 two years after its release.