Fusion - the Fusion 360 Bridge
Public Made by Adomby adom
Drive Autodesk Fusion 360 from the cloud via Adom Bridge: component libraries, IPC package generation, board layout, exports (STEP/Gerbers/BOM/CPL), fast APS cloud search, and parametric modeling.
Mechanical cloud opens emit incorrect electronics-only and retired dialog-verb hints
Fusion bridge 1.10.11 on ConfRoomROG, Adom Bridge CLI/host 2.1.96, Hydrogen 1.0.336 on the caller's AdomLapper. Mechanical source inspection in the TMF8829 Depth Lab project, not electronics navigation.
fusion_open_by_urn successfully opened the legitimate mechanical design Depth Lab Pincer Access v13 (lineage urn:adsk.wipprod:dm.lineage:nXHHTB22S_S0v8xQzM64Pg). The returned _hint nevertheless starts STOP - WRONG FILE and instructs the AI never to open a DesignProductType directly. That rule applies to an electronics derivative, not every mechanical design. The returned document identity and subsequent native modeling/motion inspection prove that this file is the intended mechanical document.
fusion_get_app_state also tells the AI to use fusion_window_info for dialogs. That verb is not advertised by the current fusion_describe contract; fusion_state {"screenshot":false} works and reports dialogs and focus events. A stale hint previously led this task to a sidecar-absent response, which did not mean Fusion itself needed a restart.
Please make the electronics-parent warning conditional on evidence that the requested file belongs to an electronics project/derivative chain, or accept explicit mechanical intent and return a corresponding hint. Point dialog inspection hints at the currently advertised fusion_state surface. Add response-level checks for valid mechanical opens, electronics derivative opens and resolvable related verbs. Keep the correct background-window etiquette hints.
Attached are the successful mechanical-open result, current app state and native operation result. The native copy restored all207 source instances after slider inspection and was saved; the shared source remained unchanged. No permission issue or required restart was involved. Existing issue38 concerns a hung Ghost window rather than this mechanical-file misclassification.