> For the complete documentation index, see [llms.txt](https://docs.emobiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.emobiq.com/emobiq-ai/readme/limitations.md). # Limitations While eMOBIQ AI is designed to streamline app development with powerful AI capabilities, it's important to be aware of certain limitations to ensure optimal usage and avoid potential issues. Understanding the current limitations of eMOBIQ AI helps ensure smooth development and sets realistic expectations. Here are some key limitations to note. ### 1) Token Usage Constraint Each interaction with the Debug Agent consumes tokens, which are used to process prompts and generate responses. The number of tokens consumed depends on the complexity and length of the request. As a result, larger or more intricate tasks may use a significant portion of your available token quota depending on the number of users active on the platform. To manage this effectively and prevent a long waiting time, it is recommended to break down complex tasks into smaller and focused prompts. ### 2) Not a Fully Automated App Builder While eMOBIQ AI significantly accelerates the app creation process, it is not a fully autonomous solution. Some level of human oversight and refinement is often required, especially when dealing with complex logic, custom integrations, or specific design requirements. In many cases, multiple iterations and adjustments may be necessary to achieve the desired outcome. You can refer to our [Debug Agent Prompting Guide](/emobiq-ai/readme/debug-agent.md) for more information. ### 3) Fact-Checking Required Like any AI system, eMOBIQ AI is not immune to errors. It may occasionally produce incorrect or suboptimal code, misinterpret prompts, or fail to align with expected behavior. Visual components may not always render exactly as intended, and API references might contain inaccuracies. Users should always verify and test the output before considering it final. Fact-checking and validation are essential steps to ensure reliability and correctness. --- # 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://docs.emobiq.com/emobiq-ai/readme/limitations.md?ask=&goal= ``` `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.