> For the complete documentation index, see [llms.txt](https://myros.gitbook.io/bp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://myros.gitbook.io/bp/roadmap.md).

# Roadmap

<figure><img src="/files/vWTnWigOPxQqiQplsIUx" alt=""><figcaption></figcaption></figure>

The Myros roadmap is structured in phases, each designed to make her more useful, more extensible, and more trusted by builders. Timelines are indicative and reviewed quarterly to reflect progress, adoption, and ecosystem priorities.

<table><thead><tr><th width="200">Phases</th><th width="149">Timeline</th><th>Summary</th></tr></thead><tbody><tr><td><strong>Phase 1: Awakening</strong></td><td>Q4 2025 - Q1 2026</td><td><ul><li>Launch the Myros Research</li><li>First Myros release</li><li>Establish native knowledge agents</li><li>Enable project creation, admin mode, user mode, and source management</li><li>Deploy website crawling, LLM responses, and conversation memory</li><li>Prepare public documentation and GitHub release</li></ul></td></tr><tr><td><strong>Phase 2: Existence</strong></td><td>Q2 2026</td><td><ul><li>Launch Myros as an independent open-source project</li><li>Refine brand identity, whitepaper, and developer positioning</li><li>Improve setup flow for builders and community operators</li><li>Add crawler caching to reduce latency and cost</li><li>Strengthen personality configuration for project-specific agents</li><li>Publish early deployment guides and example agents</li></ul></td></tr><tr><td><strong>Phase 3: Perception</strong></td><td>Q3 2026</td><td><ul><li>Expand knowledge ingestion beyond websites</li><li>Introduce file support for PDF, CSV, DOCX, and structured documents</li><li>Add vector embeddings and similarity search</li><li>Improve response accuracy through better retrieval logic</li><li>Release developer modules for custom agent behavior</li><li>Begin community contribution program</li></ul></td></tr><tr><td><strong>Phase 4: Intelligence</strong></td><td>Q4 2026</td><td><ul><li>Introduce multi-platform agent interfaces</li><li>Add Discord, web chat, and API-based integrations</li><li>Release role-based admin permissions</li><li>Add analytics for usage, source quality, and question patterns</li><li>Improve memory architecture for longer-term project context</li><li>Prepare plugin framework for community-built extensions</li></ul></td></tr><tr><td><strong>Phase 5: Autonomy</strong></td><td>Q1 2027</td><td><ul><li>Launch modular agent framework</li><li>Enable custom tools, workflows, and task automation</li><li>Support advanced source connectors such as GitHub, Notion, and databases</li><li>Release SDKs for developers and ecosystem builders</li><li>Expand self-hosting and deployment templates</li><li>Establish Myros as an open-source standard for project-specific AI agents</li></ul></td></tr><tr><td><strong>Phase 6: Myros Network</strong></td><td>Q2 2027 Onward</td><td><ul><li>Grow the Myros builder ecosystem</li><li>Support community-created plugins and agent templates</li><li>Expand into gaming, Web3, open-source, startups, and internal team productivity</li><li>Establish partnerships with projects that need living knowledge agents</li><li>Position Myros as the open-source intelligence layer for communities and products</li></ul></td></tr></tbody></table>

Roadmap is reviewed quarterly.

Progress is measured against adoption, active deployments, developer contributions, agent quality, and community usage.

Myros will evolve through transparency, builder ownership, and open-source collaboration.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://myros.gitbook.io/bp/roadmap.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.