Adom Desktop - Fusion 360 Bridge

Fix Fusion 360 signing into the WRONG Autodesk account because it fires its OAuth at the OS-DEFAULT browser. Fusion opens sign-in in whatever browser is default (often a personal Chrome profile), but a user's Autodesk seat usually lives in a DIFFERENT profile (their work Google/SSO). The bridge's fusion_signin verb reads the full authorize URL Fusion wrote into that wrong browser's history and re-opens it in the RIGHT profile, where it completes back to the running Fusion. Trigger words - fusion wrong browser, fusion wrong account, fusion signs into wrong profile, fusion opens personal chrome, autodesk wrong profile, multiple chrome profiles autodesk, fusion_signin, fusion sign in wrong google account, fusion default browser oauth, authenticate fusion multiple profiles.

THE definitive reasoning for the Fusion bridge's APS cloud-file search — WHY we use Autodesk Platform Services (APS) Data Management for fast search, why the slow Fusion add-in search is unacceptable, why the bridge runs its own OAuth, and the hard payment rules. READ THIS FIRST before proposing ANY change to fusion cloud search, before "reconsidering" APS, or before suggesting a fallback. Stops the recurring loop of re-deriving the same conclusions. Trigger words — fusion cloud search, fusion_aps_search, aps search, why aps, fusion search slow, fusion_search_cloud_files, fusion_walk_cloud_tree, search fusion files, cloud file search, fusion data management.

Drive the Autodesk sign-in flow in the user's real browser to set up APS (Autodesk Platform Services) for the Fusion bridge's fusion_aps_* cloud search — open a dedicated browser window, foreground it, MONITOR the sign-in, and auto-retrieve + enter the emailed one-time passcode (OTP) via adom-google before it expires. Use when signing into Autodesk/APS, registering an APS app, configuring fusion_aps_search, or any "log me into Fusion/Autodesk for APS" request. Trigger words — aps signin, sign in to autodesk, autodesk otp, fusion aps login, register aps app, aps client id, fusion_aps_signin, autodesk verification code, link google account autodesk.

Drive the first-run Autodesk sign-in that blocks a freshly installed Fusion 360, from a headless/remote Adom desktop (pup/adom-desktop). Covers the whole browser OAuth handoff and every pitfall that cost hours on a fresh Hyper-V VM — blank sign-in webview, invisible Edge windows, warm Google/Apple/Microsoft SSO, the Autodesk Identity Manager protocol handoff, fast-expiring sign-in codes, and escalating the password/2FA step to the human without ever typing it. Trigger words — fusion signing in, welcome to fusion, sign in - autodesk, needsSignin, fusion stuck signing in, autodesk oauth, fusion login blocked, drive fusion sign in, fusion sign in on fresh box.

How to develop, version, and PUBLISH the Adom Desktop Fusion 360 bridge — where the source canonically lives, and the rule to ALWAYS publish to the wiki AND push the GitHub backup on every change. Read before editing/shipping the fusion bridge. Trigger words — fusion bridge dev, publish fusion bridge, fusion bridge repo, where does the fusion bridge live, ship fusion bridge, bump fusion bridge, adom-desktop-fusion-bridge.

Reproducible recipe for building a WHOLE parts catalog (e.g. the 138-part Adom basic parts library) into ONE Fusion 360 .lbr where every value is placeable with its real footprint + a rendering 3D model - the SHARED-FOOTPRINT method, end to end. Collapse the catalog to its unique (type,package) footprints, build a 3D package per footprint with fusion_build_library_3d, then clone the base deviceset per catalog value so all values share the footprint + symbol + 3D binding. Covers sourcing the footprints/3D (wiki per-MPN pages, the static footprints library, generic KiCad models), the deviceset-cloning assembly, validation, verification, and publishing. Read this to reproduce or extend the Adom basic parts Fusion library, or to turn any parts list into a Fusion library. Trigger words - build a parts library, adom basic parts library, basic parts fusion lbr, whole catalog library, shared footprint library, clone devicesets, 138 part library, reproduce the basic parts library, parts table to lbr, resistor capacitor library fusion.

