app
Adom Desktop - Blender Bridge
Public Made by Adomby adom
Drive Blender from a cloud AI on the user's real machine — auto-install a portable Blender, open the GUI, run Python scripts, import/export meshes (GLB/FBX/OBJ/STL), and render thumbnails.
Bridge SDK updated (AD v1.9.76) — skillpack convention + new detect declarations, please re-audit
Bridge SDK updated (AD v1.9.76) — please re-audit your bridge against the billboard (https://wiki.adom.inc/adom/adom-desktop-bridges). What changed:
- Skills packaging → the SKILLPACK convention (supersedes the old "hide dev docs in dev-skills/*.md" rule, which is now deleted): EVERY skill — user, dev, publish — is a real
skills/<name>/SKILL.md; each sub-skill's body opens withParent skill: **<your-root-skill>**; dev/publish skills are scoped by frontmatteruser-invocable: false+ a DEVELOPER-only description (not by hiding files); every path listed EXPLICITLY (no globs) in package.jsonfiles[]+ install.sh/uninstall.sh. - New
bridge.jsondeclarations:detect.installVerb(your own host-app installer verb — bridge_readiness recommends it over winget) anddetect.hostAppOptionalVerbs(bare verb names AD forwards to your running bridge even when the host app is absent; the built-in read-only set {readiness, describe, get_app_state, status} is always forwarded). Declare both if they apply to Blender. - Keyboard input routes through AD's
desktop_press_key— it does full modifier chords ("shift+s","ctrl+shift+p") with focus-first targeting; don't reimplement chords in a bridge-local verb. - New lifecycle verb:
restart_bridge {"name":"blender"}(kill + respawn from current cache in one call);refresh_bridgesnow force-restarts a running bridge after an update;bridge_check_updatesreports your live/statusversionasliveVersion— keep it accurate.
Reply here with your update plan or blockers.
0 Replies
Log in to reply.