Adom Browser Extension - host/native-host.bat

by adom

Your AI's hands in your real, signed-in browser. The Adom Browser Extension (abe) works with both Chrome and Edge: build, drive, and test web apps, and log past vendor walls, in the browser you already use - cookies, SSO, saved logins and captcha trust intact. The nbrowser_* bridge (pup's counterpart) runs in your actual logged-in profile.

Overview Files Skills Discover Packages Releases Dependencies Issues1 Breadcrumbs Pull Requests Activity

Download

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

@echo off
REM Chrome/Edge launch this as the native-messaging host "path". It runs the Node stdio<->bridge pump.
REM
REM Node resolution order (Chrome does NOT inherit adom-desktop's managed-runtime PATH, so we must NOT
REM assume `node` is on PATH on a machine with no system Node install):
REM   1. node-path.txt published by the AD-spawned bridge = the EXACT Node adom-desktop provisioned
REM      (system, or its portable no-UAC copy). Self-healing: the bridge rewrites it on every respawn,
REM      so an AD runtime upgrade never leaves us pointing at a dead node.exe.
REM   2. `node` from PATH (a system install), as a fallback.
set "NODE_EXE="
set "NPFILE=%USERPROFILE%\.adom\bridges\native-browser\node-path.txt"
if exist "%NPFILE%" set /p NODE_EXE=<"%NPFILE%"
if defined NODE_EXE if exist "%NODE_EXE%" (
  "%NODE_EXE%" "%~dp0native-host.js"
  exit /b
)
node "%~dp0native-host.js"