What problem does it solve? When an AI agent edits networked prefabs, [Sync] fields, or [Command] methods in a Unity project using the coherence SDK, the generated code under Assets/coherence/baked becomes stale and Play mode fails. Unity MCP cannot read bake-state values or dismiss coherence's modal dialogs, so agents need file-level workarounds to trigger bakes, refresh bindings, and recover from failed bakes. ## Core Features & Use Cases - Trigger and verify bakes via MCP: Invoke the coherence/Bake menu item, wait out the forced domain reload, and confirm success through file mtimes on Gathered.schema and the baked folder rather than the unreliable console. - Refresh CoherenceSync bindings after refactors: Run the project-wide Update Bindings sweep or call CoherenceSyncUtils.UpdateBindings on a single prefab to avoid the blocking save modal. - Recover from failed bakes: Delete Assets/coherence/baked via manage_asset to replicate the "Delete Baked Scripts" button that MCP cannot click, then re-bake. - Use Case: An agent renames a [Sync] field on a networked prefab. It updates bindings on the prefab, triggers coherence/Bake, waits for compilation and domain reload to settle, then verifies Coherence.Generated types resolve before entering Play mode. ## Quick Start Ask the agent to re-bake the coherence schema and verify the baked code regenerated after your latest [Sync] field changes.