eliza: Open Source AI Interaction & Interfaces

What is eliza?

elizaOS is an open-source, MIT-licensed TypeScript framework and product stack for autonomous AI agents, built for developers who want to run or extend their own agent runtime and for end users who want a personal agent app on web, desktop, and mobile.

What it is

elizaOS is a monorepo that holds the core agent runtime, the Eliza user-facing app, the elizaos CLI, cloud services, native bridges, and first-party plugins. The bootable Linux and Android distributions live in a separate repository, elizaOS/os. The framework is model-agnostic and extended through plugins: @elizaos/core defines AgentRuntime, the canonical types, the message loop, memory and state primitives, and the plugin contracts, while @elizaos/agent assembles a standalone agent with an HTTP backend around that runtime and @elizaos/ui provides the shared React UI. A plugin exports a Plugin object and can register actions, providers, evaluators, services, model handlers, routes, events, tests, and app views.

The concrete problem it solves is the assembly work of a bespoke agent stack. Rather than wiring a chat loop, memory store, connector layer, device bridge, model handler, and user interface by hand, the monorepo ships those as a runtime plus installable plugins, so capabilities such as messaging connectors, calendar and inbox domains, browser and desktop automation, and non-custodial EVM and Solana wallet operations arrive through the same plugin contract. It lives in the TypeScript, Bun, and Node ecosystem, and it replaces the hand-rolled glue that would otherwise sit between a model provider and each application surface.

Key capabilities

AgentRuntime in @elizaos/core supplies the message loop, memory, and state primitives that every plugin plugs into.
The elizaos CLI handles project and plugin scaffolding, upgrade, and deployment.
Local inference through @elizaos/plugin-local-inference, with Eliza-1 registry tiers at 2B, 4B, 9B, and 27B text sizes based on Gemma 4.
Non-custodial EVM and Solana wallet operations bounded by approval boundaries.
Native device bridges for camera, phone, messages, contacts, location, and other platform capabilities.
Eliza app surfaces for web, desktop, and mobile, including chat, voice, memory, knowledge, document workflows, scheduled workflows, and coding-agent orchestration.
Repository command lanes including bun run build, bun run verify, bun run test, bun run test:e2e, and bun run cloud:mock for a local Eliza Cloud stack with mocks.

Who uses it and how

Developers building agents and plugins install the elizaos CLI and follow the developer docs at docs.elizaos.ai.
Contributors read CONTRIBUTING.md and AGENTS.md, which set package scoping, shared development servers, and the evidence required before a change counts as complete.
End users skip the toolchain and open the web app at cloud.eliza.app, or use the downloads at eliza.app/downloads or a published GitHub release.
Teams testing cloud behaviour locally run bun run cloud:mock instead of contacting hosted services.
People who want an entire device to be elizaOS use the installers and target guides in elizaOS/os, covering Linux and Android.

Getting started

The README directs source users to install the Bun and Node versions pinned in package.json, then clone with git clone --filter=blob:none https://github.com/elizaos/eliza.git, enter the directory, and run bun install followed by bun run dev. bun install also prepares submodules and patches, provisions supported host build prerequisites, and builds or verifies the staged desktop libelizainference, while the embedding GGUF downloads automatically during local-inference warmup.

How it compares

The facts provided list no paid products that elizaOS replaces, and they name no competing agent frameworks. On the evidence here, it stands alone in this registry.

When to use it — and when not to

A self-hoster must operate more than an application: the pinned Bun and Node toolchain, host build prerequisites for the staged desktop libelizainference, a runtime-managed GGUF embedding download, and configured model or service providers, with many capabilities gated by operating system, installed plugins, and granted permissions. Anyone who wants a fixed, fully documented capability set across every platform should not assume one here, since package-level READMEs each carry their own support and setup details. The repository also shows 1,069 open issues, which is worth weighing before adopting the framework as a stable foundation.

project readme (upstream, from github) — read inline

elizaOS

Your agentic operating system.

Eliza · Eliza Cloud · elizaOS downloads · Documentation · App catalog

elizaOS is an open-source TypeScript framework and product stack for autonomous AI agents. This monorepo contains the core runtime, the Eliza app, the CLI, cloud services, native bridges, and first-party plugins. The bootable Linux and Android distributions live in the separate elizaOS/os repository.

Choose a starting point

Goal	Start here
Use Eliza	Open the web app, visit Eliza downloads, or use a published GitHub release
Run this repository	Follow Run Eliza from source
Build an agent or plugin	Install the `elizaos` CLI and read the developer docs
Contribute	Read CONTRIBUTING.md and the repository guide in AGENTS.md
Run a whole device as elizaOS	Use the installers and target guides in `elizaOS/os`

