Build and read the result

Compilation runs on the server and returns the PDF plus the full log, without leaving the editor.

How to do it

1. Compile from the keyboard, the status bar, or the PDF pane's build button.
2. Errors and warnings are grouped in the Problems tab; filter them by severity and use Go to source to reach the line.
3. Open the Output tab for the raw latexmk log when a message needs more context than the grouped view gives.
4. Ask the assistant to explain or fix a specific problem — or all of them — straight from the Problems list.

⌃S or ⌃↵ compiles the project.

Choose the engine and root file

Compile settings belong to the project, so everyone working on it builds the same way.

How to do it

1. Open Project settings and set the root .tex file — the one that holds \documentclass and is passed to the compiler.
2. Pick the engine: pdflatex, latex, xelatex or lualatex. Fonts loaded with fontspec need XeLaTeX or LuaLaTeX.
3. Choose the TeX Live release; keeping an older one is the safest way to reproduce an old build.
4. Set the compile mode: Normal for the real document, Fast (draft) for a quicker structural check.

Tune your own build loop

Alongside the project's settings, each person has compile preferences that apply only to their browser.

How to do it

1. Turn on Auto compile to rebuild after you stop typing, or leave it off and build deliberately.
2. Turn on Stop on first error when a long log makes the real cause hard to find.
3. Jump from the cursor to the matching spot in the PDF, and click anywhere in the PDF to jump back to its source line.
4. Download the compiled PDF from the project menu or open it in its own browser tab for printing.

⌃J jumps from the source to the PDF.