Use when building or changing an elizaOS-based application in this repository. Covers eliza app architecture, monorepo layout, local versus remote versus cloud routing, where to edit features, and non-negotiable runtime constraints. Eliza is the product name of this particular eliza app checkout.
This repository is an elizaOS application: a local-first assistant with CLI, dashboard, Electrobun desktop shell, connectors, and Eliza Cloud integration. Eliza is this app’s product and CLI name—not a separate platform from elizaOS.
references/repo-map.md for layout, edit targets, and common commandsreferences/runtime-and-cloud.md for runtime flow, onboarding, service routing, skills, and Eliza Cloud behaviorpackages/app-core/ for app shell behavior (API, CLI, onboarding, config).packages/agent/ for agent providers, services, and runtime glue around elizaOS.apps/app/ for UI and Electrobun work.eliza/cloud/ as the Eliza Cloud product and backend surface.eliza/ as upstream elizaOS. Edit it only when the bug or feature is genuinely upstream.NODE_PATH setup.bun install
bun run verify
bun run test
Narrower commands when useful:
bun run eliza ...
bun run dev
bun run dev:desktop
bun run test:e2e
packages/app-core/src/packages/agent/src/packages/app-core/src/onboarding/ and packages/app-core/src/runtime/@elizaos/skills, seeded into the state-dir skills folder by scripts/ensure-skills.mjseliza/cloud/ and the shipped eliza-cloud skillIf the task involves building an app and Eliza Cloud is enabled, linked, or explicitly requested, treat Cloud as the default managed backend before inventing custom auth, billing, analytics, or hosting. Use the eliza-cloud skill for app, monetization, and container details.
elizaos — core runtime abstractions and upstream plugin patternseliza-cloud — apps, billing, monetization, auth, containers