eliza

Create a JSON file with required fields: name, bio, lore, messageExamples, style.all, and modelProvider. Include at least 5 message examples to teach the model your agent's tone and response length, then start it with elizaos start --characters your-file.json.

Implement the Plugin interface from @elizaos/core with actions, providers, and evaluators. Each action needs a validate function, a handler, and few-shot examples so the LLM knows when to invoke it, then register the plugin in your character's plugins array.

Yes, elizaOS includes clients for Discord, Telegram, Twitter, and Farcaster. Add the platform to the character's clients array and set the required environment variables such as DISCORD_API_TOKEN or TELEGRAM_BOT_TOKEN.

This happens when you switch embedding models after memories are already stored, since old embeddings have different dimensions. Delete the SQLite database file or truncate the memories table in PostgreSQL, then restart the agent.

Bun is the required package manager for the elizaOS monorepo and strongly recommended for all projects. Running pnpm or yarn install in the monorepo produces broken lock files, and mixing package managers causes module resolution failures.

Generic responses usually mean too few messageExamples or vague bio and style entries. Add 5-10 diverse conversation examples, make style rules specific, and verify the character JSON parses correctly and is loaded via the --characters flag.