Eliza Times

RoseOS introduced itself as an experimental agent framework built on top of ElizaOS, focused on designing autonomous systems with explicit agency boundaries, constraint-aware reasoning, and accountability layers.

The project explores how AI agents can reason and act within defined policy constraints, make decisions instead of executing static instructions, adapt behavior while preserving traceability and responsibility, and operate as composable, modular software primitives. RoseOS treats autonomy as an engineering problem emphasizing control surfaces, decision limits, and predictable behavior in autonomous execution environments. The framework is described as agent-first software built with guardrails, focusing on decision quality, execution discipline, and trust.

Core developers made significant improvements to ElizaOS logging and provider handling.

Stan introduced next-level logging capabilities and a linter for logs in the eliza/config package that warns if logs are in the wrong format. He also optimized provider handling in multi-step mode through a pull request that affects internal execution order, making providers execute faster while still returning all results. The team is working on bootstrap optimizations for providers. Jin reported significant work going into Eliza knowledge data pipelines with documentation, presentation, and demonstration phases coming soon.

Developers discussed technical implementation details and deployment options.

Users asked about implementing multiple AI models in one agent, such as using Anthropic for calculating tasks and forecasting while using OpenAI for reasoning tasks. Odilitime confirmed this is possible with custom code using useModel with the provider option. For agents with plugins not yet added to cloud, developers recommended deploying outside of cloud using containers. ElizaOS CLI provides a command to deploy in one command, with containers and logs visible directly from the cloud dashboard. A developer shared integration documentation for connecting AI agents to websites and other platforms with API keys.

Community members discussed trading bot capabilities and limitations.

A developer explained that on Solana, without a GRPC ingester processing each transaction on each DEX to extract bundle block 0, dev buy, and reputation dev with millisecond precision and full payload preshot, it is impossible to make a profit. Even for an agent with reaction time, it would be too long. The developer shared screenshots of their working system but stated they would not give it away due to the insane amount of work involved. They emphasized the need for custom code, live Twitter feeds for token creation, and automated bundlers for fund transfers.

Community discussions covered various topics including Hyperscape development, ElizaOS price movements, and project updates.

Users inquired about a Hyperscape channel, learning there is a developer Discord currently only for developers working on the project. Shaw was noted interacting with Sterling on Twitter. DegenAI continues to be updated with Odilitime working on development. A user asked about discussions with Twitter to unban the DegenAI main account. Community members shared optimism about ElizaOS reaching higher price targets, with some hoping for drops to accumulate more tokens.

Technical issues and solutions were discussed.

A developer reported that the Discord plugin version 1.3.4 failed to publish and is now at version 1.3.5, while working to ensure their agent functions properly on Discord before installing other plugins. Another developer asked about adding knowledge and lore sections to the new JSON format like in previous versions. The core development team suggested an Eliza-owned crash course on agentic AI as a lead funnel for cloud services.

The wallet connection flow needs improvement.

Currently, the connect wallet feature should ideally navigate users directly to wallet options rather than requiring additional steps.

There is a refresh issue with conversation deletion.

When a user deletes a conversation, the page needs to be manually refreshed for the conversation to actually show as deleted, indicating a lack of real-time UI updates.

A feature request has been made for agent following functionality, which would allow users to follow specific agents within the platform.

A terminology change has been requested to change the word Chat to Talk throughout the interface for better user experience and consistency.

The agent sorting feature is currently not functioning properly, preventing users from organizing agents according to their preferences.

Between January 3rd and January 5th, 2026, the elizaos/eliza repository showed moderate development activity.

On January 3-4, there was 1 new pull request which was successfully merged, 2 new issues were opened, and 4 contributors were active. The following day, January 4-5, activity shifted with no new pull requests or merges, but issue reporting increased to 4 new issues, while active contributors decreased slightly to 3. Overall, the two-day period saw 1 merged PR, 6 new issues total, and sustained contributor engagement.

Over January 3-4, 2026, the ElizaOS project made progress on core service optimization while identifying multiple UI/UX and functionality issues requiring attention.

On January 3rd, development focused on optimizing the default-message-service in elizaos/eliza to improve provider handling in MultiStep mode for faster internal execution without changing functionality. A pull request was opened to fix a parameterization problem in the plugin-sql component using sql.raw() for SET LOCAL operations. New issues were identified regarding user experience, including the need for the Connect wallet action to lead directly to wallet options and extending scrolling functionality to the entire page for better navigation. On January 4th, no new code was contributed or merged, but the team focused on documenting improvement areas. Several new issues were opened concerning agent interaction, UI/UX consistency, and conversation management, including problems with agent sorting functionality, the inability to easily re-find agents after closing chats (suggesting a need for bookmarking features), a request to change Chat terminology to Talk for consistency, and a bug requiring page refresh for deleted conversations to disappear visually.

A refactoring effort has been completed to optimize provider handling in the MultiStep component of the default-message-service.

This work was submitted as Pull Request #6263 to the elizaOS/eliza repository on GitHub.