{
  "version": "1.0",
  "type": "repository",
  "interval": "day",
  "date": "2025-06-25",
  "generatedAt": "2026-05-14T23:36:27.966Z",
  "sourceLastUpdated": "2026-05-14T23:36:27.966Z",
  "contentFormat": "markdown",
  "contentHash": "5f92d6834f48828c3a8014ad38d351dfa5c914ad1a050f6314f026767a5bcd41",
  "entity": {
    "repoId": "elizaos/elizaos.github.io",
    "owner": "elizaos",
    "repo": "elizaos.github.io"
  },
  "content": "# elizaos/elizaos.github.io Daily Update (Jun 25, 2025)\n## OVERVIEW \nToday's development focused on significant improvements to wallet address ingestion speed and refactoring the GitHub data fetching logic, alongside addressing critical issues related to plugin functionality and agent responses.\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### Enhanced Wallet Address Ingestion\nThe ingestion speed for wallet addresses has been significantly improved by implementing batched GraphQL requests to mitigate rate limiting. This change streamlines the process of fetching wallet data from GitHub.\n- Implemented batch processing for fetching wallet addresses, improving efficiency and mitigating rate limits. ([#134](https://github.com/elizaos/elizaos.github.io/pull/134))\n- Introduced a new pipeline step for ingesting user wallet addresses, including tracking of successful ingests. ([#132](https://github.com/elizaos/elizaos.github.io/pull/132))\n\n### Refactored GitHub Data Fetching\nThe `githubService` has been removed and its functionality integrated into an updated `github.ts` class, centralizing and improving the maintainability of GitHub data interactions.\n- Removed the `githubService` and updated the `github.ts` class to replace its functionality. ([#132](https://github.com/elizaos/elizaos.github.io/pull/132))\n- Reverted workflow changes and set up Gemini, as fetching addresses is now handled by pipelines. ([#133](https://github.com/elizaos/elizaos.github.io/pull/133))\n\n## NEWLY OPENED PULL REQUESTS\nNo new pull requests were opened today.\n\n## CLOSED ISSUES\n\n### Wallet Address Fetching Optimization\nThe issue concerning wallet address fetching during the NextJS build process has been resolved by moving this functionality to the pipelines workflow, aligning it with other GitHub data fetching operations.\n- Resolved the issue of fetching wallet addresses during NextJS build by migrating the process to pipelines. ([#130](https://github.com/elizaos/elizaos.github.io/issues/130))\n\n### Plugin Configuration and Error Resolution\nA critical bug related to the `TEXT_EMBEDDING` delegate type has been fixed by ensuring the agent character file includes the necessary OpenAI plugin.\n- Fixed the \"No handler found for delegate type: TEXT_EMBEDDING\" error by adding the `@elizaos/plugin-openai` to the agent character file. ([#5279](https://github.com/elizaos/elizaos.github.io/issues/5279))\n\n## NEW ISSUES\nNo new issues were reported today.\n\n## ACTIVE ISSUES\n\n### Custom Plugin Development Challenges\nUsers are encountering difficulties with custom plugin development, specifically with the Eliza agent only processing a single message before stopping plugin usage. A user noted a similar experience with errors during custom plugin development. Another user observed that while the agent replies correctly in the terminal, the response doesn't always appear in the interface logs, indicating a potential display or message bus issue. ([#5260](https://github.com/elizaos/elizaos.github.io/issues/5260))\n\n### Twitter Plugin Reply Issues\nThe Twitter plugin is failing to post replies to mentions or tags, despite successful loading and enabled configurations. A user reported that memories are being saved, but the response is not being delivered, suggesting a potential drop-off in the response flow. It was also noted that newlines in timeline replies are being replaced with `\\\\n\\\\n` instead of actual line breaks, which appears as raw text on Twitter. This is attributed to the template explicitly instructing the agent to use `\\\\n`. ([#29](https://github.com/elizaos/elizaos.github.io/issues/29), [#26](https://github.com/elizaos/elizaos.github.io/issues/26))"
}