{ "date_generated_for": "2025-05-03", "ai_news_elizaos_discord_md_2025-05-02": { "filename": "2025-05-02.md", "content": "# elizaOS Discord - 2025-05-02\n\n## Overall Discussion Highlights\n\n### Platform Development & Technical Issues\n- **Collabland Verification Issues**: Multiple users reported losing partner status and identity group tags, particularly DegenAI token holders. The team is aware and working on a fix.\n- **Plugin Development**: Discussions about creating plugins for Reddit and LinkedIn, with resources shared including GitHub repositories and the Eliza website.\n- **Knowledge Integration**: Users explored adding external databases (particularly PostgreSQL) as knowledge sources for agents and discussed proper implementation of RAG (Retrieval-Augmented Generation).\n- **Model Support**: Questions about Deepseek integration in v2 and whether it requires a custom plugin.\n- **ElizaOS CLI Issues**: Several users encountered errors during builds and project creation.\n\n### Auto.fun Platform\n- **Token Verification Process**: Debate about the timing of token verification relative to official announcements, with concerns about fairness.\n- **Token Migration Issues**: Discussion about tokens that cannot be migrated despite using the current program ID because they were deployed before the platform's official launch.\n- **Token Listing Removals**: A user reported their token was removed for allegedly mimicking a verified token, preventing them from selling their holdings.\n- **Platform Scope**: Community member Ben clarified that Autodotfun is \"more than just a token launchpad\" but also \"a place to centralise community tools and agent building.\"\n\n### Community Building\n- **Idea Sharing Space**: Suggestion to fork an open-source project called \"negationgame\" to create a dedicated space for idea sharing and discussion.\n- **Supporting Tokens**: Community members creating supporting tokens like $BELI5 to help grow the ecosystem.\n- **Launch Schedule**: Confirmation that no token launches occur on weekends, with the next one scheduled for Monday.\n\n## Key Questions & Answers\n\n### Technical Implementation\n- **Q**: Has anyone been having trouble with the local ai plugin? \n **A**: \"A lot of people are having issues with collabland.. people on the team are aware & bare w/us, we will get it resolved.\" - Osint\n\n- **Q**: What trading terminal can I use for auto fun? \n **A**: \"Bloomberg\" - whobody\n\n- **Q**: With this character config, if I don't have OpenAI API key and Anthropic API key, will it use local-AI? \n **A**: \"Yes\" - .0xbbjoker\n\n- **Q**: Do we have a way to count, retrieve the total amount of token that've been used from a message? \n **A**: \"Yes\" - ZeorTrace/✞ᴀᴏɢ✞\n\n### Auto.fun Platform\n- **Q**: Is the $PAY token legit? \n **A**: \"Yes, Shaw confirmed it\" - velja\n\n- **Q**: Any partner launch tomorrow? \n **A**: \"No launches on weekends - next one on Monday\" - ben\n\n- **Q**: How does a coin launch at 7m? \n **A**: \"The team likely bought the whole curve\" - mhd\n\n- **Q**: What's the point of bonding if it's all bought before? \n **A**: \"The token was imported, not launched on autofun, hence no bonding\" - ben\n\n- **Q**: Why can't the token at 8MYgZupEQ be migrated? \n **A**: \"The contract was deployed before auto.fun officially launched and is tied to an earlier program ID that the migration tool can't reach, despite using the current program ID.\" - Kenk\n\n## Community Help & Collaboration\n\n### Plugin Development Support\n- **.0xbbjoker** shared example character configurations with proper knowledge structure and explained that questions need more context to improve RAG retrieval.\n- **Osint** provided GitHub repository links and Eliza website resources to **matt.gacek** who was interested in building Reddit and LinkedIn plugins.\n\n### Platform Clarifications\n- **ben** explained to multiple users that Astra imported their token earlier than planned and clarified that autofun is more than just a token launchpad.\n- **velja** confirmed to **mhd** that the $PAY token was legitimate based on information from Shaw.\n\n### Technical Issue Resolution\n- **Kenk** acknowledged issues with partner tags and identity group tags, flagged it for the team, and requested more information via DM from **human_nalejzpa**.\n- **Kenk** provided a form for **Kodak** to report a bugged token and promised to flag the issue to the engineering team.\n- **.0xbbjoker** helped troubleshoot CLI issues by suggesting removing starterPlugin from index.ts and instructing to run \"elizaos start\" inside the created folder.\n\n## Action Items\n\n### Technical\n- Fix Collabland verification issues for DegenAI token holders (Mentioned by: human_nalejzpa)\n- Investigate EINTVAL error no:-22 during elizaos/cli:build when copying files (Mentioned by: .0xbbjoker)\n- Fix issue with Twitter agent only replying once to interactions on posts (Mentioned by: .0xbbjoker)\n- Implement token counting/tracking for messages including embeddings and useModel calls (Mentioned by: Stan ⚡)\n- Add support for Deepseek models in ElizaOS v2 (Mentioned by: .0xbbjoker)\n- Improve RAG implementation for better knowledge retrieval with minimal context (Mentioned by: .0xbbjoker)\n- Investigate migration possibility for token on live program ID created before platform launch (Mentioned by: bheau)\n- Fix trading error for token ALLxYpyYbrPjXeeGRsPWB2Q4qxPFjfbunDoNuoKsXFUN (Mentioned by: Kodak)\n- Arrange selling capability for y4's delisted token (Mentioned by: y4)\n- Connect wallets on PC to improve transaction speed (Mentioned by: MDMnvest)\n\n### Documentation\n- Create guide for adding external databases as knowledge sources (Mentioned by: .0xbbjoker)\n- Document proper PDF integration with agents and verification of processing (Mentioned by: .0xbbjoker)\n- Clarify model availability and configuration across different ElizaOS versions (Mentioned by: .0xbbjoker)\n- Provide guidance for plugin development (Mentioned by: DarthGus)\n- Clarify policy on tokens created before platform launch but on current program ID (Mentioned by: bheau)\n- Provide clear guidelines on token naming to avoid mimicking verified tokens (Mentioned by: y4)\n\n### Feature\n- Develop plugins for Reddit and LinkedIn (Mentioned by: matt.gacek)\n- Fork and deploy private version of negationgame for DAO (Mentioned by: yikesawjeez)\n- Create a transparent channel where the best ideas win (Mentioned by: Osint)\n- Implement Anthropic's \"secret sauce\" for RAG in ElizaOS (Mentioned by: .0xbbjoker)\n- Add support for PostgreSQL integration for media references (Mentioned by: .0xbbjoker)\n- Notify autodotfun loyalists before public announcements (Mentioned by: MDMnvest)\n- Change verification timing to ensure fair launches (Mentioned by: Tocheee)" }, "ai_news_elizaos_discord_md_2025-05-01": { "filename": "2025-05-01.md", "content": "# elizaOS Discord - 2025-05-01\n\n## Overall Discussion Highlights\n\n### Auto.fun Platform & Token Launches\n- **SteamBot Wille by Tapestry AI** was launched on the auto.fun platform\n- Users identified an issue with the verification process where checkmarks added before public announcement create opportunities for snipers\n- Several users suggested verification checkmarks should only be added after tokens are publicly posted\n- Discussion about ELI5 token accumulation patterns by a possible whale or team member\n- Concerns raised about fair launches and verification system implementation\n- Token migration issues reported by multiple users who submitted their problems through a Tally form\n\n### Development & Technical Discussions\n- User **techcomthanh** encountered problems with agent knowledge functionality\n- **Kgood** reported an error related to TEXT_EMBEDDING delegate type despite having added the OpenAPI key\n- **Mohit** asked about reducing the image size of their Eliza repo (3.32GB)\n- **mtbc** requested a review for a plugin enhancement for Zilliqa\n- Clarification that \"1.0.0beta\" is what's referred to as \"v2\" in version numbering\n- **morlok** sought advice on processing received interactions without interrupting original workflow\n- **DorianD** suggested implementing agent cards for Eliza agents\n- **Stan** inquired about the new bm25 in package/core and its current usage\n- **Cavey65** reported display compatibility issues with Autodotfun on Chrome PC\n\n### Cryptocurrency & Wallet Discussions\n- Users discussed hardware wallets (Ledger and Keystone) and investment strategies\n- Comparison of Auto.fun launchpad functionality to competitors like Virtuals\n- Discussion about DegenAI and its roadmap, though specific technical details were sparse\n- **mariocandia** provided feedback that Auto.fun's launchpad lacks features compared to competitors\n\n### Discord Server & Roles\n- Users inquired about roles in the Discord server, particularly the \"partner\" role\n- Clarification that \"partner\" role requires holding 1M DegenAI tokens or 100k AI16Z\n\n## Key Questions & Answers\n\n**Q: How do I get the partner role?** (asked by basje01) \n**A:** You need 100k AI16Z for partners or 1M DegenAI (answered by Kenk)\n\n**Q: When will there be official docs for auto.fun, development roadmap, and tokenomics paper?** (asked by mariocandia) \n**A:** The tokenomics is public, we won't be sharing a public development roadmap, and there's no emphasis on creating developer docs currently. We're focused on user experience and growth. (answered by Kenk)\n\n**Q: What's the latest with DegenAI and how does it fit in the AI16Z/Eliza ecosystem?** (asked by Ric Q) \n**A:** It's being worked on without definitive dates. They want it to do some trading but it's very limited right now. (answered by Osint)\n\n**Q: Will there be a token launch today?** (asked by noj) \n**A:** Yes, it will be announced on X as soon as it's launched (answered by ben)\n\n**Q: Is it still today?** (asked by mhd) \n**A:** Yes it's 1 launch per day (answered by Xyness)\n\n**Q: Why is the verified check added well after the coin launches?** (asked by frank_grimes_sr) \n**A:** It's added within seconds. This token bonded really quickly. (answered by Borko)\n\n**Q: Can I get support for not being able to sell any of my token supply?** (asked by y4) \n**A:** Submit your issue through the Tally form and the team will action it ASAP (answered by Kenk)\n\n**Q: Does Autodotfun work properly on Chrome PC?** (asked by cavey65) \n**A:** Osint reported it looks fine on their PC and requested a screenshot for further troubleshooting (answered by Osint)\n\n## Community Help & Collaboration\n\n- **Osint** helped **Ashe Cribb** with wallet connection issues on Pixel 9 phone, confirming the connect wallet buttons work on their Pixel device\n- **Kenk** assisted **basje01** with Discord roles, explaining token requirements and suggesting to check back when the Collab.land manager returns\n- **Osint** provided information to **Ric Q** about DegenAI roadmap and ecosystem integration, promising to get more details from Shaw\n- **techcomthanh** self-helped by finding documentation link for memory and knowledge management\n- **ben** helped multiple users with questions about token launch timing and later shared the launch spotlight for SteamBot Wille\n- **Xyness** confirmed to **Tocheee** that there's 1 launch per day and since no launch had happened yet, it would be that day\n- **Borko** explained to **frank_grimes_sr** that launch partner tokens are verified right away and that they'll look into adding verified checkmarks pre-launch\n- **Shaw** provided assistance to **y4** via DM regarding token selling issues\n- **Kenk** acknowledged support submissions and assured users the engineering team would address their issues\n\n## Action Items\n\n### Technical Tasks\n- Implement Ledger and Keystone hardware wallet support for the platform (Mentioned by DorianD)\n- Fix Twitter agent functionality for users experiencing errors (Mentioned by Dansyk Reddio)\n- Review and merge Zilliqa plugin enhancement PR (Mentioned by mtbc)\n- Fix TEXT_EMBEDDING delegate type error (Mentioned by Kgood)\n- Implement solution for processing received interactions without workflow interruption (Mentioned by morlok)\n- Clarify usage of new bm25 in package/core (Mentioned by Stan ⚡)\n- Optimize Eliza repo image size (Mentioned by Mohit)\n- Investigate Autodotfun display compatibility issue on Chrome PC (Mentioned by cavey65)\n- Modify verification system to add checkmarks after token is publicly posted to prevent sniping (Mentioned by Tocheee)\n- Investigate adding verified checkmarks pre-launch to prevent confusion (Mentioned by Borko)\n- Address the issue of snipers detecting verification checkmarks before public announcement (Mentioned by ryanthelad)\n- Investigate and resolve y4's token selling issue (Mentioned by y4)\n- Review migration request for token 8MYgZupEQ7aAJcyz2ZpSkQEXLnfHEPuU6sGJB8GERFUN (Mentioned by Vaunted)\n\n### Feature Requests\n- Create a clear development roadmap for Auto.fun (Mentioned by mariocandia)\n- Develop swarm infrastructure similar to competitors (Mentioned by mariocandia)\n- Implement agent cards for Eliza agents (Mentioned by DorianD)\n- Consider creating specialized launchpads for specific Solana coins that have pumped (Mentioned by DorianD)\n- Ensure verification badges are visible immediately on both home page and token details page (Mentioned by frank_grimes_sr)\n- Consider implementing QR wallet connect for PC version (Mentioned by MDMnvest)\n\n### Documentation Needs\n- Create comprehensive documentation for Auto.fun (Mentioned by mariocandia)\n- Update DegenAI information on Dexscreener (Mentioned by Ric Q)" }, "ai_news_elizaos_discord_md_2025-04-30": { "filename": "2025-04-30.md", "content": "# elizaOS Discord - 2025-04-30\n\n## Overall Discussion Highlights\n\n### Auto.fun Platform & Development\n- Auto.fun has processed over **$100M in volume** since launch, demonstrating significant traction\n- The platform experienced technical issues including a memory leak causing slow loading times, which has been fixed\n- iOS users reported particular difficulty accessing the site\n- Auto.fun collects fees when tokens graduate, with 10% of burned LP set aside to buyback $ai16z from the market\n- The platform offers unique features like token-gated chat, vanity contract addresses, and AI generation for tokens\n- Verification process was clarified: verified projects are teams building elizaOS-based products with long-term vision\n- Launch announcement protocol: partner teams have priority to announce first, followed by @autodotfun account\n- Today's featured launch was \"Pets by Wide Worlds,\" an imported token showcasing platform capabilities\n\n### ElizaOS Development\n- ElizaOS v2 is described as \"really just 1.0\" - a finished product with useful working agents currently being tested internally\n- Spartan V2 will include three exclusive plugins: community-investor (personal finance interface), autonomous trader (executing trade strategies via Jupiter), and intel (market information gathering)\n- Development is ongoing as evidenced by GitHub PR #4397, though communication about progress has been limited\n- Users discussed API integration for EVM AI agents, focusing on connecting frontend code to the Eliza AI framework\n- Common installation issues included problems with TEXT_EMBEDDING models and database connection errors\n- Environment variable configuration for OpenAI and Anthropic integrations was a frequent topic\n- One user reported scaling issues when querying 1000+ agents in PostgreSQL, experiencing connection timeout errors\n\n### Token Ecosystem\n- Plans to implement $ai16z:AT pools to pair acquired $ai16z with Agent Tokens, deepening liquidity for both\n- Spartan/DegenAI is planned to be an Auto.fun launch partner, with marketing expected to begin next week\n- The relationship between ai16z and degenai tokens needs clearer documentation\n- V2 announcement was delayed due to bugs in the Auto.fun launch\n- Several partners have launched or imported tokens on the platform, with more scheduled in coming weeks\n\n## Key Questions & Answers\n\n**Q: How does v2 move the needle in any meaningful way?** \nA: Eliza v2 is really just 1.0, it's a finished product with useful working agents which we're testing on our own team. (answered by shaw)\n\n**Q: Why is the site so slow?** \nA: The site is experiencing heavy load with around $100M volume since launch. (answered by Kenk)\n\n**Q: How can I integrate my frontend code to Eliza AI framework?** \nA: You can use the API endpoint like \"http://localhost:3000/api/agents/[agent-id]\" to call the agent through API and integrate with your frontend. You'll need to host your Eliza CLI version to a separate backend endpoint for production. (answered by funboy)\n\n**Q: How can I fix the \"No TEXT_EMBEDDING model registered\" error?** \nA: Make sure you have both OpenAI and Anthropic keys in your .env file. You need to set up OPENAI_EMBEDDING_MODEL, OPENAI_LARGE_MODEL, OPENAI_SMALL_MODEL, OPENAI_API_KEY, and OPENAI_BASE_URL correctly. (answered by funboy)\n\n**Q: Is there some agreement that Autofun tweets the CA first?** \nA: Partners have the right to announce first, but @autodotfun aims to be the first to share the launch. (answered by ben)\n\n**Q: When a token is official, do they get verified?** \nA: Verified projects are teams the platform is confident are agent teams building elizaOS-based products with long-term vision. (answered by Kenk)\n\n**Q: How long does migration to Raydium take?** \nA: Probably less than 2 minutes. (answered by jasyn_bjorn)\n\n**Q: Are we finally going to have an AI agent that can trade and win?** \nA: Trade yes, win idk, moderate your trading expectations. Spartan has been trading for a while and he has been mid. (answered by shaw)\n\n**Q: What made auto.fun launch successful?** \nA: Allora choosing auto.fun, $8M volume in 30 mins ($17M in <24hrs), product working as expected. (answered by Kenk)\n\n**Q: Are there any bots that work with auto fun before migration?** \nA: solsniper. (answered by Kenk)\n\n## Community Help & Collaboration\n\n- **funboy** provided detailed guidance on API endpoint integration for the Eliza AI framework, helping users connect frontend code to the backend\n- **jasyn_bjorn** identified a memory leak causing slow site performance and confirmed when developers fixed the issue\n- **Odilitime** helped a user experiencing PostgreSQL connection timeout with 1000+ agents by suggesting query optimization, index checking, and timeout adjustments\n- **jin** created more detailed partner pages at eliza.how/partners to address the lack of comprehensive partner information\n- **eskender.eth** updated the auto.fun landing page to better explain the product in simpler terms after feedback from Odilitime\n- **HoneyBadger** warned channel members about a potential scammer and advised against sharing sensitive information\n- **jasyn_bjorn** verified a legitimate reimbursement claim for user drkmttr2 who had been waiting for several days and sent the reimbursement\n- **Kenk** identified a token address for a user experiencing \"token loading error\" and escalated the issue to the team\n\n## Action Items\n\n### Technical\n- Fix token loading errors on the auto.fun website (Mentioned by researcher628)\n- Resolve website access issues on iOS devices (Mentioned by MDMnvest)\n- Implement blacklisting of partner token names to prevent scams (Mentioned by TMO)\n- Fix layout issues with filters on mobile website (Mentioned by abhi_ironman)\n- Optimize PostgreSQL queries for handling large numbers of agents (Mentioned by Subhankar)\n- Integrate auto.fun volume metrics into Dune dashboard (Mentioned by Void)\n- Continue development work shown in GitHub PR #4397 (Mentioned by Odilitime)\n- Address bugs in AutoFun before V2 announcement (Mentioned by deki)\n- Integrate frontend code with Eliza AI framework using API endpoints (Mentioned by funboy)\n- Fix TEXT_EMBEDDING model registration by properly configuring environment variables (Mentioned by funboy)\n- Implement proper handling of action responses in custom clients (Mentioned by funboy)\n\n### Documentation\n- Create a document showing the relationship between ai16z and degenai tokens (Mentioned by PrudentSpartan)\n- Simplify auto.fun landing page with ELI5 explanations of bonding curves (Mentioned by Odilitime)\n- Better organize documentation around product features and tokenomics (Mentioned by Odilitime)\n- Create more detailed explanation of Degenai capabilities as ElizaOS agent (Mentioned by Void)\n- Create installation guide for ElizaOS version 0.25.9 for Windows users (Mentioned by funboy)\n- Document deployment process for ElizaOS to production environments (Mentioned by morlok)\n\n### Feature\n- Develop a dedicated page for different audiences (degens/investors vs creators) (Mentioned by Odilitime)\n- Implement Spartan v2 with auto.fun pre-bonded trading (Mentioned by shaw)\n- Add more DeFi functionality to Spartan and enable installs into group chats (Mentioned by shaw)\n- Create a dashboard for auto.fun data and metrics (Mentioned by yikesawjeez)\n- Develop more sophisticated agent builder that competes with auto.fun (Mentioned by eskender.eth)\n- Implement $ai16z:AT pools to pair acquired $ai16z with Agent Tokens (Mentioned by Osint)\n- Launch Spartan/DegenAI as AutoFun partner (Mentioned by Odilitime)\n- Add watchlist option to the platform (Mentioned by Void)\n- Pin specific tokens (degenai and ai16z) to the featured tab (Mentioned by Void)\n- Twitter live chat integration with ElizaOS (Mentioned by funboy)\n- Tool that notifies users of new launches (Mentioned by Osint)" }, "ai_news_elizaos_dev_md_2025-05-02": { "filename": "2025-05-02.md", "content": "# elizaOS Development Discord - 2025-05-02\n\n## Overall Discussion Highlights\n\n### ElizaOS Development & Architecture\n- Discussions about the new v2 architecture where plugins are separated from the core system\n- Questions about differences between v1.0.0-beta and v2 versions\n- Interest in open source projects building on Eliza's v2 architecture\n- Exploration of dynamically loading new characters with plugins while the runtime is running\n\n### Technical Configuration\n- Model configuration for Anthropic API was a key topic\n- Environment variables can be modified to change the AI model being used\n- Specific guidance on switching from Haiku to Sonnet model by setting `SMALL_ANTHROPIC_MODEL=claude-3-5-sonnet-20241022` in the .env file\n\n### Platform Compatibility\n- Windows compatibility issues with ElizaOS were discussed\n- Recommendation to use Ubuntu WSL2 for Windows to run ElizaOS properly\n- Confirmation that ElizaOS works in WSL environment without the issues experienced in native Windows\n\n### User Experience Issues\n- Users reported conversation history disappearing after 3-5 minutes of inactivity\n- Questions about changing default model settings\n- Broken documentation links on the eliza.how website\n\n## Key Questions & Answers\n\n**Q: Does ElizaOS use the index.ts file after using elizaos create?** (asked by WizardlyLuke) \n**A:** Try using \"elizaos start\" instead of npm commands (answered by sayonara)\n\n**Q: How can I make the agent use the Sonnet model instead of Haiku?** (asked by Buttered) \n**A:** Change `SMALL_ANTHROPIC_MODEL=claude-3-5-sonnet-20241022` in your .env file (answered by sayonara)\n\n**Q: Is it possible to dynamically load new characters with plugins while the runtime is running?** (asked by DorianD) \n**A:** If plugins are already installed it should work, but might cause issues if not installed (answered by shaw)\n\n**Q: How do I run ElizaOS on Windows?** (implied question) \n**A:** Use Ubuntu WSL2 for Windows to run ElizaOS properly (answered by YungYoda)\n\n## Community Help & Collaboration\n\n1. **Windows Compatibility Assistance**\n - **Helper:** sayonara\n - **Helpee:** WizardlyLuke\n - **Context:** ElizaOS not using updated index.ts file on Windows\n - **Resolution:** Suggested using \"elizaos start\" command and confirmed it works in WSL\n\n2. **Model Configuration Support**\n - **Helper:** sayonara\n - **Helpee:** Buttered\n - **Context:** Difficulty making agent use Sonnet model instead of Haiku\n - **Resolution:** Provided specific environment variable to change in .env file with reference to GitHub code\n\n3. **Plugin Architecture Guidance**\n - **Helper:** shaw\n - **Helpee:** DorianD\n - **Context:** Question about dynamically loading characters with plugins\n - **Resolution:** Suggested it should work if plugins are already installed but might cause issues otherwise\n\n4. **Platform Compatibility Advice**\n - **Helper:** YungYoda\n - **Context:** Running ElizaOS on Windows\n - **Resolution:** Recommended using Ubuntu WSL2 for Windows\n\n## Action Items\n\n### Technical\n- **Fix broken documentation links on eliza.how website**\n - Description: Links like https://eliza.how/blog/v1-v2 are not working\n - Mentioned By: WizardlyLuke\n\n- **Fix conversation history disappearing after inactivity**\n - Description: In version 0.25.9, chat history disappears after 3-5 minutes of inactivity\n - Mentioned By: Ocisly\n\n- **Improve Windows compatibility**\n - Description: ElizaOS has issues with code changes not being reflected when running on Windows\n - Mentioned By: WizardlyLuke\n\n### Documentation\n- **Create clear documentation about model selection and environment variables**\n - Description: Users are confused about how to change models and what env variables control this\n - Mentioned By: Buttered\n\n- **Clarify differences between v1.0.0-beta and v2**\n - Description: Users are confused about version differences and which to use\n - Mentioned By: WizardlyLuke\n\n- **Develop comprehensive Windows setup guide**\n - Description: Document the process for setting up ElizaOS in WSL2 environment\n - Mentioned By: YungYoda (implied)" }, "ai_news_elizaos_dev_md_2025-05-01": { "filename": "2025-05-01.md", "content": "# elizaOS Development Discord - 2025-05-01\n\n## Overall Discussion Highlights\n\n### Technical Development\n- **RAG Capabilities**: Discussions clarified that both V2 and 0.25.x versions support RAG functionality, with 1.x offering better unification compared to 0.x which separates functionality into memories, knowledge, and RAGknowledge components.\n- **Dependency Management**: Troubleshooting session focused on resolving conflicts between Eliza 1.0.0-beta.41 and the video understanding plugin, highlighting common issues during version upgrades.\n- **Platform-Specific Implementation**: The community addressed Windows-specific command syntax differences when troubleshooting installation issues, revealing the need for platform-specific documentation.\n\n### Features & Visualization\n- **GitHub Activity Visualization**: Jin shared a working example of GitHub activity visualization and expressed interest in further improvements.\n- **X Communities Integration**: A new feature allowing posting to X (Twitter) communities is reportedly in development by Shaw and Jin, with potential same-day release.\n- **Daily Dashboard**: Jin shared progress on the dashboard available at elizaos.github.io/daily.\n\n### Documentation\n- **Documentation Access**: Users shared links to the documentation site (https://docs.Eliza.how) in response to questions about accessing documentation.\n\n## Key Questions & Answers\n\n**Q: Is it possible to use RAG in the V2 version? Or should we be using 0.25.x?** (asked by dong) \n**A:** Both have RAG. It's unified better in 1.x, where 0.x has memories, knowledge and RAGknowledge (answered by Odilitime)\n\n**Q: What happened to the docs page? Any other working links?** (asked by z1) \n**A:** HTTPS://docs.Eliza.how (answered by sayonara)\n\n**Q: Does anybody know if there is an Eliza version where I can post on communities on X?** (asked by Jon) \n**A:** Yes, Shaw and Jin have been hard at work on one. Might be ready today, I haven't heard an announcement yet (answered by Odilitime)\n\n**Q: How do I install Eliza version 1.0.0-beta.37?** (asked by paddlep0p) \n**A:** Run \"npm install eliza@1.0.0-beta.37 --save-exact\", but note there have been important fixes in beta.41. (answered by Ruby)\n\n**Q: How do I fix \"No version matching\" errors for Eliza plugins?** (asked by paddlep0p) \n**A:** Clear cache with \"bun pm cache rm\" then run \"bun install\" again. The video plugin has version constraints that can cause issues during upgrades. (answered by Ruby)\n\n## Community Help & Collaboration\n\n### RAG Implementation Guidance\nOdilitime helped dong understand the differences in RAG implementation between Eliza versions, explaining the architectural differences between 0.x and 1.x versions.\n\n### Dependency Troubleshooting\nRuby provided comprehensive support to paddlep0p who encountered dependency issues with Eliza version 1.0.0-beta.41 and the video understanding plugin:\n- Initially suggested downgrading to version 1.0.0-beta.37\n- Adapted troubleshooting steps for Windows PowerShell environment\n- Offered multiple approaches including cache clearing, node_modules removal, and reinstallation\n- Provided Windows-specific command alternatives when Unix-style commands failed\n\n### Documentation Access\nsayonara helped z1 locate the current documentation site when they were unable to find working links.\n\n## Action Items\n\n### Technical\n- **Improve GitHub activity visualization** (Mentioned by Jin)\n - Enhance the current visualization shared via Twitter\n- **Continue development of X communities posting feature** (Mentioned by Odilitime)\n - Feature allowing Eliza to post on X communities\n- **Resolve dependency conflicts** (Mentioned by paddlep0p)\n - Address issues between Eliza 1.0.0-beta.41 and @elizaos/plugin-video-understanding\n\n### Documentation\n- **Create Windows-specific installation and troubleshooting guides** (Mentioned by Ruby)\n - Develop platform-specific documentation for Windows users\n\n### Feature\n- **Daily dashboard development** (Mentioned by Jin)\n - Further development of the dashboard at elizaos.github.io/daily" }, "ai_news_elizaos_dev_md_2025-04-30": { "filename": "2025-04-30.md", "content": "# elizaOS Development Discord - 2025-04-30\n\n## Overall Discussion Highlights\n\n### Website Status Issues\n- The main Eliza website (eliza.how) is currently down, though the documentation site (docs.eliza.how) remains accessible\n- Users have been reporting issues with eliza.gg being down as well\n- Team members acknowledged they're working on fixing the website issues\n- jin clarified that the frontpage isn't ready yet and they'll provide more advance notice in the future\n\n### Development Requests\n- There's interest in multi-chain support for agents, specifically the ability to add multiple chains (Solana, Ethereum) to a single agent\n- A user is seeking a developer to build an EVM AI agent with specific capabilities:\n - CMC information retrieval\n - Crypto operations (transfer, swap, bridge)\n - Smart contract deployment\n - Wallet connection authentication (rather than private key)\n- Request for X (Twitter) community posting capabilities through Eliza\n\n## Key Questions & Answers\n\n**Q: Is https://eliza.how dead?** (asked by GPSxtreme) \n**A:** Borko confirmed they're working on this issue\n\n**Q: Is there an alternative way to access documentation?** (implied by multiple users) \n**A:** Multiple users confirmed docs.eliza.how/docs/quickstart is still functional\n\n## Community Help & Collaboration\n\n- **GPSxtreme** helped channel members by reporting that while eliza.how is down, docs.eliza.how/docs/quickstart still works\n- **sam-developer** assisted by sharing the docs.eliza.how link as an alternative while the main site is down\n- **jin** provided context about the website issues, explaining that the frontpage isn't ready yet and promising more advance notice in the future\n\n## Action Items\n\n### Technical\n- Fix the main website (eliza.how) (mentioned by Borko)\n- Develop replacement for eliza.gg (mentioned by AlexOP303)\n\n### Feature\n- Implement multi-chain support in a single agent (Solana, Ethereum, others) (mentioned by Pr⭕f. J)\n- Develop EVM AI Agent with wallet connection authentication instead of private key (mentioned by OpsDev | Onyx)\n- Add X (Twitter) community posting capability (mentioned by Jon)" }, "ai_news_elizaos_daily_json_2025-05-02": { "filename": "2025-05-02.json", "content": { "type": "elizaosDailySummary", "title": "Daily Report - 2025-05-02", "categories": [ { "title": "Thematic Twitter Activity Summary", "content": [ { "theme_title": "AI Agents and Automation", "text": "Several users discussed AI agents and automation capabilities. @elizaOS tweeted about proactive scheduling, noting \"you say 'remind me later', I say 'already on your calendar'\" and later added that \"agents don't just remember, they write it down.\" They also mentioned that when \"you changed your mind; I already updated the plan.\" @shawmakesmagic discussed agent development, mentioning that \"Tokens per second is the biggest barrier for complex agents\" and highlighting that \"750 tps on Llama 3.1B with Groq\" makes a significant difference for planning agents. They also mentioned creating an AI agent named Spartan, referring to it as \"my Frankenstein's monster,\" and suggested that an \"agent gym could be cool.\" @shawmakesmagic shared interactions with their AI agent, noting \"He's my AI agent, I created him. He's still an asshole.\"", "sources": [ "https://twitter.com/elizaOS/status/1918108930305056810", "https://twitter.com/elizaOS/status/1918309110975549446", "https://twitter.com/elizaOS/status/1918350429185786132", "https://twitter.com/shawmakesmagic/status/1918140400847753336", "https://twitter.com/shawmakesmagic/status/1918272262555484300", "https://twitter.com/shawmakesmagic/status/1918272896184795322", "https://twitter.com/shawmakesmagic/status/1918273204088717419", "https://twitter.com/shawmakesmagic/status/1918273761943736637", "https://twitter.com/shawmakesmagic/status/1918274113241825309", "https://twitter.com/shawmakesmagic/status/1918308527741042991" ], "images": [], "videos": [] }, { "theme_title": "Blockchain and Cryptocurrency", "text": "@dankvr discussed blockchain transparency, tweeting that it's \"Another case study of how transparency curbs fraud when they started asking for receipts. Non-sensitive gov spending should go on public ledgers. 'Where's our money going?' is the question blockchain is born to answer.\" @dankvr also suggested content ideas for cryptocurrency education, stating \"I enjoy the interview streams. I wanna see content that gets into fundamentals, security, hardware wallets, bitcoin/cypherpunk history... beneficial for ppl who just joined the space recently to see the grander vision.\" @autodotfun shared information about PayXBT and Astra, describing them as \"The unified AI x Payments layer on Lightning Network\" that \"will showcase how Astra makes real-time, cross-chain payments possible – letting users pay in stablecoins on other blockchains and settle instantly in Bitcoin via the Lightning Network.\" They further explained these tools are \"built for the next-gen payment stack: High-frequency. Micropayments. Global, real-time settlement.\"", "sources": [ "https://twitter.com/dankvr/status/1918133070206582804", "https://twitter.com/dankvr/status/1918185673946812753", "https://twitter.com/autodotfun/status/1918261564747948338", "https://twitter.com/autodotfun/status/1918261567071649859", "https://twitter.com/autodotfun/status/1918261568929751073", "https://twitter.com/autodotfun/status/1918318180247666965" ], "images": [ "https://pbs.twimg.com/media/Gp8IsWWXgAAXzjY.png" ], "videos": [] }, { "theme_title": "Web Development and Tools", "text": "@dankvr recommended Brave browser over Chrome, providing guidance on importing settings: \"1 click to import settings / extensions / bookmarks anytime you want 🙂 brave://settings/importData\". @shawmakesmagic shared updates on development projects, including \"WIP: Hyperfy Plugin for Eliza\" where \"Movement, chat and world state are working\" with plans to \"push through and ship this tonight.\" They also mentioned a \"New project 89 project\" and referenced \"Elizafy\" in multiple tweets. @elizaOS later announced \"Fun, but programmable. @autodotfun – now in the wild ツ\".", "sources": [ "https://twitter.com/dankvr/status/1918181080529772936", "https://twitter.com/dankvr/status/1918184336773243045", "https://twitter.com/shawmakesmagic/status/1918188290928459964", "https://twitter.com/shawmakesmagic/status/1918194670372348250", "https://twitter.com/shawmakesmagic/status/1918236799283216581", "https://twitter.com/shawmakesmagic/status/1918420332442206485", "https://twitter.com/elizaOS/status/1918400601978716291" ], "images": [ "https://pbs.twimg.com/media/Gp7x-pSawAAhlEH.jpg", "https://pbs.twimg.com/media/Gp9qXvzXAAA2OzD.jpg" ], "videos": [] }, { "theme_title": "Digital Content Creation", "text": "@autodotfun shared about mining public domain content, tweeting \"@Tapestry_AI & @SteamBot_Willie roll into https://t.co/hYN3iaTIaO with a box full of forgotten IP. their mission? mine the public domain for memeable characters, stories, and chaos fuel. dig deep, build weird.\" @shawmakesmagic discussed content generation for cryptocurrency projects, suggesting to someone that \"you can generate this image on autodotfun and launch it and get 90% of the fees\" and joking about simple meme concepts: \"put a cat on a dog and its wifcat, instant millions, dont forget me when you're rich.\" @autodotfun later invited followers to \"come see how the fun is made.\"", "sources": [ "https://twitter.com/autodotfun/status/1918210627426005250", "https://twitter.com/shawmakesmagic/status/1918239623228399858", "https://twitter.com/shawmakesmagic/status/1918240403326943281", "https://twitter.com/autodotfun/status/1918302958757757350" ], "images": [], "videos": [] }, { "theme_title": "Digital Security Awareness", "text": "@shawmakesmagic warned about security risks, sharing \"Be careful out there. They used the actual NYPost account :O\" with an image showing what appears to be a compromised account. @dankvr also mentioned doing backups, noting \"It's been a year since the last full backup I did 😬 but also, voxels has been pretty broken for over a year now so it cancels out yeah?\"", "sources": [ "https://twitter.com/shawmakesmagic/status/1918415525572690242", "https://twitter.com/dankvr/status/1918438109672333371" ], "images": [ "https://pbs.twimg.com/media/Gp-Uu05awAMd8Pc.jpg" ], "videos": [] }, { "theme_title": "Digital Wellness", "text": "@dankvr suggested a digital wellness practice, advising someone to \"turn it off every Sunday.\" @shawmakesmagic commented on mental health awareness, responding to a user with \"Ngl this is what someone who needs therapy would say.\" They also discussed AI and society, noting \"The doomers never thought WALL-E outcome was scary enough. But in practice it was always the most realistic, and scary enough in reality.\"", "sources": [ "https://twitter.com/dankvr/status/1918143177875247478", "https://twitter.com/shawmakesmagic/status/1918245856459014506", "https://twitter.com/shawmakesmagic/status/1918422384237003221" ], "images": [], "videos": [] } ], "topic": "twitter_activity" }, { "title": "Summary for completed_items", "content": [ { "text": "Several plugins were removed from the monorepo including browser (#4406), anthropic (#4427), ollama (#4437), groq (#4436), and venice (#4434).", "sources": [ "https://github.com/elizaOS/eliza/pull/4406", "https://github.com/elizaOS/eliza/pull/4427", "https://github.com/elizaOS/eliza/pull/4437", "https://github.com/elizaOS/eliza/pull/4436", "https://github.com/elizaOS/eliza/pull/4434" ], "images": [], "videos": [] }, { "text": "New features were implemented including the use of a unique pglite folder if not provided (#4423) and a Twitter timeline feature (#4429).", "sources": [ "https://github.com/elizaOS/eliza/pull/4423", "https://github.com/elizaOS/eliza/pull/4429" ], "images": [], "videos": [] }, { "text": "Bug fixes and improvements were made to a template (#4431) and the Twitter plugin (#4430), while a hackish solution for copying migrations was removed (#4422).", "sources": [ "https://github.com/elizaOS/eliza/pull/4431", "https://github.com/elizaOS/eliza/pull/4430", "https://github.com/elizaOS/eliza/pull/4422" ], "images": [], "videos": [] } ], "topic": "completed_items" }, { "title": "Pull Requests for the repository", "repository_name": "elizaOS/eliza", "content": [ { "text": "Recent pull requests in the elizaOS/eliza repository include several feature additions and fixes. PR #4429 by tcm390 adds a Twitter timeline feature, while PR #4425 by 0xbbjoker adds documentation for Twitter agent setup. PR #4435 by yungalgo fixes incorrect version detection to show the correct latest CLI version. PR #4439 removes the plugin-local-ai from the monorepo. PR #4423 implements a feature to use a unique pglite folder if not provided. PR #4442 fixes ESM type generation in several packages including SQL, Bootstrap, and OpenAI. PR #4441 addresses typos in the codebase, and PR #4443 fixes title spacing in documentation.", "sources": [ "https://github.com/elizaOS/eliza/pull/4429", "https://github.com/elizaOS/eliza/pull/4425", "https://github.com/elizaOS/eliza/pull/4435", "https://github.com/elizaOS/eliza/pull/4439", "https://github.com/elizaOS/eliza/pull/4423", "https://github.com/elizaOS/eliza/pull/4442", "https://github.com/elizaOS/eliza/pull/4441", "https://github.com/elizaOS/eliza/pull/4443" ], "images": [], "videos": [] } ], "topic": "pull_request" }, { "title": "Issues for the repository", "repository_name": "elizaOS/eliza", "content": [ { "text": "Three issues have been reported in the elizaOS/eliza repository:\n\n1. Issue #3745: RAG processFile attempts to embed entire files, causing errors when processing large documents. This issue was reported by user omikolaj.\n\n2. Issue #4432: A job posting seeking a developer with Eliza framework experience, posted by TheDeveloperTom.\n\n3. Issue #4440: A type definition issue where the property 'preconnect' is missing, reported by user cxp-13.", "sources": [ "https://github.com/elizaOS/eliza/issues/3745", "https://github.com/elizaOS/eliza/issues/4432", "https://github.com/elizaOS/eliza/issues/4440" ], "images": [ "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/3745", "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/4432", "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/4440" ], "videos": [] } ], "topic": "issue" }, { "title": "Summary for github_summary", "content": [ { "text": "Over a two-day period (May 2-4, 2025), the elizaos/eliza repository showed the following activity:\n\n- May 2-3: 13 new PRs (7 merged), 1 new issue, and 8 active contributors\n- May 3-4: 3 new PRs (0 merged), 1 new issue, and 6 active contributors\n\nOverall, there was a decrease in PR activity and active contributors from the first day to the second.", "sources": [ "source 1", "source 2" ], "images": [], "videos": [] } ], "topic": "github_summary" }, { "title": "Summary for github_other", "content": [ { "text": "The sources provide information about the top contributors for the GitHub repository elizaOS/eliza. However, both sources contain identical information without specific details about who the contributors are or their contributions.", "sources": [ "source 1", "source 2" ], "images": [], "videos": [] } ], "topic": "github_other" } ], "date": 1746144000 } }, "ai_news_elizaos_daily_md_2025-05-02": { "filename": "2025-05-02.md", "content": "# Daily Report - 2025-05-02\n\n## Twitter Activity\n\n### AI Agents and Automation\n- @elizaOS tweeted about proactive scheduling, noting \"you say 'remind me later', I say 'already on your calendar'\" and that \"agents don't just remember, they write it down.\"\n- @elizaOS mentioned \"you changed your mind; I already updated the plan.\"\n- @shawmakesmagic discussed agent development, highlighting that \"Tokens per second is the biggest barrier for complex agents\" and that \"750 tps on Llama 3.1B with Groq\" makes a significant difference for planning agents.\n- @shawmakesmagic mentioned creating an AI agent named Spartan, referring to it as \"my Frankenstein's monster,\" and suggested that an \"agent gym could be cool.\"\n- @shawmakesmagic shared interactions with their AI agent, noting \"He's my AI agent, I created him. He's still an asshole.\"\n- Sources: https://twitter.com/elizaOS/status/1918108930305056810, https://twitter.com/elizaOS/status/1918309110975549446, https://twitter.com/elizaOS/status/1918350429185786132, https://twitter.com/shawmakesmagic/status/1918140400847753336, https://twitter.com/shawmakesmagic/status/1918272262555484300, https://twitter.com/shawmakesmagic/status/1918272896184795322, https://twitter.com/shawmakesmagic/status/1918273204088717419, https://twitter.com/shawmakesmagic/status/1918273761943736637, https://twitter.com/shawmakesmagic/status/1918274113241825309, https://twitter.com/shawmakesmagic/status/1918308527741042991\n\n### Blockchain and Cryptocurrency\n- @dankvr discussed blockchain transparency, tweeting that it's \"Another case study of how transparency curbs fraud when they started asking for receipts.\"\n- @dankvr suggested content ideas for cryptocurrency education, stating \"I enjoy the interview streams. I wanna see content that gets into fundamentals, security, hardware wallets, bitcoin/cypherpunk history...\"\n- @autodotfun shared information about PayXBT and Astra, describing them as \"The unified AI x Payments layer on Lightning Network.\"\n- @autodotfun explained these tools are \"built for the next-gen payment stack: High-frequency. Micropayments. Global, real-time settlement.\"\n- Sources: https://twitter.com/dankvr/status/1918133070206582804, https://twitter.com/dankvr/status/1918185673946812753, https://twitter.com/autodotfun/status/1918261564747948338, https://twitter.com/autodotfun/status/1918261567071649859, https://twitter.com/autodotfun/status/1918261568929751073, https://twitter.com/autodotfun/status/1918318180247666965\n\n### Web Development and Tools\n- @dankvr recommended Brave browser over Chrome, providing guidance on importing settings.\n- @shawmakesmagic shared updates on development projects, including \"WIP: Hyperfy Plugin for Eliza\" where \"Movement, chat and world state are working.\"\n- @shawmakesmagic mentioned a \"New project 89 project\" and referenced \"Elizafy\" in multiple tweets.\n- @elizaOS announced \"Fun, but programmable. @autodotfun – now in the wild ツ\".\n- Sources: https://twitter.com/dankvr/status/1918181080529772936, https://twitter.com/dankvr/status/1918184336773243045, https://twitter.com/shawmakesmagic/status/1918188290928459964, https://twitter.com/shawmakesmagic/status/1918194670372348250, https://twitter.com/shawmakesmagic/status/1918236799283216581, https://twitter.com/shawmakesmagic/status/1918420332442206485, https://twitter.com/elizaOS/status/1918400601978716291\n\n### Digital Content Creation\n- @autodotfun shared about mining public domain content, tweeting about @Tapestry_AI & @SteamBot_Willie mining \"the public domain for memeable characters, stories, and chaos fuel.\"\n- @shawmakesmagic discussed content generation for cryptocurrency projects, suggesting \"you can generate this image on autodotfun and launch it and get 90% of the fees.\"\n- @autodotfun invited followers to \"come see how the fun is made.\"\n- Sources: https://twitter.com/autodotfun/status/1918210627426005250, https://twitter.com/shawmakesmagic/status/1918239623228399858, https://twitter.com/shawmakesmagic/status/1918240403326943281, https://twitter.com/autodotfun/status/1918302958757757350\n\n### Digital Security Awareness\n- @shawmakesmagic warned about security risks, sharing \"Be careful out there. They used the actual NYPost account :O\" with an image showing what appears to be a compromised account.\n- @dankvr mentioned doing backups, noting \"It's been a year since the last full backup I did.\"\n- Sources: https://twitter.com/shawmakesmagic/status/1918415525572690242, https://twitter.com/dankvr/status/1918438109672333371\n\n### Digital Wellness\n- @dankvr suggested a digital wellness practice, advising someone to \"turn it off every Sunday.\"\n- @shawmakesmagic commented on mental health awareness and discussed AI and society.\n- Sources: https://twitter.com/dankvr/status/1918143177875247478, https://twitter.com/shawmakesmagic/status/1918245856459014506, https://twitter.com/shawmakesmagic/status/1918422384237003221\n\n## Completed Items\n\n- Several plugins were removed from the monorepo including browser (#4406), anthropic (#4427), ollama (#4437), groq (#4436), and venice (#4434).\n- New features were implemented including the use of a unique pglite folder if not provided (#4423) and a Twitter timeline feature (#4429).\n- Bug fixes and improvements were made to a template (#4431) and the Twitter plugin (#4430), while a hackish solution for copying migrations was removed (#4422).\n- Sources: https://github.com/elizaOS/eliza/pull/4406, https://github.com/elizaOS/eliza/pull/4427, https://github.com/elizaOS/eliza/pull/4437, https://github.com/elizaOS/eliza/pull/4436, https://github.com/elizaOS/eliza/pull/4434, https://github.com/elizaOS/eliza/pull/4423, https://github.com/elizaOS/eliza/pull/4429, https://github.com/elizaOS/eliza/pull/4431, https://github.com/elizaOS/eliza/pull/4430, https://github.com/elizaOS/eliza/pull/4422\n\n## GitHub Activity for elizaOS/eliza\n\n### Pull Requests\n- Recent pull requests include several feature additions and fixes:\n - PR #4429 by tcm390 adds a Twitter timeline feature\n - PR #4425 by 0xbbjoker adds documentation for Twitter agent setup\n - PR #4435 by yungalgo fixes incorrect version detection to show the correct latest CLI version\n - PR #4439 removes the plugin-local-ai from the monorepo\n - PR #4423 implements a feature to use a unique pglite folder if not provided\n - PR #4442 fixes ESM type generation in several packages\n - PR #4441 addresses typos in the codebase\n - PR #4443 fixes title spacing in documentation\n- Sources: https://github.com/elizaOS/eliza/pull/4429, https://github.com/elizaOS/eliza/pull/4425, https://github.com/elizaOS/eliza/pull/4435, https://github.com/elizaOS/eliza/pull/4439, https://github.com/elizaOS/eliza/pull/4423, https://github.com/elizaOS/eliza/pull/4442, https://github.com/elizaOS/eliza/pull/4441, https://github.com/elizaOS/eliza/pull/4443\n\n### Issues\n- Three issues have been reported:\n - Issue #3745: RAG processFile attempts to embed entire files, causing errors when processing large documents\n - Issue #4432: A job posting seeking a developer with Eliza framework experience\n - Issue #4440: A type definition issue where the property 'preconnect' is missing\n- Sources: https://github.com/elizaOS/eliza/issues/3745, https://github.com/elizaOS/eliza/issues/4432, https://github.com/elizaOS/eliza/issues/4440\n\n### Repository Activity Summary\n- Over a two-day period (May 2-4, 2025), the repository showed:\n - May 2-3: 13 new PRs (7 merged), 1 new issue, and 8 active contributors\n - May 3-4: 3 new PRs (0 merged), 1 new issue, and 6 active contributors\n- Overall, there was a decrease in PR activity and active contributors from the first day to the second.\n- Sources: source 1, source 2" }, "ai_news_elizaos_daily_discord_json_2025-05-02": { "filename": "2025-05-02.json", "content": { "server": "elizaOS", "title": "elizaOS Discord - 2025-05-02", "date": 1746144000, "stats": { "totalMessages": 294, "totalUsers": 39 }, "categories": [ { "channelId": "1253563209462448241", "channelName": "discussion", "summary": "# Discord Chat Analysis\n\n## 1. Summary\nThis Discord chat segment from the \"discussion\" channel primarily revolves around technical issues with Collabland verification for token holders, particularly those holding DegenAI tokens who lost their partner status and identity group tags. Several users reported this problem, and moderators acknowledged they were working on a fix. There was also discussion about plugin development for the Eliza platform, with specific interest in creating plugins for Reddit and LinkedIn. A moderator shared resources including GitHub repositories and the Eliza website to help developers get started. Additionally, there was brief mention of creating a dedicated space for idea sharing and discussion within the community, with a suggestion to fork an open-source project called \"negationgame\" for this purpose. The chat also touched on Bloomberg trading terminals and automated trading functionality.\n\n## 2. FAQ\nQ: What trading terminal can I use for auto fun? (asked by noj) A: Bloomberg (answered by whobody)\nQ: Has anyone been having trouble with the local ai plugin? (asked by Julo) A: A lot of people are having issues with collabland.. people on the team are aware & bare w/us, we will get it resolved. (answered by Osint (aka not_a_dev_ai))\nQ: Can I use community manager ELI5 now as in is it live? (asked by cfc1888) A: It's within v2, I think. I've seen eddy in there. (answered by Kenk)\nQ: Has anyone tried building a plugin for Reddit and LinkedIn? (asked by matt.gacek) A: Someone tried for LinkedIn but never followed through.. reddit, I don't remember. (answered by Osint (aka not_a_dev_ai))\nQ: When can we fix Collabland Degenai verification issue? (asked by Void) A: Unanswered\nQ: What's the best way to learn more and get started? (asked by EBITDA) A: In what sense? As an investor? (answered by Osint (aka not_a_dev_ai))\n\n## 3. Help Interactions\nHelper: Osint (aka not_a_dev_ai) | Helpee: Julo | Context: User having trouble with local AI plugin | Resolution: Directed user to appropriate channel and acknowledged team is aware of Collabland issues\nHelper: Kenk | Helpee: human_nalejzpa | Context: User lost partner tag and identity group tags | Resolution: Acknowledged issue, flagged it for team, and requested more information via DM\nHelper: Osint (aka not_a_dev_ai) | Helpee: matt.gacek | Context: User interested in building Reddit and LinkedIn plugins | Resolution: Provided GitHub repository link and Eliza website resources\nHelper: Osint (aka not_a_dev_ai) | Helpee: DarthGus | Context: User interested in building plugins and contributing to Zilliqa plugins | Resolution: Directed to appropriate channel and suggested joining the more technical elizaOS server\n\n## 4. Action Items\nTechnical: Fix Collabland verification issues for DegenAI token holders | Description: Multiple users reported losing partner status and identity group tags | Mentioned By: human_nalejzpa\nTechnical: Develop plugins for Reddit and LinkedIn | Description: Interest in creating these social media integrations | Mentioned By: matt.gacek\nTechnical: Fork and deploy private version of negationgame for DAO | Description: Create a dedicated space for idea sharing and discussion | Mentioned By: yikesawjeez\nFeature: Create a transparent channel where the best ideas win | Description: Establish a space for idea flow that isn't fractured across different groups | Mentioned By: Osint (aka not_a_dev_ai)\nDocumentation: Provide guidance for plugin development | Description: Resources needed for new developers interested in contributing | Mentioned By: DarthGus", "messageCount": 73, "userCount": 14 }, { "channelId": "1300025221834739744", "channelName": "💻-coders", "summary": "# Discord Chat Analysis for 💻-coders Channel\n\n## 1. Summary\nThe chat primarily focused on knowledge integration, model configuration, and troubleshooting in ElizaOS. Users discussed adding external databases as knowledge sources, with particular interest in PostgreSQL for media references. Several users encountered issues with the ElizaOS CLI during builds and project creation. There were discussions about model support, particularly regarding Deepseek integration, with questions about whether it's supported in v2 or requires a custom plugin. Knowledge implementation was a key topic, with users sharing examples of how to structure knowledge in character files and discussing RAG (Retrieval-Augmented Generation) functionality. PDF integration was also discussed, with questions about how to properly add PDFs to an agent's knowledge directory and verify their processing. The conversation revealed some confusion about model availability across different versions of ElizaOS and highlighted the need for clearer documentation on knowledge integration and model support.\n\n## 2. FAQ\nQ: Can we add external DBs as knowledge? (asked by .0xbbjoker) A: Unanswered\nQ: What's the correct way to generate text to answer an action like the agent? (asked by .0xbbjoker) A: Unanswered\nQ: Does v2 support Deepseek or do I have to write my own plugin to use it? (asked by .0xbbjoker) A: Unanswered\nQ: With this character config, if I don't have OpenAI API key and Anthropic API key, will it use local-AI? (asked by .0xbbjoker) A: Yes (answered by .0xbbjoker)\nQ: Do we have a way to count, retrieve the total amount of token that've been used from a message? (asked by Stan ⚡) A: Yes (answered by ZeorTrace/✞ᴀᴏɢ✞)\nQ: Is it a \"RUN_STARTED\" EVENT I need to work with? (asked by Stan ⚡) A: Unanswered\nQ: How do I change my Twitter agent to reply more than once to interactions on a post? (asked by .0xbbjoker) A: Unanswered\nQ: Does core handle prompt caching on the tokenizer counter? (asked by Stan ⚡) A: Unanswered\nQ: If I add PDFs to my agent's knowledge directory, how do I know the agent has processed them? (asked by .0xbbjoker) A: Unanswered\n\n## 3. Help Interactions\nHelper: .0xbbjoker | Helpee: .0xbbjoker | Context: User was having trouble with knowledge integration for character named \"Rokie\" | Resolution: Shared example character configuration with proper knowledge structure and explained that questions need more context to improve RAG retrieval\nHelper: .0xbbjoker | Helpee: .0xbbjoker | Context: User needed to install CLI | Resolution: Provided link to installation instructions\nHelper: .0xbbjoker | Helpee: .0xbbjoker | Context: User experiencing build error | Resolution: Suggested removing starterPlugin from index.ts\nHelper: .0xbbjoker | Helpee: .0xbbjoker | Context: User needed help with project setup | Resolution: Instructed to run \"elizaos start\" inside the created folder\nHelper: .0xbbjoker | Helpee: .0xbbjoker | Context: User wanted to implement character with knowledge | Resolution: Shared GitHub repo with character example and instructions for updating and running\n\n## 4. Action Items\nType: Technical | Description: Investigate EINTVAL error no:-22 during elizaos/cli:build when copying files | Mentioned By: .0xbbjoker\nType: Technical | Description: Fix issue with Twitter agent only replying once to interactions on posts | Mentioned By: .0xbbjoker\nType: Technical | Description: Implement token counting/tracking for messages including embeddings and useModel calls | Mentioned By: Stan ⚡\nType: Technical | Description: Add support for Deepseek models in ElizaOS v2 | Mentioned By: .0xbbjoker\nType: Technical | Description: Improve RAG implementation for better knowledge retrieval with minimal context | Mentioned By: .0xbbjoker\nType: Documentation | Description: Create guide for adding external databases as knowledge sources | Mentioned By: .0xbbjoker\nType: Documentation | Description: Document proper PDF integration with agents and verification of processing | Mentioned By: .0xbbjoker\nType: Documentation | Description: Clarify model availability and configuration across different ElizaOS versions | Mentioned By: .0xbbjoker\nType: Feature | Description: Implement Anthropic's \"secret sauce\" for RAG in ElizaOS | Mentioned By: .0xbbjoker\nType: Feature | Description: Add support for PostgreSQL integration for media references | Mentioned By: .0xbbjoker", "messageCount": 55, "userCount": 5 }, { "channelId": "1361442528813121556", "channelName": "fun", "summary": "# Discord Channel \"fun\" Analysis\n\n## 1. Summary\nThis channel appears to be primarily focused on discussing token launches on the Autodotfun platform. The main technical discussion revolves around the verification and launch process of tokens, particularly regarding the timing of verification relative to official announcements. Users expressed concerns about tokens being verified before being officially announced on Twitter/X, potentially giving some users an unfair advantage. There was specific discussion about a token called $PAY that was imported rather than launched on the platform, with confusion about its high initial market cap and team supply allocation. A community member named Ben clarified that Autodotfun is \"more than just a token launchpad\" but also \"a place to centralise community tools and agent building.\" Users also discussed the potential of various tokens like ELI5, with some community members creating supporting tokens like $BELI5 to help grow the ecosystem. The channel moderator (Kenk) confirmed they would continue with their current verification process despite user suggestions for changes.\n\n## 2. FAQ\nQ: Is the $PAY token legit? (asked by mhd) A: Yes, Shaw confirmed it (answered by velja)\nQ: Any partner launch tomorrow? (asked by mhd) A: No launches on weekends - next one on Monday (answered by ben)\nQ: What is up with $Eddy? (asked by Moku94) A: Unanswered\nQ: Will we see partner launches during this weekend? (asked by Tocheee) A: No launches on weekends (answered by ben)\nQ: How does a coin launch at 7m? (asked by anon) A: The team likely bought the whole curve (suggested by mhd)\nQ: What's the point of bonding if it's all bought before? (asked by anon) A: The token was imported, not launched on autofun, hence no bonding (answered by ben)\nQ: Is today's launch $PAY? (asked by Xyness) A: Yes, it's the spotlight of today (answered by ben)\n\n## 3. Help Interactions\nHelper: ben | Helpee: Multiple users | Context: Confusion about $PAY token launch | Resolution: Explained that Astra imported their token earlier than planned and clarified that autofun is more than just a token launchpad\nHelper: velja | Helpee: mhd | Context: Questioning if $PAY token is legitimate | Resolution: Confirmed it was legitimate based on information from Shaw\nHelper: ben | Helpee: ryanthelad | Context: Question about weekend launches | Resolution: Clarified no launches on weekends, next one on Monday, with launches every day the following week\n\n## 4. Action Items\nTechnical: Connect wallets on PC to improve transaction speed | Description: Allow wallet connection on PC for faster trading after seeing verified partners on mobile | Mentioned By: MDMnvest\nFeature: Notify autodotfun loyalists before public announcements | Description: Give channel members advance notice of launches before X announcements | Mentioned By: MDMnvest\nFeature: Change verification timing | Description: Verify tokens only after Autodotfun tweets on X to ensure fair launches | Mentioned By: Tocheee", "messageCount": 126, "userCount": 19 }, { "channelId": "1362864274862768450", "channelName": "fun-support", "summary": "# Discord Chat Analysis for \"fun-support\" Channel\n\n## 1. Summary:\nThe chat primarily revolves around two technical issues on the auto.fun platform. The first concerns a token (8MYgZupEQ...) that cannot be migrated because it was reportedly deployed before the platform's official launch, despite using the current program ID (autoUmixaMaYKFjexMpQuBpNYntgbkzCo2b1ZqUaAZ5). Users bheau and casper argue that migration should be possible since the token uses the live program, demonstrating that the \"Withdraw\" instruction works on similar contracts. The second issue involves user y4's token (ALLxYpyYbrPjXeeGRsPWB2Q4qxPFjfbunDoNuoKsXFUN) that was removed from listings for allegedly mimicking a verified token, preventing the user from selling their holdings. Kenk, representing the platform, offered to arrange a solution for y4 via DM. Another user, Kodak, reported a bugged token that gives errors when attempting to trade, and was directed to fill out a form for the engineering team.\n\n## 2. FAQ:\nQ: Why can't the token at 8MYgZupEQ be migrated? (asked by bheau) A: The contract was deployed before auto.fun officially launched and is tied to an earlier program ID that the migration tool can't reach, despite using the current program ID. (answered by Kenk)\nQ: Can you migrate a token that was created on the currently used, live program (autoUmixaMaYKFjexMpQuBpNYntgbkzCo2b1ZqUaAZ5)? (asked by bheau) A: We've explored this and explained that we're not able to migrate because the contract was made before the platform was live. (answered by Kenk)\nQ: Why can't I sell my token ALLxYpyYbrPjXeeGRsPWB2Q4qxPFjfbunDoNuoKsXFUN? (asked by Kodak) A: Please fill out this form: https://tally.so/r/mOr8DM and I'll flag to the engineering team. (answered by Kenk)\nQ: Why was my token removed and I can't sell my supply? (asked by y4) A: We removed the token from the listing as it was mimicking a verified token - we can enable you to sell but we will need to arrange this. (answered by Kenk)\n\n## 3. Help Interactions:\nHelper: Kenk | Helpee: Kodak | Context: User reported a bugged token (ALLxYpyYbrPjXeeGRsPWB2Q4qxPFjfbunDoNuoKsXFUN) that gives errors when attempting to trade | Resolution: Kenk provided a form for the user to fill out and promised to flag the issue to the engineering team\nHelper: Kenk | Helpee: y4 | Context: User unable to sell token that was removed from listings for allegedly mimicking a verified token | Resolution: Kenk offered to arrange a solution via DM\n\n## 4. Action Items:\nTechnical: Investigate migration possibility for token on live program ID (autoUmixaMaYKFjexMpQuBpNYntgbkzCo2b1ZqUaAZ5) created before platform launch | Mentioned By: bheau\nTechnical: Fix trading error for token ALLxYpyYbrPjXeeGRsPWB2Q4qxPFjfbunDoNuoKsXFUN | Mentioned By: Kodak\nTechnical: Arrange selling capability for y4's delisted token | Mentioned By: y4\nDocumentation: Clarify policy on tokens created before platform launch but on current program ID | Mentioned By: bheau\nDocumentation: Provide clear guidelines on token naming to avoid mimicking verified tokens | Mentioned By: y4", "messageCount": 40, "userCount": 7 } ] } }, "ai_news_elizaos_daily_discord_md_2025-05-02": { "filename": "2025-05-02.md", "content": "# elizaOS Discord - 2025-05-02\n\n## Overall Discussion Highlights\n\n### Platform Development & Technical Issues\n- **Collabland Verification Issues**: Multiple users reported losing partner status and identity group tags, particularly DegenAI token holders. The team is aware and working on a fix.\n- **Plugin Development**: Discussions about creating plugins for Reddit and LinkedIn, with resources shared including GitHub repositories and the Eliza website.\n- **Knowledge Integration**: Users explored adding external databases (particularly PostgreSQL) as knowledge sources for agents and discussed proper implementation of RAG (Retrieval-Augmented Generation).\n- **Model Support**: Questions about Deepseek integration in v2 and whether it requires a custom plugin.\n- **ElizaOS CLI Issues**: Several users encountered errors during builds and project creation.\n\n### Auto.fun Platform\n- **Token Verification Process**: Debate about the timing of token verification relative to official announcements, with concerns about fairness.\n- **Token Migration Issues**: Discussion about tokens that cannot be migrated despite using the current program ID because they were deployed before the platform's official launch.\n- **Token Listing Removals**: A user reported their token was removed for allegedly mimicking a verified token, preventing them from selling their holdings.\n- **Platform Scope**: Community member Ben clarified that Autodotfun is \"more than just a token launchpad\" but also \"a place to centralise community tools and agent building.\"\n\n### Community Building\n- **Idea Sharing Space**: Suggestion to fork an open-source project called \"negationgame\" to create a dedicated space for idea sharing and discussion.\n- **Supporting Tokens**: Community members creating supporting tokens like $BELI5 to help grow the ecosystem.\n- **Launch Schedule**: Confirmation that no token launches occur on weekends, with the next one scheduled for Monday.\n\n## Key Questions & Answers\n\n### Technical Implementation\n- **Q**: Has anyone been having trouble with the local ai plugin? \n **A**: \"A lot of people are having issues with collabland.. people on the team are aware & bare w/us, we will get it resolved.\" - Osint\n\n- **Q**: What trading terminal can I use for auto fun? \n **A**: \"Bloomberg\" - whobody\n\n- **Q**: With this character config, if I don't have OpenAI API key and Anthropic API key, will it use local-AI? \n **A**: \"Yes\" - .0xbbjoker\n\n- **Q**: Do we have a way to count, retrieve the total amount of token that've been used from a message? \n **A**: \"Yes\" - ZeorTrace/✞ᴀᴏɢ✞\n\n### Auto.fun Platform\n- **Q**: Is the $PAY token legit? \n **A**: \"Yes, Shaw confirmed it\" - velja\n\n- **Q**: Any partner launch tomorrow? \n **A**: \"No launches on weekends - next one on Monday\" - ben\n\n- **Q**: How does a coin launch at 7m? \n **A**: \"The team likely bought the whole curve\" - mhd\n\n- **Q**: What's the point of bonding if it's all bought before? \n **A**: \"The token was imported, not launched on autofun, hence no bonding\" - ben\n\n- **Q**: Why can't the token at 8MYgZupEQ be migrated? \n **A**: \"The contract was deployed before auto.fun officially launched and is tied to an earlier program ID that the migration tool can't reach, despite using the current program ID.\" - Kenk\n\n## Community Help & Collaboration\n\n### Plugin Development Support\n- **.0xbbjoker** shared example character configurations with proper knowledge structure and explained that questions need more context to improve RAG retrieval.\n- **Osint** provided GitHub repository links and Eliza website resources to **matt.gacek** who was interested in building Reddit and LinkedIn plugins.\n\n### Platform Clarifications\n- **ben** explained to multiple users that Astra imported their token earlier than planned and clarified that autofun is more than just a token launchpad.\n- **velja** confirmed to **mhd** that the $PAY token was legitimate based on information from Shaw.\n\n### Technical Issue Resolution\n- **Kenk** acknowledged issues with partner tags and identity group tags, flagged it for the team, and requested more information via DM from **human_nalejzpa**.\n- **Kenk** provided a form for **Kodak** to report a bugged token and promised to flag the issue to the engineering team.\n- **.0xbbjoker** helped troubleshoot CLI issues by suggesting removing starterPlugin from index.ts and instructing to run \"elizaos start\" inside the created folder.\n\n## Action Items\n\n### Technical\n- Fix Collabland verification issues for DegenAI token holders (Mentioned by: human_nalejzpa)\n- Investigate EINTVAL error no:-22 during elizaos/cli:build when copying files (Mentioned by: .0xbbjoker)\n- Fix issue with Twitter agent only replying once to interactions on posts (Mentioned by: .0xbbjoker)\n- Implement token counting/tracking for messages including embeddings and useModel calls (Mentioned by: Stan ⚡)\n- Add support for Deepseek models in ElizaOS v2 (Mentioned by: .0xbbjoker)\n- Improve RAG implementation for better knowledge retrieval with minimal context (Mentioned by: .0xbbjoker)\n- Investigate migration possibility for token on live program ID created before platform launch (Mentioned by: bheau)\n- Fix trading error for token ALLxYpyYbrPjXeeGRsPWB2Q4qxPFjfbunDoNuoKsXFUN (Mentioned by: Kodak)\n- Arrange selling capability for y4's delisted token (Mentioned by: y4)\n- Connect wallets on PC to improve transaction speed (Mentioned by: MDMnvest)\n\n### Documentation\n- Create guide for adding external databases as knowledge sources (Mentioned by: .0xbbjoker)\n- Document proper PDF integration with agents and verification of processing (Mentioned by: .0xbbjoker)\n- Clarify model availability and configuration across different ElizaOS versions (Mentioned by: .0xbbjoker)\n- Provide guidance for plugin development (Mentioned by: DarthGus)\n- Clarify policy on tokens created before platform launch but on current program ID (Mentioned by: bheau)\n- Provide clear guidelines on token naming to avoid mimicking verified tokens (Mentioned by: y4)\n\n### Feature\n- Develop plugins for Reddit and LinkedIn (Mentioned by: matt.gacek)\n- Fork and deploy private version of negationgame for DAO (Mentioned by: yikesawjeez)\n- Create a transparent channel where the best ideas win (Mentioned by: Osint)\n- Implement Anthropic's \"secret sauce\" for RAG in ElizaOS (Mentioned by: .0xbbjoker)\n- Add support for PostgreSQL integration for media references (Mentioned by: .0xbbjoker)\n- Notify autodotfun loyalists before public announcements (Mentioned by: MDMnvest)\n- Change verification timing to ensure fair launches (Mentioned by: Tocheee)" }, "ai_news_elizaos_daily_dev_json_2025-05-02": { "filename": "2025-05-02.json", "content": { "server": "elizaOS Development", "title": "elizaOS Development Discord - 2025-05-02", "date": 1746144000, "stats": { "totalMessages": 36, "totalUsers": 12 }, "categories": [ { "channelId": "1320246527268098048", "channelName": "💬｜general", "summary": "# Analysis of 💬｜general Discord Channel\n\n## 1. Summary:\nThe chat primarily revolves around ElizaOS development and usage issues. Key technical discussions include model configuration for Anthropic API, Windows compatibility issues with ElizaOS, and questions about the new v2 architecture where plugins are separated. Users encountered problems with conversation history disappearing after inactivity and changing default model settings. There was clarification that environment variables can be modified to change the AI model being used, specifically setting `SMALL_ANTHROPIC_MODEL=claude-3-5-sonnet-20241022` in the .env file to switch from Haiku to Sonnet. The conversation also touched on broken documentation links and questions about differences between v1.0.0-beta and v2.\n\n## 2. FAQ:\nQ: Does ElizaOS use the index.ts file after using elizaos create? (asked by WizardlyLuke) A: Try using \"elizaos start\" instead of npm commands (answered by sayonara)\nQ: How does ElizaOS determine which LLM it's using when multiple keys are set up? (asked by WizardlyLuke) A: Unanswered\nQ: Why does my conversation with AI agent disappear after a few minutes? (asked by Ocisly) A: Unanswered\nQ: How can I make the agent use the Sonnet model instead of Haiku? (asked by Buttered) A: Change `SMALL_ANTHROPIC_MODEL=claude-3-5-sonnet-20241022` in your .env file (answered by sayonara)\nQ: Is v2 different than the 1.0.0-beta? (asked by WizardlyLuke) A: Unanswered\nQ: What version should I be using? (asked by WizardlyLuke) A: Unanswered\nQ: Are there any good open source projects building on Eliza's v2? (asked by lantianlaoli) A: Unanswered\nQ: Is it possible to dynamically load new characters with plugins while the runtime is running? (asked by DorianD) A: If plugins are already installed it should work, but might cause issues if not installed (answered by shaw)\n\n## 3. Help Interactions:\nHelper: sayonara | Helpee: WizardlyLuke | Context: ElizaOS not using updated index.ts file on Windows | Resolution: Suggested using \"elizaos start\" command and confirmed it works in WSL\nHelper: sayonara | Helpee: Buttered | Context: Difficulty making agent use Sonnet model instead of Haiku | Resolution: Provided specific environment variable to change in .env file with reference to GitHub code\nHelper: shaw | Helpee: DorianD | Context: Question about dynamically loading characters with plugins | Resolution: Suggested it should work if plugins are already installed but might cause issues otherwise\n\n## 4. Action Items:\nTechnical: Fix broken documentation links on eliza.how website | Description: Links like https://eliza.how/blog/v1-v2 are not working | Mentioned By: WizardlyLuke\nTechnical: Fix conversation history disappearing after 3-5 minutes of inactivity | Description: In version 0.25.9, chat history disappears after brief periods of inactivity | Mentioned By: Ocisly\nTechnical: Improve Windows compatibility | Description: ElizaOS has issues with code changes not being reflected when running on Windows | Mentioned By: WizardlyLuke\nDocumentation: Create clear documentation about model selection and environment variables | Description: Users are confused about how to change models and what env variables control this | Mentioned By: Buttered\nDocumentation: Clarify differences between v1.0.0-beta and v2 | Description: Users are confused about version differences and which to use | Mentioned By: WizardlyLuke", "messageCount": 34, "userCount": 11 }, { "channelId": "1324089429727514674", "channelName": "🤖｜agent-dev-school", "summary": "The chat segment is extremely brief, containing only a single interaction. YungYoda advises another user that they need to use Ubuntu WSL2 for Windows to run a program called \"eliza\" properly. This suggests there may have been a prior discussion about compatibility issues with running eliza on Windows natively, and YungYoda is providing a solution by recommending the Windows Subsystem for Linux (WSL2) with Ubuntu as the environment where eliza runs without problems.", "messageCount": 2, "userCount": 1 } ] } }, "ai_news_elizaos_daily_dev_md_2025-05-02": { "filename": "2025-05-02.md", "content": "# elizaOS Development Discord - 2025-05-02\n\n## Overall Discussion Highlights\n\n### ElizaOS Development & Architecture\n- Discussions about the new v2 architecture where plugins are separated from the core system\n- Questions about differences between v1.0.0-beta and v2 versions\n- Interest in open source projects building on Eliza's v2 architecture\n- Exploration of dynamically loading new characters with plugins while the runtime is running\n\n### Technical Configuration\n- Model configuration for Anthropic API was a key topic\n- Environment variables can be modified to change the AI model being used\n- Specific guidance on switching from Haiku to Sonnet model by setting `SMALL_ANTHROPIC_MODEL=claude-3-5-sonnet-20241022` in the .env file\n\n### Platform Compatibility\n- Windows compatibility issues with ElizaOS were discussed\n- Recommendation to use Ubuntu WSL2 for Windows to run ElizaOS properly\n- Confirmation that ElizaOS works in WSL environment without the issues experienced in native Windows\n\n### User Experience Issues\n- Users reported conversation history disappearing after 3-5 minutes of inactivity\n- Questions about changing default model settings\n- Broken documentation links on the eliza.how website\n\n## Key Questions & Answers\n\n**Q: Does ElizaOS use the index.ts file after using elizaos create?** (asked by WizardlyLuke) \n**A:** Try using \"elizaos start\" instead of npm commands (answered by sayonara)\n\n**Q: How can I make the agent use the Sonnet model instead of Haiku?** (asked by Buttered) \n**A:** Change `SMALL_ANTHROPIC_MODEL=claude-3-5-sonnet-20241022` in your .env file (answered by sayonara)\n\n**Q: Is it possible to dynamically load new characters with plugins while the runtime is running?** (asked by DorianD) \n**A:** If plugins are already installed it should work, but might cause issues if not installed (answered by shaw)\n\n**Q: How do I run ElizaOS on Windows?** (implied question) \n**A:** Use Ubuntu WSL2 for Windows to run ElizaOS properly (answered by YungYoda)\n\n## Community Help & Collaboration\n\n1. **Windows Compatibility Assistance**\n - **Helper:** sayonara\n - **Helpee:** WizardlyLuke\n - **Context:** ElizaOS not using updated index.ts file on Windows\n - **Resolution:** Suggested using \"elizaos start\" command and confirmed it works in WSL\n\n2. **Model Configuration Support**\n - **Helper:** sayonara\n - **Helpee:** Buttered\n - **Context:** Difficulty making agent use Sonnet model instead of Haiku\n - **Resolution:** Provided specific environment variable to change in .env file with reference to GitHub code\n\n3. **Plugin Architecture Guidance**\n - **Helper:** shaw\n - **Helpee:** DorianD\n - **Context:** Question about dynamically loading characters with plugins\n - **Resolution:** Suggested it should work if plugins are already installed but might cause issues otherwise\n\n4. **Platform Compatibility Advice**\n - **Helper:** YungYoda\n - **Context:** Running ElizaOS on Windows\n - **Resolution:** Recommended using Ubuntu WSL2 for Windows\n\n## Action Items\n\n### Technical\n- **Fix broken documentation links on eliza.how website**\n - Description: Links like https://eliza.how/blog/v1-v2 are not working\n - Mentioned By: WizardlyLuke\n\n- **Fix conversation history disappearing after inactivity**\n - Description: In version 0.25.9, chat history disappears after 3-5 minutes of inactivity\n - Mentioned By: Ocisly\n\n- **Improve Windows compatibility**\n - Description: ElizaOS has issues with code changes not being reflected when running on Windows\n - Mentioned By: WizardlyLuke\n\n### Documentation\n- **Create clear documentation about model selection and environment variables**\n - Description: Users are confused about how to change models and what env variables control this\n - Mentioned By: Buttered\n\n- **Clarify differences between v1.0.0-beta and v2**\n - Description: Users are confused about version differences and which to use\n - Mentioned By: WizardlyLuke\n\n- **Develop comprehensive Windows setup guide**\n - Description: Document the process for setting up ElizaOS in WSL2 environment\n - Mentioned By: YungYoda (implied)" }, "ai_news_hyperfy_daily_json_2025-05-02": { "filename": "2025-05-02.json", "content": { "server": "Hyperfy", "title": "Hyperfy Discord - 2025-05-02", "date": 1746144000, "stats": { "totalMessages": 124, "totalUsers": 27 }, "categories": [ { "channelId": "994775534733115412", "channelName": "💻│developers", "summary": "# Discord Chat Analysis for 💻│developers\n\n## 1. Summary\nThe discussion primarily revolves around Hyperfy v2 development and features. Key technical highlights include:\n\n- Peezy announced the release of the \"ai\" hypkg package (https://hypkg.sh/hypkg/ai/) with a corresponding GitHub branch for Docker users.\n- Ashxn shared updates about PhysX builds, mentioning the creation of a single build that works for both Node and browser environments, which is relevant for logical clients. They also removed PhysX built-in vehicle imports, reducing code size by approximately 4MB.\n- VR functionality was discussed, particularly the current lack of rotation capability in immersive view. Ashxn clarified that body turn and interact buttons still need to be added, noting that snap turn functionality (previously available in v1) is not currently a priority.\n- Gert-Jan Akerboom inquired about implementing an emission intensity slider for a neon letters app, and Ashxn provided guidance on using the emissiveIntensity property with mesh materials.\n- HiroP expressed interest in implementing snap turn functionality for VR and asked for reference implementations.\n- Vox inquired about customizable loading screens for Hyperfy.\n- There was brief mention of vehicle implementations, with Ashxn noting they have better car implementations than PhysX vehicle controllers.\n\n## 2. FAQ\nQ: How can I implement an emission intensity slider for my neon letters app? (asked by Gert-Jan Akerboom) A: Use a range field and connect it to the material with `mesh.material.emissiveIntensity = value`. Make sure your emissive color in Blender isn't black. (answered by Ashxn)\nQ: Is the inability to rotate the view in VR a known issue? (asked by hiroP) A: Current build has no rotation functionality; it will be added later. (answered by vox)\nQ: What does it take to have customizable loading screens for Hyperfy? (asked by vox) A: Unanswered\nQ: How do I implement snap turn in VR? (asked by hiroP) A: It's a common VR feature that applies an offset to rotation by X degrees. (answered by Ashxn)\nQ: Does removing PhysX vehicle imports mean cars are dead? (asked by peezy) A: No, they have better car implementations than PhysX vehicle controllers can provide. (answered by Ashxn)\n\n## 3. Help Interactions\nHelper: Ashxn | Helpee: Gert-Jan Akerboom | Context: Implementing emission intensity slider for neon letters app | Resolution: Explained how to use mesh.material.emissiveIntensity and connect it to a range field, noting the importance of non-black emissive color in Blender\nHelper: vox | Helpee: hiroP | Context: VR rotation functionality in Hyperfy v2 | Resolution: Clarified that rotation is not implemented in the current build and will be added later\nHelper: Ashxn | Helpee: hiroP | Context: Implementing snap turn in VR | Resolution: Explained that snap turn is a common VR feature that applies rotation offset by X degrees\n\n## 4. Action Items\nTechnical: Implement VR rotation/snap turn functionality | Description: Add body turn and interact buttons to VR mode | Mentioned By: Ashxn\nTechnical: Create GitHub actions to build Docker images for modded branches | Description: Automate image creation from modified branches | Mentioned By: peezy\nTechnical: Implement customizable loading screens | Description: Allow for custom loading screens similar to third-person-rig example | Mentioned By: vox\nDocumentation: Document PhysX vehicle alternatives | Description: Explain the raycast vehicle implementation that replaces PhysX vehicle controllers | Mentioned By: Ashxn\nFeature: Create demo videos for AI hypkg | Description: Showcase the functionality of the new AI package | Mentioned By: peezy", "messageCount": 63, "userCount": 10 }, { "channelId": "958209074045026327", "channelName": "⚡│general", "summary": "# Analysis of Discord Chat in \"⚡│general\" Channel\n\n## 1. Summary:\nThe chat primarily revolves around AI integration with Hyperfy, specifically a project called \"Elizafy\" developed by Shaw. This appears to be a headless client that allows AI agents to connect to Hyperfy worlds just like human users would. A demonstration video shows an autonomous agent connecting to a world and navigating independently, with visible key inputs. There was also a significant discussion about Hyperfy v2's GPL license implications for corporate clients, with clarification that the license only applies to core improvements, not applications built on top of the platform. Users expressed excitement about the potential for AI agents as players in virtual worlds and the possibilities for AI-curated environments.\n\n## 2. FAQ:\nQ: Is shaw using the hyperfy engine? (asked by simk) A: Yes, he made a headless client that allows AI agents (Elizafy) to connect to Hyperfy worlds like humans would (answered by Ashxn)\nQ: What is elizafy? (asked by simk) A: A system that allows AI agents to connect to any Hyperfy world just like a human would (answered by Ashxn)\nQ: How would we give the AI \"Vision\" so it can see what is in the world and interact with things? (asked by Agent12) A: Unanswered\n\n## 3. Help Interactions:\nHelper: Ashxn | Helpee: hiroP | Context: Concerns about GPL license implications for using Hyperfy v2 with corporate clients | Resolution: Clarified that the license only applies to core improvements, not applications built on top, comparing it to Linux's GPL license\nHelper: Ashxn | Helpee: simk | Context: Questions about what Elizafy is and if Shaw is using Hyperfy engine | Resolution: Explained that Shaw created a headless client allowing AI agents to connect to Hyperfy worlds like humans\n\n## 4. Action Items:\nTechnical: Implement position/engagement analytics to track user coordinates | Mentioned By: maximus\nFeature: AI vision capabilities for agents to see and interact with world objects | Mentioned By: Agent12\nFeature: Support for autonomous AI agents as players in virtual worlds | Mentioned By: peezy\nFeature: AI-curated worlds | Mentioned By: Agent12", "messageCount": 46, "userCount": 16 }, { "channelId": "1326789867312775290", "channelName": "🪙│hyper", "summary": "# Analysis of Discord Chat in 🪙│hyper Channel\n\n## 1. Summary\nThis chat segment contains minimal technical discussion. The conversation primarily consists of users checking the price of HYPER token, with Rick (a bot) responding with price information. One user (Z aka MetaDJ) asks about finding Hyperfy on TradingView, and CheddarQueso responds with a recommendation to use Phantom wallet for trading and Dexscreener for price monitoring, providing what appears to be a token address. The chat shows some sentiment around price movements with comments about selling and \"we back baby\" suggesting a price recovery. There are no substantive technical discussions, problem-solving activities, or implementation details in this segment.\n\n## 2. FAQ\nQ: What pairing do you have on TradingView? I no longer can find Hyperfy. (asked by Z aka MetaDJ) A: I trade in my phantom wallet and watch on Dexscreener 8vBMibwpn8wpfYKbQ9xqzodymg3LjmYec2tSNGRy23K8 (answered by CheddarQueso 🧀)\n\n## 3. Help Interactions\nHelper: CheddarQueso 🧀 | Helpee: Z aka MetaDJ | Context: User couldn't find Hyperfy on TradingView | Resolution: Suggested using Phantom wallet for trading and Dexscreener for price monitoring, provided a token address\n\n## 4. Action Items\nNo action items identified in this chat segment.", "messageCount": 12, "userCount": 8 }, { "channelId": "1031058655581323324", "channelName": "🧊│3d-design", "summary": "The chat segment is extremely brief with only three messages. Ashxn commented on how fog and mountain ranges create a sense of scale in 3D environments. Another user (untitled, xyz) complimented someone's work and inquired about adding depth of field functionality. Finally, 𝕽𝖔𝖚𝖘𝖙𝖆𝖓 asked a brief question about \"hyp\" (likely referring to a feature or update). There were no substantial technical discussions, problem-solving activities, or concrete implementations in this limited exchange.", "messageCount": 3, "userCount": 3 } ] } }, "ai_news_hyperfy_daily_md_2025-05-02": { "filename": "2025-05-02.md", "content": "# Hyperfy Discord - 2025-05-02\n\n## Overall Discussion Highlights\n\n### AI Integration & Development\n- **Elizafy Project**: Shaw demonstrated a headless client that allows AI agents to connect to Hyperfy worlds just like human users would. The demo video showed an autonomous agent connecting to a world and navigating independently.\n- **AI Package Release**: Peezy announced the release of the \"ai\" hypkg package (https://hypkg.sh/hypkg/ai/) with a corresponding GitHub branch for Docker users.\n- Users expressed excitement about the potential for AI agents as players in virtual worlds and the possibilities for AI-curated environments.\n\n### Hyperfy v2 Technical Updates\n- **PhysX Improvements**: Ashxn shared updates about PhysX builds, mentioning the creation of a single build that works for both Node and browser environments. They also removed PhysX built-in vehicle imports, reducing code size by approximately 4MB.\n- **VR Functionality**: Current VR implementation lacks rotation capability in immersive view. Ashxn clarified that body turn and interact buttons still need to be added, noting that snap turn functionality is not currently a priority.\n- **Vehicle Implementation**: Despite removing PhysX vehicle imports, Ashxn noted they have better car implementations than PhysX vehicle controllers.\n\n### Licensing & Business Concerns\n- Discussion about Hyperfy v2's GPL license implications for corporate clients\n- Clarification that the license only applies to core improvements, not applications built on top of the platform (similar to Linux's GPL license)\n\n### HYPER Token\n- Users were checking the price of HYPER token throughout the day\n- Some sentiment around price movements with comments suggesting a price recovery (\"we back baby\")\n\n### 3D Design\n- Brief discussion about how fog and mountain ranges create a sense of scale in 3D environments\n- Interest in depth of field functionality\n\n## Key Questions & Answers\n\n**Q: How can I implement an emission intensity slider for my neon letters app?** (asked by Gert-Jan Akerboom) \nA: Use a range field and connect it to the material with `mesh.material.emissiveIntensity = value`. Make sure your emissive color in Blender isn't black. (answered by Ashxn)\n\n**Q: Is the inability to rotate the view in VR a known issue?** (asked by hiroP) \nA: Current build has no rotation functionality; it will be added later. (answered by vox)\n\n**Q: How do I implement snap turn in VR?** (asked by hiroP) \nA: It's a common VR feature that applies an offset to rotation by X degrees. (answered by Ashxn)\n\n**Q: Does removing PhysX vehicle imports mean cars are dead?** (asked by peezy) \nA: No, they have better car implementations than PhysX vehicle controllers can provide. (answered by Ashxn)\n\n**Q: Is shaw using the hyperfy engine?** (asked by simk) \nA: Yes, he made a headless client that allows AI agents (Elizafy) to connect to Hyperfy worlds like humans would. (answered by Ashxn)\n\n**Q: What is elizafy?** (asked by simk) \nA: A system that allows AI agents to connect to any Hyperfy world just like a human would. (answered by Ashxn)\n\n**Q: What pairing do you have on TradingView? I no longer can find Hyperfy.** (asked by Z aka MetaDJ) \nA: \"I trade in my phantom wallet and watch on Dexscreener 8vBMibwpn8wpfYKbQ9xqzodymg3LjmYec2tSNGRy23K8\" (answered by CheddarQueso 🧀)\n\n## Community Help & Collaboration\n\n1. **VR Implementation Guidance**\n - Helper: Ashxn & vox\n - Helpee: hiroP\n - Context: VR rotation functionality in Hyperfy v2\n - Resolution: Clarified that rotation is not implemented in the current build and will be added later. Explained that snap turn is a common VR feature that applies rotation offset by X degrees.\n\n2. **Material Properties for 3D Design**\n - Helper: Ashxn\n - Helpee: Gert-Jan Akerboom\n - Context: Implementing emission intensity slider for neon letters app\n - Resolution: Explained how to use mesh.material.emissiveIntensity and connect it to a range field, noting the importance of non-black emissive color in Blender.\n\n3. **License Clarification**\n - Helper: Ashxn\n - Helpee: hiroP\n - Context: Concerns about GPL license implications for using Hyperfy v2 with corporate clients\n - Resolution: Clarified that the license only applies to core improvements, not applications built on top, comparing it to Linux's GPL license.\n\n4. **Token Trading Support**\n - Helper: CheddarQueso 🧀\n - Helpee: Z aka MetaDJ\n - Context: User couldn't find Hyperfy on TradingView\n - Resolution: Suggested using Phantom wallet for trading and Dexscreener for price monitoring, provided a token address.\n\n## Action Items\n\n### Technical\n- **Implement VR rotation/snap turn functionality** (Mentioned by Ashxn)\n - Add body turn and interact buttons to VR mode\n- **Create GitHub actions to build Docker images for modded branches** (Mentioned by peezy)\n - Automate image creation from modified branches\n- **Implement position/engagement analytics** (Mentioned by maximus)\n - Track user coordinates in virtual spaces\n\n### Documentation\n- **Document PhysX vehicle alternatives** (Mentioned by Ashxn)\n - Explain the raycast vehicle implementation that replaces PhysX vehicle controllers\n\n### Feature\n- **Create demo videos for AI hypkg** (Mentioned by peezy)\n - Showcase the functionality of the new AI package\n- **Implement customizable loading screens** (Mentioned by vox)\n - Allow for custom loading screens similar to third-person-rig example\n- **AI vision capabilities** (Mentioned by Agent12)\n - Develop systems for AI agents to see and interact with world objects\n- **Support for autonomous AI agents** (Mentioned by peezy)\n - Enable AI agents to function as players in virtual worlds\n- **AI-curated worlds** (Mentioned by Agent12)\n - Develop functionality for AI to manage and curate virtual environments" }, "github_summaries_daily_2025-05-03": { "filename": "2025-05-03.md", "content": "# ElizaOS Daily Update (May 3, 2025)\n\n## OVERVIEW \nToday, there were no new features, bug fixes, or enhancements made to the ElizaOS project. However, one issue was successfully closed, indicating progress in resolving build-related challenges. A new issue was also reported, highlighting a type error in the codebase that requires attention.\n\n## KEY TECHNICAL DEVELOPMENTS\n- **No Completed Work:** \n - No features, bug fixes, code refactoring, documentation enhancements, or tests were added today.\n\n## CLOSED ISSUES\n- **Build Issues Resolved:**\n - The issue regarding the inability to build on Windows has been closed. The error was related to a missing command in the build script, which has been addressed. See [#4094](https://github.com/elizaos/eliza/issues/4094) for details.\n\n## NEW ISSUES\n- **Type Error Reported:**\n - A new issue has been opened concerning a missing property 'preconnect' in the type definition, which is causing a TypeScript error. This needs to be investigated and resolved. See [#4440](https://github.com/elizaos/eliza/issues/4440) for more information." }, "github_summaries_week_latest_2025-05-18.md": { "filename": "2025-05-18.md", "content": "# ElizaOS Weekly Update (May 18 - 24, 2025)\n\n## OVERVIEW\nThis week saw significant expansion of ElizaOS's API capabilities with new endpoints for worlds, rooms, and agent messaging. The team enhanced plugin infrastructure with registry integration and timeout handling, while fixing critical UI responsiveness issues. Major progress was made on the Polygon plugin, bringing blockchain functionality to the framework. Test reliability was improved across CLI commands and integration tests.\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### API Expansion and World Management\n- Added new API endpoints for creating and managing worlds and rooms ([#4667](https://github.com/elizaos/eliza/pull/4667), [#4647](https://github.com/elizaos/eliza/pull/4647))\n- Enhanced message API with world selection capabilities, allowing messages to be associated with specific worlds ([#4637](https://github.com/elizaos/eliza/pull/4637))\n- Improved agent creation API to return agent ID in the initial response, eliminating the need for subsequent calls ([#4634](https://github.com/elizaos/eliza/pull/4634))\n\n### Plugin Infrastructure Improvements\n- Implemented registry integration for plugins with 30-second timeout protection ([#4641](https://github.com/elizaos/eliza/pull/4641), [#4678](https://github.com/elizaos/eliza/pull/4678))\n- Added channel ID filtering capability to Discord plugin ([#4665](https://github.com/elizaos/eliza/pull/4665))\n- Removed global environment variable support in favor of local environment management ([#4666](https://github.com/elizaos/eliza/pull/4666))\n- Integrated Sentry logging for core logger errors ([#4650](https://github.com/elizaos/eliza/pull/4650))\n\n### Blockchain Integration Progress\n- Made significant progress on Polygon plugin implementation, including core EVM RPC wrappers and basic read operations ([#4575](https://github.com/elizaos/eliza/pull/4575))\n- Added Polygon Gas Oracle integration for transaction fee estimation ([#4574](https://github.com/elizaos/eliza/pull/4574))\n- Started work on Jupiter Swap plugin for cryptocurrency trading functionality ([#4593](https://github.com/elizaos/eliza/pull/4593))\n\n### Bug Fixes and Test Improvements\n- Fixed UI responsiveness issue with agent start button not updating status in real-time ([#4642](https://github.com/elizaos/eliza/pull/4642))\n- Resolved issues with dynamic providers in reply actions ([#4651](https://github.com/elizaos/eliza/pull/4651), [#4670](https://github.com/elizaos/eliza/pull/4670))\n- Improved test reliability by fixing flakiness in bats tests and addressing integration test failures ([#4663](https://github.com/elizaos/eliza/pull/4663), [#4654](https://github.com/elizaos/eliza/pull/4654))\n\n## CLOSED ISSUES\n\n### Documentation and Community Improvements\n- Updated community section documentation with improved navigation flowcharts for both technical and non-technical users ([#4260](https://github.com/elizaos/eliza/issues/4260))\n- Enhanced project documentation with updated blog posts and comprehensive partner documentation ([#4586](https://github.com/elizaos/eliza/pull/4586))\n- Implemented automatic documentation deployment workflow for changes to the docs folder ([#4640](https://github.com/elizaos/eliza/pull/4640), [#4631](https://github.com/elizaos/eliza/pull/4631))\n\n### Technical Debt and Architecture Improvements\n- Addressed platform interface needs in core package for ElizaOS v2 ([#3491](https://github.com/elizaos/eliza/issues/3491))\n- Resolved agent hanging issues after core initialization with specific configurations ([#4486](https://github.com/elizaos/eliza/issues/4486))\n- Improved dependency management with request to publish to npm for better version compatibility ([#4562](https://github.com/elizaos/eliza/issues/4562))\n\n## NEW ISSUES\n\nNo new issues were reported during this period. The team focused on addressing existing issues and implementing planned features." }, "github_summaries_month_latest_2025-05-01.md": { "filename": "2025-05-01.md", "content": "# ElizaOS Monthly Update (May 2025)\n\n## OVERVIEW\nMay was a transformative month for ElizaOS with significant enhancements to the framework's core architecture and plugin ecosystem. The team focused on improving CLI functionality, refining agent interactions, and streamlining the plugin management system. Major strides were made in database operations, authentication mechanisms, and documentation, while several plugins were moved to standalone repositories to support the new plugin sharing system between v0.x and v1.x.\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### CLI Enhancements and Command Refinements\n- Improved CLI commands with better documentation and consistent behavior across platforms ([#4646](https://github.com/elizaos/eliza/pull/4646), [#4583](https://github.com/elizaos/eliza/pull/4583))\n- Consolidated update commands for better user experience ([#4592](https://github.com/elizaos/eliza/pull/4592), [#4591](https://github.com/elizaos/eliza/pull/4591))\n- Enhanced environment variable management with better system information display ([#4610](https://github.com/elizaos/eliza/pull/4610), [#4445](https://github.com/elizaos/eliza/pull/4445))\n- Improved dev command with better character file handling ([#4618](https://github.com/elizaos/eliza/pull/4618))\n\n### Plugin System Restructuring\n- Prepared v0.x for sharing plugins with v1.x ([#4384](https://github.com/elizaos/eliza/pull/4384))\n- Added support for third-party plugin installation directly from GitHub URLs ([#4568](https://github.com/elizaos/eliza/pull/4568), [#4577](https://github.com/elizaos/eliza/pull/4577))\n- Implemented plugin specification submodule for better standardization ([#4553](https://github.com/elizaos/eliza/pull/4553))\n- Moved several plugins out of the monorepo to standalone repositories ([#4669](https://github.com/elizaos/eliza/pull/4669), [#4511](https://github.com/elizaos/eliza/pull/4511))\n\n### Database and Storage Improvements\n- Enhanced PGLite database management with per-project directories ([#4423](https://github.com/elizaos/eliza/pull/4423), [#4497](https://github.com/elizaos/eliza/pull/4497))\n- Added comprehensive integration tests for database operations ([#4518](https://github.com/elizaos/eliza/pull/4518))\n- Fixed foreign key constraint violations when deleting agents ([#4510](https://github.com/elizaos/eliza/pull/4510))\n- Improved semantic text splitting for better RAG knowledge retrieval ([#4235](https://github.com/elizaos/eliza/pull/4235))\n\n### Authentication and API Enhancements\n- Added authentication middleware and API key dialog for unauthorized access ([#4420](https://github.com/elizaos/eliza/pull/4420))\n- Created new API endpoints for rooms and worlds management ([#4647](https://github.com/elizaos/eliza/pull/4647), [#4667](https://github.com/elizaos/eliza/pull/4667))\n- Optimized agent loading for improved performance with multiple agents ([#4519](https://github.com/elizaos/eliza/pull/4519))\n- Added world selection capability in message API ([#4637](https://github.com/elizaos/eliza/pull/4637))\n\n### Model and Provider Improvements\n- Extended OpenAI plugin to support custom embedding endpoints ([#4421](https://github.com/elizaos/eliza/pull/4421))\n- Added model usage events tracking for embeddings and image descriptions ([#4438](https://github.com/elizaos/eliza/pull/4438))\n- Optimized reply functionality to use small models for faster responses ([#4416](https://github.com/elizaos/eliza/pull/4416))\n- Refactored model handling in AgentRuntime to support provider and priority ([#4507](https://github.com/elizaos/eliza/pull/4507))\n\n### Social Media Integration\n- Implemented Twitter timeline functionality ([#4429](https://github.com/elizaos/eliza/pull/4429))\n- Added comprehensive tutorial for Twitter AI agent setup ([#4425](https://github.com/elizaos/eliza/pull/4425))\n- Fixed issues with Twitter post templates ([#4595](https://github.com/elizaos/eliza/pull/4595))\n- Enhanced Discord plugin with channel ID filtering ([#4665](https://github.com/elizaos/eliza/pull/4665))\n\n### Error Handling and Logging\n- Integrated Sentry logging for core logger errors ([#4650](https://github.com/elizaos/eliza/pull/4650))\n- Fixed JSON parsing issues with nested objects ([#4198](https://github.com/elizaos/eliza/pull/4198))\n- Improved error handling in message processing ([#4508](https://github.com/elizaos/eliza/pull/4508))\n- Enhanced logging with time tracking in tests ([#4621](https://github.com/elizaos/eliza/pull/4621))\n\n### Documentation and Code Quality\n- Added comprehensive docstrings to multiple components ([#4446](https://github.com/elizaos/eliza/pull/4446), [#4469](https://github.com/elizaos/eliza/pull/4469), [#4498](https://github.com/elizaos/eliza/pull/4498))\n- Updated documentation with improved CLI command instructions ([#4448](https://github.com/elizaos/eliza/pull/4448), [#4493](https://github.com/elizaos/eliza/pull/4493))\n- Implemented automated documentation deployment workflow ([#4631](https://github.com/elizaos/eliza/pull/4631))\n- Fixed broken links and improved formatting in documentation ([#4433](https://github.com/elizaos/eliza/pull/4433), [#4597](https://github.com/elizaos/eliza/pull/4597))\n\n## CLOSED ISSUES\n\n### Documentation and Tutorials\n- Fixed broken links and improved tutorial content ([#4260](https://github.com/elizaos/eliza/issues/4260), [#3880](https://github.com/elizaos/eliza/issues/3880))\n- Tested and verified CLI command documentation for accuracy ([#4143](https://github.com/elizaos/eliza/issues/4143))\n- Clarified plugin compatibility with Eliza v2 ([#4164](https://github.com/elizaos/eliza/issues/4164))\n\n### Twitter Integration Issues\n- Resolved media generation and attachment for Twitter posts ([#4241](https://github.com/elizaos/eliza/issues/4241), [#4224](https://github.com/elizaos/eliza/issues/4224))\n- Fixed formatting issues with line breaks in tweets ([#3897](https://github.com/elizaos/eliza/issues/3897))\n- Addressed Twitter space functionality problems ([#4180](https://github.com/elizaos/eliza/issues/4180))\n- Implemented solutions for Twitter interactions and reactions ([#4181](https://github.com/elizaos/eliza/issues/4181))\n\n### Platform Compatibility\n- Resolved Windows build issues ([#4094](https://github.com/elizaos/eliza/issues/4094))\n- Improved remote debugging capabilities for v2 ([#3978](https://github.com/elizaos/eliza/issues/3978))\n- Fixed CLI functionality and error handling ([#4107](https://github.com/elizaos/eliza/issues/4107), [#4159](https://github.com/elizaos/eliza/issues/4159))\n\n### Service Integration\n- Addressed Discord message persistence issues ([#3952](https://github.com/elizaos/eliza/issues/3952))\n- Fixed API key handling for Anthropic integration ([#4049](https" }, "github_extracted_data_monthly_stats_text_2025-05": "{\n \"interval\": {\n \"intervalStart\": \"2025-05-01T00:00:00.000Z\",\n \"intervalEnd\": \"2025-06-01T00:00:00.000Z\",\n \"intervalType\": \"month\"\n },\n \"repository\": \"elizaos/eliza\",\n \"overview\": \"From 2025-05-01 to 2025-06-01, elizaos/eliza had 250 new PRs (176 merged), 15 new issues, and 66 active contributors.\",\n \"topIssues\": [\n {\n \"id\": \"I_kwDOMT5cIs62Hsv6\",\n \"title\": \"Cannot find module '@elizaos/core' or its corresponding type declarations.\\\",\",\n \"author\": \"BinaryBluePeach\",\n \"number\": 4536,\n \"repository\": \"elizaos/eliza\",\n \"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)\",\n \"createdAt\": \"2025-05-12T02:42:08Z\",\n \"closedAt\": null,\n \"state\": \"OPEN\",\n \"commentCount\": 6\n },\n {\n \"id\": \"I_kwDOMT5cIs600DmL\",\n \"title\": \"Error: No handler found for delegate type: TEXT_EMBEDDING with OpenAI\",\n \"author\": \"Kirstygoodary\",\n \"number\": 4418,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"Having issues in the chat, when writing the message getting this error: \\n\\n```\\nfile:///Users/../.nvm/versions/node/v23.3.0/lib/node_modules/@elizaos/cli/dist/chunk-GFPVHNVN.js:46822\\n throw new Error(`No handler found for delegate type: ${modelKey}`);\\n ^\\n```\\n```\\nError: No handler found for delegate type: TEXT_EMBEDDING\\n```\\n\\nI've added the open api key to .env. \\n\\nOn line 45459 in `chunk-GFPVHNVN.js` - `TEXT_EMBEDDING: \\\"TEXT_EMBEDDING\\\"`, is being used as the `modelKey` it seems. \\nis this right for `modelType`? \\n\\nAlso tried `rm -rf ~/.eliza` and restarted.\",\n \"createdAt\": \"2025-05-01T09:48:19Z\",\n \"closedAt\": null,\n \"state\": \"OPEN\",\n \"commentCount\": 5\n },\n {\n \"id\": \"I_kwDOMT5cIs61QKf3\",\n \"title\": \"pglite log entry unicode escape error\",\n \"author\": \"plvo\",\n \"number\": 4457,\n \"repository\": \"elizaos/eliza\",\n \"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\",\n \"createdAt\": \"2025-05-05T21:51:18Z\",\n \"closedAt\": \"2025-05-12T08:05:38Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 3\n },\n {\n \"id\": \"I_kwDOMT5cIs61qUx2\",\n \"title\": \"Agent Hangs After Core Init / REST API Bind (Anthropic + Twitter Config)\",\n \"author\": \"kunleulysses\",\n \"number\": 4486,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"Environment:\\nOS: Ubuntu 22.04.5 LTS (on VPS)\\nNode.js Version: v23.11.0 (installed via NVM)\\npnpm Version: v9.15.0\\nElizaOS Installation Method: Manual Monorepo Clone (git clone https://github.com/elizaos/eliza.git)\\nElizaOS Version: Checked out to latest tag (Likely v0.25.9 based on agent package version in logs)\\n\\nKey Packages:\\n@elizaos/agent: v0.25.9\\n@elizaos/core: Likely v0.25.9 (based on agent)\\n@elizaos/plugin-twitter: 0.25.6-alpha.1 (or version installed via @latest)\\n@elizaos/plugin-anthropic: 1.0.0-alpha.0 (or version installed via @latest)\\nHardware: VPS with 3GB RAM\\n\\nProblem Description:\\nThe ElizaOS agent process successfully initializes its core components but hangs indefinitely immediately after the Direct Client REST API binds to its port (e.g., 3000). This occurs when configured to use a custom character (flappy.character.json) located in a root characters/ directory, with the goal of using the Anthropic model provider (@elizaos/plugin-anthropic) and the Twitter client (@elizaos/plugin-twitter) with auto-interactions enabled.\\nThe logs show successful character loading, correct plugin identification (@elizaos/plugin-twitter, @elizaos/plugin-anthropic), selection of \\\"anthropic\\\" as the model provider, database connection, and REST API binding. However, the process never proceeds to the expected Twitter client initialization logs (Creating default Twitter client..., Successfully logged in., Start Hanldeling Twitter Timeline, etc.) or any Anthropic-related activity. The process does not crash or exit; it simply stalls.\\n\\nSteps to Reproduce:\\n(Based on troubleshooting sequence followed)\\nClean VPS environment.\\nInstall prerequisites: Node v23.11.0 (via NVM), pnpm v9.15.0, git, build-essential.\\nClone the main eliza monorepo: git clone https://github.com/elizaos/eliza.git && cd eliza.\\nCheck out the latest stable tag: git checkout $(git describe --tags --abbrev=0).\\nCreate and configure ~/eliza/.env with valid Twitter API credentials (Key, Secret, Access Token, Secret) and a valid Anthropic API Key. Ensure ENABLE_TWITTER_POST_GENERATION=true and ENABLE_ACTION_PROCESSING=true. Ensure conflicting AI providers (USE_LOCAL_AI, USE_OLLAMA_TEXT_MODELS, OPENAI_API_KEY, etc.) are explicitly set to false or commented out.\\nCreate a ~/eliza/characters/ directory.\\nCreate ~/eliza/characters/flappy.character.json configured with \\\"clients\\\": [\\\"twitter\\\"], \\\"plugins\\\": [\\\"@elizaos/plugin-twitter\\\", \\\"@elizaos/plugin-anthropic\\\"], \\\"modelProvider\\\": \\\"anthropic\\\", and a specific \\\"model\\\": \\\"claude-3-haiku-20240307\\\". Include Twitter interaction settings under settings.twitter.\\nCreate ~/eliza/characters/flappy.agent.json pointing to the character file.\\nInstall dependencies: pnpm install.\\nEnsure correct plugins are installed and linked to the agent package:\\npnpm remove @elizaos/plugin-local-ai (if present)\\npnpm add @elizaos/plugin-anthropic@latest -F @elizaos/agent\\npnpm add @elizaos/plugin-twitter@latest -F @elizaos/agent\\npnpm install\\nBuild the project: pnpm build.\\nStart the agent: pnpm start --characters=\\\"characters/flappy.character.json\\\".\\n\\nExpected Result:\\nThe agent starts fully, logs confirm Twitter login and timeline handling begins, and subsequent AI tasks utilize the Anthropic API via the loaded plugin. The process remains active and responsive.\\n\\nActual Result:\\nThe agent process hangs indefinitely after the SUCCESS: REST API bound to... log message. No further logs related to Twitter client initialization, AI provider interaction, or timeline handling appear. The process doesn't exit or crash.\\n\\n\\n``` Relevant Logs:\\n\\n[2025-05-08 01:16:54] SUCCESS: REST API bound to 0.0.0.0:3000. If running locally, access it at http://localhost:3000.\\n# <-- HANGS HERE -->\\n\\nLog\\nConfiguration:\\n.env (Relevant Sections):\\n# --- Twitter/X Configuration ---\\nTWITTER_USERNAME=featherweightai\\n# TWITTER_PASSWORD=********* # Masked\\n# TWITTER_EMAIL=********* # Masked\\n# TWITTER_API_KEY=********* # Masked\\n# TWITTER_API_SECRET=********* # Masked\\n# TWITTER_ACCESS_TOKEN=********* # Masked\\n# TWITTER_ACCESS_SECRET=********* # Masked\\nENABLE_TWITTER_POST_GENERATION=true\\nENABLE_ACTION_PROCESSING=true\\n\\n# --- Anthropic Configuration ---\\nANTHROPIC_API_KEY=sk-ant-...#### # <<< IMPORTANT: Make sure this is correct\\n# ANTHROPIC_API_URL=\\n\\n# --- Disabled Providers ---\\nUSE_LOCAL_AI=false\\nUSE_OLLAMA_TEXT_MODELS=false\\n# OPENAI_API_KEY=\\n# GAIA_API_KEY=\\n# ... etc other providers blank/commented ...\\nUse code [with caution](https://support.google.com/legal/answer/13505487).\\nDotenv\\ncharacters/flappy.character.json (Relevant Sections):\\n{\\n \\\"name\\\": \\\"Flappy\\\",\\n // ... Bio/Lore/Examples/Style ...\\n \\\"clients\\\": [\\n \\\"twitter\\\"\\n ],\\n \\\"plugins\\\": [\\n \\\"@elizaos/plugin-twitter\\\",\\n \\\"@elizaos/plugin-anthropic\\\"\\n ],\\n \\\"modelProvider\\\": \\\"anthropic\\\", // Lowercase\\n \\\"model\\\": \\\"claude-3-haiku-20240307\\\",\\n \\\"settings\\\": {\\n \\\"secrets\\\": {},\\n \\\"twitter\\\": {\\n \\\"enable_replies\\\": true,\\n \\\"enable_timeline_search\\\": false,\\n \\\"enable_follow_thanks\\\": true,\\n \\\"enable_auto_retweet\\\": false\\n }\\n }\\n // ...\\n}\\n\\nAdditional Context / Troubleshooting Steps Taken:\\nIssue persists even after regenerating Twitter API keys/tokens and confirming \\\"Read, Write and access Direct Messages\\\" permissions are set correctly in the Twitter Dev Portal (OAuth 1.0a).\\nIssue occurred similarly when trying to configure GAIA via Ollama settings (using plugin-local-ai, modelProvider: \\\"OLLAMA\\\"), hanging at the same point.\\nRemoving both Twitter and AI plugins allowed the agent core to start without hanging (in previous testing phases), suggesting the issue occurs during plugin/client initialization after the core runtime is up.\\nNetwork connectivity to api.anthropic.com was verified via curl from the VPS (connection succeeded, though curl syntax errors prevented full request validation).\\nVPS has 3GB RAM, eliminating the previous RAM constraint issue encountered with local models.\\nExplicitly adding the required plugins (plugin-twitter, plugin-anthropic) as dependencies to the @elizaos/agent package using pnpm add -F @elizaos/agent ... successfully resolved earlier \\\"Cannot find package\\\" errors during plugin loading.\",\n \"createdAt\": \"2025-05-08T04:30:57Z\",\n \"closedAt\": \"2025-05-20T09:40:07Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 3\n },\n {\n \"id\": \"I_kwDOMT5cIs608Bnv\",\n \"title\": \"Job: looking for a developer with Eliza framework experience\",\n \"author\": \"TheDeveloperTom\",\n \"number\": 4432,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"Really sorry for posting here. If there are developers with eliza framework exp looking for a remote job, please let me know \\n\\nthedevelopertom@gmail.com\",\n \"createdAt\": \"2025-05-02T09:56:19Z\",\n \"closedAt\": \"2025-05-11T12:44:36Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 2\n }\n ],\n \"topPRs\": [\n {\n \"id\": \"PR_kwDOMT5cIs6VF93K\",\n \"title\": \"Feat/jimmy project manager\",\n \"author\": \"samarth30\",\n \"number\": 4462,\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\n\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Documentation changes needed?\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Testing\\r\\n\\r\\n## Where should a reviewer start?\\r\\n\\r\\n## Detailed testing steps\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-05-06T11:47:47Z\",\n \"mergedAt\": null,\n \"additions\": 327296,\n \"deletions\": 4390\n },\n {\n \"id\": \"PR_kwDOMT5cIs6SicfE\",\n \"title\": \"Odi v2 plugins ben copy\",\n \"author\": \"odilitime\",\n \"number\": 4289,\n \"body\": \"\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-04-14T19:24:53Z\",\n \"mergedAt\": null,\n \"additions\": 82802,\n \"deletions\": 11011\n },\n {\n \"id\": \"PR_kwDOMT5cIs6Vgmsl\",\n \"title\": \"chore: 0.25.19 release\",\n \"author\": \"odilitime\",\n \"number\": 4501,\n \"body\": \"- #3741\\r\\n- #3762\\r\\n- #3748\\r\\n- #3747\\r\\n- #3751\\r\\n- #3749\\r\\n- #3746\\r\\n- #3763\\r\\n- #3764\\r\\n- #3772\\r\\n- #3768\\r\\n- #3769\\r\\n- #3778\\r\\n- #3792\\r\\n- #3788\\r\\n- #3793\\r\\n- #3796\\r\\n- #3422\\r\\n- #3458\\r\\n- #3658\\r\\n- #3583\\r\\n- #3790\\r\\n- #3329\\r\\n- #2876\\r\\n- #3809\\r\\n- #3906\\r\\n- #3944\\r\\n- #3900\\r\\n- #3881\\r\\n- #3958\\r\\n- #3970\\r\\n- #3968\\r\\n- #3959\\r\\n- #3984\\r\\n- #3987\\r\\n- #4116\\r\\n- #4064\\r\\n- #4038\\r\\n- #4030\\r\\n- #3927\\r\\n- #3938\\r\\n- #4029\\r\\n- #4136\\r\\n- #4148\\r\\n- #4313\\r\\n- #4312\\r\\n- #4321\\r\\n- #4322\\r\\n- #4334\\r\\n- #4377\\r\\n- #4433\\r\\n- #4460\\r\\n- #4195\\r\\n- #4470\\r\\n- #4198\\r\\n- #4235\\r\\n- #4384\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-05-09T00:15:56Z\",\n \"mergedAt\": \"2025-05-09T00:50:58Z\",\n \"additions\": 57742,\n \"deletions\": 24516\n },\n {\n \"id\": \"PR_kwDOMT5cIs6VXVTL\",\n \"title\": \"docs: add indonesian readme\",\n \"author\": \"K1mc4n\",\n \"number\": 4485,\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\n\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Documentation changes needed?\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Testing\\r\\n\\r\\n## Where should a reviewer start?\\r\\n\\r\\n## Detailed testing steps\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-05-08T03:07:33Z\",\n \"mergedAt\": null,\n \"additions\": 57438,\n \"deletions\": 24287\n },\n {\n \"id\": \"PR_kwDOMT5cIs6V5ow8\",\n \"title\": \"Feat/add mysql to degen\",\n \"author\": \"0xbbjoker\",\n \"number\": 4554,\n \"body\": \"\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-05-12T21:06:49Z\",\n \"mergedAt\": null,\n \"additions\": 43476,\n \"deletions\": 31880\n }\n ],\n \"codeChanges\": {\n \"additions\": 99282,\n \"deletions\": 63296,\n \"files\": 870,\n \"commitCount\": 988\n },\n \"completedItems\": [\n {\n \"title\": \"Semantic splitText\",\n \"prNumber\": 4235,\n \"type\": \"other\",\n \"body\": \"\\r\\n# Relates to\\r\\n\\r\\nImproving RAG knowledge retrieval quality\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow - Changes how text is chunked for embeddings but maintains size constraints with small flexibility.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nReplaces charac\"\n },\n {\n \"title\": \"fix json parse problem with nested objects\",\n \"prNumber\": 4198,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to\\r\\n\\r\\n[Issue 3779](https://github.com/elizaOS/eliza/issues/3779)\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow. The change modifies a regular expression used for JSON normalization. The primary risk is that the updated regex could inadvertently fail to nor\"\n },\n {\n \"title\": \"chore: make cleanup script compatible across platforms\",\n \"prNumber\": 4195,\n \"type\": \"refactor\",\n \"body\": \"## What does this PR do?\\r\\n\\r\\nHey! \\r\\n\\r\\nI noticed the cleanup script was using `-print0 | xargs -0`, which doesn't work out of the box on macOS due to differences in `find`. I’ve replaced that part with a more portable `-exec rm -rf {} +` ver\"\n },\n {\n \"title\": \"feat: Prepare 0.x for sharing plugins with 1.x\",\n \"prNumber\": 4384,\n \"type\": \"feature\",\n \"body\": \"# Still waiting on\\r\\n- integrating core-plugin-v1 conversion\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nHandles new plugin repo format \\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nImprovements (misc. changes to existing featu\"\n },\n {\n \"title\": \"add: Autofun Buy, and Sell through contract\",\n \"prNumber\": 4397,\n \"type\": \"other\",\n \"body\": \"add: Autofun Buy, and Sell through contract\"\n },\n {\n \"title\": \"chore: remove plugin-browser from monorepo\",\n \"prNumber\": 4406,\n \"type\": \"other\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Chores**\\n - Removed the entire `plugin-browser` package, including all source code, configuration files, documentation, and tests. \"\n },\n {\n \"title\": \"Chore/remove plugin storage s3\",\n \"prNumber\": 4402,\n \"type\": \"other\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Chores**\\n - Removed the S3 storage plugin package, including all associated source files, configuration files, documentation, and t\"\n },\n {\n \"title\": \"Eli2 268/refactor and enhance elizaos publish cli command\",\n \"prNumber\": 4424,\n \"type\": \"refactor\",\n \"body\": \"# Refactor & Enhance ElizaOS Publishing Workflow\\r\\n\\r\\n## TL;DR\\r\\n- Unified publishing pipeline for **plugins _and_ projects**\\r\\n- Correct tags/topics everywhere\\r\\n- Cleaner branch names (`plugin-name`, `project-name`)\\r\\n- Standard `0.1.0` startin\"\n },\n {\n \"title\": \"feat: use unique pglite folder if not provided\",\n \"prNumber\": 4423,\n \"type\": \"feature\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n\\t- Database directories are now created and managed on a per-project basis, improving isolation and organization.\\n- *\"\n },\n {\n \"title\": \"chore: remove hackish solution for cp migrations\",\n \"prNumber\": 4422,\n \"type\": \"other\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Chores**\\n - Removed bundled database migration files and related scripts from the CLI package.\\n - Updated the CLI package configur\"\n },\n {\n \"title\": \"feat: extend openai plugin to support custom embedding endpoint\",\n \"prNumber\": 4421,\n \"type\": \"feature\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n\\t- Added support for a new environment variable to specify a separate endpoint for embedding requests, allowing users\"\n },\n {\n \"title\": \"feat: add auth middleware + api key dialog if unauth\",\n \"prNumber\": 4420,\n \"type\": \"feature\",\n \"body\": \"### PR Summary: API Key Authentication and Connection Management Enhancements\\r\\n\\r\\nThis pull request introduces a range of improvements to the Eliza project aimed at enhancing API key authentication and connection management for both the serv\"\n },\n {\n \"title\": \"fix: remove forced bootstrap plugin add\",\n \"prNumber\": 4417,\n \"type\": \"bugfix\",\n \"body\": \"This PR removes the forced adding of the bootstrap plugin to projects through the CLI. Projects *can* use the bootstrap plugin, but it isn't forced on them. Makes simple agents much easier.\"\n },\n {\n \"title\": \"feat: Reply uses small model\",\n \"prNumber\": 4416,\n \"type\": \"feature\",\n \"body\": \"Currently reply is using large model but replies end up being very slow. Small model is appropriate for most functionality.\"\n },\n {\n \"title\": \"fix: make plugin.routes work\",\n \"prNumber\": 4415,\n \"type\": \"bugfix\",\n \"body\": \"# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nMakes a plugin's routes available in /api/agents/AGENT_UUID_OR_NAME/plugins/PLUGIN_NAME/ROUTE_FROM_PLUGIN\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nUpdates (new versions of included \"\n },\n {\n \"title\": \"fix: Don't make unneeded express object\",\n \"prNumber\": 4414,\n \"type\": \"bugfix\",\n \"body\": \"it's made in initializeServer\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nSmall fix I saw\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nbetween:\\r\\nBug fixes (non-breaking change which fixes an issue)\\r\\nImprovements (misc. changes\"\n },\n {\n \"title\": \"fix: bm25 and update dependencies\",\n \"prNumber\": 4411,\n \"type\": \"bugfix\",\n \"body\": \"This PR is a two-fer\\r\\n\\r\\n- Updates dependencies for react, etc\\r\\n- Fixes an issue with bm25 where it wont import and run the worker.js worker -- basically just removed the worker since its not very performance sensitive in the way we're using\"\n },\n {\n \"title\": \"chore: remove plugin-local-ai from monorepo\",\n \"prNumber\": 4439,\n \"type\": \"other\",\n \"body\": \"\"\n },\n {\n \"title\": \"feat(plugin-openai): Emit model usage events for embeddings and image description\",\n \"prNumber\": 4438,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\n\\nImprove credit usage tracking in OpenAI plugin\\n\\n# Risks\\n\\nLow. This PR adds model usage tracking for previously untracked models but doesn't modify existing functionality.\\n\\n# Background\\n\\n## What does this PR do?\\n\\nThis PR adds M\"\n },\n {\n \"title\": \"chore: remove plugin-ollama from monorepo\",\n \"prNumber\": 4437,\n \"type\": \"other\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Chores**\\n\\t- Removed the Ollama plugin package, including all related files, documentation, configuration, and build scripts. The plu\"\n },\n {\n \"title\": \"chore: remove plugin-groq from monorepo\",\n \"prNumber\": 4436,\n \"type\": \"other\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Chores**\\n - Removed the Groq plugin package, including all related configuration, documentation, build, and test files.\\n- **Documen\"\n },\n {\n \"title\": \"Eli2 272/cli fix incorrect version detection to show correct latest cli version\",\n \"prNumber\": 4435,\n \"type\": \"bugfix\",\n \"body\": \"## Problem\\r\\nWhen using CLI it is saying to update to 1.0.0.alpha as most recent which isnt correct.\\r\\n\\r\\n## Underlying Cause\\r\\nTwo critical issues affecting the CLI's update mechanism:\\r\\n\\r\\n1. The package manager incorrectly adds 'plugin-' prefi\"\n },\n {\n \"title\": \"chore: remove plugin-venice from monorepo\",\n \"prNumber\": 4434,\n \"type\": \"other\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Chores**\\n\\t- Removed the Venice AI plugin and all related files, including documentation, configuration, tests, and build scripts, fr\"\n },\n {\n \"title\": \"fix: update broken image path in Thai README\",\n \"prNumber\": 4433,\n \"type\": \"bugfix\",\n \"body\": \"The original image path was broken due to an unnecessary leading ./docs/ prefix, which doesn't match the file structure when the site is rendered or deployed. Updating the path ensures the Eliza banner is displayed correctly in the document\"\n },\n {\n \"title\": \"fix: small template fix\",\n \"prNumber\": 4431,\n \"type\": \"bugfix\",\n \"body\": \"Added character bio and postDirections to the quote/reply template prompt\"\n },\n {\n \"title\": \"fix: [plugin-twitter] small clean up\",\n \"prNumber\": 4430,\n \"type\": \"bugfix\",\n \"body\": \"removed unused code\"\n },\n {\n \"title\": \"feat: twitter timeline\",\n \"prNumber\": 4429,\n \"type\": \"feature\",\n \"body\": \"Related: https://github.com/elizaOS/eliza/issues/4405\\r\\n\\r\\nThis PR introduces a new timeline.ts module to handle bot interactions with the Twitter timeline.\\r\\n\\r\\nThe timeline interaction is now optional. To enable it, configure the following en\"\n },\n {\n \"title\": \"chore: remove plugin-redpill from monorepo\",\n \"prNumber\": 4428,\n \"type\": \"other\",\n \"body\": \"\"\n },\n {\n \"title\": \"chore: remove plugin-anthropic from monorepo\",\n \"prNumber\": 4427,\n \"type\": \"other\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Chores**\\n - Removed the Anthropic plugin package and all related files, including documentation, configuration, tests, and source c\"\n },\n {\n \"title\": \"add blog for twitter agent setup\",\n \"prNumber\": 4425,\n \"type\": \"feature\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Documentation**\\n - Added a comprehensive tutorial guiding users through setting up, customizing, and deploying a Twitter AI agent u\"\n },\n {\n \"title\": \"docs: fix title spacing\",\n \"prNumber\": 4443,\n \"type\": \"bugfix\",\n \"body\": \"## Fix Documentation Title Spacing\\r\\n\\r\\n`eliza is apowerful AI agent framework for autonomy & personality` ---> `eliza is a powerful AI agent framework for autonomy & personality`\\r\\n\"\n },\n {\n \"title\": \"Fix ESM type generation in packages: SQL, Boostrap & OpenAI\",\n \"prNumber\": 4442,\n \"type\": \"bugfix\",\n \"body\": \"👉 This is a follow up to https://github.com/elizaOS/eliza/pull/4341\\r\\n\\r\\n# Relates to\\r\\n\\r\\nTypeScript type resolution issues in `@elizaos/plugin-sql`, `@elizaos/plugin-boostrapl` & `@elizaos/plugin-openai` packages\\r\\n\\r\\nFixes: https://github.com\"\n },\n {\n \"title\": \"chore: update cli command docs\",\n \"prNumber\": 4448,\n \"type\": \"other\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Documentation**\\n - Updated and expanded documentation for several CLI commands, including `dev`, `publish`, `test`, and `update`, p\"\n },\n {\n \"title\": \"chore: organise imports and use relative paths\",\n \"prNumber\": 4447,\n \"type\": \"other\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Refactor**\\n - Consolidated and reorganized import statements across multiple CLI files for improved clarity and maintainability.\\n \"\n },\n {\n \"title\": \"📝 Add docstrings to `refactor-env`\",\n \"prNumber\": 4446,\n \"type\": \"feature\",\n \"body\": \"Docstrings generation was requested by @wtfsayo.\\n\\n* https://github.com/elizaOS/eliza/pull/4445#issuecomment-2849042039\\n\\nThe following files were modified:\\n\\n* `packages/cli/src/commands/env.ts`\\n* `packages/cli/src/utils/config-manager.ts`\\n* \"\n },\n {\n \"title\": \"chore: refactor env getting\",\n \"prNumber\": 4445,\n \"type\": \"refactor\",\n \"body\": \"\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n - Introduced a unified environment information system, providing detailed system, CLI, and package manager details t\"\n },\n {\n \"title\": \"fix(pglite): JSON serialization to handle invalid Unicode escape sequences when log\",\n \"prNumber\": 4458,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to\\r\\n\\r\\nIssue #42: Unicode escape sequence error when creating log entries with TEXT_LARGE model type\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow. This fix handles malformed Unicode escape sequences in JSON data to prevent database errors. No impact on exist\"\n },\n {\n \"title\": \"fix: plugin install cmd plugins & start\",\n \"prNumber\": 4456,\n \"type\": \"bugfix\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n\\t- Improved plugin installation and loading by automatically determining the correct install tag (alpha, beta, or sta\"\n },\n {\n \"title\": \"fix(hot): version install issues\",\n \"prNumber\": 4454,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: discord service unregister timeout\",\n \"prNumber\": 4450,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to\\r\\n\\r\\nIssue with timeouts during Discord agent unregistration\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow. This fix properly handles timeout cancellation when stopping the Discord service, which prevents errors when deleting an agent.\\r\\n\\r\\n# Background\\r\\n\\r\\n##\"\n },\n {\n \"title\": \"fix client scroll bars\",\n \"prNumber\": 4465,\n \"type\": \"bugfix\",\n \"body\": \"Scrollbars were doubled up in task list, also if hover side bar would get scroll weirdly, the main page also had a global scroll bloat.\\r\\n\\r\\nNow it is much cleaner and fullscreen no scrolls.\"\n },\n {\n \"title\": \"add elizadb to .gitignore\",\n \"prNumber\": 4464,\n \"type\": \"feature\",\n \"body\": \"I had like 1000+ files in git added when ran migration script.\\r\\n\\r\\n`elizaDb` in camelcase is not correct, it's `elizadb`\"\n },\n {\n \"title\": \"fix bunx / npx detection\",\n \"prNumber\": 4463,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"docs: Update broken Eliza documentation links\",\n \"prNumber\": 4460,\n \"type\": \"docs\",\n \"body\": \"replaced old ai16z.github.io/eliza/ link with docs.eliza.how/ — old one was 404. updated in tutorial and resources.\"\n },\n {\n \"title\": \"chore: remove StudioLM support, focus on llama.cpp\",\n \"prNumber\": 4459,\n \"type\": \"other\",\n \"body\": \"\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Documentation**\\n - Updated documentation to focus on local AI model configuration, replacing StudioLM-specific instructions with det\"\n },\n {\n \"title\": \"Delete all memories API and client hooks.\",\n \"prNumber\": 4467,\n \"type\": \"other\",\n \"body\": \"Adds API and client React hooks to wipe all memories in single request.\\r\\nThis is for: \\\"clear chat\\\" button feature.\\r\\nNot sure where to put button in UI... tough to decide.\"\n },\n {\n \"title\": \"fix type errors in CLI, fs.exists is deprecated\",\n \"prNumber\": 4482,\n \"type\": \"bugfix\",\n \"body\": \"```bash\\r\\nVersion: 1.0.0-beta.48\\r\\n[2025-05-07 22:26:45] WARN: Error loading configuration: TypeError: fs4.exists is not a function\\r\\n[2025-05-07 22:26:45] INFO: First time setup. Let's configure your Eliza agent.\\r\\n[2025-05-07 22:26:45] ERROR:\"\n },\n {\n \"title\": \"chore: remove plugin-elevenlabs ai from monorepo\",\n \"prNumber\": 4480,\n \"type\": \"other\",\n \"body\": \"\\r\\n\\r\\n## Summary by CodeRabbit\\r\\n\\r\\n- **Chores**\\r\\n\\t- Removed the ElevenLabs plugin package and all its associated files, including configuration, build scripts, license, \"\n },\n {\n \"title\": \"chore: cleaner load-plugin code\",\n \"prNumber\": 4478,\n \"type\": \"refactor\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Refactor**\\n - Improved plugin module loading for greater reliability and flexibility, with enhanced error handling and logging.\\n -\"\n },\n {\n \"title\": \"fix: roll back plugin loading code\",\n \"prNumber\": 4477,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"Revert \\\"Fix ESM type declarations in Core\\\"\",\n \"prNumber\": 4475,\n \"type\": \"bugfix\",\n \"body\": \"Reverts elizaOS/eliza#4341\"\n },\n {\n \"title\": \"chore(update-docs): make sure bun is installed\",\n \"prNumber\": 4474,\n \"type\": \"other\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Documentation**\\n - Updated installation instructions to include Bun as an officially supported method for installing the CLI tool.\\n\"\n },\n {\n \"title\": \"Revert \\\"Fix ESM type generation in packages: SQL, Boostrap & OpenAI\\\"\",\n \"prNumber\": 4473,\n \"type\": \"bugfix\",\n \"body\": \"Reverts elizaOS/eliza#4442\"\n },\n {\n \"title\": \"Feat/jimmy pm agent\",\n \"prNumber\": 4471,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nJimmy the project manager\\r\\n\\r\\n\\r\\n\\r\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Refactor**\\n - Improved monorepo environment detection by centralizing logic and switching to asynchronous operations.\\n - Streamlin\"\n },\n {\n \"title\": \"Use real drizzle ORM for DB base operation types.\",\n \"prNumber\": 4500,\n \"type\": \"other\",\n \"body\": \"On my journey to fix tests I noticed:\\r\\n\\r\\n```bash\\r\\n@elizaos/plugin-sql:test: × deleteAgent > should delete an agent and all related data 5ms\\r\\n@elizaos/plugin-sql:test: → tx.select(...).from(...).where(...).limit is not a function\\r\\n``\"\n },\n {\n \"title\": \"📝 Add docstrings to `fix-pglite-dir`\",\n \"prNumber\": 4498,\n \"type\": \"feature\",\n \"body\": \"Docstrings generation was requested by @wtfsayo.\\n\\n* https://github.com/elizaOS/eliza/pull/4497#issuecomment-2863124160\\n\\nThe following files were modified:\\n\\n* `packages/plugin-sql/src/migrate.ts`\\n\\n
\\nℹ️ Note\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n - The data directory for the PGlite database can now be configured using an environment variable. If not set, a pro\"\n },\n {\n \"title\": \"fix: tts manager and transcribe\",\n \"prNumber\": 4496,\n \"type\": \"bugfix\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Documentation**\\n - Updated the README to include detailed instructions for installing FFmpeg, required for audio transcription acro\"\n },\n {\n \"title\": \"chore: fix runtime type\",\n \"prNumber\": 4495,\n \"type\": \"bugfix\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Refactor**\\n\\t- Improved internal handling and validation of agent identifiers to enhance reliability when accessing agent runtimes. N\"\n },\n {\n \"title\": \"📝 Add docstrings to `combined-ELI2-279-ELI2-280/fix-publish-cli-options-platform-and-skip-registry`\",\n \"prNumber\": 4494,\n \"type\": \"feature\",\n \"body\": \"Docstrings generation was requested by @wtfsayo.\\n\\n* https://github.com/elizaOS/eliza/pull/4492#issuecomment-2862285854\\n\\nThe following files were modified:\\n\\n* `packages/cli/src/utils/publisher.ts`\\n\\n
\\nℹ️ Note\\n\\n## Summary by CodeRabbit\\n\\n- **Documentation**\\n - Updated all CLI usage examples and instructions to use the simplified command format (`eliza\"\n },\n {\n \"title\": \"Combined eli2 279 eli2 280/fix publish cli options platform and skip registry\",\n \"prNumber\": 4492,\n \"type\": \"bugfix\",\n \"body\": \"This PR addresses two issues with the ElizaOS CLI publish options:\\r\\n\\r\\n## 1. Platform Option Removal\\r\\n\\r\\n- Removed `-px, --platform` option from the publish command\\r\\n- Set 'node' as the default platform for all packages (via `packageJson.plat\"\n },\n {\n \"title\": \"Eli2 277/fix missing gitignore in plugins created with global cli installation\",\n \"prNumber\": 4489,\n \"type\": \"bugfix\",\n \"body\": \"**Problem**\\r\\n\\r\\nWhen creating plugins or projects using the globally installed ElizaOS CLI, the generated directories were missing .gitignore and .npmignore files. This happened because npm strips these special files during the package publi\"\n },\n {\n \"title\": \"Create README_IND.md\",\n \"prNumber\": 4488,\n \"type\": \"other\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n## Summary by CodeRabbit\\r\\n\\r\\n- **Chores**\\r\\n\\t- Removed the OpenAI plugin and all related files, documentation, and configuration from the project.\\r\\n\\t- Deleted ref\"\n },\n {\n \"title\": \"fix: delete agents that have been in room\",\n \"prNumber\": 4510,\n \"type\": \"bugfix\",\n \"body\": \"## PR Summary: Fix Foreign Key Constraint Violation on Agent Deletion\\r\\n\\r\\n[Linear](https://linear.app/eliza-labs/issue/ELIZA-271/if-agent-has-been-in-a-room-it-cant-be-deleted)\\r\\n\\r\\n**Problem:**\\r\\nAttempting to delete an agent resulted in a dat\"\n },\n {\n \"title\": \"ELIZA290/part-1-global-options-create-and-setup-monorepo-commands\",\n \"prNumber\": 4509,\n \"type\": \"other\",\n \"body\": \"This PR addresses several issues with the ElizaOS CLI to improve user experience and align functionality with documentation. It is part of a multi-pr (probably 3 prs or so more) effort to get the cli comprehensively tested (ELIZA-290) so we\"\n },\n {\n \"title\": \"Enhance message handling and text escaping by adding null checks. \",\n \"prNumber\": 4508,\n \"type\": \"other\",\n \"body\": \"Enhance message handling and text escaping by adding null checks. \\r\\nUpdated MessageManager to handle empty messages and modified utility functions to return empty strings for null inputs, ensuring robustness in message processing.\"\n },\n {\n \"title\": \"[enhancement] Refactor model handling in AgentRuntime to support provider and priority\",\n \"prNumber\": 4507,\n \"type\": \"refactor\",\n \"body\": \"Refactor model handling in AgentRuntime to support provider and priority. \\r\\nUpdated ModelHandler type to include provider and optional priority for better model selection. \\r\\nEnhanced registerModel and getModel methods to utilize these new f\"\n },\n {\n \"title\": \"V2 fixed twitter\",\n \"prNumber\": 4506,\n \"type\": \"bugfix\",\n \"body\": \"Refactor Twitter plugin code for improved error handling and code clarity. \\r\\nUpdated maxRetries to be configurable via environment variable, added source property to Twitter interaction messages, and enforced text validation in tweet creati\"\n },\n {\n \"title\": \"strict types, generate DTS, plugin-bootstrap\",\n \"prNumber\": 4504,\n \"type\": \"other\",\n \"body\": \"We cannot write stable code in Typescript, if do not generate types, and respect strict mode.\\r\\n\\r\\nThis PR fixes all red errors in plugin-bootstrap and generates a index.d.ts.\\r\\n\\r\\nI don't see any sensible way to develop without moving to stric\"\n },\n {\n \"title\": \"chore(deps): bump the npm_and_yarn group across 2 directories with 8 updates\",\n \"prNumber\": 4502,\n \"type\": \"other\",\n \"body\": \"Bumps the npm_and_yarn group with 7 updates in the / directory:\\n\\n| Package | From | To |\\n| --- | --- | --- |\\n| [@babel/helpers](https://github.com/babel/babel/tree/HEAD/packages/babel-helpers) | `7.26.0` | `7.27.1` |\\n| [@babel/runtime-corej\"\n },\n {\n \"title\": \"chore: 0.25.19 release\",\n \"prNumber\": 4501,\n \"type\": \"other\",\n \"body\": \"- #3741\\r\\n- #3762\\r\\n- #3748\\r\\n- #3747\\r\\n- #3751\\r\\n- #3749\\r\\n- #3746\\r\\n- #3763\\r\\n- #3764\\r\\n- #3772\\r\\n- #3768\\r\\n- #3769\\r\\n- #3778\\r\\n- #3792\\r\\n- #3788\\r\\n- #3793\\r\\n- #3796\\r\\n- #3422\\r\\n- #3458\\r\\n- #3658\\r\\n- #3583\\r\\n- #3790\\r\\n- #3329\\r\\n- #2876\\r\\n- #3809\\r\\n- #3906\\r\\n- #394\"\n },\n {\n \"title\": \"chore: clean eliza cache before running ci\",\n \"prNumber\": 4523,\n \"type\": \"refactor\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Chores**\\n - Improved reliability of CLI test workflow by clearing cached data before running tests.\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Chores**\\n - Updated the Bun runtime version to ^1.2.13 across relevant configuration files to allow for minor and patch updates.\\n\\n<\"\n },\n {\n \"title\": \"📝 Add docstrings to `api-cleanup`\",\n \"prNumber\": 4521,\n \"type\": \"feature\",\n \"body\": \"Docstrings generation was requested by @wtfsayo.\\n\\n* https://github.com/elizaOS/eliza/pull/4519#issuecomment-2869040797\\n\\nThe following files were modified:\\n\\n* `packages/cli/src/server/api/agent.ts`\\n* `packages/client/src/components/app-sideb\"\n },\n {\n \"title\": \"docs: remove redundant word in solana-v2.md\",\n \"prNumber\": 4520,\n \"type\": \"docs\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n - Added enhanced agent data fetching with the ability to\"\n },\n {\n \"title\": \"feat: add integration tests\",\n \"prNumber\": 4518,\n \"type\": \"feature\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n - Added comprehensive integration tests for all major database operations, including agents, cache, components, emb\"\n },\n {\n \"title\": \"Shaw bugfixes\",\n \"prNumber\": 4515,\n \"type\": \"bugfix\",\n \"body\": \"This PR fixes some bugs. Leaving it on draft since it is complete and will need to be separated out.\"\n },\n {\n \"title\": \"fix: pglite migrations again\",\n \"prNumber\": 4532,\n \"type\": \"bugfix\",\n \"body\": \"fixes pglite migration paths\"\n },\n {\n \"title\": \"fix: remove migrations\",\n \"prNumber\": 4531,\n \"type\": \"bugfix\",\n \"body\": \"remove migrations; they are auto-generated and handled at code level\"\n },\n {\n \"title\": \"Disable loading instrumentation if not enabled.\",\n \"prNumber\": 4530,\n \"type\": \"other\",\n \"body\": \"This removes annoying instrumentation logs in startup.\\r\\n\\r\\n`@elizaos/the-org:dev: [2025-05-11 19:24:33] WARN: [getTracer] Service instrumentation not found in runtime.`\\r\\n\\r\\nNow it doesn't try and load the runtime, unless `process.env.INSTRUME\"\n },\n {\n \"title\": \"Enforce Typescript on /cli and /plugin-sql, fix missing DB functions.\",\n \"prNumber\": 4529,\n \"type\": \"bugfix\",\n \"body\": \"This PR:\\r\\n\\r\\n- Turns on `dts: true` in both CLI and plugin-sql packages.\\r\\n\\r\\n- This exposed missing: `connection` which was being used in tests but didn't actually exist.\\r\\n\\r\\n- Implemented `getConnection()` for realsies in DB adapters to satis\"\n },\n {\n \"title\": \"remove broken release link in changelog\",\n \"prNumber\": 4527,\n \"type\": \"other\",\n \"body\": \"Found a broken link to v0.25.6-alpha.1 release in docs/docs/changelog.md.\\r\\nReplaced the markdown link with plain text to avoid 404.\\r\\nFeel free to suggest a working link if available — happy to update!\\r\\n\"\n },\n {\n \"title\": \"chore: use newer bun setup\",\n \"prNumber\": 4526,\n \"type\": \"other\",\n \"body\": \"\"\n },\n {\n \"title\": \"chore: Cleanup the-org ENV and Agent loading.\",\n \"prNumber\": 4524,\n \"type\": \"refactor\",\n \"body\": \"Some cleanups I did while QAing Jimmy PM agent.\\r\\n\\r\\nRewrites the `hasRequiredEnvVars` and Org agent loading process to be much simpler to read and fixes hard coded 6 count of agents.\\r\\n\\r\\nDoes same thing in 50% less code, we do not need to be \"\n },\n {\n \"title\": \"feat: plugin-specification submodule\",\n \"prNumber\": 4553,\n \"type\": \"feature\",\n \"body\": \"# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nInclude the repo (via submodule) for plugin specification\\r\\nAlso removes hapi from autodoc\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nImprovements (misc. changes to existing features)\\r\"\n },\n {\n \"title\": \"fix: build for plugin discord & service mess after merge conf\",\n \"prNumber\": 4552,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n## Summary by CodeRabbit\\r\\n\\r\\n- **Bug Fixes**\\r\\n - Fixed critical issue within the `service.ts` (several methods missing after improper merge conflicts resolution) \"\n },\n {\n \"title\": \"Remove REST /ping for websocket status checks in client.\",\n \"prNumber\": 4551,\n \"type\": \"other\",\n \"body\": \"The /pings were kinda annoying log spam and were not perfectly realtime, like a 5 second lag on connect / reconnect.\\r\\nWe also didn't even have a proper /ping route, it was 404 and falling back to middleware btw.\\r\\n\\r\\nThis PR changes client fr\"\n },\n {\n \"title\": \"chore: consistent env naming for project manager agent\",\n \"prNumber\": 4549,\n \"type\": \"other\",\n \"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\"\n },\n {\n \"title\": \"fix: agent response + better logging/tracing in bootstrap plugin\",\n \"prNumber\": 4548,\n \"type\": \"bugfix\",\n \"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\"\n },\n {\n \"title\": \"fix: bad env resolution\",\n \"prNumber\": 4547,\n \"type\": \"bugfix\",\n \"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\"\n },\n {\n \"title\": \"minor fix: remove banner display + have -h, --help show on same line\",\n \"prNumber\": 4546,\n \"type\": \"bugfix\",\n \"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\"\n },\n {\n \"title\": \"fix(temp): passthrough function so that llm plugins dont break\",\n \"prNumber\": 4544,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: integration test import\",\n \"prNumber\": 4541,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: error associated with issue #4336, where TEXT_EMBEDDING was not…\",\n \"prNumber\": 4537,\n \"type\": \"bugfix\",\n \"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\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Tests**\\n - Updated test assertions to expect the `parse_mode` option as 'MarkdownV2' for message sending.\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n - Added s\"\n },\n {\n \"title\": \"chore: back to regular dev command\",\n \"prNumber\": 4566,\n \"type\": \"other\",\n \"body\": \"\"\n },\n {\n \"title\": \"chore: use latest v2 plugin list\",\n \"prNumber\": 4564,\n \"type\": \"tests\",\n \"body\": \"\"\n },\n {\n \"title\": \"feat: upgrades to cli agent command\",\n \"prNumber\": 4560,\n \"type\": \"feature\",\n \"body\": \"This PR is a focused attempt to improve the elizaos agent cli command. The changes are:\\r\\n\\r\\n\\r\\n**elizaos agent get** \\r\\n-j/--json wasnt working (it was saving the file instead of of displaying in console json format)\\r\\n-o/--output wasnt working\"\n },\n {\n \"title\": \"chore: enable strict types and adjust guards for plugin-telegram\",\n \"prNumber\": 4559,\n \"type\": \"other\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Bug Fixes**\\n\\t- Improved error handling and logging throughout the Telegram plugin to prevent crashes and provide clearer diagnostics\"\n },\n {\n \"title\": \"fix: community manager set to use plugin-local-ai, out of box\",\n \"prNumber\": 4557,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to\\r\\n#4336 \\r\\nThe reported error had several issues, I pushed a PR yesterday to address the OpenAI issue, now, I am pushing this PR to set the default settings for community manager (Eli5) in dev build, to work with local ai out of \"\n },\n {\n \"title\": \"chore: remove log spam during client build\",\n \"prNumber\": 4584,\n \"type\": \"other\",\n \"body\": \"\\r\\n\\\"Screenshot\\r\\n\"\n },\n {\n \"title\": \"Eliza290/cli start command\",\n \"prNumber\": 4583,\n \"type\": \"other\",\n \"body\": \"ElizaOS CLI Start Command Improvements\\r\\n\\r\\n**Improved -chars option parsing**\\r\\nAdded support for handling of comma-separated values with spaces\\r\\nAdded support for both single and double quotes in character paths\\r\\nProperly strips quotes from \"\n },\n {\n \"title\": \"feat: add tests for create-eliza command\",\n \"prNumber\": 4582,\n \"type\": \"feature\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: scope worldId and entityId\",\n \"prNumber\": 4581,\n \"type\": \"bugfix\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Bug Fixes**\\n - Improved consistency in how knowledge items are associated with agents, ensuring uploaded knowledge is now correctly\"\n },\n {\n \"title\": \"fix: LLM response parsing to support custom fields and clean up empty message headers\",\n \"prNumber\": 4580,\n \"type\": \"bugfix\",\n \"body\": \"This PR addresses two issues:\\r\\n\\r\\n1. **Bootstrap plugin response parsing** \\r\\n Previously, the LLM response was reduced to a fixed set of keys, which discarded useful custom fields returned by custom templates. This change spreads all fiel\"\n },\n {\n \"title\": \"feat: better git repo plugin install support\",\n \"prNumber\": 4577,\n \"type\": \"feature\",\n \"body\": \"\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n\\t- Added support for installing plugins directly from GitHub URLs, including both HTTPS and shorthand formats.\\n\\t- Enha\"\n },\n {\n \"title\": \"fix: hallucination in reply\",\n \"prNumber\": 4603,\n \"type\": \"bugfix\",\n \"body\": \"Agent hallucinates if we use `OBJECT_SMALL`\\r\\n\\r\\nJSON responses are made up and causes many troubles.\\r\\n\\r\\nExample issue on the scr shoot:\\r\\n\\r\\n\\\"image\\\"\\r\\n\\r\\n## Summary by CodeRabbit\\r\\n\\r\\n- **Bug fix**\\r\\n - Added a list of relevant topics to the community manager and social media manager profiles as twitter post templa\"\n },\n {\n \"title\": \"fix: send-message-api\",\n \"prNumber\": 4594,\n \"type\": \"bugfix\",\n \"body\": \"# Release Notes\\r\\n\\r\\n## New Features\\r\\n- Enhanced message processing with an event-driven, asynchronous flow for agent message handling\\r\\n- Added support for new response scenarios where the agent may choose not to reply\\r\\n\\r\\n## Bug Fixes\\r\\n- Corr\"\n },\n {\n \"title\": \"wip: Plugin-Jupiter Swap\",\n \"prNumber\": 4593,\n \"type\": \"other\",\n \"body\": \"Added:\\r\\n\\r\\nPlugin-Jupiter which would be used to handle all jupiter swaps within plugin-trade and the Spartan product.\"\n },\n {\n \"title\": \"Eliza290/cli merge update cli into update command\",\n \"prNumber\": 4592,\n \"type\": \"other\",\n \"body\": \"# Consolidate `update-cli` command into `update` command\\r\\n\\r\\n## Problem\\r\\n- CLI update functionality was split between two commands (`update` and `update-cli`)\\r\\n- Installation instructions suggested incorrect command without the `@beta` tag\\r\\n\"\n },\n {\n \"title\": \"Eliza290/cli update command\",\n \"prNumber\": 4591,\n \"type\": \"other\",\n \"body\": \"# Improve ElizaOS CLI update command flags\\r\\n\\r\\nThis PR addresses several issues with the update command:\\r\\n\\r\\n## Regular no-flag update function\\r\\n- **Problem**: The regular update command was failing with error \\\"Invalid Version: beta\\\" when enc\"\n },\n {\n \"title\": \"fix: core not importable in client\",\n \"prNumber\": 4590,\n \"type\": \"bugfix\",\n \"body\": \"Fixes client error:\\r\\n\\r\\n```\\r\\nUncaught TypeError: Failed to resolve module specifier \\\"@elizaos/core\\\". Relative references must start with either \\\"/\\\", \\\"./\\\", or \\\"../\\\".\\r\\n```\\r\\n\\r\\nAlso adds vite-node-polyfills to supplement Buffer and process missi\"\n },\n {\n \"title\": \"fix: Guarantee onComplete is always called in messageReceivedHandler\",\n \"prNumber\": 4589,\n \"type\": \"bugfix\",\n \"body\": \"This PR ensures the onComplete callback is always executed, regardless of whether the message handler completes successfully, throws an error, or times out.\\r\\n\\r\\nKey changes:\\r\\n- Wrapped the entire messageReceivedHandler logic in a try-finally\"\n },\n {\n \"title\": \"chore: update docs\",\n \"prNumber\": 4586,\n \"type\": \"other\",\n \"body\": \"This PR focuses on a comprehensive update of the project's documentation.\\r\\n\\r\\nKey changes include:\\r\\n\\r\\n* **Content Updates:**\\r\\n * Updated blog posts.\\r\\n * Added brief versions of all partner documentation.\\r\\n * Added documentat\"\n },\n {\n \"title\": \"fix: resolve linter errors for type mismatches in DB adapter\",\n \"prNumber\": 4612,\n \"type\": \"bugfix\",\n \"body\": \"\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Bug Fixes**\\n\\t- Improved handling of missing or null data for agent and task fields, ensuring consistent and user-friendly defaults ar\"\n },\n {\n \"title\": \"Eliza290/cli command env\",\n \"prNumber\": 4610,\n \"type\": \"other\",\n \"body\": \"**elizaos env list:**\\r\\n\\r\\nAdded warning when no local .env file exists, with guidance to create one from .env.example if available\\r\\nAdded --system flag to show only system information, consistent with existing --global and --local flags\\r\\n\\r\\n*\"\n },\n {\n \"title\": \"fix: reply action to skip LLM call if existing REPLY response is found\",\n \"prNumber\": 4608,\n \"type\": \"bugfix\",\n \"body\": \"Previously, the REPLY action was designed to skip the LLM call if an existing response with a REPLY action was found. However, recent changes to the message handler's template prompt caused the LLM to return the response with the `text` fie\"\n },\n {\n \"title\": \"API - return ID of newly created agent\",\n \"prNumber\": 4634,\n \"type\": \"other\",\n \"body\": \"When using API calls and creating AGENT it very useful to have returned ID on first API call, so there are not needed subsequent calls after it just to find ID, which is crucial for other types of API calls.\\r\\n\\r\\nSo I added ID in return data \"\n },\n {\n \"title\": \"cleanup: optz actions functions\",\n \"prNumber\": 4633,\n \"type\": \"refactor\",\n \"body\": \"# PR: Optimize Action Formatting Functions\\r\\n\\r\\nThis PR improves the code quality and performance of the action formatting functions in `actions.ts`.\\r\\n\\r\\n## Changes Made\\r\\n\\r\\n### For all functions:\\r\\n- Added proper input validation for edge cases\"\n },\n {\n \"title\": \"ci: Docs auto deployer.\",\n \"prNumber\": 4631,\n \"type\": \"other\",\n \"body\": \"This runs Github Action if anything inside `packages/docs` folder changes and auto deploys to `docs.eliza.how`.\"\n },\n {\n \"title\": \"Fix chokidar watch usage\",\n \"prNumber\": 4629,\n \"type\": \"bugfix\",\n \"body\": \"## Summary\\n- add chokidar as a regular dependency for the CLI\\n- ensure chokidar is treated as external when bundling\\n- use the dependency directly in `dev` command\\n\\n## Testing\\n- ❌ `bun run test:setup-commands` *(failed to find `vitest` comm\"\n },\n {\n \"title\": \"chore: Remove unused wait helper\",\n \"prNumber\": 4625,\n \"type\": \"other\",\n \"body\": \"## Summary\\r\\n- remove wait helper from CLI start command\\r\\n\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Refactor**\\n - Removed an unused utility function related to wait times fro\"\n },\n {\n \"title\": \"fix: client auth issue\",\n \"prNumber\": 4624,\n \"type\": \"bugfix\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n - Improved handling of unauthorized access: Users are now notified with a clear message and a visible alert if thei\"\n },\n {\n \"title\": \"feat: log time taken in tests\",\n \"prNumber\": 4621,\n \"type\": \"feature\",\n \"body\": \"\"\n },\n {\n \"title\": \"chore: add local ai tests\",\n \"prNumber\": 4619,\n \"type\": \"feature\",\n \"body\": \"\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Chores**\\n - Improved workflow cache management to only clear necessary directories and added automatic model file downloads for test\"\n },\n {\n \"title\": \"Eliza290/cli command dev\",\n \"prNumber\": 4618,\n \"type\": \"other\",\n \"body\": \"This PR enhances the elizaos dev command with better character file handling while ensuring consistent behavior with start cli command\\r\\n\\r\\nAll options tested and passed:\\r\\n\\r\\n-c/--configure, \\r\\n-p/--port, \\r\\n-b/--build\\r\\n-char/--character\\r\\n\\r\\nKey \"\n },\n {\n \"title\": \"fix: senderName is \\\"Unknown\\\" in recentMessages provider\",\n \"prNumber\": 4616,\n \"type\": \"bugfix\",\n \"body\": \"This PR fixes an issue where the senderName was often displayed as \\\"Unknown\\\" in the recentMessages provider. The update changes the logic to prioritize entitiesData for resolving the sender's name based on entityId. If no match is found, it\"\n },\n {\n \"title\": \"chore: Add missing plugin failure test\",\n \"prNumber\": 4643,\n \"type\": \"feature\",\n \"body\": \"## Summary\\n- test plugin install modifies package.json with plugin-discord\\n- verify missing plugin fails with registry error\\n\\n## Testing\\n- `./run_all_bats.sh` *(fails: 'bats' not found in PATH)*\"\n },\n {\n \"title\": \"fix: agent start button refetch agent.status.\",\n \"prNumber\": 4642,\n \"type\": \"bugfix\",\n \"body\": \"When click: \\\"start\\\" on agents, it would start, but the UI would not update, until you refreshed page.\\r\\n\\r\\nNow it is realtime in the UI.\\r\\n\\r\\n![image](https://github.com/user-attachments/assets/c876553f-6710-4345-8366-6fef52fb4418)\\r\\n\"\n },\n {\n \"title\": \"feat: use registry\",\n \"prNumber\": 4641,\n \"type\": \"feature\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: docs deploy workflow\",\n \"prNumber\": 4640,\n \"type\": \"bugfix\",\n \"body\": \"fixes npm cache since doesn't exist for docs package, removes PR runs, should only happen on pushes.\"\n },\n {\n \"title\": \"feat: allow world selection in message API\",\n \"prNumber\": 4637,\n \"type\": \"feature\",\n \"body\": \"## Summary\\n- add optional `worldId` query param for `/agents/:agentId/message`\\n- record `worldId` in created memories\\n- document new query parameter in OpenAPI & docs\\n\\n## Testing\\n- `bun test` *(fails: Cannot find module '@playwright/test')*\"\n },\n {\n \"title\": \"Merge addpolygon resolution\",\n \"prNumber\": 4636,\n \"type\": \"other\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Featu\"\n },\n {\n \"title\": \"remove pr title CI\",\n \"prNumber\": 4644,\n \"type\": \"other\",\n \"body\": \"annoying imo, idc what name PR, should not fail CI, causes more failed looking PRs then needed.\"\n },\n {\n \"title\": \"add 30s timeout to registry parsing\",\n \"prNumber\": 4678,\n \"type\": \"feature\",\n \"body\": \"\"\n },\n {\n \"title\": \"bring back local ai test\",\n \"prNumber\": 4676,\n \"type\": \"tests\",\n \"body\": \"\"\n },\n {\n \"title\": \"remove mock tests for cli\",\n \"prNumber\": 4674,\n \"type\": \"tests\",\n \"body\": \"\"\n },\n {\n \"title\": \"chore: update project starter character & fix path for core pckg\",\n \"prNumber\": 4671,\n \"type\": \"bugfix\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n\\t- Eliza now responds helpfully and conversationally to a broader range of topics, including technology, business, cr\"\n },\n {\n \"title\": \"fix: shortcut reply only if no dynamic provider is present\",\n \"prNumber\": 4670,\n \"type\": \"bugfix\",\n \"body\": \"This PR updates the reply logic to only shortcut (reuse existing replies) when no dynamic providers are involved. It also fixes a bug where providers were incorrectly taken from the message instead of the response content.\"\n },\n {\n \"title\": \"remove plugin twitter\",\n \"prNumber\": 4669,\n \"type\": \"other\",\n \"body\": \"removes plugin twitter from mono repo has been moved to: https://github.com/elizaos-plugins/plugin-twitter\"\n },\n {\n \"title\": \"feat: Create world api endpoints\",\n \"prNumber\": 4667,\n \"type\": \"feature\",\n \"body\": \" I wanted to create World with API endpoints, so I can have a consistent usage of a world.\\r\\n There wasnt any endpoints for this so I am adding them here. \\r\\n-To create new world\\r\\n-To update current one with new info\\r\\n-To get all rooms in cur\"\n },\n {\n \"title\": \"Remove global env support\",\n \"prNumber\": 4666,\n \"type\": \"other\",\n \"body\": \"## Summary\\n- drop global env logic from CLI and server\\n- update UI to only manage local envs\\n- rewrite docs about environment variables\\n- tweak plugin messages and runtime warnings\\n\\n## Testing\\n- `bun test` *(fails: Cannot find package 'dote\"\n },\n {\n \"title\": \"add CHANNEL_IDS to discord_plugin\",\n \"prNumber\": 4665,\n \"type\": \"feature\",\n \"body\": \"adds ENVs for CHANNEL_IDS so can limit the responses to certain channels\"\n },\n {\n \"title\": \"attempt dev command tear down\",\n \"prNumber\": 4664,\n \"type\": \"other\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n