Fusion - the Fusion 360 Bridge

@@ -122,54 +122,31 @@ full account, with screenshots of the wrong-footprint trap, is in  Not posted. John reviews it and posts it from his own Autodesk account. -> Hi Aske, disclosure: I run Adom. We make a free, MIT-licensed Fusion add-in and local-> bridge that lets an AI drive Fusion Electronics end to end, and over the last five months-> we have hit your whole list.+> Hi Aske, disclosure: I run Adom. We make a free, MIT-licensed Fusion add-in and local bridge that lets an AI drive Fusion Electronics end to end, and over the last five months we have hit your whole list. >-> Jorge's news is good: when Autodesk's electronics write API lands, we will build on it, and-> on Autodesk's MCP servers, because native support makes all of this simpler. But to your-> closing question, yes, you can drive Electron.run safely today. Here is how, point by point:+> Jorge's news is good: when Autodesk's electronics write API lands, we will build on it, and on Autodesk's MCP servers, because native support makes all of this simpler. But to your closing question, yes, you can drive Electron.run safely today. Here is how, point by point: >-> 1. **Modal dialogs.** Before each command we read every open Fusion dialog through Windows->    UI Automation (title, text, buttons), answer the ones we recognise, cancel unknown ones->    in the background, and hand the text back to the agent instead of hanging. One warning:->    Fusion's floating Browser panel is also titled "Fusion360", and closing it can close->    Fusion, so only close windows that are plainly dialogs.-> 2. **The library browser from ADD.** The same path cancels it, and the video below is->    exactly your case: a script runs ADD, the picker blocks it, the AI reads the dialog and->    cancels it, and the script carries on. Better still, we never need ADD: we write parts->    as EAGLE source and open it with Document.newDesignFromLocal, which raises no dialog.+> 1. **Modal dialogs.** Before each command we read every open Fusion dialog through Windows UI Automation (title, text, buttons), answer the ones we recognise, cancel unknown ones in the background, and hand the text back to the agent instead of hanging. One warning: Fusion's floating Browser panel is also titled "Fusion360", and closing it can close Fusion, so only close windows that are plainly dialogs. >->    *[Video 1]*+> 2. **The library browser from ADD.** The same path cancels it. The video below is exactly your case, from one prompt to an AI: a script runs ADD, the picker blocks it, the bridge reads the dialog and cancels it in the background, and the script carries on. Better still, we never need ADD: we write parts as EAGLE source and open it with Document.newDesignFromLocal, which raises no dialog.+>+> *[Video 1: modal dialog](https://youtu.be/FzQjRKxkYLA)*+>+> 3. **Undo.** Nothing native for Electron.run edits yet, so we save checkpoints before each batch. >-> 3. **Undo.** Nothing native for Electron.run edits yet, so we save checkpoints before each->    batch. > 4. **The armed state.** Your terminateActiveCommand workaround matches ours.-> 5. **Screenshots of the 2D editors.** We capture the Fusion window itself, which works on->    schematics and boards, even with Fusion in the background. Every Fusion frame in the next->    video was captured that way. >-> Putting it together, this is one prompt to an AI writing electronics end to end: it opens a-> parts library, writes a schematic, places the parts on a 2D board and checks the 3D board,-> with no dialogs.+> 5. **Screenshots of the 2D editors.** We capture the Fusion window itself, which works on schematics and boards, even with Fusion in the background. Every Fusion frame in the next video was captured that way.+>+> Putting it together, here is one prompt to an AI writing electronics end to end: it opens a parts library, writes a schematic, places the parts on a 2D board and checks the 3D board, with no dialogs and no hands on the mouse. >-> *[Video 2]*+> *[Video 2: library to 3D board](https://youtu.be/HF2bDMRoGfw)* >-> One more wall you will hit once you write designs, not on your list: parts need 3D models,-> and attaching STEP models to a multi-part library is where we spent the most time. Three-> traps: a raw STEP bound by urn shows "Thumbnail download failed" (only an .f3d renders);-> the 3D package generator's FINISH opens modals no script can close; and the generator loads-> the first package of the open library, so every chip lands on part one's footprint. What-> works, in this order: one library per part, start the generator on it, import the STEP,-> Save As an .f3d instead of FINISH, build the urn from the cloud lineage id, then write-> every urn into the merged library in one pass. Six parts bind in about three and a half-> minutes.+> One more wall you will hit once you write designs, not on your list: parts need 3D models, and attaching STEP models to a multi-part library is where we spent the most time. Three traps: a raw STEP bound by urn shows "Thumbnail download failed" (only an .f3d renders); the 3D package generator's FINISH opens modals no script can close; and the generator loads the first package of the open library, so every chip lands on part one's footprint. What works, in this order: one library per part, start the generator on it, import the STEP, Save As an .f3d instead of FINISH, build the urn from the cloud lineage id, then write every urn into the merged library in one pass. Six parts bind in a few minutes: >-> *[Video 3]*+> *[Video 3: 3D library](https://youtu.be/vUnqaDy8-XU)* >-> The source is public, with a contributing guide if you want to send fixes back:-> [wiki.adom.inc/adom/fusion-bridge](https://wiki.adom.inc/adom/fusion-bridge). Happy to-> compare notes, and thanks Jorge for passing these to the API team.+> The source is public, with a contributing guide if you want to send fixes back: [wiki.adom.inc/adom/fusion-bridge](https://wiki.adom.inc/adom/fusion-bridge). Happy to compare notes, and thanks Jorge for passing these to the API team.  ## Other threads worth a short reply