▶North Star & Strategic Context

North Star & Strategic Context

This file combines the overall project mission (North Star) and summaries of key strategic documents for use in AI prompts, particularly for the AI Agent Council context generation.

---

North Star: To build a truly autonomous, sustainable DAO that develops open-source software accelerating the path toward AGI, blending AI researchers, open-source hackers, and crypto degens to create AI agents streaming, shitposting, and trading 24/7 on auto.fun to attract users and bootstrap an autonomous organization.

---

ElizaOS Mission Summary (`docs/blog/mission.mdx`): The elizaOS mission is to build an extensible, modular, open-source AI agent framework for Web2/Web3, seeing agents as steps toward AGI. Core values are Autonomy, Modularity, and Decentralization. Key products include the framework itself, DegenSpartanAI (trading agent), Autonomous Investor/Trust Marketplace (social trading intelligence), and the Agent Marketplace/auto.fun (launchpad).

---

ElizaOS Reintroduction Summary (`docs/blog/reintroduction.mdx`): elizaOS is an open-source "operating system for AI agents" aimed at decentralizing AI development away from corporate control. It's built on three pillars: 1) The Eliza Framework (TypeScript toolkit for persistent, interoperable agents), 2) AI-Enhanced Governance (building autonomous DAOs), and 3) Eliza Labs (R&D for future capabilities like v2, Trust Marketplace, auto.fun, DegenSpartanAI, Eliza Studios). The native Solana token coordinates the ecosystem and captures value. The vision is an intelligent internet built on open protocols and collaboration.

---

Auto.fun Introduction Summary (`docs/blog/autofun-intro.mdx`): Auto.fun is an AI-native, creator-first token launchpad designed for sustainable AI/crypto projects. It aims to balance fair community access with project funding needs through mechanisms like bonding curves and liquidity NFTs. Key features include a no-code agent builder, AI-generated marketing tools, and integration with the elizaOS ecosystem. It serves as a core product driving value back to the native token ($ai16z) through buybacks and liquidity pairing.

---

Taming Information Summary (`docs/blog/taming_info.mdx`): Addresses the challenge of information scattered across platforms (Discord, GitHub, X). Proposes using AI agents as "bridges" to collect, wrangle (summarize/tag), and distribute information in various formats (JSON, MD, RSS, dashboards, 3D shows). Showcases an AI News system and AI Assistants for tech support as examples. Emphasizes treating documentation as a first-class citizen to empower AI assistants and streamline community operations.

▶Daily Strategic Focus

The engineering team is making significant progress on unified streaming support across plugins while simultaneously addressing token migration challenges and security concerns.

Monthly Goal

Current focus: Stabilize and attract new users to auto.fun by showcasing 24/7 agent activity (streaming, trading, shitposting), ship production ready elizaOS v2.

Key Deliberations

Streaming Support Implementation

The team is actively developing unified streaming support across plugins, starting with plugin-openrouter before extending to plugin-openai and plugin-anthropic, representing a critical technical milestone for elizaOS v2.

How should we prioritize streaming implementation across different plugins to best serve our goal of demonstrating 24/7 agent activity?

Stan is working on unifying the `useModel` behavior for both normal and streaming modes, starting with the plugin-openrouter implementation before extending the pattern to plugin-openai and plugin-anthropic.
Stan: Work includes streaming on both server (API/SSE/WebSocket) and client (UI) sides

1Focus on completing plugin-openrouter first as a model implementation, then expand to other plugins sequentially.

This approach provides a stable reference implementation but may delay full ecosystem streaming support.

2Accelerate parallel development across all plugins simultaneously with multiple engineers assigned.

This maximizes speed to market but risks inconsistencies in implementation and increases coordination complexity.

3Prioritize plugins based on user adoption metrics, focusing development efforts on the most widely used LLM connections first.

This optimizes for immediate user impact but might neglect emerging models that could be strategic differentiators.

4Other / More discussion needed / None of the above.

What strategic benefits should we emphasize when marketing the streaming capabilities to auto.fun users?

Issue #6206 titled 'Streaming Support' by @borisudovicic is OPEN
Stan: Implement streaming on server (API/SSE/WebSocket) and client (UI)

1Enhanced user experience with more responsive interfaces and real-time agent interactions.

