AI assistants
Assistant connections are in controlled testing and are not yet generally available. When enabled for your Studio environment, User Settings → AI assistants shows your connection address and connected apps. You sign in with your normal Studio account and approve the requested read and edit access. No terminal, API key, configuration file, or locally installed Studio server is needed.
Connect an app
Open Assistant settings in Studio and copy the address shown there.
- Claude: open Customize → Connectors and add a custom connector with that address. Follow Studio sign-in and consent, then enable the connector for your conversation. In Team or Enterprise, an organization owner may first need to add the connector in organization settings. See Claude’s remote connector guide.
- Codex desktop: open Settings → MCP servers → Add server, choose Streamable HTTP, and enter the address. Save/restart if prompted, then choose Authenticate and complete Studio sign-in and consent. The official desktop guide uses desktop app naming that can differ by version; the exact supported versions remain under verification.
Keep the Studio editor open, connected and visible. Ask the assistant to list your open editors and connect to the tab label shown in Studio. Ready for assistant means the tab is available; Assistant connected means an app has attached. Your app may also ask you to approve tool use.
Work with a map
The initial supported workflow reads the current view and locations, shows a map image, renames an existing location, checks the result, and undoes that assistant change when it is still safe. For example: “In the tab labeled Assistant acceptance, rename Information to Customer Services.” The assistant should read the location first and use its current observation when making the change. Linked map labels follow the same update as a normal Studio name edit.
Changes apply to your shared draft immediately. Collaborators see them through normal collaboration. Publishing remains the existing deliberate Publish workflow. An applied tool result confirms the editor changed its draft; normal synchronization still needs to save it.
Choose the right tab
Each open editor has its own venue name · Tab identifier. With multiple tabs, choose one explicitly. Closing a tab does not move the assistant to another tab automatically. Bring the chosen tab to the foreground and keep it connected before sending commands; a background tab pauses execution.
Two tabs showing the same map still share the same draft. A change made in one appears in the other. The attached tab determines the current view, selection, floor and undo history. If that tab reloads, attach to its new tab identifier. Earlier assistant undo history is not reconstructed after reload.
Pause, undo and disconnect
Pause stops new assistant work in that tab. Resume makes it available again. Studio also blocks assistant edits while a dialog, unfinished tool interaction or incompatible local edit is active. Finish or cancel that interaction, then ask the assistant to read the latest state before continuing.
Ask to undo the specific assistant operation. If a manual or collaborator edit has changed its targets, Studio refuses an incompatible undo and directs you to normal history. It does not overwrite later work.
If a request times out or its outcome is unknown, ask the assistant to check its operation receipt and read the map. Do not repeat the edit until its outcome is understood. An expired observation requires a new read. A disconnected or reloaded tab needs explicit attachment again.
Disconnect in the editor closes that tab’s bridge. To remove an app’s account access, open Assistant settings and disconnect the app there. If acknowledgment is lost, the page preserves the connection entry and explains that its status is uncertain; check it before retrying manually.