← Commit history
.insiders-stage/fusion-bridge/version.json+4−4
@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "fusion360",-  "version": "1.11.5",-  "url": "https://wiki.adom.inc/download/adom/fusion-bridge/1.11.5/adom-bridge-fusion-v1.11.5.zip",-  "sha256": "988896c6bf753fc240b687439da1d07708adde5c7eab9474d8ef80bbb5d68523",-  "size": 6533568,+  "version": "1.11.6",+  "url": "https://wiki.adom.inc/download/adom/fusion-bridge/1.11.6/adom-bridge-fusion-v1.11.6.zip",+  "sha256": "32a0ccf3d122b356da52d0af5e7e9738760a3db8e5875b94569c12afa6355e3a",+  "size": 6534478,   "verbPrefixes": [     "fusion_"   ],
.release-page-head+1−1
@@ -1 +1 @@-9436b06b320188d540065defd29c62818af6130f\ No newline at end of file+41e2680e02570a407c723d2f70d35391e80ae295\ No newline at end of file
CHANGELOG.md+7
@@ -3,6 +3,13 @@ All notable changes to the Adom Bridge Fusion 360 bridge, newest first. Canonical: https://wiki.adom.inc/adom/fusion-bridge ยท GitHub backup: `adom-inc/fusion-bridge` +## 1.11.6 (2026-09-23)++- `fusion_aps_search` and `fusion_aps_recent` declare a 120 s budget. A hub-wide search takes 20-30 s on Adom's+  hub (each folder's results are paged and filtered by name on the bridge, because Autodesk's own name filter is+  unreliable), and under the inherited 60 s default a slow moment at Autodesk turned into a timeout. The hints no+  longer promise "~2 s" cloud lookups; they say hub-wide takes 20-30 s and projectId makes it a few seconds.+ ## 1.11.5 (2026-09-23)  - Faster cloud search. `fusion_aps_search` fetched every project's top folders one at a time before searching (16
install.sh

  
page.json+25−9
@@ -11,10 +11,6 @@     "uninstall": "./uninstall.sh"   },   "tags": [-    "ab",-    "bridge",-    "fusion",-    "desktop-app",     "fusion360",     "autodesk",     "cad",@@ -80,9 +76,6 @@     "add a 3d model to a component",     "make a fusion 360 library with 3d",     "set up the fusion bridge",-    "fusion dashboard",-    "fusion status page",-    "open the fusion launch page",     "aps not configured",     "share aps client id across my org",     "set up fusion cloud search for my company",@@ -115,5 +108,28 @@       "label": "Part volume",       "prompt": "How much material does each printed part in this assembly use?"     }-  ]-}+  ],+  "agent_permissions": {+    "allow_bash": [],+    "allow": [+      "adom-desktop-fusion-bridge read-only verbs (via the adom-bridge CLI): fusion_readiness, fusion_get_app_state, fusion_addin_status, fusion_check_dialogs - state queries; they change nothing.",+      "adom-desktop-fusion-bridge read-only verbs: fusion_alerts (reads Fusion's own log for toasts), fusion_document_info, fusion_window_info, fusion_board_info, fusion_library_parts - inspect only.",+      "adom-desktop-fusion-bridge read-only verbs: fusion_prove_result (a persisted run report), fusion_plan_library_import (report-only preflight), fusion_list_cloud_projects, fusion_describe.",+      "adom-desktop-fusion-bridge evidence captures fusion_screenshot_fusion and fusion_capture_library_views read pixels and write local image files only."+    ],+    "soft_deny": [+      "adom-desktop-fusion-bridge lifecycle verbs fusion_stop, fusion_kill, fusion_restart_for_addin close or kill the Fusion application - keep the human prompt.",+      "adom-desktop-fusion-bridge fusion_install_fusion silently installs Autodesk Fusion on the user's machine.",+      "adom-desktop-fusion-bridge fusion_cleanup_cloud_files deletes files from the user's Autodesk cloud hub.",+      "adom-desktop-fusion-bridge managed-library verbs (fusion_managed_library_push/pull/create/link/unlink) publish to or overwrite the user's library.io libraries."+    ],+    "environment": [+      "adom-desktop-fusion-bridge is the Fusion 360 bridge for Adom Bridge; its fusion_* verbs are invoked through the adom-bridge CLI and drive Autodesk Fusion on the user's own desktop.",+      "adom-desktop-fusion-bridge desktop actions also pass Adom Bridge's own human-approval gate (caller identity, per-call reason, Activity Log) - a container approval is the first of two gates."+    ]+  },+  "author": {+    "name": "John Lauer",+    "email": "[email protected]"+  }+}\ No newline at end of file
rust/Cargo.lock+5−5
@@ -10,7 +10,7 @@ checksum = "320119579fcad9c21884f5c4861d16174d0e06250625266f50fe6898340abefa"  [[package]] name = "adom-fusion-bridge"-version = "1.11.5"+version = "1.11.6" dependencies = [  "base64",  "chrono",@@ -273,7 +273,7 @@ dependencies = [  [[package]] name = "fusion-core"-version = "1.11.5"+version = "1.11.6" dependencies = [  "serde",  "serde_json",@@ -283,7 +283,7 @@ dependencies = [  [[package]] name = "fusion-lbr"-version = "1.11.5"+version = "1.11.6" dependencies = [  "regex",  "roxmltree",@@ -295,14 +295,14 @@ dependencies = [  [[package]] name = "fusion-os-mac"-version = "1.11.5"+version = "1.11.6" dependencies = [  "fusion-core", ]  [[package]] name = "fusion-os-win"-version = "1.11.5"+version = "1.11.6" dependencies = [  "fusion-core",  "windows-sys 0.59.0",
rust/core/src/readiness_hints.json+2−2
@@ -6,9 +6,9 @@  "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 ~2s cloud lookups. Autodesk's MCP server is ",+ "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 gets to ~2 seconds. 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.",
rust/core/tests/golden/readiness.json+6−6
@@ -270,7 +270,7 @@    "launchStartedAt": null   },   "result": {-   "_hint": "READY - drive Fusion (fusion_open_lbr / build_library_3d / etc.). APS cloud search is signed in too, so use fusion_aps_search for ~2s cloud lookups. Autodesk's MCP server is OFF - fusion_mcp_enable can turn it on for the user (~10s, drives the Preferences dialog).",+   "_hint": "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 OFF - fusion_mcp_enable can turn it on for the user (~10s, drives the Preferences dialog).",    "addinStale": false,    "addinVersion": "1.0.19",    "bridgeVersion": "TEST",@@ -367,7 +367,7 @@    "launchStartedAt": 1800000000.0   },   "result": {-   "_hint": "READY - drive Fusion (fusion_open_lbr / build_library_3d / etc.). APS cloud search is signed in too, so use fusion_aps_search for ~2s cloud lookups. Autodesk's MCP server is OFF - fusion_mcp_enable can turn it on for the user (~10s, drives the Preferences dialog). NOTE: the add-in's HTTP server is up but its main thread did not execute a test command yet - not drivable this second",+   "_hint": "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 OFF - fusion_mcp_enable can turn it on for the user (~10s, drives the Preferences dialog). NOTE: the add-in's HTTP server is up but its main thread did not execute a test command yet - not drivable this second",    "addinStale": false,    "addinVersion": "1.0.19",    "bridgeVersion": "TEST",@@ -429,7 +429,7 @@    "launchHealedAt": null   },   "result": {-   "_hint": "READY - drive Fusion (fusion_open_lbr / build_library_3d / etc.). APS cloud search is signed in too, so use fusion_aps_search for ~2s cloud lookups. Autodesk's MCP server is OFF - fusion_mcp_enable can turn it on for the user (~10s, drives the Preferences dialog).",+   "_hint": "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 OFF - fusion_mcp_enable can turn it on for the user (~10s, drives the Preferences dialog).",    "addinStale": false,    "addinVersion": "1.0.19",    "bridgeVersion": "TEST",@@ -479,7 +479,7 @@    "launchHealedAt": null   },   "result": {-   "_hint": "READY - drive Fusion (fusion_open_lbr / build_library_3d / etc.). APS cloud search is signed in too, so use fusion_aps_search for ~2s cloud lookups. Autodesk's MCP server is LIVE (fusion_mcp_* verbs work).",+   "_hint": "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 LIVE (fusion_mcp_* verbs work).",    "addinStale": false,    "addinVersion": "1.0.19",    "bridgeVersion": "TEST",@@ -580,7 +580,7 @@    "launchHealedAt": null   },   "result": {-   "_hint": "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 gets to ~2 seconds. Autodesk's MCP server is OFF - fusion_mcp_enable can turn it on for the user (~10s, drives the Preferences dialog).",+   "_hint": "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 OFF - fusion_mcp_enable can turn it on for the user (~10s, drives the Preferences dialog).",    "addinStale": false,    "addinVersion": "1.0.19",    "bridgeVersion": "TEST",@@ -630,7 +630,7 @@    "launchHealedAt": null   },   "result": {-   "_hint": "READY - drive Fusion (fusion_open_lbr / build_library_3d / etc.). APS cloud search is signed in too, so use fusion_aps_search for ~2s cloud lookups. Autodesk's MCP server is OFF - fusion_mcp_enable can turn it on for the user (~10s, drives the Preferences dialog). AUTO-UPDATE is OFF (the user opted out, sticky) - do NOT click Fusion's update prompts for them.",+   "_hint": "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 OFF - fusion_mcp_enable can turn it on for the user (~10s, drives the Preferences dialog). AUTO-UPDATE is OFF (the user opted out, sticky) - do NOT click Fusion's update prompts for them.",    "addinStale": false,    "addinVersion": "1.0.19",    "bridgeVersion": "TEST",
tools/check-naming.sh

  
tools/check-portable.sh

  
tools/promote.sh

  
tools/release.sh