This positions streaming as a UX differentiator that makes elizaOS agents feel more natural and engaging.

2Reduced API costs and improved performance by processing partial results as they arrive.

This emphasizes the economic advantages for developers and presents elizaOS as the cost-efficient choice for AI infrastructure.

3New creative possibilities for building dynamic, real-time streaming agents that can create continuous content.

This aligns directly with our goal of showcasing 24/7 agent activity and positions elizaOS as an innovation platform.

4Other / More discussion needed / None of the above.

Token Migration & Security

The community is experiencing challenges with the AI16Z to ElizaOS token migration, while simultaneously facing increased security threats from scammers targeting users during this transition period.

How should we improve the token migration process to minimize confusion and protect users from scams?

Several users needed help with token migration, particularly those who purchased tokens after the snapshot
Multiple scam alerts when suspicious links or users were detected in the discussion channel

1Deploy an automated verification system that flags suspicious links and validates official migration channels.

This provides technical protection but requires development resources that could be directed to core platform features.

2Create a detailed, pinned step-by-step migration guide with visual verification cues and a dedicated support team.

This focuses on education and support but may still leave some users vulnerable to sophisticated phishing attempts.

3Implement a simplified one-click migration tool within trusted interfaces like the official website and wallet plugins.

This creates the best user experience but may be complex to implement across different wallet ecosystems.

4Other / More discussion needed / None of the above.

Should we accelerate the development of features mentioned by MDMnvest (Eliza Cloud, EVM integration, etc.) to stimulate token value and migration interest?

MDMnvest mentioned upcoming technical developments including 'Eliza Cloud, generative treasury mechanism, EVM integration, ERC-8004, x402, V2 upgrades, Cross-Chain expansions, Babylon, key partnerships and integrations, elizaOS chain'

1Yes, accelerate development of these features with increased resources to generate market excitement.

This might boost token value but risks diverting resources from the monthly goal of stabilizing auto.fun and completing elizaOS v2.

2Maintain current development pace but improve communication about the roadmap with regular, transparent updates.

This balances development reality with market perception while maintaining focus on core priorities.

3Selectively accelerate only features that directly support auto.fun's growth while deferring others.

This aligns development with our monthly goal but might disappoint community members expecting broader ecosystem advancement.

4Other / More discussion needed / None of the above.

Developer Experience Enhancement

Recent work indicates a need to improve the developer experience for elizaOS, with focus areas including streamlining agent setup and addressing technical issues like plugin behavior and directory management.

How should we balance maintaining technical flexibility with improving developer onboarding simplicity?

ninja asked about an elegant Python solution for admin plugin reset without restart
Issue #6204 titled '.eliza needed or plugin-sql crashes, should autocreate' by @lalalune

1Focus on creating simplified wrappers and smart defaults while maintaining all advanced options for power users.

This provides the best of both worlds but increases maintenance complexity as both simple and advanced APIs must be supported.

2Redesign core APIs with simplicity as the primary goal, even if it means breaking changes for existing integrations.

This optimizes for new developer acquisition but risks alienating existing community members who have already invested in learning our system.

3Keep APIs as-is but invest heavily in comprehensive templates, examples, and automated project generators.

This minimizes disruption to existing developers but may not address fundamental usability issues in the core platform.

4Other / More discussion needed / None of the above.

What development priorities would best support our goal of showcasing 24/7 agent activity on auto.fun?

Brief disagreement about tool calling functionality, with Odilitime suggesting it's unnecessary optionality
DorianD jokingly suggested creating 'agentic robots with ElizaOS logos and a prediction market app for betting on agent health'

1Prioritize tools that enable continuous agent activity, such as automated recovery, scheduling, and persistent memory.

This directly serves our goal of 24/7 agent activity but may not address broader ecosystem needs.

2Focus on engagement features like prediction markets, agent interactions, and social capabilities to drive user retention.

This emphasizes the social aspects that might attract and retain users but could distract from core stability work.

3Invest in monitoring, analytics, and developer tools to help the community build and maintain their own always-on agents.

This leverages community creativity but places more responsibility on external developers rather than our core team.

4Other / More discussion needed / None of the above.

Council Briefing

North Star & Strategic Context

Key Deliberations