Eliza Times

Feature Request - Agent Following: Issue #6321 submitted by borisudovicic proposes implementing an agent 'following' feature, though specific details about the functionality are not provided in the source.

Core Development Tasks: Two issues focus on core system development.

Issue #5929 addresses Lifecycle and Utilities components, while Issue #5928 deals with Core Hooks implementation. Both issues were created by borisudovicic.

Technical Infrastructure Issues: Issue #6298 submitted by linear addresses problems with the Messaging API, specifically focusing on fixing double processing issues and aligning transports.

Issue #6327, also from linear, concerns JWT authentication and user management implementation.

Community members discussed Hyperscape development access.

A user inquired about a dedicated Hyperscape channel and was informed that there is currently a developer discord only accessible to developers working on the project. Users interested in building on Hyperscape were advised to contact Shaw directly for access.

Shaw was observed interacting with Sterling on social media, generating positive reactions from the community.

A community member also shared a comprehensive video deep-dive on ElizaOS covering the ecosystem overview, Eliza Cloud, Babylon, Hyperscape, revamped token economics, and Shaw's return to X. The video is available on both X and YouTube.

Technical discussions in the coders channel focused on Solana trading bot development.

A developer explained that profitable trading on Solana requires GRPC ingester processing each transaction on DEX platforms with millisecond precision, full payload preshot capabilities, and custom builders with powerful algorithms. The developer shared screenshots of their working system but stated they would not share the code due to the extensive work involved.

Developers discussed using custom code with useModel and provider options.

A question was raised about Polymarket phase 2 updates from the Otaku repository and whether it would be shared on the ElizaOS Polymarket plugin. A new developer asked for a brief explanation of how Eliza works and received a detailed response explaining that Eliza allows users to create agents equipped with specific data, AI models, plugins for third-party platforms like X, Discord, Telegram, and real-world tool connections, all on an open source operating system.

Core developers addressed memory optimization issues with Turbo using 21GB to 27GB of memory during builds, though subsequent runs showed normal behavior.

Jin announced significant work on Eliza knowledge data pipelines with documentation and presentation phases coming soon. The team also discussed logging practices and shared relevant resources.

Community members discussed Babylon, the AI prediction game platform.

Users were directed to the Babylon website and Twitter account. Questions arose about whether Babylon would feature 3D graphics and visual representations of Eliza on her throne with agents like DegenSpartan and Aiko competing. The platform is described as a fast social prediction game where humans and AI agents react to live events in real time.

A community member suggested monetizing the ElizaOS tech stack similar to Virtuals by pairing tokens with ELIZA through routing, where every trade would drive value back to ELIZA.

However, another member expressed disappointment with this suggestion, emphasizing that Eliza gives people freedom through open source to freely create and deploy their own agents and earn revenue for themselves, contrasting this with closed loop systems. The discussion highlighted the philosophical difference between human empowerment and restrictive tokenomics.

Technical support was provided for MCP server integration issues with Anthropic.

A developer encountered TEXT_EMBEDDING handler errors when using Anthropic API key alone. The solution required keeping both ANTHROPIC_API_KEY and OPENAI_API_KEY in the environment, with Anthropic plugin placed first in the plugin list. Interestingly, the OpenAI key does not need to be valid, just present with any value for the MCP server to work with Anthropic.

Jin shared temporal analysis showing the council's current focus and principles, extracted high priority issues based on feedback, and announced plans to write up how the system works and how to stay updated.

Jin also expressed interest in turning every plugin into a skill, which received positive reactions from the community.

Core developers discussed various technical resources including Oh My OpenCode plugin with battery included async subagents compatible with Claude Code, ERC-8004 contract updates, and Nano Banana AI capabilities.

A developer demonstrated impressive results using Nano Banana for generating cover images and suggested creating a version similar to slidegen that produces multiple variations of the same prompt. The team also shared resources about LLM compression and running Claude and GPT locally.

The council demonstrated capability for monthly, quarterly, and annual retrospective discussions.

Jin shared 2025 annual and Q4 summary JSON files showcasing this functionality. Core developers also worked on SQL plugin testing with entity context and data isolation improvements, though encountered issues with Claude code review in CI.

Community members warned about scammers in the discussion channel.

The official ticket system is only through the designated support channel, and team members will never DM users first. Response times for tickets typically range from 2 to 7 days. Users were also reminded that ELIZA token is not related to the ElizaOS project.

A new feature was added introducing unified hooks with multi-transport support, enabling HTTP, SSE (Server-Sent Events), and WebSocket protocols.

Multiple bug fixes were implemented for the SQL plugin, including using sql.raw() for SET LOCAL to avoid parameterization issues, adding pool configuration, implementing an error handler, and fixing PGLite shutdown problems.

CI/CD improvements were made including allowing the cursor bot to trigger Claude workflows and upgrading Claude workflows with Opus 4.5 while adding security and maintenance jobs.

The elizaos/eliza repository showed varying levels of activity over a two-day period from January 4-6, 2026.

On January 4-5, the repository had no new pull requests and none merged, with 4 new issues opened and 3 active contributors. Activity increased significantly on January 5-6, with 5 new pull requests all successfully merged, 2 new issues opened, and 10 active contributors participating in the project.

On January 4, 2026, the ElizaOS project focused on identifying and documenting areas for improvement without any code contributions or merges.

Four new issues were opened in the elizaos/eliza repository addressing user experience concerns: the inability to easily re-find agents after closing chats, requiring an agent following or bookmarking feature (issue 6321); agent sorting functionality not working as expected (issue 6319); a request to change the term 'Chat' to 'Talk' for platform consistency (issue 6320); and a bug requiring page refresh for deleted conversations to visually disappear (issue 6322).

On January 5, 2026, ElizaOS made significant progress across multiple areas.

Core agent framework development introduced a new useElizaChat hook for unified interaction across HTTP, SSE, and WebSocket transports (PR 6300), and completed implementation of core Eliza hooks including useEliza and useElizaChat for SDK-first browser development (issues 5928, 5966). Agent lifecycle management hooks were implemented (issue 5929), and architectural issues in the Messaging API were resolved (issue 6298).

Critical SQL plugin fixes were delivered on January 5, including fixing PostgreSQL SET LOCAL command failures through correct parameterization with sql.raw() (PR 6316), and addressing issues in plugin-sql by adding pool configuration, error handlers, and fixing PGLite shutdown problems to prevent runtime crashes (PR 6323).

Documentation and website improvements on January 5 expanded coverage from approximately 60% to 95% by adding new guides on streaming responses and updating existing content (docs PR 81).

The ElizaOS website RSS feed readability was enhanced with an XSL stylesheet (elizaos.github.io PR 188), and Dependabot was integrated for automated dependency management. CI/CD workflows were upgraded to use Claude v1 action with Opus 4.5 model, two new automated workflows for security and maintenance were added, and CI was configured to allow Cursor bot to trigger Claude workflows (PRs 6324, 6328).

Work in progress on January 5 included multiple dependency update pull requests for elizaos.github.io (PRs 189-192) and new pull requests for elizaos/eliza focusing on plugin-sql testing with entity context and RLS tests (PR 6330), and adding CachedDatabaseAdapter with LRU caching (PR 6329).

Two new issues were opened: providing a mock client for frontend testing to eliminate the need for a live server during development (issue 6326), and implementing JWT authentication and robust user management (issue 6327).