> For the complete documentation index, see [llms.txt](https://docs.trymito.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trymito.io/misc/release-notes/january-2nd-inline-completions-arrive.md). # January 2nd - Inline Completions Arrive Happy New Year! We're kicking off 2025 with some exciting updates to Mito AI. This includes inline completions, a more intuitive chat workflow, and dark mode. ### Inline Completions * As you type in a code cell, you'll now see code suggestions. Press the **Tab** key to accept a suggestion. * Try writing comments as blueprints for your code and let the AI generate the corresponding implementation. ### New Chat Workflows * **Enhanced Q\&A Abilities**: Mito AI now determines whether your question requires code or just an explanation, making it suitable for tasks ranging from planning to execution. * **Cell Previews**: When chatting with Mito AI, a preview of the active cell is shown, so you can easily reference its content when asking questions. * **Code Suggestions Preview**: Press **CMD+Y** to preview a code suggestion. Press the same shortcut again to accept it. * Code suggestions can also be added directly to any selected cell. ### UI Changes * Chat messages now automatically scroll to show the latest response from Mito AI. * Dark mode support. --- # 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.trymito.io/misc/release-notes/january-2nd-inline-completions-arrive.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.