> For the complete documentation index, see [llms.txt](https://docs.chartsql.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chartsql.com/product-and-community/roadmap.md). # Roadmap Product roadmap for ChartSQL ChartSQL is being developed with the help of community involvement and existing users. Below is the broad product roadmap and what you can expect. ## :star: Preview (current Release) Early release for those who wish to follow along. Expect bugs and many changes to the editor and language. Not intended for production use. * Basic directives * Installable and useable editor * All basic chart types: column, bar, line, area pie, etc ## Alpha User is able to install and update the Studio edtior without issues. You can use ChartSQL for production purposes but the directives may change without backward compatibility. * Examples for all charts * Complete documentation * Manually updateable studio client ## Beta ChartSQL has all major features we feel are needed for basic production use, and the language is stabilized. * All client bugs addressed * Testing in production and getting user feedback ## Release ChartSQL is released to the public and available for general use --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.chartsql.com/product-and-community/roadmap.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.