{
  "version": "1.0",
  "type": "repository",
  "interval": "day",
  "date": "2025-06-26",
  "generatedAt": "2026-05-13T23:41:49.224Z",
  "sourceLastUpdated": "2026-05-13T23:41:49.224Z",
  "contentFormat": "markdown",
  "contentHash": "2159f0938fccb6eed98b998aa484aca198fb3981a64e60612d20d80198e35df0",
  "entity": {
    "repoId": "elizaos/eliza",
    "owner": "elizaos",
    "repo": "eliza"
  },
  "content": "# elizaos/eliza Daily Update (Jun 26, 2025)\n\n## OVERVIEW \nToday's development focused on enhancing model selection flexibility, improving the CLI's user experience for environment variable prompts, and addressing numerous bug fixes across various components, including plugin functionality, client-side UI, and core infrastructure.\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### Enhanced Model and Embedding Selection\nSignificant progress was made in expanding model provider support. Users can now select OpenRouter for both language and embedding models, improving flexibility and addressing community requests. Additionally, Ollama embedding selection was refined, preventing unnecessary plugin loading.\n- [#5264](https://github.com/elizaos/eliza/pull/5264)\n- [#5285](https://github.com/elizaos/eliza/pull/5285)\n\n### Improved CLI User Experience and Plugin Management\nThe CLI's environment variable prompting experience was significantly improved by replacing `readline` with a more user-friendly interface. Plugin management also saw fixes, including ensuring the \"hello world\" plugin returns a response and restricting plugin removal to the 'X' icon.\n- [#5291](https://github.com/elizaos/eliza/pull/5291)\n- [#5296](https://github.com/elizaos/eliza/pull/5296)\n- [#5290](https://github.com/elizaos/eliza/pull/5290)\n\n### Core Infrastructure and Client-Side Bug Fixes\nSeveral critical bugs were resolved across the core system and client. This includes fixing group creation success handling, addressing Docker post-install hook issues, correcting foreign key constraints in the SQL plugin, and resolving agent panel loading problems. Core package imports for Bun were also fixed.\n- [#5293](https://github.com/elizaos/eliza/pull/5293)\n- [#5289](https://github.com/elizaos/eliza/pull/5289)\n- [#5287](https://github.com/elizaos/eliza/pull/5287)\n- [#5282](https://github.com/elizaos/eliza/pull/5282)\n- [#5284](https://github.com/elizaos/eliza/pull/5284)\n\n## NEWLY OPENED PULL REQUESTS\n- [#5299](https://github.com/elizaos/eliza/pull/5299): A proof-of-concept draft for a new workflows plugin has been initiated.\n- [#5288](https://github.com/elizaos/eliza/pull/5288): This PR proposes implementing a server factory pattern and enhancing the overall server structure.\n\n## CLOSED ISSUES\n\n### CLI Plugin Creation Fix\nAn issue where attempting to create a new plugin within the `./packages` directory resulted in a \"Workspace name already exists\" error was identified and promptly closed.\n- [#5292](https://github.com/elizaos/eliza/issues/5292)\n\n## NEW ISSUES\n\n### CLI Input Consistency\nA new issue was opened to standardize CLI input methods by migrating all remaining prompts to use `@clack/prompts` for consistency across the command-line interface.\n- [#5295](https://github.com/elizaos/eliza/issues/5295)\n\n## ACTIVE ISSUES\n\n### Character Save Size Limit\nThe issue [#5268](https://github.com/elizaos/eliza/issues/5268) reports an \"Error 500: request entity too large\" when attempting to save a large character file (~150kb). The latest comment from @lalalune requests an increase in the file size limit to 100MB for characters and a regression test to prevent future occurrences.\n\n### Split Personality Due to Username Change\nIssue [#105](https://github.com/elizaos/eliza/issues/105) describes a \"split personality\" problem where a GitHub username change results in two profiles and split contributions. @0xCardiE suggests using GitHub's internal user ID as the base instead of the username to ensure consistent tracking regardless of username changes. @META-DREAMER notes that this would require updating the database to link multiple identities to a single user and handling complex edge cases like multiple username changes, as the GitHub username is currently the primary key."
}