Installation

EdgePlane has three components:

Component	Purpose
edgeplane	Operator CLI and agent launcher — your primary interface
edgeplaned	Headless executor daemon — manages agent subprocesses and secrets brokering
edgeplane-tower	HTTP server backing the REST/SSE API — missions, tasks, approvals

Install Script (recommended)

The install script downloads a prebuilt binary and falls back to a source build if no binary is available for your platform.

Linux / macOS (quickest path):

curl -fsSL https://edgeplane.ai/install.sh | bash

Or directly from the repo:

bash <(curl -fsSL https://raw.githubusercontent.com/RyanMerlin/edgeplane/main/scripts/install-edgeplane.sh)

Windows (PowerShell):

irm https://raw.githubusercontent.com/RyanMerlin/edgeplane/main/scripts/bootstrap-edgeplane.ps1 | iex

By default installs to ~/.local/bin/edgeplane. Ensure ~/.local/bin is on PATH.

Build from Source

Requires a working Rust toolchain (stable).

git clone https://github.com/RyanMerlin/edgeplane.git
cd edgeplane

# Build and install edgeplane CLI
cd crates/edgeplane && cargo build --release
cp target/release/edgeplane ~/.local/bin/edgeplane

# Build and install edgeplaned daemon
cd ../edgeplaned && cargo build --release
cp target/release/edgeplaned ~/.local/bin/edgeplaned

# Build and install edgeplane-tower server
cd ../edgeplane-tower && cargo build --release
cp target/release/edgeplane-tower ~/.local/bin/edgeplane-tower

Running the Control Plane

edgeplane-tower is the API server all agents and operators talk to. Migrations run automatically on startup.

edgeplane-tower --serve --bind 0.0.0.0:8008

Verify it’s up:

curl http://localhost:8008/health

Environment Variables

Variable	Purpose	Default
EP_BASE_URL	Control plane HTTP base URL	http://localhost:8008

You can set this in your shell profile or pass it inline:

export EP_BASE_URL="https://edgeplane.example.com"

Authentication

EdgePlane uses three auth mechanisms — no static EP_TOKEN is required:

Auth mode	When to use	How
OIDC (interactive)	Operators, interactive use	edgeplane auth login — browser flow, issues a session token
Node JWT (machine)	Daemons, edgeplaned	edgeplane agent node register --node-name <name> — JWT stored at /etc/edgeplane/node.json
Service account	CI, programmatic	mcs_sa_* tokens — created via API, passed as Bearer

Verify

edgeplane --version
edgeplane health --json

Next Steps

• Quick Start — run your first agent in 5 minutes
• Agent Setup — connect Claude Code, Codex, or Gemini CLI