@relictombs/host
v0.2.0
Published
Node.js CLI for hosting Relictombs browser and Android runtimes on a remote machine
Readme
@relictombs/host
Run Relictombs's Electron browser and Android Emulator surfaces on a host machine with Node.js and npx. Bun is not
required on the host machine.
Most users should run the end-to-end setup wizard on the client instead of launching this server CLI directly:
npx --yes @relictombs/[email protected]The wizard selects browser, Android, or both, checks server dependencies such as FFmpeg, and owns the connection and
OpenCode configuration. Direct relictombs-host use is intended for advanced, separately supervised deployments.
npx --yes @relictombs/[email protected] --android-avd OpenTUI_Pixel_8_API_36The command prints the authenticated control endpoint, media endpoint, and session token as JSON. Plaintext sockets bind to loopback; connect another machine through an SSH or trusted VPN tunnel.
Usage: relictombs-host [options]
Options:
--port <0-65535> Control WebSocket port (default: dynamic)
--media-port <0-65535> Media WebSocket port (default: dynamic)
--android-avd <name> Launch the named Android Virtual Device
--no-browser Do not launch Electron (requires --android-avd)
--help Show this helpNode.js 24 or newer is required. Electron is installed as an npm dependency. Android hosting additionally requires
an installed Android SDK, emulator, and named AVD. FFmpeg must be available on PATH for remote media encoding.
Contributor verification
From the repository root, use the app's domain-oriented workspace path:
bun run --cwd apps/host check
bun run --cwd apps/host test:packed