app
Altium - the Altium Bridge
Public Made by Adomby adom
Adom Bridge for Altium Designer: a resident DelphiScript agent gives the AI eval, the 1,100-command process launcher, all 8 EDA surfaces with screenshots, compile/ERC, DRC, OutJob outputs, native SchLib/PcbLib authoring with STEP 3D bodies, and dialog handling by PID.
← Commit history
v0.2.25 (insiders): 0.2.25: a document that did not open is a failure with the reason (file_not_found / view_only_no_author_seat / document_not_opened); 14 verbs stop instead of running against the wrong document; suite passes on AD 26.9.1 and Altium Develop
4 files changed
+8−3
CHANGELOG.md+5@@ -1,5 +1,10 @@ # Changelog +## 0.2.25 (2026-09-20)+- **A document that did not open is now a failure, with the reason.** `altium_open_document` (and the open every library/board verb does first) answered `ok:true` with `shown:false` buried in `data` when Altium silently refused the file; the verb then failed with a misleading "open the SchLib first" / "current document is not a schematic library". Now: `errorCode: file_not_found`, `view_only_no_author_seat` or `document_not_opened`, and 14 verbs that need the document stop there instead of running against the wrong one (`run_drc`'s refocus and `import_part`'s opens stay best-effort). Projects are exempt (they have no document view).+- `view_only_no_author_seat`: measured on Altium Designer Develop. A second running Altium (another machine) held the workspace's only Author seat; Develop raised "Workspace Unavailable" at launch (acknowledged by the reaper), showed "There are no Author seats available ... view-only mode" behind the warning triangle, kept already-open documents working and refused every new one. The hint says so and gives the fix: close the other Altium cleanly, relaunch this one. No sign-in is involved.+- The SOIC-8 / QFN-24 (9 heatsink vias) / BGA-36 suite now passes on BOTH Altium Designer 26.9.1 and Altium Designer Develop.+ ## 0.2.24 (2026-09-20) - `altium_selftest_script_error` knows both safe outcomes and reports which one it saw in `outcome`. Running 0.2.23 on a second Altium (Altium Designer Develop) showed the same deliberate error does NOT halt there: the engine raises a catchable exception, the agent's own handler answers `ok:false` in about 2 s and the loop never stops (`contained_by_agent`). AD 26.9.1 halts on a breakpoint and needs the bridge's recovery (`halted_and_recovered`). 0.2.23 called the first a failure. A timeout or a dialog left on screen is still the only FAIL. This is also why the 0.2.20 wedge never showed on the machine it was developed on.
package.json+1−1@@ -1,6 +1,6 @@ { "slug": "altium-bridge",- "version": "0.2.24",+ "version": "0.2.25", "type": "app", "description": "Skills for your container so your AI knows how to drive the Altium Designer bridge (altium_* verbs). The bridge runtime itself is the release zip; Adom Bridge loads that.", "tags": [
src/BRIDGE_VERSION+1−1@@ -1 +1 @@-0.2.24+0.2.25
src/bridge.json+1−1@@ -2,7 +2,7 @@ "manifest_version": 1, "name": "altium", "displayName": "Altium Designer",- "version": "0.2.24",+ "version": "0.2.25", "description": "Drive Altium Designer from Adom: a resident DelphiScript agent (eval + the 1,100-command process launcher), the X2 -R command line, UIA over the VCL shell, dialogs by PID, screenshots of every Altium window, and Altium 365.", "homepage": "https://wiki.adom.inc/adom/altium-bridge", "docs": "https://wiki.adom.inc/adom/altium-bridge",