{ "interval": { "intervalStart": "2025-05-12T00:00:00.000Z", "intervalEnd": "2025-05-13T00:00:00.000Z", "intervalType": "day" }, "repository": "elizaos/eliza", "overview": "From 2025-05-12 to 2025-05-13, elizaos/eliza had 21 new PRs (7 merged), 1 new issues, and 11 active contributors.", "topIssues": [ { "id": "I_kwDOMT5cIs62Hsv6", "title": "Cannot find module '@elizaos/core' or its corresponding type declarations.\",", "author": "BinaryBluePeach", "number": 4536, "repository": "elizaos/eliza", "body": "**It has 3 problems. When I clicked on Agent, source, and then default character it showed this.** I would appreciate some help. Thanks!\n\n\"owner\": \"typescript\",\n\t\"code\": \"2307\",\n\t\"severity\": 8,\n\t\"message\": \"Cannot find module '@elizaos/core' or its corresponding type declarations.\",\n\t\"source\": \"ts\",\n\t\"startLineNumber\": 1,\n\t\"startColumn\": 51,\n\t\"endLineNumber\": 1,\n\t\"endColumn\": 66\n\nowner\": \"typescript\",\n \"severity\": 8,\n \"message\": \"Cannot find type definition file for 'node'.\\n The file is in the program because:\\n Entry point of type library 'node' specified in compilerOptions\",\n \"source\": \"ts\",\n \"startLineNumber\": 1,\n \"startColumn\": 1,\n \"endLineNumber\": 1,\n \"endColumn\": 2\n\n\n\"owner\": \"typescript\",\n \"severity\": 8,\n \"message\": \"Cannot find type definition file for 'jest'.\\n The file is in the program because:\\n Entry point of type library 'jest' specified in compilerOptions\",\n \"source\": \"ts\",\n \"startLineNumber\": 1,\n \"startColumn\": 1,\n \"endLineNumber\": 1,\n \"endColumn\": 2\n\n![Image](https://github.com/user-attachments/assets/316e0faa-a12b-4881-824d-fff85271232f)", "createdAt": "2025-05-12T02:42:08Z", "closedAt": null, "state": "OPEN", "commentCount": 2 }, { "id": "I_kwDOMT5cIs6xKrBN", "title": "Twitter interactions fetched but reactions not implemented yet", "author": "tcm390", "number": 4181, "repository": "elizaos/eliza", "body": "Currently, we fetch the interactions for Twitter, but we haven't implemented reactions for those interactions yet:\n\nhttps://github.com/elizaOS/eliza/blob/9179074304d8c069004baa05e55c632898e06601/packages/plugin-twitter/src/interactions.ts#L308", "createdAt": "2025-04-04T13:18:50Z", "closedAt": "2025-05-12T18:34:53Z", "state": "CLOSED", "commentCount": 0 }, { "id": "I_kwDOMT5cIs6xKo89", "title": "Twitter space is not working", "author": "tcm390", "number": 4180, "repository": "elizaos/eliza", "body": "I'm getting the following dyld error when trying to use space in twitter plugin\n\n\"Image\"\n\nIt seems like this might be caused by Bun not being fully compatible with wrtc.\n\n", "createdAt": "2025-04-04T13:15:32Z", "closedAt": "2025-05-12T18:34:54Z", "state": "CLOSED", "commentCount": 0 }, { "id": "I_kwDOMT5cIs6tLQeS", "title": "Fix Building a Social AI Agent in 15 Minutes", "author": "552020", "number": 3880, "repository": "elizaos/eliza", "body": "**Describe the bug**\n\nOn the page https://elizaos.github.io/eliza/docs/tutorials/nader_tutorial_15min/\n\n1. The embedded video by Nader Dabit [How to Build a Social AI Agent in 15 minutes with X, Telegram, Onchain Capabilities | Full Tutorial](https://www.youtube.com/watch?v=6PZVwNTl5hI&ab_channel=NaderDabit) seems to be outdated. \n2. The textual description below the video, to setup the Twitter Agent, doesn't follow the video and it's outdated as well. \n\n**To Reproduce**\n\n1. Follow the video and check if it works\n2. Follow the description below the video and check if it works\n\n**Expected behavior**\n\nA tutorial that let developer to build a Social Agent in 15 minutes\n\n**Screenshots**\n\nN/A\n\n**Additional context**\n\nI'm happy to help to fix it, but I'm still working my way through the documentation to understand how to implement the Twitter/X agent. \n\n---\n\nWhat is also a little bit confusing is that in the docs Twitter is described as a Client ...\n\n\"Image\"\n\n\n... but the link brings us to the repo plugins/twitter-client ...\n\n\n\"Image\"\n\nSo apparently some of the plugins are clients but not all plugins are client. \n\n---\n\nThe doc for the plugins page seems also to be outdated since it uses the package `elizaos-plugins/plugin-twitter`, that probably doesn't exist anymore. \n\n\"Image\"\n\n---\n\nIn the README of the twitter plugin, this snippet is suggested for installation but it's not clear in which file it should be places. I suppose in `src/index.ts` \n\n\"Image\"\n\n---\n\n### **Nader Dabit** approach\n\nNadir is creating a new file `mainCharacter` file in `/agent/src` https://github.com/dabit3/ai-agent-cognitivedriftt/blob/main/agent/src/mainCharacter.ts. \n```\nimport { Character, ModelProviderName, Clients } from \"@ai16z/eliza\";\nimport { defaultCharacter } from './defaultCharacter.ts'\n\nexport const mainCharacter: Character = {\n ...defaultCharacter,\n clients: [Clients.TWITTER],\n modelProvider: ModelProviderName.CLAUDE_VERTEX,\n name: \"cognitivedriftt\",\n}\n```\n1. Eliza has been moved from `@ai16z/eliza`\n2. The Twitter Client is an autonomous plugin now. So ` clients: [Clients.TWITTER],` is not valid anymore. \n\n### Approach in the description below the video\n\n```\nimport { DefaultCharacter } from \"./defaultCharacter\";\nimport { clients } from \"../globalClients\";\n\nexport const mainCharacter = {\n ...DefaultCharacter,\n clients: { twitter: clients.twitter },\n modelProvider: modelProviders.anthropic,\n};\n```\n\nThe `globalClinets` file doesn't exist anymore anywhere in the Eliza repo and it doesn't seem to fit the way we are supposed to integrate the Twitter Plugin/Client as described in the README of https://github.com/elizaos-plugins/client-twitter", "createdAt": "2025-03-09T12:51:15Z", "closedAt": "2025-05-12T18:34:55Z", "state": "CLOSED", "commentCount": 0 }, { "id": "I_kwDOMT5cIs61QKf3", "title": "pglite log entry unicode escape error", "author": "plvo", "number": 4457, "repository": "elizaos/eliza", "body": "**Describe the bug**\n\nWhen attempting to create a log entry with the `useModel:TEXT_LARGE` type, the operation fails due to an `unsupported Unicode escape sequence` error. This results in the log entry not being created, impacting the reliability of our tracking system.\n\n**To Reproduce**\n\nSteps to reproduce the behavior:\n\n1. Trigger a model usage event of type `useModel:TEXT_LARGE`.\n2. Ensure that the payload contains a string with an invalid Unicode escape (e.g. malformed `\\u` sequence).\n3. Observe the failure to log the event.\n\n**Expected behavior**\n\nThe log entry should be created successfully, or the input should be sanitized/validated to prevent the escape sequence error.\n\n**Screenshots**\n\nN/A\n\n**Additional context**\n\nHere is the error output:\n\n```\n[2025-05-05 21:44:53] ERROR: Failed to create log entry:\n type: \"useModel:TEXT_LARGE\"\n roomId: \"964d1ca6-29f9-00e0-b2c6-b16caf5bbed7\"\n entityId: \"964d1ca6-29f9-00e0-b2c6-b16caf5bbed7\"\n error: \"unsupported Unicode escape sequence\"\n\n# ... drizzle error\n\n\nerror: unsupported Unicode escape sequence\n at ye.Ve (file:///workspaces/x/agent/node_modules/@electric-sql/pglite/dist/chunk-EADU5A67.js:1:17602)\n at ye.nt (file:///workspaces/x/agent/node_modules/@electric-sql/pglite/dist/chunk-EADU5A67.js:1:14988)\n at ye.parse (file:///workspaces/x/agent/node_modules/@electric-sql/pglite/dist/chunk-EADU5A67.js:1:13740)\n at pe.execProtocol (file:///workspaces/x/agent/node_modules/@electric-sql/pglite/dist/index.js:3:239489)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async pe.l (file:///workspaces/x/agent/node_modules/@electric-sql/pglite/dist/chunk-A7RFOIQ7.js:8:1911)\n at async file:///workspaces/x/agent/node_modules/@electric-sql/pglite/dist/chunk-A7RFOIQ7.js:8:2407 {\n length: 250,\n severity: 'ERROR',\n code: '22P05',\n detail: '\\\\u0000 cannot be converted to text.',\n hint: undefined,\n position: undefined,\n internalPosition: undefined,\n internalQuery: undefined,\n where: 'JSON data, line 1: ...n environnement virtuel :\\\\\"}}],\\\\n \\\\u0000...\\n' +\n \"unnamed portal parameter $2 = '...'\",\n schema: undefined,\n table: undefined,\n column: undefined,\n dataType: undefined,\n constraint: undefined,\n file: 'jsonfuncs.c',\n line: '638',\n routine: 'json_errsave_error'\n}\n\n\n```\n\nThis seems to be triggered during JSON parsing or serialization, potentially from malformed input data that includes a broken escape like `\\u`.\n", "createdAt": "2025-05-05T21:51:18Z", "closedAt": "2025-05-12T08:05:38Z", "state": "CLOSED", "commentCount": 0 } ], "topPRs": [ { "id": "PR_kwDOMT5cIs6V5ow8", "title": "Feat/add mysql to degen", "author": "0xbbjoker", "number": 4554, "body": "", "repository": "elizaos/eliza", "createdAt": "2025-05-12T21:06:49Z", "mergedAt": null, "additions": 43476, "deletions": 31880 }, { "id": "PR_kwDOMT5cIs6Vhb53", "title": "feat: add plugin specification wrappers", "author": "odilitime", "number": 4505, "body": "I'm posting this here for team review, these will be committed and maintained in a separate repo and will be submoduled in.\r\n\r\nThis establishes a V2 core specification and a V1 core specification that wrap the real internal core. \r\n\r\nAll 1.x plugins must use core-plugin-v2 instead of `@elizaos/core`\r\nAll 0.x plugins must use core-plugin-v1 instead of `@elizaos/core`\r\n\r\nmaybe they should be v0 and v1\r\n\r\n", "repository": "elizaos/eliza", "createdAt": "2025-05-09T03:53:18Z", "mergedAt": null, "additions": 7673, "deletions": 0 }, { "id": "PR_kwDOMT5cIs6VxJVG", "title": "ELIZA290/part-2-plugins-agent-cli-commands", "author": "yungalgo", "number": 4538, "body": "SUMMARY:\r\n\r\nfull functional testing of plugins and agent commands. \r\n\r\nPLUGINS COMMANDS\r\n\r\nelizaos plugins -h/–help\r\n\r\nShowing all options and commands correctly. Minor problems:\r\nShowing -h and –help on two separate lines, which is not standard\r\nDisplaying the banner and version, which is not standard\r\n\r\nPROPOSED SOLUTION: show -h, –help on the same line and remove banner display\r\n\r\nelizaos plugins list|l\r\n\r\nWorking – currently returning a hardcoded list. This should ideally return a list connected to elizaos-plugins, npm, etc. But we will leave this for now.\r\n\r\nelizaos plugins add|install\r\n\r\nIssues with dependency loops when installing plugins in monorepo context (e.g. plugins that are in packages dir). Can’t handle workspace dependencies properly or distinguish between monorepo root and other projects.\r\n\r\nPROPOSED SOLUTION: Add monorepo context detection, Add workspace package detection, use special handling for monorepo root (uses workspace:* references in package.json). Avoids npm install for root to prevent dependency loops. For other projects in monorepo, falls back to standard installation. Added fallback mechanisms if workspace installation fails\r\n\r\nelizaos plugins installed-plugins\r\n\r\nWorking – lists plugins that are referenced as deps in package.json, this is correct implementation for portable monorepo design\r\n\r\nelizaos plugins installed-plugins\r\n\r\nWorks as expected in both monorepo and created projects\r\n\r\nAGENT COMMANDS\r\n\r\nelizaos agent -h/–help\r\n\r\nWorks correctly, displays helper text, options, and commands as expected\r\n\r\nelizaos agent list|ls (-j/–json)\r\n\r\nWorks correctly – if you run it with no agents running it gives correct error, if its run with agents running it gives the correct agent info. JSON flag works too.\r\n\r\nelizaos agent get|g (-n/–name, -j/–json, -o/–output)\r\n\r\nA few minor bugs:\r\n\r\nThe --json flag incorrectly requires a name parameter when it should display all agents in JSON format without requiring any name parameter.\r\nWhen using elizaos agent get -n eliza --json, the command incorrectly saves to a file named \"eliza\" instead of displaying the JSON output in the terminal.\r\nThe --output flag doesn't work at all. When using -n eliza --output testie, it should save the agent data as JSON to \"testie.json\" but currently does nothing.\r\nelizaos agent get without a flag passed shows the same exact table as list. But get’s purpose should be about showing the char file in the terminal as opposed to list which just shows all the agents running with their names and ids and status.\r\n\r\nPROPOSED SOLUTION: make --json display JSON output without saving to file, make --output save to file without displaying, and allowing --json to work without requiring a name parameter to list all agents. If user runs agent get without a flag, it shows an interactive menu showing all available agents.\r\n\r\nelizaos agent start|s (-n/–name, –path)\r\n\r\nSeveral issues, but broadly, it was confusing create and start functions, and had some options that didnt make sense. We would expect elizaos agent start -n ELIZA to start an instance of an existing agent character JSON called eliza in the current dir. Similar behavior would be expected with a –path passed. But this was failing with a \"Bad Request\" error. The command's scope was unclear - it was attempting to both create new agents and start existing ones, which made the error handling and response parsing complex and error-prone. Also it had the –json flag which didnt make sense to have at all. And the –remote-url is something that makes sense to pass for agent creation, not for agent starting.\r\n\r\nPROPOSED SOLUTION: The solution was to clarify the command's scope to focus solely on starting existing agents, removing the outdated options from the help text. We implemented a consistent two-step process: first create the agent if it doesn't exist (using the character JSON), then start its runtime. This was implemented uniformly across all three ways to use the command: by name (-n), by path (--path), or interactively (no flags). The command now properly handles the agent lifecycle by ensuring the agent exists in the database before attempting to start its runtime, and it provides clear feedback at each step of the process.\r\n\r\nelizaos agent stop|st\r\n\r\nWorking, added some interactive cli features if no flag passed\r\n\r\nPROPOSED SOLUTION: add interactive cli func\r\n\r\nelizaos agent remove|rm\r\n\r\nWorking, added some interactive cli features if no flag passed\r\n\r\nPROPOSED SOLUTION: add interactive cli func\r\n\r\nelizaos agent set\r\n\r\nWas not working, re-vamped it to have an interactive shell\r\n\r\nPROPOSED SOLUTION: add interactive cli shell", "repository": "elizaos/eliza", "createdAt": "2025-05-12T05:10:55Z", "mergedAt": null, "additions": 1518, "deletions": 466 }, { "id": "PR_kwDOMT5cIs6VwR5-", "title": "ELIZA290/part-2-plugins-agent-cli-commands", "author": "yungalgo", "number": 4535, "body": "SUMMARY: \r\n\r\nfull functional testing of plugins and agent commands. \r\n\r\nPLUGINS COMMANDS\r\n\r\nelizaos plugins -h/–help\r\n\r\nShowing all options and commands correctly. Minor problems:\r\nShowing -h and –help on two separate lines, which is not standard\r\nDisplaying the banner and version, which is not standard\r\n\r\nPROPOSED SOLUTION: show -h, –help on the same line and remove banner display\r\n\r\nelizaos plugins list|l\r\n\r\nWorking – currently returning a hardcoded list. This should ideally return a list connected to elizaos-plugins, npm, etc. But we will leave this for now.\r\n\r\nelizaos plugins add|install\r\n\r\nIssues with dependency loops when installing plugins in monorepo context (e.g. plugins that are in packages dir). Can’t handle workspace dependencies properly or distinguish between monorepo root and other projects.\r\n\r\nPROPOSED SOLUTION: Add monorepo context detection, Add workspace package detection, use special handling for monorepo root (uses workspace:* references in package.json). Avoids npm install for root to prevent dependency loops. For other projects in monorepo, falls back to standard installation. Added fallback mechanisms if workspace installation fails\r\n\r\nelizaos plugins installed-plugins\r\n\r\nWorking – lists plugins that are referenced as deps in package.json, this is correct implementation for portable monorepo design\r\n\r\nelizaos plugins installed-plugins\r\n\r\nWorks as expected in both monorepo and created projects\r\n\r\n\r\nAGENT COMMANDS\r\n\r\n\r\nelizaos agent -h/–help\r\n\r\nWorks correctly, displays helper text, options, and commands as expected\r\n\r\nelizaos agent list|ls (-j/–json)\r\n\r\nWorks correctly – if you run it with no agents running it gives correct error, if its run with agents running it gives the correct agent info. JSON flag works too.\r\n\r\nelizaos agent get|g (-n/–name, -j/–json, -o/–output)\r\n\r\nA few minor bugs:\r\n\r\nThe --json flag incorrectly requires a name parameter when it should display all agents in JSON format without requiring any name parameter.\r\nWhen using elizaos agent get -n eliza --json, the command incorrectly saves to a file named \"eliza\" instead of displaying the JSON output in the terminal.\r\nThe --output flag doesn't work at all. When using -n eliza --output testie, it should save the agent data as JSON to \"testie.json\" but currently does nothing.\r\nelizaos agent get without a flag passed shows the same exact table as list. But get’s purpose should be about showing the char file in the terminal as opposed to list which just shows all the agents running with their names and ids and status.\r\n\r\nPROPOSED SOLUTION: make --json display JSON output without saving to file, make --output save to file without displaying, and allowing --json to work without requiring a name parameter to list all agents. If user runs agent get without a flag, it shows an interactive menu showing all available agents.\r\n\r\nelizaos agent start|s (-n/–name, –path)\r\n\r\nSeveral issues, but broadly, it was confusing create and start functions, and had some options that didnt make sense. We would expect elizaos agent start -n ELIZA to start an instance of an existing agent character JSON called eliza in the current dir. Similar behavior would be expected with a –path passed. But this was failing with a \"Bad Request\" error. The command's scope was unclear - it was attempting to both create new agents and start existing ones, which made the error handling and response parsing complex and error-prone. Also it had the –json flag which didnt make sense to have at all. And the –remote-url is something that makes sense to pass for agent creation, not for agent starting.\r\n\r\n\r\nPROPOSED SOLUTION: The solution was to clarify the command's scope to focus solely on starting existing agents, removing the outdated options from the help text. We implemented a consistent two-step process: first create the agent if it doesn't exist (using the character JSON), then start its runtime. This was implemented uniformly across all three ways to use the command: by name (-n), by path (--path), or interactively (no flags). The command now properly handles the agent lifecycle by ensuring the agent exists in the database before attempting to start its runtime, and it provides clear feedback at each step of the process.\r\n\r\nelizaos agent stop|st\r\n\r\nWorking, added some interactive cli features if no flag passed\r\n\r\nPROPOSED SOLUTION: add interactive cli func\r\n\r\nelizaos agent remove|rm\r\n\r\nWorking, added some interactive cli features if no flag passed\r\n\r\nPROPOSED SOLUTION: add interactive cli func\r\n\r\nelizaos agent set\r\n\r\nWas not working, re-vamped it to have an interactive shell\r\n\r\nPROPOSED SOLUTION: add interactive cli shell\r\n", "repository": "elizaos/eliza", "createdAt": "2025-05-12T01:32:28Z", "mergedAt": null, "additions": 1518, "deletions": 466 }, { "id": "PR_kwDOMT5cIs6VxjG9", "title": "ELIZA290/part-2-cli-plugins-agent-fresh", "author": "yungalgo", "number": 4543, "body": "## Summary of Plugin and Agent Command Testing\r\n\r\nThis document summarizes the testing results for plugins and agent commands, outlining identified issues and proposed solutions.\r\n\r\n### Plugins Commands\r\n\r\n* **`elizaos plugins -h/–help`**\r\n * **Status:** Working, but with minor issues.\r\n * **Problems:**\r\n * `-h` and `–help` displayed on separate lines (non-standard).\r\n * Banner and version information displayed (non-standard).\r\n * **Proposed Solution:** Display `-h` and `–help` on the same line, and remove the banner.\r\n\r\n* **`elizaos plugins list|l`**\r\n * **Status:** Working, returning a hardcoded list.\r\n * **Improvement:** Ideally, the list should dynamically fetch data from sources like `elizaos-plugins` or npm. This is a future enhancement.\r\n\r\n* **`elizaos plugins add|install`**\r\n * **Issues:** Dependency loop problems in monorepo environments (e.g., in `packages` directory). Difficulty handling workspace dependencies and distinguishing between monorepo root and other projects.\r\n * **Proposed Solution:**\r\n * Implement monorepo context detection.\r\n * Implement workspace package detection.\r\n * Special handling for the monorepo root (using `workspace:*` references in `package.json` to avoid `npm install` and prevent loops). For other projects, revert to standard installation.\r\n * Add fallback mechanisms if workspace installation fails.\r\n\r\n* **`elizaos plugins installed-plugins`**\r\n * **Status:** Working correctly, lists plugins referenced as dependencies in `package.json` (correct for portable monorepo design).\r\n\r\n* **`elizaos plugins installed-plugins`**\r\n * **Status:** Works as expected in both monorepo and created projects. (Duplicate entry, likely a typo).\r\n\r\n### Agent Commands\r\n\r\n* **`elizaos agent -h/–help`**\r\n * **Status:** Works correctly, displaying expected help text, options, and commands.\r\n\r\n* **`elizaos agent list|ls (-j/–json)`**\r\n * **Status:** Works correctly. Handles no agents running and agent information display. JSON flag works as expected.\r\n\r\n* **`elizaos agent get|g (-n/–name, -j/–json, -o/–output)`**\r\n * **Issues:**\r\n * `--json` flag incorrectly requires a name parameter (should display all agents in JSON).\r\n * `elizaos agent get -n eliza --json` saves output to a file named \"eliza\" instead of displaying JSON in the terminal.\r\n * `--output` flag is non-functional. It should save to a file (e.g., \"testie.json\") but does nothing.\r\n * `elizaos agent get` without flags shows the same table as `list`. It should display the character file content.\r\n * **Proposed Solution:**\r\n * Make `--json` display JSON output without file saving.\r\n * Make `--output` save to a file without terminal display.\r\n * Allow `--json` to function without a name parameter to list all agents in JSON format.\r\n * Implement an interactive menu to display available agents when `agent get` is used without flags.\r\n\r\n* **`elizaos agent start|s (-n/–name, –path)`**\r\n * **Issues:** Command scope confusion: trying to both create and start agents. Confusing options. Errors (\"Bad Request\") encountered. The `--json` flag and `--remote-url` were inappropriate for this command.\r\n * **Proposed Solution:**\r\n * Focus the command solely on starting existing agents. Remove unnecessary options from help text.\r\n * Implement a two-step process: Ensure the agent exists (by creating it if needed based on the character JSON file), then start its runtime.\r\n * Handle agent lifecycle correctly to start only existing agents. The command now uses a database to track existing agents.\r\n * Handle all three usage methods (by name, path, or interactively) uniformly.\r\n\r\n* **`elizaos agent stop|st`**\r\n * **Status:** Working. Interactive CLI features added when no flags are passed.\r\n * **Proposed Solution:** Add interactive CLI functionality.\r\n\r\n* **`elizaos agent remove|rm`**\r\n * **Status:** Working. Interactive CLI features added when no flags are passed.\r\n * **Proposed Solution:** Add interactive CLI functionality.\r\n\r\n* **`elizaos agent set`**\r\n * **Status:** Was not working; re-vamped for an interactive shell.\r\n * **Proposed Solution:** Add interactive CLI shell.\r\n\n\n\n\n## Summary by CodeRabbit\n\n- **New Features**\n - Added interactive prompts and improved error handling for agent management commands, including starting, stopping, removing, and configuring agents.\n - Extended the create command to support initializing agents from templates.\n - Enhanced plugin management to support monorepo workspaces during plugin add/remove operations.\n\n- **Bug Fixes**\n - Improved test scripts for better isolation, reliability, and diagnostics, especially in CI environments.\n - Enhanced server startup and database initialization logic for more robust handling of PostgreSQL vector extension errors.\n\n- **Documentation**\n - Updated command descriptions and help texts for clarity and accuracy.\n\n- **Tests**\n - Improved test setup, teardown, and logging for better stability and diagnostics in automated environments.\n\n", "repository": "elizaos/eliza", "createdAt": "2025-05-12T06:21:13Z", "mergedAt": null, "additions": 1449, "deletions": 334 } ], "codeChanges": { "additions": 146, "deletions": 140, "files": 20, "commitCount": 49 }, "completedItems": [ { "title": "chore: consistent env naming for project manager agent", "prNumber": 4549, "type": "other", "body": "\n\n\n\n## Summary by CodeRabbit\n\n- **New Features**\n - Activated support for the Anthropic plugin in the project manager character.\n- **Chores**\n - Updated the environ" }, { "title": "fix: agent response + better logging/tracing in bootstrap plugin", "prNumber": 4548, "type": "bugfix", "body": "\n\n\n\n## Summary by CodeRabbit\n\n- **Bug Fixes**\n - Improved handling of undefined or missing properties in entity and room details to prevent potential errors and ensu" }, { "title": "fix: bad env resolution", "prNumber": 4547, "type": "bugfix", "body": "fixes regression from merging bad PRs; env resolution is already handled by 'start.ts` in cli package\n\n\n\n## Summary by CodeRabbit\n\n- **Chores**\n - Removed environmen" }, { "title": "minor fix: remove banner display + have -h, --help show on same line", "prNumber": 4546, "type": "bugfix", "body": "**NO LOGIC OR FUNCTIONALITY CHANGES**\r\n\r\nin order to keep the cli helper text ux uniform and consistent, i made these two minor changes:\r\n\r\n- removed the displayBanner(), kinda random to show it in elizaos plugins -- this is mostly called d" }, { "title": "fix(temp): passthrough function so that llm plugins dont break", "prNumber": 4544, "type": "bugfix", "body": "" }, { "title": "fix: integration test import", "prNumber": 4541, "type": "bugfix", "body": "" }, { "title": "fix: error associated with issue #4336, where TEXT_EMBEDDING was not…", "prNumber": 4537, "type": "bugfix", "body": "… loaded, it was caused to openai plugin not having an export for getProviderBaseURL\r\n\r\n\r\n\r\n# Relates to\r\n\r\n#4336 \r\n\r\n