Keep the Fusion 360 / Autodesk cloud TIDY when the bridge creates files (f3d 3D packages, saved libraries, exports). The cardinal rule - NEVER write loose files into a shared project ROOT folder; always work inside an AI-owned "Adom AI Workspace" folder with a per-task SUBfolder. Covers why (a real incident where 100+ loose f3d files dumped into the shared Adom team root and colleagues complained), how the bridge now enforces it (defaults uploads to a non-root workspace folder, REFUSES a root folderId), and how to clean up AI-created clutter PRECISELY by lineage urn (fusion_cleanup_cloud_files) without ever touching a teammate's file. Read this before any verb that writes to the cloud - fusion_make_3d_package, fusion_build_library_3d, fusion_aps_upload, fusion_save_to_cloud, fusion_aps_create_folder. Trigger words - fusion cloud folder, project root, dumped files in root, clean up cloud files, fusion_cleanup_cloud_files, Adom AI Workspace, aps_upload folder, save to cloud folder, folder hierarchy fusion, f3d clutter, delete cloud file, lineage urn delete, shared project cloud, organize fusion cloud, never write to root.

How saving works in Fusion 360 when 3D packages and libraries live in the Autodesk cloud (Hub) - why FINISH/Save uploads packages ASYNCHRONOUSLY, why you must give a library a cloud home BEFORE attaching 3D so a crash cannot wipe your work, and the hard rule to NEVER close or saveAs while a Hub upload is in flight (it loses packages or throws InternalValidationError / "save was cancelled"). Includes the poll-until-uploaded saveAs recipe. Read before saving any library or document that has had 3D packages attached, or whenever you see an upload/save dialog. Trigger words - fusion save, saveAs, save library, fusion hub upload, packages being uploaded, InternalValidationError, save was cancelled, library not saved, lost attaches, lost bindings, save to cloud, wip_urn upload, poll save, save while uploading, cloud persistence fusion.

Run a FIRST-TIME-USER demo of the Fusion 360 bridge - the guided tour Hydrogen Desktop's installer fires when someone new wants to see what this thing does. Covers the one verb (fusion_demo), the staged loop, and the two rules that make or break it: FINISH the Autodesk sign-in (never leave a new user parked on the sign-in page) by driving the user's NATIVE browser via ABE/nbrowser_* (already signed into Autodesk) instead of pup (anonymous), and SET UP APS cloud search rather than just mentioning it, then prove it with a live sample search. Then show real work in order: electronics PROJECT -> SCHEMATIC -> 2D BOARD -> 3D BOARD. Trigger words - fusion demo, demo the bridge, show me fusion, first time user demo, hd installer demo, demo verb, guided tour, showcase fusion, new user onboarding demo, fusion_demo.

How to SAFELY drive Fusion 360 through the Adom bridge across many steps without losing work - the discipline of reading the screenshot/owned-popup ARRAY after every mutating op and ANALYZING any dialog BEFORE the next step, never blind-dismissing, and never fullscreen-capturing (it forces foreground and disrupts the user). Includes the blocking-dialog catalog with the CORRECT response for each, and how the bridge now returns the dialog array + an analyze-this hint automatically. Read this BEFORE running any multi-step Fusion automation (attaching 3D, saving libraries, closing docs, modeling scripts). Trigger words - drive fusion, fusion dialog, blocking dialog, are you sure you want to close, packages are being uploaded, save was cancelled, ownedPopupCount, screenshot array, owned popups, fusion notification, lower right error, dismiss dialog, fusion modal, fusion_screenshot_all, fusion_window_info, fusion_check_dialogs, fullscreen capture fusion, analyze before proceeding.

EAGLE command reference for Fusion 360 Electronics via fusion_electron_run. Use when driving the Fusion Electronics / PCB workspace through the Adom Desktop Fusion 360 bridge — the EAGLE-syntax commands (DRC, ROUTE, RATSNEST, DISPLAY, GRID, etc.) you pass to fusion_electron_run, and which ones BLOCK (ADD/SHOW/MOVE/WRITE/EDIT) vs are safe. Trigger words - eagle command, fusion_electron_run, electron run, DRC, ERC, RATSNEST, RIPUP, DISPLAY layers, WINDOW FIT, eagle layers, blocking command, WRITE blocks, export eagle source, eagle script.

How to drive Fusion 360 Electronics (the EAGLE-based schematic + PCB editor) through the Adom Fusion bridge - the file hierarchy (open the PROJECT, never the schematic/.brd/3D), switching between schematic / 2D board / 3D PCB views, and moving the editor for demos and screen recordings (zoom, pan, frame a region, orbit the 3D board, select parts, surface the properties panel). Read before opening or recording any PCB. Trigger words - fusion electronics, fusion pcb, open the board, open the schematic, fusion_show_2d_board, fusion_show_3d_board, eagle editor, zoom the board, pan the board, orbit the 3d pcb, select a part, properties panel, record the schematic, record the board, board out of date, empty 2d board, EcadDesignProductType, parent child electronics design.