Run Eliza from source

The repository pins Bun and Node versions in package.json. Install those versions, then:

git clone --filter=blob:none https://github.com/elizaos/eliza.git
cd eliza
bun install
bun run dev

bun install also prepares submodules and patches, provisions supported host build prerequisites, and builds or verifies the staged desktop libelizainference. The embedding GGUF remains runtime-managed and downloads automatically during local-inference warmup. Fetch archived artifact fixtures explicitly with bun run fetch:archive-artifacts when needed.

Common repository commands:

bun run build       # build the workspace with Turbo
bun run verify      # package parity, dependency, type, lint, and audit gates
bun run test        # repository unit/integration test lane
bun run test:e2e    # end-to-end lane
bun run cloud:mock  # local Eliza Cloud stack with mocks

See AGENTS.md for package scoping, shared development servers, and the evidence required before a change is considered complete.

What is in the stack?

Eliza

Eliza is the user-facing agent app for web, desktop, and mobile targets. Its capabilities are supplied by the runtime and installed plugins, including:

chat, voice, memory, knowledge, and document workflows;
messaging and workspace connectors;
calendar, reminders, inbox, goals, health, and other personal-assistant domains;
browser and desktop automation;
camera, phone, messages, contacts, location, and other native device bridges;
non-custodial EVM and Solana wallet operations with approval boundaries; and
scheduled workflows, coding-agent orchestration, and installable app views.

Availability depends on the operating system, installed plugins, granted permissions, and configured model or service providers. Package-level READMEs document the exact support and setup for each capability.

The framework

The framework is model-agnostic and extended through plugins:

@elizaos/core defines AgentRuntime, the canonical types, the message loop, memory and state primitives, and plugin contracts.
@elizaos/agent assembles a standalone agent and HTTP backend around the core runtime.
@elizaos/app-core provides shared application hosting, API, and platform orchestration for Eliza app targets.
@elizaos/ui contains the shared React UI used by app surfaces.
elizaos is the project and plugin scaffolding, upgrade, and deployment CLI.

A plugin exports a Plugin object. Plugins can register actions, providers, evaluators, services, model handlers, routes, events, tests, and app views. See the plugin component guide and the first-party implementations under plugins/.

Local inference

@elizaos/plugin-local-inference provides the Eliza-1 on-device path. The current Eliza-1 registry contains 2B, 4B, 9B, and 27B text tiers based on Gemma 4, plus local embeddings, speech, vision, and image-generation assets. Hardware detection and model routing select supported backends; after the required assets are downloaded, eligible operations can run without a network connection.

Local inference is not forced on hardware that cannot support it. Eliza can route each model capability to local, direct-provider, or Eliza Cloud backends.

Eliza Cloud

Eliza Cloud is optional. It provides account and authentication services, hosted model routing, application and agent deployment, remote connectivity, and cross-device product services. The local runtime and direct model-provider configuration remain first-class paths.

elizaOS distributions

The standalone elizaOS/os repository owns bootable Linux and AOSP distributions, installers, release manifests, and OS toolchains. This monorepo retains the Eliza application shells and native runtime bridges used by desktop, iOS, Android, and device integrations.

Build with `elizaos`

The beta CLI published from this branch uses the unscoped elizaos package:

bun add --global elizaos@beta
elizaos create my-project --template project
elizaos create plugin-example --template plugin

Projects are deployable workspaces; plugins are reusable capability packages. The packaged templates and their scaffold contracts live in packages/elizaos/templates/.

To embed the runtime directly without the CLI or application host, import @elizaos/core. The scenario runner provides executable integration coverage against a real runtime and, when configured, live models.

Repository map

packages/        runtime, hosts, UI, CLI, docs, cloud, native code, and tooling
plugins/         first-party model, connector, domain, app, and device plugins
scripts/         repository-wide checks, test orchestration, and release tools
patches/         dependency patches applied during installation

Every maintained package or plugin should explain its public surface, scripts, configuration, and local constraints in its own README.md and paired CLAUDE.md / AGENTS.md. Read the nearest package guide before making changes.

Contributing

Open an issue before a non-trivial change and submit work through a pull request against develop. CONTRIBUTING.md defines the coordination, testing, synchronization, and human-verifiable evidence requirements.

Report vulnerabilities privately through the security policy, not a public issue.

License

MIT

Frequently asked questions

Is eliza free to use?

eliza is open source under the MIT licence. There is no licence fee and no seat count — you can self-host it or, where the project offers one, pay a vendor for a managed version instead.

What does eliza do?

Open source agentic operating system

What is eliza written in?

eliza is primarily written in TypeScript. Its source is publicly available at https://github.com/elizaOS/eliza, and it has 19,354 GitHub stars.