Your agentic operating system.
<a href="https://eliza.app">Homepage</a> ·
<a href="https://app.elizacloud.ai">Web app</a> ·
<a href="https://os.elizacloud.ai">Install the OS</a> ·
<a href="https://docs.elizaos.ai/">Docs</a> ·
<a href="https://plugins.elizacloud.ai">App catalog</a>
elizaOS is an open-source, local-first operating system for AI agents. Two parts:
The agent, your data, and the models all run on your device. Eliza Cloud is optional — add it for hosted inference, sync, and deploys.
| Platform | How |
|---|---|
| Web | Open app.elizacloud.ai |
| Desktop — macOS · Windows · Linux | Download from GitHub Releases |
| iOS · Android | App Store · Play · sideload |
Run from source:
git clone --filter=blob:none https://github.com/elizaos/eliza.git
cd eliza
bun install
bun run dev # API + the Eliza app UI
To run a whole device as elizaOS instead, see elizaOS — the operating system.
The app ships with:
Eliza can run the whole pipeline on your device via Eliza-1, the on-device model family (Gemma-4):
Pick a model in Settings → Model Routing and it downloads and pins; from then on it works with no network.
elizaOS runs apps, not just an agent. An app is a plugin that adds a surface inside Eliza; the runtime installs, launches, and tracks it like real software, and it survives restarts.
packages/registry, plus any npm package tagged elizaos.plugin-browser, plugin-documents, plugin-phone, plugin-task-coordinator.packages/os is the real, bootable distribution. Downloads and hardware are at os.elizacloud.ai.
packages/os/linux) — boots a full desktop with Eliza built in from a USB stick. amd64 · arm64 · riscv64.packages/os/android) — Eliza is the system launcher and assistant, on Pixel-class devices.The OS is bootable today; full device certification and production update channels are in progress — see the per-target READMEs for status.
Optional managed backend for going beyond one device. Never required — local-only is first-class. It adds:
The runtime is open source and yours to extend. Start with the CLI:
bun add -g elizaos@beta
elizaos create my-app --template project # a deployable app workspace
elizaos create my-plugin -t plugin # a runtime plugin (action/provider/service)
The runtime is model-agnostic (OpenAI, Anthropic, Gemini, Grok, Llama, local Eliza-1, …) and extended through a small set of primitives:
@elizaos/core (packages/core) — the agent loop, plugin model, and message/memory/state primitives.@elizaos/agent (packages/agent) — AgentRuntime, the plugin loader, and the default plugin map.@elizaos/app-core (packages/app-core) — the API + dashboard host that runs agents.elizaos (packages/elizaos) — the CLI: create, info, upgrade.A plugin exports a Plugin that registers actions (what the agent does), providers (prompt context), services (long-lived singletons), and evaluators (post-response work). Import @elizaos/core directly to use the runtime with no CLI or UI — see packages/examples and the evaluation suites in packages/benchmarks. Full guides: docs.elizaos.ai.
bun install # workspace install
bun run install:light # skip the large artifact download when disk or time is tight
bun run dev # API + Vite UI for apps/app
bun run build # turbo build across the workspace
bun run test # full test suite
bun run cloud:mock # boot the local cloud backend stack with mocks
The repo is self-contained — runtime, CLI, dashboard, native OS forks, cloud backend, and first-party plugins all live here. Every package carries its own README.md; read it before working inside. Tree map: AGENTS.md.
Contributions welcome. Open an issue before sending a non-trivial PR. Before
opening a PR, read CONTRIBUTING.md and the evidence standard
in AGENTS.md; frontend-testable changes need screenshots (JPG), an
MP4 video walkthrough, logs, and any relevant real-LLM trajectories attached
inline in the PR itself. Agents and maintainers working from a GitHub Project
board use the coordination workflow in CONTRIBUTING.md before
claiming kanban work. Active MVP work is coordinated on the
LifeOps Personal Assistant MVP board
and in Discussions; in-flight
design docs live in
packages/docs/ongoing-development/.
To report a security vulnerability, follow SECURITY.md; do not open a public issue.
MIT — see LICENSE.
$ claude mcp add eliza \
-- python -m otcore.mcp_server <graph>