Quickstart

Install Host first, then plan an Agent.

Alpha path: Host on your computer → pair your account → dry-run an approved Agent recipe from Account → use the app or local web surfaces. Real blank-machine Agent install is not shipped yet.

1. Host 2. Pair 3. Agent dry-run 4. Use tools

Start with Host Open account dry-run

Alpha boundary

Real blank-machine Agent install is not shipped. Account dry-run validates an approved recipe only — no download, no Host mutation.

Install the Host on your computer

Host comes first. It keeps your computer available for approved phone and web requests. Prefer the termee CLI (build → install → setup/connect). Full upgrade/reinstall steps are in the docs.

make build-linux-host
# install dist/termee-linux-* as ~/bin/termee, then:
termee setup --relay=wss://staging.termee.ai/ws --code=PASTE --start
termee status

Host upgrade / install guide Host CLI reference

Future public installer placeholder: curl -fsSL https://termee.ai/install.sh | bash. That one-liner is not the Alpha path yet. Local relay/host demo: make run-relay / make run-host-terminal.

Pair your phone or web account

Create or sign in to a web account, then pair so your user owns the Host. In the local alpha, the Relay can create or accept a pairing code.

Create web account Sign in

curl -X POST http://localhost:8080/pair/codes

Pairing codes are short-lived. If pairing fails, create a new code and make sure the Relay and Host are both running.

Dry-run an approved Agent recipe

After the Host is paired, open Account, choose a Host and an allowlisted recipe (for example Hermes), and click Run install dry-run.

Alpha only validates the plan: source URL shape, digest format, platform, and registration steps. It does not download, execute installers, or mutate App Entry config.

Open account dry-run See setup path on landing

Real install (dry_run=false) is rejected until Beta opt-in. Do not expect a blank machine to receive a remote Agent binary from this Alpha flow.

Use the app or an existing entry

Pick an App Entry already on the Host and send a request. Public store links are placeholders while the mobile app is in alpha. For local Android testing, run the Flutter app from `apps/mobile`.

Android local run

Flutter and Android local run

Run the mobile app against local Relay.

Use the Flutter workspace in `apps/mobile`. Point the app to your local Relay URL with the existing dart-define flow documented in the mobile README.

make run-relay
make run-host-terminal
make flutter-run-emulator

Use `10.0.2.2` for Android emulator access to your Mac's localhost. Use your Mac LAN IP for a physical Android device.

Web account links

Open the current local web surfaces.

Create account /web/register.html Sign in /web/login.html Account + Agent dry-run /web/account.html

Account dry-run posts to `POST /api/account/install-jobs` with `dry_run=true`. Ops is isolated at /web/ops/login.html (not linked from user pages).

Help

Common setup notes

Why Host before Agent?

Remote Agent install targets a paired Host. Without Host first, there is nowhere safe to validate or (later) register an Agent recipe.

Does Alpha install Agents on a blank machine?

No. Alpha only dry-runs approved recipes from the account page. Real download, install, and App Entry registration wait for Beta opt-in.

The phone cannot connect.

Check that Relay is running on port 8080, that the app points at the right URL, and that the Host is paired.

The account disappears after restart.

Memory-mode accounts disappear when Relay restarts without Postgres. Use Docker Compose with Postgres for a persistent local account.

Where do I change plans locally?

Open Ops, enter `dev-ops-token`, and update the alpha plan metadata. This does not start real billing.