eliza-app-development

name	eliza-app-development
description	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.

eliza app development

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.

Read These References First

• references/repo-map.md for layout, edit targets, and common commands
• references/runtime-and-cloud.md for runtime flow, onboarding, service routing, skills, and Eliza Cloud behavior

Editing Heuristics

• Prefer packages/app-core/ for app shell behavior (API, CLI, onboarding, config).
• Prefer packages/agent/ for agent providers, services, and runtime glue around elizaOS.
• Prefer apps/app/ for UI and Electrobun work.
• Treat eliza/cloud/ as the Eliza Cloud product and backend surface.
• Treat eliza/ as upstream elizaOS. Edit it only when the bug or feature is genuinely upstream.

Hard Constraints

• Do not remove NODE_PATH setup.
• Do not remove the Bun exports patch.
• Do not remove Electrobun startup error guards.
• Keep Node and Bun paths working.

Repo Workflow

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

Where to Look First

• Product and runtime behavior: packages/app-core/src/
• Prompt, provider, and skill plumbing: packages/agent/src/
• Onboarding and routing: packages/app-core/src/onboarding/ and packages/app-core/src/runtime/
• Shipped default skills: bundled in @elizaos/skills, seeded into the state-dir skills folder by scripts/ensure-skills.mjs
• Eliza Cloud backend or monetization: eliza/cloud/ and the shipped eliza-cloud skill

Cloud Default

If 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.

When the app clearly uses AI inference, treat it as a Cloud-backed monetized app even if the user does not say "monetized", "OAuth", or "domain". Chatbots, companions, assistants, generators, summarizers, and model-backed tools must use Eliza Cloud app auth and /api/v1/apps/{id}/chat through the local app proxy. Do not satisfy these requests with local canned responses. If the request is ambiguous about whether AI/auth is needed, ask one concise clarification before building.

Related Skills

• elizaos — core runtime abstractions and upstream plugin patterns
• eliza-cloud — apps, billing, monetization, auth, containers