OR3 Connect

This package contains the advanced OR3 Connect bootstrap and the local Intern launcher. Remote Connect is not a managed-Cloud launch feature yet: the old https://or3.chat default is intentionally disabled. See the Connect release status page for the immutable package and binary-asset contract.

Start local OR3 Intern without Go or a PATH edit with the coordinated immutable package and binary release:

npx @or3/[email protected] intern

For a source checkout, you can install the same CLI directly:

./scripts/install-cli.sh
or3-intern setup
or3-intern chat

For a one-off source run, go run ./cmd/or3-intern ... remains available.

To connect an installed external agent, choose its runtime and an explicitly verified staging or self-hosted endpoint:

or3-intern connect openclaw --cloud-url https://staging.example.test
or3-intern connect hermes --cloud-url https://staging.example.test

The command checks the runtime, asks before installing or changing anything, opens the normal OR3 browser approval, configures the loopback API, and keeps the named Cloudflare tunnel running as a background service. Runtime-owned model/provider onboarding still happens in OpenClaw or Hermes first.

With Bun:

bunx @or3/connect

The bootstrap downloads checksum-verified or3-intern and, for remote Connect, cloudflared release assets into ~/.or3/bin, then opens OR3's browser device authorization. Downloads are streamed, deadline-bounded, and installed atomically under a shared lock. A valid cached install continues to work offline.

Manage the connection from any fresh terminal:

npx @or3/connect status
npx @or3/connect doctor
npx @or3/connect disconnect

The bootstrap never asks for an API token or puts tunnel credentials in process arguments.

Those management commands operate on a previously configured advanced connection. Local/offline OR3 remains account-free; managed Cloud Connect is withheld until its public staging flow is proved.