Skip to main content
Connecting a BYO machine is three moves: create the machine record, run a daemon on the computer, and grant the machine to the projects that should use it. The dashboard’s Connect a machine dialog, the CLI’s omnara machines create-local, and the API’s connect endpoint each do the first two in one step, and can attach project grants at the same time.

Create the machine record

A machine starts as a record in the control plane — the daemon attaches to it later using a machine token. The token is shown only once, so save the complete value and treat it as opaque.
With All projects selected in the project switcher, open Machines and click Connect machine. In the Connect a machine dialog, set the machine name — this is what agent configs reference as machine_name, so pick something stable — and optionally pick projects under Share with. Click Connect machine; the next screen shows the machine token alongside the install command for the daemon install step below.
display_name is what agent configs reference as machine_name, so pick something stable. cwd, env, and secret_env are execution defaults for every process on this machine; secret_env injects secret values by sec_… reference at process launch, so credentials never sit in the machine record.

Install the daemon

omnara machines create-local runs this step for you. Otherwise, on the target computer, run the installer and paste the machine token when prompted:
The installer supports macOS and Linux on amd64 and arm64. It installs omnarad under ~/.omnarad and registers it as a user service using systemd on Linux or launchd on macOS. When no launchd or systemd user service manager is available, omnarad runs in the foreground instead; press Ctrl-C to stop it and run omnarad start to launch it again. The daemon connects outbound and updates itself. Manage it with omnarad start|stop|restart|status, or remove it with omnarad uninstall. Once the daemon connects, the machine appears online.

Grant the machine to a project

Machines are org-level; a project’s agents can only target machines granted to that project.
If you didn’t share the machine while connecting it, select All projects in the project switcher, find its row under Machines, click Share with project, and select the project.From a project, open its Machines page and click Share machines. The page’s Shared machines table lists existing shares; click Stop sharing to revoke one.
With the grant in place, configs in that project can reference the machine:

Manage a machine

The dashboard’s Machines page (with All projects selected in the project switcher) shows every machine you can access. omnara machines list and the org API provide the same view and explain whether access comes from your org role, having created the machine, or a project grant. The project API lists only machines that project’s agents can use. You can update cwd, env, and secret_env with omnara machines update {machine-id} or through the API; machine names cannot be changed. Machine tokens can be created, listed, and revoked through the API. Deleting a BYO machine disconnects its daemon, revokes its tokens, removes its grants, and releases its agent bindings. In the dashboard, open the machine’s row menu and click Delete; in the CLI, run omnara machines delete {machine-id}.