> 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/april-18-2023-cell-editor-improvements-byo-large-language-model-and-more.md).

# April 18, 2023: Cell Editor Improvements, BYO Large Language Model, and more

## BYO Large Language Model

Enterprises that are building their own large language models for privacy or security reasons can now bring them to Mito Enterprise. 

## Cell Editor Improvements

The formula writing experience in Mito has now been overhauled. Included:

1. The cell editor will expand as your formula grows in length.
2. The function documentation displayed will be relevant more of the time.
3. Other minor improvements - with a resizable formula bar coming soon!

#### More Import Methods

1. Import multiple ranges from a single CSV file. Simply select a CSV file in the import taskpane, then click `Configure` and then click to import multiple ranges.
2. Add more starts with and contains conditions to Excel range import, so users can locate better datasets.

####


---

# 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/april-18-2023-cell-editor-improvements-byo-large-language-model-and-more.md?ask=<question>&goal=<user_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.