What live sync doesCopy Anchor Link

When you are signed in, every modeler you have open on a draft is connected to the others, and to your AI agent:

• A change you make in one browser shows at once in your other browsers with the same draft open, such as your laptop and your phone.
• A change your agent makes over MCP shows at once in every browser that has the draft open, with a notice that your agent changed it.
• A change you make in the browser reaches your agent's copy too, so its next command builds on your edit.

Live sync is only between your own browsers and your own agent. Nobody else sees your draft until you publish it.

The status lineCopy Anchor Link

Next to the save status, the modeler shows:

• live, or live · 2 of your devices when the draft is open elsewhere too;
• · agent while your agent has changed something in the last two minutes;
• updated from another device or updated from your agent for a few seconds after a change arrives;
• connecting…, or offline: changes stay here until back.

Each change that arrives from elsewhere is one step you can Undo.

SavingCopy Anchor Link

Measurements still save to your account as before. When your agent changes the draft, one of your open browsers saves the change to the draft, as it saves your own edits. With no browser open, the agent's changes wait in its working copy until it saves them, and a browser opened later shows them. See Agent tools.

PhotosCopy Anchor Link

Photos are processed on your devices and kept in the browser you added them in. To follow you to another signed-in browser, a photo passes through Rack Maker's server in transit only, and is never stored. Both browsers must be open at the same time; otherwise it doesn't arrive, and the face says so. See Tracing photos and drawings.

Your agent never sends photos, so its traced faces carry numbers only.

ConflictsCopy Anchor Link

Each change carries the whole draft, and the last change to arrive wins:

• Between browsers: if two of your browsers change the draft at the same moment, the one that reached the server last is what every browser ends up with. Changes are whole drafts, never mixed.
• Your agent and the browser: if you change the draft while one of your agent's commands is running, the command refuses ("run the command again") rather than write over your edit. Your agent runs it again on the newer draft.
• Your agent saving: if the draft changed in the browser since the agent last looked, its save refuses unless it chooses to overwrite. It can also drop its own copy and take the browser's.

OfflineCopy Anchor Link

Without a connection, the modeler works as before: your changes stay in this browser until it is back, and photos stay where they are. When the connection is back, what changed here goes out, or the draft as saved elsewhere comes in.

When the draft is publishedCopy Anchor Link

If the draft is published or submitted for review from elsewhere (by your agent, or another browser), each open modeler says so: "This draft was published. What you change next goes into a new revision." It stops saving to that revision, and your next change starts a new one. See Publishing.