> 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/openreview-tex-support.md).

# OpenReview TeX support

OpenReview renders TeX with [MathJax](https://docs.mathjax.org/en/latest/index.html), with some specific considerations, which are described below:

## Delimiters

Mark the text that should be rendered as TeX with one of these pairs:

|                | Delimiters |
| -------------- | ---------- |
| Inline math    | `$...$`    |
| Displayed math | `$$...$$`  |

Anything outside the delimiters is treated as ordinary text or Markdown. Displayed math is aligned to the left rather than centred. 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) for a full example.

## Math-mode macros only

The TeX input processor implements only the math-mode macros of TeX and LaTeX, not the text-mode macros. So, for example, MathJax does not implement `\emph` or `\begin{enumerate}...\end{enumerate}` or other text-mode macros or environments. You must use Markdown (if enabled) to handle such formatting tasks.

## Some environments are supported only in part

Some features in MathJax might be limited. For example, MathJax only implements a limited subset of the array environment’s preamble; i.e., only the l, r, c, and | characters alongside : for dashed lines — everything else is ignored.

## Some commands are restricted

MathJax runs with its `safe` extension enabled, because your notation is displayed to other people on a shared page. Constructs that set arbitrary links, styles, font sizes, or element classes and ids are filtered out or restricted. A command can therefore be stripped here even though MathJax implements it and it works in your own LaTeX build.

## TeX in a Markdown-enabled field

When adding TeX content to a Markdown enabled field, it is important that all backslashes (\\) are escaped (i.e. replaced with \\\\) to prevent Markdown from stripping the backslashes before the TeX notation is parsed. If Markdown is not enabled, this is not necessary.

The same formula therefore looks different depending on the field:

```
Markdown not enabled:  $\frac{a}{b}$
Markdown enabled:      $\\frac{a}{b}$
```

Underscores need the same treatment when they appear at the beginning or the end of a word.

## TeX inside an HTML document

Keep in mind that your mathematics is part of an HTML document, so you need to be aware of the special characters used by HTML as part of its markup. There cannot be HTML tags within the math delimiters as TeX-formatted math does not include HTML tags. Make sure to add spaces around any `<` or `>` symbols to ensure they are not treated as open tags.

It is best not to mix HTML tags with TeX at all. Text that begins with `<` is treated as an HTML block, and the whole field can lose its Markdown formatting as a result.


---

# 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/openreview-tex-support.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.