Hand off AI game dialogue without losing the story

The problem

You hand over dialogue work, then explain the story again. Your teammate needs character voices, quest names and unfinished decisions. A chat summary can miss why you changed a line.

When you switch tools, which files did the first tool change? Your teammate needs the latest work and clear answers.

How onemind helps

A Project is a folder of work, like one client or one product. A Mind holds your team's shared rules for AI tools. Matrix is where your team sees AI tasks, questions and shared changes. Safe Check is an automatic check of a proposed rule before your team administrator approves it. You keep shared rules in Minds and chapter decisions with the task.

What it can save

Handing over game work takes time when you have to explain the task again. Say 4 people each lose about 30 minutes a week re-explaining a task when it changes hands. That is about 9 hours a month, worth about US$520 at US$60 an hour.

4 people × 30 minutes ÷ 60 × 52 ÷ 12 ≈ 9 hours a month.

This is an example estimate, not a measured result. Use your own team's numbers. You can try them in the Solutions section on the onemind homepage. You still need to read results, so some time goes to a quicker check instead of disappearing.

An example

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

1. You set up the Quest dialogue Project with the local folder holding dialogue/chapter-3.json and locales/ja/chapter-3.json. Your Team Mind says to keep line names and placeholders unchanged, and report checks actually run. Placeholders mark spaces for inserted words. Your Style and Lore Mind holds voices, quest names and questions to flag. Connect Codex and Cursor here; Claude Code can receive the same approved rules. Another game keeps its own rules.

2. Your translation reviewer creates “Update chapter 3 dialogue” in Matrix. The narrative designer owns the Mac and connected Codex tool. They open a new chat with Codex in this folder and supply the revised encounter notes. They request consistent voices, unchanged line names and placeholders, and a list of names needing review. Check that the approved rules show as Delivered first.

3. Codex finds conflicting quest names in the notes and Japanese file. It asks which to keep. The designer leaves the question in Matrix for the reviewer. Needs me is the list of things waiting for your answer; the reviewer finds the question there.

4. The owner selects Share changes before asking for review. Teammates cannot see local edits until they are shared. The reviewer finds the Project chat in Matrix and reads the shared files. They answer: keep the established Japanese name for this chapter, and leave the line names unchanged.

5. You could continue Codex on the original Mac if it is available. Instead, hand the task to Cursor for this Project, getting owner approval if requested. Cursor receives the previous result, not Codex's full chat. Include the naming decision, file paths and remaining checks. The next developer compares the shared copy with the working files before continuing.

6. The developer asks Cursor to finish the Japanese edits. A suitable reviewer reads the dialogue in context, checks names and placeholders, and reviews the check results. The owner shares later edits again. Answering a chapter question does not change the Mind. Shared rules need a separate proposal, Safe Check and approval.

How to know it worked

• The tools show the approved rules as Delivered for the Quest dialogue Project.
• The next result includes the answered question and remaining checks.
• After Tool finished, you inspect the shared files and check names, line names and placeholders.
• A reviewer checks the Japanese wording and the scene before you use it.

What onemind doesn't do yet

• Automatic learning from finished tasks is coming. You still propose shared rules yourself.
• Pull-request and check status on Matrix tasks is coming. Read the actual check results yourself.
• Shared rules do not guarantee correct dialogue or update an open chat. You decide story facts; onemind does not replace translation or game review.
• Share later edits again. Keep unreleased story details only in the rules and task files you intend to share.

Read next

Read Hand off AI tasks without losing the details and Stop repeating the same rules to every AI tool. See Matrix tasks, Matrix conversations and Matrix for the controls.

Learn more

Use Matrix tasks to follow the work and Matrix conversations to find its chat. Matrix explains how your team works together.