> For the complete documentation index, see [llms.txt](https://docs.nested-knowledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nested-knowledge.com/resources/support/supported-platforms.md).

# Supported Platforms

Learn what platforms are supported in Nested Knowledge.

### Desktop <a href="#desktop" id="desktop"></a>

AutoLit and Synthesis are developed and tested on Chrome, FireFox, and Edge browsers. Any display or functional issues in these browsers can be [reported](https://nested-knowledge.nolt.io/) (we really appreciate it!). Other common browsers, such as Safari, while not officially supported, are expected to function.

Internet Explorer, which reached [the end of its lifecycle in Summer 2022](https://docs.microsoft.com/en-us/lifecycle/faq/internet-explorer-microsoft-edge), is not a supported browser, and Nested Knowledge may have display and functional problems on it. It is recommended to avoid IE.

### Mobile <a href="#mobile" id="mobile"></a>

#### Synthesis <a href="#synthesis" id="synthesis"></a>

All Synthesis pages are designed and tested for responsiveness on mobile web browsers.

#### AutoLit <a href="#autolit" id="autolit"></a>

We recommend accessing AutoLit from desktop devices with at least 800px screen width.

A version of mobile AutoLit was supported from mid-2021 to late-2023. It was deprecated due to poor adoption, limited functionality, and reduction of development pace on the core desktop application.


---

# 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.nested-knowledge.com/resources/support/supported-platforms.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.