> For the complete documentation index, see [llms.txt](https://docs.openreview.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openreview.net/v1/reference/openreview-tex.md).

# OpenReview TeX

OpenReview renders TeX and LaTeX notation with the open source library [MathJax](https://docs.mathjax.org/en/latest/index.html). It is available in forum comments and reviews, paper abstracts, and venue homepages. Use `$...$` for inline math and `$$...$$` for displayed math.

* [OpenReview TeX support](/v1/reference/openreview-tex/openreview-tex-support.md) describes what MathJax supports, what it restricts, and how TeX interacts with Markdown and with the surrounding HTML.
* [Common Issues with LaTeX Code Display](/v1/reference/openreview-tex/common-issues-with-latex-code-display.md) covers what to check when your notation does not render the way you expect.

For an example of writing formulas in a submission or a review, see [How to add formulas or use mathematical notation](/v1/how-to-guides/submissions-comments-reviews-and-decisions/how-to-add-formulas-or-use-mathematical-notation.md).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openreview.net/v1/reference/openreview-tex.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 `build a script that syncs our docs to a CMS` 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.