Hand work between ChatGPT, Claude and Cursor without losing the thread

29 October 2026

You plan in one AI and build in another, and neither knows what the other did. How one TaskFlow list lets each assistant pick up where the last one stopped.

Many of us now use more than one AI assistant. ChatGPT on the phone for thinking out loud, Claude for writing, Cursor or Claude Code for the code. Each is good at its part. None of them knows what the others did.

So the hand-over is you. You copy a plan out of one chat, paste it into another, explain again what was decided, and hope nothing important stayed behind. The context lives in your clipboard, and that is where it gets lost.

One list they all read and write

TaskFlow runs a remote MCP server at https://taskflow.denegra.ai/mcp. MCP is the open standard assistants use to connect to tools they can act on. Connect each assistant you use to that same address, and they all work on the same task list — yours, the one you open in the app.

• ChatGPT: Plugins, then Add, then Custom MCP server. This works on ChatGPT’s free plan too.
• claude.ai: Settings, then Connectors, then Add custom connector.
• Cursor: add the same URL as a remote MCP server in Cursor’s MCP settings.
• Claude Code: the one line below.

claude mcp add --transport http taskflow https://taskflow.denegra.ai/mcp

Each time, a TaskFlow consent page opens. You sign in if you need to, and approve. On that page you also choose what this AI may see: all your flows, or only some. An AI limited to some flows cannot read your inbox or your meeting notes, and cannot create new flows — useful when a coding assistant only needs the project, not your personal list.

Each AI works under its own name

A connected AI does not act as you. It works as itself — "ChatGPT", "Claude", "Cursor (local)", "Claude Code (local)" — and every change it makes shows in the task’s history with an AGENT badge and its name.

How a hand-over works

There are twenty-four tools. Most are the ordinary ones: list flows and tasks, search, read, create, update and complete a task, create a flow, read the inbox, get the daily briefing; others read and file meeting notes and read and attach files. Six exist for working together:

• Resume is where an AI starts. It returns what that AI owns or is working on, with the note it left, and what people or other AIs changed since its last action.
• Claim and release: an AI claims a task before working on it, so another AI waits instead of starting on it too. A claim expires after 15 minutes unless renewed, up to 120; an "own" claim lasts across chats until it is released.
• Save a working note: where it stopped, what is decided, what comes next. Notes are versioned, so two writers cannot silently overwrite each other.
• Comment: leave a comment on the task.
• Hand off: pass the task to another connected AI by name, or to a person on the flow, who is notified — with a note on what is left.

An example

Say you start planning a launch in ChatGPT on your phone, on the way home. You talk it through and it puts the tasks into your Launch flow. Dates like "tomorrow" or "+3d" are resolved by TaskFlow in your own timezone, not guessed by the model.

The next morning you open Claude Code at your desk and ask it to pick up the launch. It calls resume, sees the new tasks and what changed overnight, and claims "API docs". It writes the docs, saves a working note on what is done and what is still open, and hands the review back to you.

You did not copy anything between the two. The task’s history says who did what: ChatGPT created it, Claude Code claimed it, left a note and handed it to you.

Keeping an eye on them

The Connected AIs screen — under Profile or Assistant, on the web and in the iPhone and Android app — lists every AI you have connected: when it was last active, when it was connected, which flows it sees, and its recent actions ("completed…", "handed on…", "commented on…"). "Change" changes which flows it sees. "Disconnect" stops it at once: its next request is refused, and it lets go of the tasks it was working on.

And nothing gets deleted. No connected AI can delete anything; finishing a task moves it to done, which you can undo.

Going the other way

Sometimes you just want one task in a chat. On any task, "Copy for AI" on the web or "Send to an AI" on the phone gives a compact, prompt-ready text: title, flow, column, due date as YYYY-MM-DD, priority, labels, description and subtasks. The assignee is left out on purpose. For a whole flow, the Export window has a "For an AI" format.

The work and its context live in one place you control, and whichever assistant you open next starts from there, not from zero.