Native install

What this is for. Native install is one of three ways to run EYAS (native / Docker / Kubernetes). Pick native when you want Bun on the machine, host CLIs (claude, grok, kimi) on the same PATH, and the fewest moving parts. Default UI: http://localhost:3100 — not 3000.

When to use it

A developer laptop or a single VPS with Bun 1.x (or Node 22+).
You want host CLI providers without wrapping them in a container.
You are restoring a backup onto a matching --version install.

Typical workflow

Install Bun 1.x (or Node 22+).
git clone + bun install or run scripts/install.sh (macOS/Linux) / scripts/install.ps1 (Windows).
Add bin/ to PATH so eyas works.
./bin/eyas start (background) or ./bin/eyas serve (foreground logs).
Open http://localhost:3100 and complete the setup wizard.

Features

Methods

git clone + bun install + ./bin/eyas start
scripts/install.sh (macOS/Linux)
scripts/install.ps1 (Windows)

One-line:

curl -fsSL https://raw.githubusercontent.com/eyssen/eyas/main/scripts/install.sh | bash

Non-interactive: append bash -s -- --yes. Pin a release: --version 0.8.16-beta.

Pinned version restore: installer --version x.y.z-beta matching the backup version.

Claude Code on the host

Install Claude Code (claude) on the same PATH as EYAS, or set EYAS_CLAUDE_CODE_BIN to its absolute path — a service started by launchd or systemd often has a shorter PATH than your shell. The provider is available only once that binary is signed in (claude auth status). eyas doctor shows which binary EYAS runs on its Claude Code runtime line. See Providers — Claude Code runtime.

Workspaces on a source install

A source install run from a git clone keeps its data directory inside that checkout, so conversation workspaces go to your user’s application-data directory instead (for example ~/Library/Application Support/eyas/<instance>/workspaces on macOS). See Configuration — Conversation workspaces.