Hand off AI tasks without losing the details

The problem

You pass an AI task to a teammate, then spend another conversation explaining what happened. The first tool changed some files. A question stopped the work. Now someone must find the original request and work out which choices you accepted.

A copied chat can make that harder. Old ideas sit beside the current plan. A message saying the work is ready does not show whether your teammate can see the changes. You need a clear next step, the right files, and a way to find the person who must answer.

How onemind helps

Your Project is a folder of work, like one client or one product. Its Mind holds your team's shared rules for AI tools. Matrix is where your team sees AI tasks, their requests, and their latest results. Needs me is the list of things waiting for your answer. You can find a chat, continue it, or pass its latest result to another connected tool.

An example

This is a made-up example to show how it works, not a real customer.

1. You ask a developer using Claude Code to improve a saved-reports screen. When no reports exist, it should explain what to do next. Your approved Mind already says to reuse existing screen parts, support keyboard use, and include every supported language.

2. The developer checks that the rules show as Delivered for Claude Code in this Project's folder. They start a new chat with the tool. It prepares the change, but one question remains: should the button create a report or open the report library?

3. The developer leaves the latest result and that question on the Matrix task. You find the task through search or Needs me. You read the request and answer: open the report library. That choice stays with this task unless you separately propose it as a shared rule.

4. You can continue the original chat with Claude Code on the Mac that holds it. That Mac must be available. Instead, you choose a teammate using Codex to finish the task. Codex must be connected to the same Project, and any requested tool-owner approval must come first.

5. The developer writes a clear handoff: the chosen button action, the screen part already used, the remaining languages, and the checks needed. Codex starts from that last result. It cannot open Claude Code's full chat, so missing details need to be added before work continues.

6. The first developer uses Share changes so your teammate can read the code changes. Your teammate compares that copy with the working files before asking Codex to continue. You then review the screen, every language, keyboard use, and the checks that actually ran.

How to know it worked

• The shared rules show as approved, with Delivered for the receiving tool and Project folder.
• Your teammate can read the latest decision, open questions, and shared changes.
• The next result opens the report library and keeps the agreed screen rules.
• You review the result even when the task says Tool finished.

What onemind doesn't do yet

• A handoff passes the latest result, not the full chat. Continuing the original chat needs its Mac to be available.
• Code stays on its owner's Mac until they share changes. Later edits need another share.
• Automatic learning from finished tasks is coming. Pull-request and check status on Matrix tasks are also coming.
• onemind does not replace your own review. A tool can miss a rule or leave work unchecked.

Read next

Stop repeating the same rules to every AI tool, Fix an AI mistake once, for every tool, and Keep each Project’s AI rules separate. Read Matrix tasks, Matrix conversations, and Minds and review.

Learn more

Use Matrix tasks and Matrix conversations to try one handoff. Check what your teammate can read before asking them to continue.