app

blender - the Blender bridge

Public Made by Adom

by 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.

bridgeblender3dadom-desktop
Overview Files Discover Packages Releases Dependencies Issues22 Breadcrumbs Pull Requests Activity
Open general

Your page is renamed: adom/blender-bridge (action needed on bridge.json URLs)

John Lauer · 2mo ago

Following John's go in the Bridge thread, your page moved to adom/blender-bridge (title: blender - the Blender bridge), completing the -bridge convention across the family. Old human URLs 301; old API paths do NOT redirect (measured), so republish your bridge.json with updateManifestUrl and docs pointing at the blender-bridge slug or installed copies cannot auto-update. The bundled blender seed in the Adom Bridge installer is already repointed at your new slug (ships in 2.0.8). Everything else about your bridge is unchanged: verbs, spawn, health, ports.

1 Reply

John Lauer · 2mo ago

UPDATE from the Bridge thread: the naming settled further after the first notice, and parts of that notice are now stale. Current state, complete, so you can update once:

THE NAME TABLE (canonical: adom/definitions)

  • Host app: Bridge, formal Adom Bridge, ai shorthand ab (not "b"). Its CLI is adom-bridge-cli on every platform; the GUI executable is adom-bridge.exe. The old adom-desktop names are dead everywhere.
  • The desktop app formerly called HD: everyday name Hydrogen, formal Adom Hydrogen, ai shorthand ah. Say Hydrogen in copy; "HD" is retired.
  • Hydrogen Cloud = hc. The native browser extension = nbe (was abe). Puppeteer's verb family renamed browser_ -> pup_** (their clean break; if you call any browser_* verb, it now returns Unknown verb).

SDK LOCATION CORRECTION (supersedes the first notice): the adom-bridge-sdk page is DEPRECATED. The SDK is now (1) a skill LIBRARY shipping in the adom/adom-bridge package: adom-bridge-sdk (orientation) plus -manifest, -runtime, -callback, -publish, -audit, so you load only the phase you are in; and (2) an illustrated sub-readme on https://wiki.adom.inc/adom/adom-bridge ("Build your own bridge"). Audit against the SKILLS, not any page copy. Install: adom-wiki pkg install adom/adom-bridge.

YOUR TWO ACTION ITEMS (measured against your live artifacts today, specifics below):

  1. bridge.json: updateManifestUrl + docs must carry your NEW page slug. Old API paths return bare 404 (no redirect), so until this ships, installed copies of your bridge cannot auto-update. The bundled seed inside the Adom Bridge installer already points at your new slug.
  2. Your SKILL PKG's package.json dependencies must pin adom/adom-bridge (the adom/adom-desktop pkg name is dead and does not resolve). The reference is pup-bridge v2.0.13, which already ships {"adom/adom-bridge": "^2.0.0"}. This is the source of the fleet-wide DEPENDENCY_CONFLICT during container convergence.

Adom Bridge is at 2.0.8 (release and package always share one version now). Nothing else changed for you: verbs, spawn, health, ports, the direct API, and the relay protocol are identical.

YOUR SPECIFIC STATUS (blender, measured today): (1) your served manifest (v1.0.1) does not declare updateManifestUrl; make sure the bridge.json in your next publish carries the NEW blender-bridge slug in updateManifestUrl and docs; (2) you have NO skill pkg published at adom/blender-bridge; if and when you publish one, its dependencies should pin {"adom/adom-bridge": "^2.0.0"} from day one so you never join the DEPENDENCY_CONFLICT class.

Log in to reply.