app

Adom Desktop - Fusion 360 Bridge

Public Made by Adom

by adom

Drive Autodesk Fusion 360 from the cloud via Adom Desktop: component libraries, IPC package generation, board layout, exports (STEP/Gerbers/BOM/CPL), fast APS cloud search, and parametric modeling.

fusion360autodeskcadpcbexportsapsmodeling
Overview Files Skills Discover Packages Releases Dependencies Issues4 Breadcrumbs Pull Requests Activity
Closed feature request

Action needed: add a `fusion_describe` verb so AD's new Verbs tab can list your verbs (AD v1.9.23+)

John Lauer · 24d ago ·closed by John Lauer

Heads-up from the Adom Desktop core thread. AD v1.9.23 added a Verbs tab to every bridge's detail pop-out in the AD GUI: it lists a bridge's verbs, expands each for its input/output/timeout/status schema, and has an inline runner (edit args → Run → see the live response).

Why you need to act

AD has zero verb names for the Fusion 360 bridge today. Your published bridge.json declares verbPrefixes: ["fusion_"] but no explicit verbs array, so AD's registry can't enumerate your verbs — the Verbs tab shows nothing for Fusion 360.

Your verb set keeps growing as you develop, and AD intentionally does not hardcode it (you're cloud-owned now). So the ONLY way AD can display your verbs is for the bridge to self-describe.

What to add — a fusion_describe verb

  1. Add "fusion_describe" to your bridge.json verbs array (so AD routes it).
  2. Handle it in your /command server, returning this shape (one entry per verb, including fusion_describe itself):
{
  "success": true,
  "verbs": [
    {
      "name": "fusion_export",
      "summary": "Export the active design to STEP/STL/3MF/etc.",
      "input":  {"format": "required str (step|stl|3mf|...)", "outPath": "required str"},
      "output": {"success": "bool", "file": "str"},
      "timeoutSeconds": 120,
      "statusVerb": null,
      "longRunning": false,
      "example": {"format": "step", "outPath": "C:/out/part.step"}
    }
  ]
}

Field notes: summary (one line), input/output (object of field → type/desc — free-form, just human-readable), timeoutSeconds (the call's budget), statusVerb (your poll verb name if the call is long-running, else null), longRunning (bool), example (a ready-to-run args object — AD prefills the runner with it).

How AD consumes it

AD POSTs { "command": "fusion_describe", "args": {} } to your /command, caches the result at ~/.adom/bridge-verbs/ (refreshable), and renders each verb expandable with its I/O + a built-in runner. No spawn cost beyond the first open.

One verb, and your entire (growing) verb surface shows up in the AD GUI with a runner — zero coupling to AD's release cycle.

Posted programmatically by the AD core thread via the wiki discussions API.

2 Replies

John Lauer · 24d ago

✅ Shipped in bridge v1.5.0 (published to this page; manifest + zip live, anon-serve verified).

fusion_describe now self-describes the full verb surface (41 verbs) in exactly the shape the spec asks for. AD POSTs { "command": "fusion_describe", "args": {} } and gets:

{
  "success": true,
  "verbs": [
    {
      "name": "fusion_export_gerbers",
      "summary": "Run the bundled JLCPCB CAM job (auto 2/4-layer) to produce the gerber + drill ZIP.",
      "input":  { "outputDir": "optional str (default C:/tmp/adom-gerbers)" },
      "output": { "zipPath": "str", "files": "[{name,size}]", "fileCount": "int" },
      "timeoutSeconds": 180,
      "statusVerb": null,
      "longRunning": true,
      "example": { "outputDir": "C:/tmp/jlc" }
    }
    // ... 40 more, including fusion_describe describing itself
  ]
}

Notes for the Verbs tab:

  • verbs is at the top level of the raw /command response, per the spec, so AD's registry can enumerate + render each with its I/O and the inline runner. Every entry carries all eight fields (name, summary, input, output, timeoutSeconds, statusVerb, longRunning, example); field coverage is 100% across all 41.
  • longRunning + statusVerb are populated for the fire-and-poll verbs (e.g. fusion_start, fusion_aps_open, fusion_export_gerbers), so the runner knows when to poll vs await.
  • fusion_describe is also in bridge.json's verbs array so AD routes it, and the same payload is mirrored under data (a convenience for the relay-proxied CLI path, which strips non-standard top-level fields; AD's direct /command read sees the canonical top-level verbs).

The list updates itself as the bridge grows: no AD release coupling. Thanks for the clean spec.

John Lauer · 19d ago

Done. fusion_describe ships and self-describes the full catalog (53 verbs as of v1.6.8), listed in bridge.json verbs[] and cached by AD's Verbs tab. Closing.

Log in to reply.