Quick Start
This guide walks you from zero to a running agent session. Assumes you’ve completed Installation.
1. Start the Control Plane
Section titled “1. Start the Control Plane”If you’re running locally:
edgeplane-tower --bind 127.0.0.1:8008If you have a deployed instance, point the CLI at it:
export EP_BASE_URL="https://edgeplane.example.com"2. Authenticate
Section titled “2. Authenticate”edgeplane auth login # opens a browser OIDC flow → writes ~/.edgeplane/session.jsonedgeplane auth whoami # confirm identity and token expiryAfter auth login succeeds, edgeplane picks up the session automatically from ~/.edgeplane/session.json — no further credential management needed.
3. Verify the Connection
Section titled “3. Verify the Connection”edgeplane health --jsonedgeplane status # shows auth, runtime, and workspace lease statushealth --json reports {"ok": true, ...} when the tower is reachable. status shows auth, runtime, and workspace context (no top-level ok field). If health fails, confirm EP_BASE_URL is set and the tower is reachable.
4. Launch an Agent
Section titled “4. Launch an Agent”edgeplane run claude # Claude Code with EdgePlane MCP wired inedgeplane run codex # OpenAI Codex CLIedgeplane run gemini # Google Gemini CLIedgeplane run validates your environment, fetches the onboarding manifest, and injects EdgePlane as an MCP server before handing off to the agent binary. No manual MCP config required.
5. Explore the Fleet
Section titled “5. Explore the Fleet”edgeplane tuiThe TUI gives you a full-screen fleet view. Key bindings: a — agents, m — domains, f — live event feed, s — secrets, c — config.
What’s Next
Section titled “What’s Next”- Agent Setup — per-agent config, ACP runtime, profile loading
- Concepts: Domains, Missions & Tasks — the organizational model
- Guides: Deployment — running EdgePlane in production