Eaon Code is a full-screen coding agent for the terminal, with multi-provider model access, durable sessions, and an extension system for adapting it to a project or team.
What Eaon Code includes
- Plan mode (
/plan) restricts the agent to read-only exploration and shows a small mode indicator.
- Swarm mode (
/swarm) makes the parent orchestrate 2–6 named specialist sub-agents in parallel, then reconcile and verify their work.
- Observable sub-agents run in isolated sessions with a persistent live activity view. Open
/agents to inspect conversations, steer work, or press x twice to stop a run; completed results expand with Ctrl+O.
- Built-in browser control is powered by BetterWright. Eaon can browse and interact with live pages in a persistent, policy-guarded browser without a separate extension install.
- Full-screen TUI by default, with Amber as the default theme and separate dark- and light-theme lists in the theme picker and setup.
- Eaon configuration paths use
~/.eaon/agent and project .eaon/ directories. Existing .pi configuration directories remain usable as a compatibility path; Eaon Code does not move or delete them.
The core agent also includes file and shell tools, streaming responses, session branching and compaction, provider login and API-key auth, skills, prompts, extensions, themes, package management, and print/JSON/RPC/SDK interfaces.
Browser control
Eaon Code includes BetterWright's official Pi browser integration as a built-in feature. The browser tools are ready in the agent without installing BetterWright as a separate extension. BetterWright keeps a browser session across calls and applies its network and browser policies while Eaon navigates and interacts with pages.
On first use, install BetterChromium once with Bun 1.4 or newer:
bunx betterwright setup
See the BetterWright setup guide and package page for the integration details.
Install
One line:
curl -fsSL https://raw.githubusercontent.com/eaonlabs/eaon-code/main/install.sh | bash
The installer clones the repository into ~/.local/share/eaon-code and builds it with Bun. It needs Git and Bun on PATH.
The CLI command is eaon-code:
export ANTHROPIC_API_KEY=sk-ant-... # or another provider
eaon-code
Or launch and log in interactively:
eaon-code
/login
Local run from a private clone (no publish required):
git clone https://github.com/eaonlabs/eaon-code.git
cd eaon-code
bun install --frozen-lockfile --ignore-scripts
bun run try:local -- --help # Build the checkout and run its CLI without installing it
Packages
New installs use ~/.eaon/agent/ for user settings, credentials, sessions, and resources, and .eaon/ for project-local settings and resources. Existing .pi directories are still recognized when no corresponding .eaon directory exists, so upgrading does not strand or rewrite existing data.
Permissions & containerization
Eaon Code does not include a built-in permission system for restricting filesystem, process, network, or credential access. By default it runs with the permissions of the user and process that launched it.
If you need stronger boundaries, containerize or sandbox it. See packages/coding-agent/docs/containerization.md for three patterns:
- Gondolin extension: keep the agent and provider auth on the host while routing tools and
! commands into a local Linux micro-VM.
- Plain Docker: run the whole process in a local container.
- OpenShell: run the whole process in a policy-controlled sandbox.
Development
bun install --frozen-lockfile --ignore-scripts # Install all dependencies without running lifecycle scripts
bun run build # Refresh model data, then build all packages
bun run try:local -- --help # Build and run this checkout without installing it
bun run build:offline # Rebuild using existing model data without network access
bun run check # Lint, format, and type check
./test.sh # Run tests (skips LLM-dependent tests without API keys)
See CONTRIBUTING.md and AGENTS.md.
License
MIT
