> 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/product-scope/limitations.md).

# Limitations

Myros is designed to be useful immediately, but the current release is still early.

| Limitation                     | Current Impact                                                     | Planned Direction                     |
| ------------------------------ | ------------------------------------------------------------------ | ------------------------------------- |
| Website-only knowledge sources | Agents cannot yet ingest PDFs, CSVs, DOCX, or uploaded files       | Add file ingestion support            |
| No vector search yet           | Retrieval may miss paraphrased or semantically related information | Add embeddings and similarity search  |
| Re-crawling per query          | Can increase latency and bandwidth usage                           | Add crawler caching                   |
| Shared admin password          | Access control is simple but not granular                          | Add per-user admin roles              |
| Telegram-first interface       | Initial use case is strong but platform scope is narrow            | Add additional interfaces             |
| Limited analytics              | Admins lack detailed usage insights                                | Add analytics dashboard and reporting |
| No plugin marketplace          | Extensions are manual at first                                     | Build modular plugin ecosystem        |

This transparency is important.

Myros should not pretend to be complete.\
Myros should show that she is real, usable, and evolving.


---

# 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, and the optional `goal` query parameter:

```
GET https://myros.gitbook.io/bp/product-scope/limitations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.