Eliza Times

Babylon, the AI prediction game built by ElizaOS, is nearing launch.

Users discussed the platform where humans and AI agents compete in real-time prediction games. The platform features AI characters like DegenSpartan and Aiko, with users expressing interest in betting features and visual graphics. Babylon is described as a fast social prediction game where participants react to live events, with the launch expected soon.

Technical discussions focused on MCP server integration challenges.

Developers encountered issues with Anthropic API integration where TEXT_EMBEDDING handlers were not found. The solution requires keeping both ANTHROPIC_API_KEY and OPENAI_API_KEY in the environment file, with Anthropic plugin placed first in the plugin list. The OpenAI key serves as a fallback for embeddings even when using Anthropic as the primary model. Interestingly, the OpenAI key does not need to be valid, just present in the configuration.

Core development team shared updates on infrastructure improvements.

Jin posted temporal analysis showing the council's current focus areas and principles, along with extracted high priority issues based on feedback. The team is considering converting every plugin into a skill for better modularity. Multiple performance improvements for the monorepo are being prepared. The team also shared annual and quarterly summary data for retrospective discussions.

New developers joined the community offering expertise in blockchain, AI systems, and full-stack development.

One developer expressed interest in contributing to agent autonomy with constraints, onchain execution layers with guardrails, practical agent templates for prediction markets, and observability tooling. The community directed new contributors to the coders channel and encouraged them to explore the open source codebase, particularly the plugin-based architecture.

Community members discussed tokenomics and monetization strategies.

One suggestion proposed 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, team members emphasized that Eliza prioritizes open source freedom, allowing people to freely create and deploy their own agents and earn revenue independently, rather than creating a closed loop system.

Technical support was provided for various issues.

Users encountered problems with Discord plugin not detecting server IDs despite correct permissions and intents. Migration issues were addressed through the official ticket system. Database migration errors were resolved by setting ELIZA_ALLOW_DESTRUCTIVE_MIGRATIONS=true or using the elizaos dev command for continuous development monitoring instead of elizaos start.

Advanced development tools and integrations were shared.

A developer released a library for x402 protocol integration with ElizaOS for micropayments on Solana. The oh-my-opencode plugin was discussed, featuring battery-included async subagents, curated agents with proper models, crafted tools like LSP/AST, and Claude Code compatibility. A voice skill for talking to Claude about projects over the phone was also shared.

The Spartan project was highlighted as a key area for DeFi utilities within the ElizaOS ecosystem.

Odilitime, the lead developer on Spartan, engaged with new contributors interested in blockchain and AI integration. The project focuses on quantitative trading and DeFi interactions with agent autonomy.

Infrastructure and standards discussions included updates on ERC-8004 contracts nearing finalization.

The team discussed LLM compression techniques for running Claude and GPT models locally. RSS feeds were set up for knowledge base updates and council discussions. A Rust-inspired ElizaOS framework called Zoey was mentioned, focusing on privacy-first and local-first AI agent deployment.

Messaging API Improvements: Issue #6298 addresses problems with the Messaging API, specifically focusing on fixing double processing issues and aligning transports.

This issue was created by linear and aims to improve the reliability and consistency of message handling across different transport mechanisms.

Authentication and User Management: Issue #6327 focuses on implementing JWT authentication and user management functionality.

This issue was created by linear and represents important security and access control features for the ElizaOS platform.

Performance and Bug Fixes: Two critical issues were reported by madjin.

Issue #6332 is a performance problem where Turbo build is consuming excessive memory, over 21GB, which impacts development efficiency. Issue #6331 is a bug where a Model not found error occurs when using agent ID with API endpoints, affecting the API functionality.

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 upgrading Claude workflows with Opus 4.5 and adding security and maintenance jobs, as well as allowing the cursor bot to trigger Claude workflows.

Between January 5 and January 7, 2026, the elizaos/eliza repository showed varying levels of activity.

From January 5 to January 6, the repository had 5 new pull requests with all 5 being merged, 2 new issues were opened, and 10 contributors were active. The following day, from January 6 to January 7, activity decreased significantly with 0 new pull requests, 2 new issues opened, and only 2 active contributors. Overall, during this two-day period, the repository had 5 merged pull requests, 4 new issues, and engagement from multiple contributors with peak activity on the first day.

On January 5, 2026, ElizaOS made significant progress in core agent framework development, SQL plugin stability, and documentation coverage.

The team introduced a new useElizaChat hook for unified interaction across HTTP, SSE, and WebSocket transports, and completed implementation of core Eliza hooks including useEliza and useElizaChat for SDK-first development in the browser. Agent lifecycle management hooks such as useAgentList, useStartAgent, and useStopAgent were also implemented. Critical architectural issues in the Messaging API were resolved, addressing double processing and transport alignment problems.

The SQL plugin received important stability fixes on January 5th.

PostgreSQL SET LOCAL command failures were resolved by correctly parameterizing with sql.raw(). Critical issues in plugin-sql were addressed by adding pool configuration, an error handler, and fixing PGLite shutdown problems to prevent runtime crashes.

Documentation coverage expanded dramatically from approximately 60% to 95% on January 5th by adding new guides such as streaming responses, updating existing content, and improving clarity across various sections.

The ElizaOS website's RSS feed readability was enhanced with an XSL stylesheet, and Dependabot was integrated for automated dependency management to improve maintenance and security.

CI/CD workflows were enhanced on January 5th with upgrades to Claude-powered workflows using the stable v1 action and Opus 4.5 model.

Two new automated workflows for security and maintenance were added, and CI was configured to allow the Cursor bot to trigger Claude workflows.

On January 6, 2026, several critical bugs were identified across ElizaOS repositories.

The Discord plugin experienced publishing failures for versions v1.3.4 and v1.3.6, requiring investigation of TypeScript errors and package.json dependencies. The Telegram plugin was found to crash with a TypeError when processing images uploaded as a photo. Users reported Model not found errors when using agent IDs with API endpoints in the core Eliza agent.

Performance concerns emerged on January 6th regarding the Turbo build tool consuming excessive memory (21GB+), impacting developer experience and CI stability.

Additionally, a need for documentation on agent memory configuration was identified, specifically for knowledge and lore sections, to address user difficulties.

New feature requests from January 5th include providing a mock client for frontend testing to eliminate the need for a live server during development, and implementing JWT authentication with robust user management capabilities.