> 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/mito-ai/smart-debugging.md).

# Smart Debugging

Is your code erroring because you typed a variable name incorrectly? Maybe you mixed up your single and double quotes? Or maybe it's something more complicated and nuanced like accidentally running Jupyter code cells out of order. Debugging errors like these can be challenging and frustrating, taking you out of the flow of exploring and analyzing your data.&#x20;

Mito makes it easy to debug these errors using AI. Just ask for help.&#x20;

<figure><img src="https://2294704369-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MP_U5ZCmiamDOXEOOTC%2Fuploads%2F9r7MKQbhF2OLwJuvV94o%2FErrorResolution.gif?alt=media&amp;token=32c78f36-0124-459e-ba70-2ac2f72065c0" alt=""><figcaption><p>Debugging with AI</p></figcaption></figure>

### How to debug errors using AI?

When a code cell errors, click the `Fix Error in AI Chat` button to have Mito AI automatically try to fix your error. It will use the context of the code cell and variables that you have defined to figure out why your code is erroring and suggest a fix.&#x20;


---

# 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/mito-ai/smart-debugging.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.
