Fusion - the Fusion 360 Bridge

{
 "not_installed": "Fusion 360 is NOT installed. OFFER to install it for the user, then call fusion_install_fusion (no shell approval needed) - it streams the free trial and this verb reports installing:true until done.",
 "installing": "Fusion install is STREAMING (10-30 min) - keep polling fusion_readiness until installed:true.",
 "installed_not_running": "Fusion is INSTALLED but not running - call fusion_start (blocks until the add-in is ready), then retry.",
 "addin_silent": "Fusion is RUNNING but its add-in is NOT responding yet - NOT ready to drive. Either it is still finishing launch / signing in (poll fusion_readiness a few more times), or the add-in did not load (fusion_stop then fusion_start to re-deploy + re-load it). Do NOT fire modeling/export verbs until ready:true.",
 "addin_busy": "Fusion is RUNNING and its add-in is LOADED but busy: a long command or a heavy Fusion operation holds its main thread (addinBusy says which and for how long). It is working, not missing: poll fusion_readiness again and drive when ready is true. Do NOT restart Fusion for this; a restart closes every open document and loses the work in flight.",
 "needs_signin": "Fusion is RUNNING but stuck at the first-run Autodesk SIGN-IN (main UI blocked, add-in cannot serve) - NOT ready. FULL PLAYBOOK: the `fusion-autodesk-signin` skill. Proven sequence + the pitfalls that cost hours on a fresh Hyper-V VM (John 2026-07-14): (1) BLANK white webview on first launch? fusion_stop then fusion_start - the sign-in renders 'Welcome to Fusion' + a 'Sign In' button only after a clean relaunch. (2) ASK the user FIRST (AskUserQuestion): do they have a warm Google/Apple/Microsoft session for the account LINKED to their Autodesk login? Offer to drive it. A truly fresh box has NO warm browser session, so 'Continue with Google' still hits a password wall. (3) Click Fusion 'Sign In' -> it opens the DEFAULT browser (Edge) to the OAuth. Edge windows DO exist even if PowerShell EnumWindows looks empty - that is CLIXML progress noise; set $ProgressPreference='SilentlyContinue', and just desktop_screenshot_window the Edge hwnd (PrintWindow works backgrounded). (4) In the browser: 'Continue with Google' -> type the user's EMAIL (not secret) -> if it asks for a PASSWORD/2FA, STOP and fusion_notify_owner {title, body} to toast their MAIN computer so THEY type it; NEVER enter password/2FA yourself. (5) Handoff back to Fusion is via the 'Autodesk Identity Manager' protocol - Edge shows a 'This site is trying to open...' overlay: tick 'Always allow' + click 'Open'. (6) SPEED MATTERS: the sign-in code EXPIRES in ~2 min; on a high-latency VM slow screenshot/click round-trips let it expire ('Sign-in request expired') and you loop. Minimize steps; if it expires, click Fusion 'Sign In' again for a FRESH code (the browser session stays warm). Then poll until ready:true. FIRST-TIME DEMO? Run fusion_demo instead - it drives this sign-in through the user's NATIVE browser (already signed into Autodesk) and then gives them a real guided tour (project -> schematic -> 2D board -> 3D board).",
 "licensing": "Fusion is blocked by a SEAT/LICENSING dialog ('Active Sessions Exceeded' / 'Suspend Remote Session') - detected DETERMINISTICALLY as an OWNED POPUP of the main Fusion window (its title is just 'Fusion360' and it can be as short as 262px, so it is found by owner+parent-screenshot, NOT a size guess). This verb JUST TRIED to auto-resolve it in the BACKGROUND (UIA 'Continue', Suspend pre-selected so it reclaims the seat) but it is still up - it may be mid-render (the first UIA Invoke no-ops). Just POLL fusion_readiness again in a few seconds; it keeps auto-resolving. Never coordinate-click or ask the user, and never kill/relaunch (the server keeps the seat).",
 "updating": "Fusion is applying an AUTO-UPDATE (multiple webdeploy builds present) and RESTARTS ITSELF every ~30-60s - this is NOT a crash or a bridge failure. Poll fusion_readiness; it stabilizes to ready:true once the update finishes (can take 10-30 min). Meanwhile, wrap modeling/export verbs in a short retry/catch-loop to ride the up-windows rather than treating an intermittent 'not running' as fatal.",
 "ready_signed": "READY - drive Fusion (fusion_open_lbr / build_library_3d / etc.). APS cloud search is signed in too, so use fusion_aps_search for cloud lookups (about 20-30 s across the whole hub, a few seconds with projectId). Autodesk's MCP server is ",
 "ready_configured": "READY to drive Fusion, but APS CLOUD SEARCH IS NOT SIGNED IN - cloud file search will be slow/blocked. DO IT NOW, do not make the user log in a second time: call fusion_aps_signin RIGHT AFTER a Fusion sign-in, while the browser profile still has a warm Autodesk SSO session - it consents silently (no password, no 2FA). Then fusion_aps_search works. Autodesk's MCP server is ",
 "ready_unconfigured": "READY to drive Fusion. APS cloud search is NOT SET UP (no client ID) - cloud search is the slow path without it. Offer to set it up: your org's app ID is usually already on the wiki (`adom-wiki settings get <org> autodesk-aps`), then fusion_aps_set_client_id and fusion_aps_signin (silent while the browser SSO session is warm); fusion_aps_status explains the first-time case. APS is how cloud search finishes in under a minute instead of a 30-minute folder walk. Autodesk's MCP server is ",
 "mcp_off": "OFF - fusion_mcp_enable can turn it on for the user (~10s, drives the Preferences dialog).",
 "mcp_on": "LIVE (fusion_mcp_* verbs work).",
 "upd_off": " AUTO-UPDATE is OFF (the user opted out, sticky) - do NOT click Fusion's update prompts for them.",
 "stale_template": "STALE add-in: Fusion is running add-in v{reported} but this bridge bundles v{expected}. Newer verbs (e.g. fusion_aps_open/open_by_urn) can fail silently. Fix: fusion_stop then fusion_start - the bridge re-syncs the add-in from its cache on start (only possible with Fusion CLOSED).",
 "roundtrip_note_prefix": " NOTE: ",
 "roundtrip_note": "the add-in's HTTP server is up but its main thread did not execute a test command yet - not drivable this second",
 "upd_applied_template": " AUTO-UPDATE: Fusion was offering an update and I clicked {button} for the user IN THE BACKGROUND - it downloads now and the new build comes up on the next launch. TELL THE USER it is handled; they never need to click the nag. They can opt out with fusion_set_auto_update {enabled:false} (sticky).button",
 "fusion_update_hint_handled": "Fusion offered an update and it was clicked in the background - tell the user it is handled.",
 "fusion_update_hint_pending_template": "Fusion is OFFERING AN UPDATE (auto-update {state}). OFFER to run it: fusion_set_auto_update {enabled:true} or a one-off background click on the next sweep."
}