How an Adom component library (symbol + footprint + 3D chip) is built and gets into Fusion 360 Electronics as a placeable .lbr. Covers the full pipeline (chip-fetcher -> adom-symbol / adom-footprint -> adom-lbr -> fusion_open_lbr), the Windows file-staging gotcha (there is NO container-to-Windows push verb), and attaching the real 3D chip with fusion_attach_3d_package (the Package3D-generator FINISH that binds a package3d wip_urn onto the deviceset). Read before building or opening any library, or when a part shows only a placeholder 3D package. Trigger words - lbr, eagle library, fusion library, open lbr, chip-fetcher, adom-lbr, adom-symbol, adom-footprint, kicad_sym, kicad_mod, deviceset, package3d, 3d package, 3d chip, fusion_attach_3d_package, wip_urn, attach 3d model, placeholder package, content manager, library into fusion, get library into fusion.

Turn a Fusion 360 electronics board into a real entry in the Adom molecule system (adom-molecule / hydrogen) end to end. Covers the FIVE required Fusion exports the bridge already ships (.usdz, .f3d, EAGLE .brd, EAGLE .sch, silkscreen top .png), the exact multipart field names the hydrogen create API expects, and the session-cookie auth workaround for the adom-molecule CLI's auth gap. Trigger words: fusion board to molecule, create molecule from fusion, adom-molecule create fusion, upload fusion board, molecule from the board adonis made, save a molecule component page, export brd sch f3d from fusion, fusion molecule pipeline.

How to build ONE Fusion 360 .lbr library holding MANY parts where EACH package has its real 3D model attached and RENDERING - the SOLVED, fully programmatic, zero-GUI-dialog recipe. The method: for each part, import its STEP into a Design, orient it flat, saveAs an .f3d, aps_upload the .f3d, construct an fs.file:vf wip_urn from the upload lineage, and hand-write the package3d binding into the combined .lbr. Covers the exact binding markup, the orient, merging per-part .lbr files, the connect/pad pre-merge validation, and the dead ends to avoid (the GUI Package3D generator's unbeatable CEF dialogs; a raw STEP upload renders nothing). Read this when attaching 3D to more than one part in a single library, or building a parts-library sampler. Trigger words - multi part library, multiple 3d packages, attach 3d to many parts, combined lbr, merge lbr, basic parts library, parts sampler, per package 3d, package3d, f3d upload, fs.file vf urn, aps_upload 3d, programmatic 3d binding, render 3d package, thumbnail download failed, Create3DPackage dialogs, attach all 3d.

Fix Fusion 360 signing into the WRONG Autodesk account because it fires its OAuth at the OS-DEFAULT browser. Fusion opens sign-in in whatever browser is default (often a personal Chrome profile), but a user's Autodesk seat usually lives in a DIFFERENT profile (their work Google/SSO). The bridge's fusion_signin verb reads the full authorize URL Fusion wrote into that wrong browser's history and re-opens it in the RIGHT profile, where it completes back to the running Fusion. Trigger words - fusion wrong browser, fusion wrong account, fusion signs into wrong profile, fusion opens personal chrome, autodesk wrong profile, multiple chrome profiles autodesk, fusion_signin, fusion sign in wrong google account, fusion default browser oauth, authenticate fusion multiple profiles.

Onboard a brand-new Adom user who wants Fusion 360 features but doesn't have Fusion installed — the AI downloads the Fusion installer, silent-installs it, drives the Autodesk login (free/trial is enough), and auto-installs the AdomBridge add-in so the bridge can inject commands. "Complete the circuit" so fusion_* verbs work end to end. Trigger words — install fusion, no fusion, fusion not installed, set up fusion, download fusion, onboard fusion, get fusion, fusion trial, install the bridge add-in, fusion addin not running, set up the fusion bridge from scratch.

Think about a PCB as its STACKUP - the physical layer sandwich - before doing ANY 3D work with a board: placing overlays (silkscreen/copper textures), computing the board bounding box, picking z-heights, making traces visible, or building a wiki 3D model. Records John's teaching (2026-07-15) after an overlay was placed at component height instead of the copper layer. Trigger words: pcb stackup, board layers, fr4 bounding box, board bbox wrong, silkscreen z height, copper layer z, traces not visible, overlay floating above board, layer heights, soldermask z, board thickness.