app
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.
← Commit history
v1.9.65: automation doctrine enforced in code
12 files changed
+180−24
BRIDGE_VERSION+1−1@@ -1 +1 @@-1.9.62+1.9.65
CHANGELOG.md+17@@ -3,6 +3,23 @@ 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.9.65 - 2026-08-18++- **THE AUTOMATION DOCTRINE, enforced in code (John: "never make the adom user do anything+ manually").** Every Dashboard action that needs Fusion now calls `ensure_ready()` first: it+ joins an in-flight auto-green instead of duplicating it, waits with narration, and SELF-HEALS+ while waiting - clears blocking dialogs, and restarts Fusion once if it is running but the+ add-in never came up (waiting longer never fixes a missing add-in; it only loads at launch).+ Surface clicks that still fail get a remediation pass (dismiss dialogs, re-ready, re-stage the+ part) and one retry before any error is shown. The old "Fusion is not ready - press Setup"+ refusal is gone; it was a failure of this bridge, not an instruction for the user.+ PROVEN live: with Fusion KILLED, a single Symbol click launched it, staged IN-S63BTG from the+ wiki, bound the 3D, generated the test project, and rendered the symbol - 5m30s, no human step.+- Doctrine recorded in CLAUDE.md and dev-skills/fusion-dashboard so it survives this session.+- Settings: the white halo around the modal was Chrome's default focus ring, drawn in currentColor+ because the dialog is focused on open to keep it scrolled to the top; suppressed on the+ container only (children keep their teal focus-visible rings).+ ## 1.9.63 - 2026-08-18 (dashboard only; bridge zip stays 1.9.62) - **The house scrollbar, everywhere** (John: "that scrollbar is hideous"). Thin, transparent
CLAUDE.md+24@@ -16,6 +16,30 @@ all of this and filed its own bridge bugs as "adom-desktop" requests. Don't.) - So: a `fusion_*` verb behaves wrong, a hint is missing, APS misbehaves, the add-in is stale → it's **your code**, fix it here and republish. It is NOT an adom-bridge request. +## THE AUTOMATION DOCTRINE (John, 2026-08-18, verbatim - this outranks tidy error messages)++> "your whole goal is to automate the life of the adom user and never slow them down or stop+> them from getting their goal done. so stupid errors that you can easily fix are supposed to+> always just work automatically. never make the adom user do anything manually."++Concretely, for every verb, button, and surface in this bridge:++- **A click is a GOAL, not a request for an audit.** If Fusion is closed, launch it. If the+ add-in is not serving, restart Fusion (the add-in only loads at launch). If a modal blocks+ the main thread, clear it. If a library fell out of the session, re-stage it. THEN do the+ thing the user asked for.+- **Never return an error the code could have fixed.** "Press Setup and try again",+ "Fusion is not running", "open the library first" are all FAILURES OF THIS BRIDGE, not+ user instructions. Remediate, retry once, and only then report - with what you tried.+- **Narrate, do not block.** Say what you are fixing (toast/hint) while you fix it, so the wait+ is legible; never make the human perform the fix.+- **The only legitimate stops** are things code genuinely cannot do: a password, a 2FA code, an+ unconfigured APS client id, a hardware/licensing decision that risks the user's other machine.+ Toast those at the exact moment they are needed, having already done everything around them.++Implemented reference: `dashboard/src/main.rs` `ensure_ready()` + the remediate-and-retry pass in+`show_surface()`.+ ## Where to TALK to ab (learned the hard way, 2026-08-17) **The adom/adom-bridge-sdk repo is DEPRECATED as a discussion venue** - the SDK moved INTO the
adom-bridge-fusion-manifest.json+4−4@@ -1,10 +1,10 @@ { "manifest_version": 1, "name": "fusion360",- "version": "1.9.62",- "url": "https://wiki.adom.inc/download/adom/fusion-bridge/1.9.62/adom-bridge-fusion-v1.9.62.zip",- "sha256": "5f28232cd79b3ee8094ebaacf4be3716f771709e95cfedac0da7505423f40d1a",- "size": 405827,+ "version": "1.9.65",+ "url": "https://wiki.adom.inc/download/adom/fusion-bridge/1.9.65/adom-bridge-fusion-v1.9.65.zip",+ "sha256": "27c33da22d67295b986b1dc624443b9af7ee6fe1d41c2fc55462e278c9bc402a",+ "size": 405829, "verbPrefixes": [ "fusion_" ],
bin/fusion-dashboard⋯ 1 unchanged line ⋯
dashboard/Cargo.toml+1−1@@ -1,6 +1,6 @@ [package] name = "fusion-dashboard"-version = "1.9.63"+version = "1.9.65" edition = "2021" [dependencies]
dashboard/src/main.rs+97−8@@ -157,7 +157,7 @@ fn action(ai_thread: &str, target: &str, name: &str, args: &serde_json::Value) - "set_driving_badge" => bridge(ai_thread, target, "fusion_set_driving_badge", &a), "mcp_enable" => bridge(ai_thread, target, "fusion_mcp_enable", "{}"), "aps_signin" => bridge(ai_thread, target, "fusion_aps_signin", "{}"),- "import_basic_part" => import_basic_part(ai_thread, target, args),+ "import_basic_part" => import_basic_part(ai_thread, target, args), // readiness handled by the caller _ => serde_json::json!({"error": format!("unknown action {}", name), "_hint": "Actions: start, stop, signin, tour, tour_progress, set_auto_update, set_seat_takeover, mcp_enable, aps_signin, import_basic_part."}), }@@ -371,6 +371,66 @@ fn auto_green(app: &Arc<App>, target: &str) { }); } +/// Make the box ready, do not lecture the user about it (John, 2026-08-18: "when i load the+/// dashboard you're supposed to get everything ready for me ... launching the dashboard is like+/// opening fusion and making sure its fully setup and ready for the ai to control it").+/// Any action that needs Fusion calls this FIRST: it returns immediately when ready, otherwise+/// it kicks auto-green (single-flight, so an in-flight launch is joined rather than duplicated)+/// and waits, narrating progress, before the caller proceeds.+fn ensure_ready(app: &Arc<App>, target: &str, max_wait_s: u64) -> bool {+ let ai = app.ai_thread.clone();+ let is_ready = || unwrap_data(&bridge(&ai, target, "fusion_readiness", "{}"))["ready"]+ .as_bool().unwrap_or(false);+ if is_ready() { return true; }+ app.hub.broadcast("toast", &serde_json::json!({+ "message": format!("Getting {} ready first - launching Fusion and waiting for the bridge add-in", target),+ "kind": ""}));+ auto_green(app, target); // no-op if one is already running+ let t0 = Instant::now();+ let mut announced = false;+ let mut restarted = false;+ while t0.elapsed() < Duration::from_secs(max_wait_s) {+ std::thread::sleep(Duration::from_secs(5));+ // SELF-HEAL rather than wait on a broken state (John, 2026-08-18: "even if something is+ // off, you should be detecting that and then auto launching all the needed pieces ...+ // never make the adom user do anything manually"). Two mechanically fixable states:+ // a) a modal is blocking the add-in -> clear it;+ // b) Fusion is up but the add-in never came up -> restart it ONCE (the add-in loads at+ // launch, so stop+start is the actual remedy; more waiting never fixes it).+ if t0.elapsed() > Duration::from_secs(40) && !is_ready() {+ let st = unwrap_data(&bridge(&ai, target, "fusion_state", "{\"screenshot\":false}"));+ if st["blockingDialogs"].as_array().map(|a| !a.is_empty()).unwrap_or(false) {+ app.log("ensure_ready: clearing blocking dialogs".into());+ bridge(&ai, target, "fusion_dismiss_blocking_dialogs", "{}");+ }+ if !restarted && t0.elapsed() > Duration::from_secs(90)+ && st["running"].as_bool().unwrap_or(false)+ && !st["addinResponding"].as_bool().unwrap_or(false) {+ restarted = true;+ app.hub.broadcast("toast", &serde_json::json!({+ "message": "Fusion is up but its bridge add-in did not start - restarting Fusion for you", "kind": ""}));+ app.log("ensure_ready: add-in not serving, restarting Fusion".into());+ bridge(&ai, target, "fusion_stop", "{\"reason\":\"dashboard: add-in not serving, restarting to load it\"}");+ std::thread::sleep(Duration::from_secs(4));+ bridge(&ai, target, "fusion_kill", "{}");+ std::thread::sleep(Duration::from_secs(3));+ bridge(&ai, target, "fusion_start", "{}");+ }+ }+ if is_ready() {+ app.hub.broadcast("toast", &serde_json::json!({"message": "Fusion is ready - continuing", "kind": "ok"}));+ app.hub.broadcast("state", &gather_status(&ai, target));+ return true;+ }+ if !announced && t0.elapsed() > Duration::from_secs(45) {+ announced = true;+ app.hub.broadcast("toast", &serde_json::json!({+ "message": "Still waiting on Fusion (a cold start takes a minute or two)", "kind": ""}));+ }+ }+ false+}+ // ── SURFACES DEMO (John, 2026-08-18) ───────────────────────────────────────────────────── // The same eight-surface showcase the ab web-control demo runs, but on a DIFFERENT adom basic // part (default aravk/in-s63btg, a green 0603 LED - web control uses the red 0402 IN-S42ATR),@@ -396,11 +456,9 @@ fn stage_demo_part(app: &Arc<App>, target: &str, page: &str) -> Result<(String, app.hub.broadcast("toast", &serde_json::json!({"message": msg, "kind": kind})); app.log(format!("surfaces: {}", msg)); };- // Fail FAST and clearly if the box is not ready - otherwise we stage files onto a machine- // whose Fusion is closed and every surface returns a confusing "not running".- let rd = unwrap_data(&bridge(&ai, target, "fusion_readiness", "{}"));- if rd["ready"].as_bool() != Some(true) {- return Err(format!("Fusion is not ready on {} - press Setup (or turn on 'Get everything ready') and try again", target));+ // GET it ready rather than refusing: a click means "show me this", not "audit my setup".+ if !ensure_ready(app, target, 240) {+ return Err(format!("Fusion did not become ready on {} within 4 minutes. Open the Settings and check the status cards - a sign-in wall or a stuck launch will say so there.", target)); } toast(&format!("Staging {} from the wiki (clone -> send -> bind 3D -> generate project)", page), ""); let tmp = format!("/tmp/fd-surfaces-{}", std::process::id());@@ -461,8 +519,28 @@ fn show_surface(app: &Arc<App>, target: &str, key: &str, page: &str) -> serde_js "library" => serde_json::json!({"libraryPath": lib}), _ => serde_json::json!({}), // design surfaces act on the generated project };- let r = unwrap_data(&bridge(&ai, target, verb, &args.to_string()));- let ok = r["success"].as_bool().unwrap_or(false);+ let mut r = unwrap_data(&bridge(&ai, target, verb, &args.to_string()));+ let mut ok = r["success"].as_bool().unwrap_or(false);+ if !ok {+ // AUTO-REMEDIATE then retry once: every failure here has a mechanical fix the user+ // should never perform by hand (a modal blocking the main thread, a not-serving add-in,+ // a library that fell out of the session).+ app.log(format!("surface {} failed ({}), remediating", key, r["error"]));+ app.hub.broadcast("toast", &serde_json::json!({+ "message": format!("{} did not open first try - clearing the way and retrying", label), "kind": ""}));+ bridge(&ai, target, "fusion_dismiss_blocking_dialogs", "{}");+ let err = r["error"].as_str().unwrap_or("").to_lowercase();+ if err.contains("not running") || err.contains("not responding") || err.contains("add-in") {+ ensure_ready(app, target, 180);+ }+ if err.contains("edit") || err.contains("library") || err.contains("deviceset") || err.contains("not found") {+ app.staged.lock().unwrap().remove(&format!("{}|{}", target, page));+ let _ = stage_demo_part(app, target, page);+ }+ std::thread::sleep(Duration::from_secs(2));+ r = unwrap_data(&bridge(&ai, target, verb, &args.to_string()));+ ok = r["success"].as_bool().unwrap_or(false);+ } // Render it: fusion_state is the render-me verb (the show verbs open in the background). let mut shot = serde_json::Value::Null; if ok {@@ -605,6 +683,17 @@ fn handle_conn(app: &Arc<App>, mut stream: TcpStream) { let name = body["action"].as_str().unwrap_or("").to_string(); let t = body["target"].as_str().map(|s| s.to_string()).unwrap_or_else(|| app.tgt()); app.log(format!("action {} target={}", name, t));+ // Actions that DRIVE Fusion get the box ready first (auto-green semantics), instead+ // of returning "not running" and making the user chase a Setup button.+ if matches!(name.as_str(), "tour" | "import_basic_part") {+ if !ensure_ready(app, &t, 240) {+ respond_json(&mut stream, &serde_json::json!({+ "success": false,+ "error": format!("Fusion did not become ready on {} within 4 minutes", t),+ "_hint": "Open Settings and read the status cards - a sign-in wall or a stuck launch is reported there."}));+ return;+ }+ } let out = action(&app.ai_thread, &t, &name, &body["args"]); respond_json(&mut stream, &out); }
dashboard/ui/index.html+6@@ -67,6 +67,12 @@ input:focus-visible{outline:none;border-color:var(--accent) !important} .toast.ok{border-left-color:var(--green)}.toast.err{border-left-color:var(--red)} dialog{margin:auto;background:var(--overlay);color:var(--text-body);border:1px solid var(--border);border-radius:12px;padding:20px;max-width:520px;width:92vw} dialog::backdrop{background:rgba(0,0,0,.55)}+/* The dialog is focused programmatically on open (so it scrolls to the top instead of jumping+ to the first input). Chrome then paints its DEFAULT focus ring in currentColor - a light+ 2px halo that reads as a white border around the modal (John spotted it, 2026-08-18). The+ container is not a control, so it takes no ring; its CHILDREN keep their teal focus-visible+ rings for keyboard users. */+dialog:focus,dialog:focus-visible{outline:none} .setrow{display:flex;align-items:center;justify-content:space-between;gap:14px;padding:12px 0;border-bottom:1px solid var(--border)} .toggle{width:42px;height:24px;border-radius:999px;background:var(--elevated);border:1px solid var(--border);position:relative;cursor:pointer;flex:none;transition:border-color .15s ease} .toggle:hover{border-color:var(--accent)}
dev-skills/fusion-dashboard/SKILL.md+17@@ -98,6 +98,23 @@ fusion-dashboard status # one-shot JSON (the LED 7. Verify the circle end-to-end: `adom-wiki pkg install adom/fusion-bridge` in a container -> `fusion-dashboard health` -> `serve` -> `curl /api/status` returns live LEDs. +## The automation doctrine (John, 2026-08-18) - the Dashboard NEVER hands the user a chore++> "even if something is off, you should be detecting that and then auto launching all the needed+> pieces and features, and then continuing on with the symbol ... never make the adom user do+> anything manually."++- Opening the Dashboard = an intent to work: auto-green launches Fusion, drives sign-in, enables+ MCP, signs in to APS (toggle-able, sticky).+- EVERY action that needs Fusion calls `ensure_ready()` first, which joins an in-flight+ auto-green rather than duplicating it, and SELF-HEALS while waiting: clears blocking dialogs,+ and restarts Fusion once if it is running but the add-in never came up (waiting longer never+ fixes a missing add-in - it only loads at launch).+- Surface clicks that fail get a remediation pass (dismiss dialogs, re-ready, re-stage the part)+ and ONE retry before any error reaches the user.+- The old behavior - returning "Fusion is not ready, press Setup" - is the anti-pattern this+ section exists to forbid.+ ## Hard-won build lessons (v1.9.44, 2026-08-16 - John called out the misses) 1. **The house contract is ALL mandatory, not a menu.** v1.9.42 shipped without a favicon,
install.sh+1−1@@ -21,7 +21,7 @@ echo "Installed fusion-bridge skills: $(ls "$PKG_DIR/skills" 2>/dev/null | tr '\ # binary (the three-artifact pattern: bridge zip -> ab, THIS pkg -> container skills + # this download, page media -> wiki). Per the wiki's PKG_VS_RELEASE policy, binaries are # platform-tagged RELEASE assets, never tarball content - the installer fetches them.-DASH_VERSION="1.9.63"+DASH_VERSION="1.9.65" DASH_URL="https://wiki.adom.inc/download/adom/fusion-bridge/${DASH_VERSION}/fusion-dashboard" DEST="" if [ -w /usr/local/bin ]; then DEST=/usr/local/bin
package.json+1−1@@ -1,6 +1,6 @@ { "slug": "fusion-bridge",- "version": "1.9.63",+ "version": "1.9.65", "type": "app", "description": "This package installs the bridge's SKILLS into your container so your AI knows how to drive it; Adom Bridge loads the bridge runtime itself from the release zip.", "dependencies": {
page.json+11−8@@ -1,16 +1,20 @@ { "slug": "fusion-bridge",- "version": "1.9.63",+ "version": "1.9.65", "type": "app", "description": "This package installs the bridge's SKILLS into your container so your AI knows how to drive it; Adom Bridge loads the bridge runtime itself from the release zip.", "dependencies": {- "adom/adom-desktop": "*"+ "adom/adom-desktop": "^1.9.0" }, "scripts": { "install": "./install.sh", "uninstall": "./uninstall.sh" }, "tags": [+ "ab",+ "bridge",+ "fusion",+ "desktop-app", "fusion360", "autodesk", "cad",@@ -70,7 +74,10 @@ "build a basic parts library", "add a 3d model to a component", "make a fusion 360 library with 3d",- "set up the fusion bridge"+ "set up the fusion bridge",+ "fusion dashboard",+ "fusion status page",+ "open the fusion launch page" ], "discovery_pitch": "Use the Adom Bridge Fusion 360 bridge when the user wants to DRIVE Autodesk Fusion 360 from the cloud: open/search their team's Fusion cloud designs, lay out a PCB or do electronics, export STEP/IGES/STL/Gerbers/BOM, or build a component library with real rendering 3D. It runs Fusion on the user's own machine via Adom Bridge. NOT for web/browser/login/form-filling (that's the native-browser extension) and NOT for KiCad (that's the kicad bridge).", "brief": "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.",@@ -99,9 +106,5 @@ "label": "Part volume", "prompt": "How much material does each printed part in this assembly use?" }- ],- "author": {- "name": "John Lauer",- "email": "[email protected]"- }+ ] }