{
  "version": "1.0",
  "type": "repository",
  "interval": "day",
  "date": "2025-06-25",
  "generatedAt": "2026-05-14T23:36:27.965Z",
  "sourceLastUpdated": "2026-05-14T23:36:27.965Z",
  "contentFormat": "markdown",
  "contentHash": "eca3594b6ee092268ca525babcd67935a41496e47a1a6185f0172d161dfb8579",
  "entity": {
    "repoId": "elizaos-plugins/registry",
    "owner": "elizaos-plugins",
    "repo": "registry"
  },
  "content": "# elizaos-plugins/registry Daily Update (Jun 25, 2025)\n\n## OVERVIEW \nToday's focus was on addressing critical bug reports related to custom plugin development and agent communication, alongside the initiation of a new plugin integration.\n\n## KEY TECHNICAL DEVELOPMENTS\n\nNo new features, bug fixes, code refactoring, documentation enhancements, or tests were added today.\n\n## NEWLY OPENED PULL REQUESTS\n\nA new pull request, [#180](https://github.com/elizaos-plugins/registry/pull/180), was opened to add the `@esscrypt/plugin-polkadot` to the registry. Its status is pending review.\n\n## CLOSED ISSUES\n\n### Plugin Configuration and Agent Response\nIssue [#5279](https://github.com/elizaos-plugins/registry/issues/5279), \"No handler found for delegate type: TEXT_EMBEDDING,\" was closed today. The resolution involved ensuring the agent character file included the `openai` plugin, which resolved the `TEXT_EMBEDDING` error and allowed the agent to reply successfully.\n\n## NEW ISSUES\n\nNo new issues were opened today.\n\n## ACTIVE ISSUES\n\n### Custom Plugin Development Challenges\nIssue [#5260](https://github.com/elizaos-plugins/registry/issues/5260), \"Create custom plugin for onchain AI agent,\" continues to be active. The original poster, yehia67, reported difficulties with Eliza as an agent only supporting one message before stopping plugin usage, and also noted that agent replies sometimes appear in the terminal but not on the interface logs. omariosman echoed similar experiences with errors during custom plugin development. The latest comment from wtfsayo suggests that the issue might be related to sending responses via both callback and return in the action, advising to use only one method.\n\n### Twitter Plugin Functionality\nIssues [#26](https://github.com/elizaos-plugins/registry/issues/26), \"Newlines in timeline replies are replaced with \\\\n\\\\n instead of actual line breaks,\" and [#29](https://github.com/elizaos-plugins/registry/issues/29), \"Twitter plugin not posting replies to mentions or tags,\" remain active. For [#26](https://github.com/elizaos-plugins/registry/issues/26), gnomonprime identified that the `plugin-twitter` template explicitly instructs the agent to use `\\\\n\\\\n` for newlines, causing the literal text to appear instead of actual line breaks. Regarding [#29](https://github.com/elizaos-plugins/registry/issues/29), gnomonprime observed similar behavior where memories are saved but responses are not delivered, suggesting it might be a random occurrence also seen in the web UI."
}