One project. Connected tools. A shorter path back to writing.
01 / Compiler
A build is more than a PDF.
Your local TeX toolchain does the typesetting. LatexDo connects its output to the preview, source
navigation, and errors you can act on.
From source to page
Local compilation
main.texLaTeX
1\documentclass{article}
2\begin{document}
3\sectoinsection{Introduction}
4A small idea, beautifully typeset.
5\end{document}
!
Unknown LaTeX command
main.tex · line 3
\sectoin
✓
Source corrected. Ready to rebuild.
Project source1 error locatedSource updated
TeX
latexmk
main.pdf100%
AN EXAMPLE MANUSCRIPT
A small idea.
Your next paper starts here.
1 Introduction
A small idea, beautifully typeset.
1
PDF
Waiting for a successful build
✓ Build complete
PDF preview
SyncTeX positions
Structured diagnostics
05 / 05
Build again. See the page.
Start with your source.
Your local TeX engine builds.
The log points to the problem.
You correct the source.
Build again. See the page.
An illustrative build: latexmk runs the local TeX engine; log analysis locates an error. After a
source edit, a successful rebuild returns a PDF and SyncTeX positions. LatexDo explains errors; the
compiler does not edit your source.
02 / AI harness
A model, with tools and a feedback loop.
The harness connects a language model to your workspace. Follow a request from allowed context to a
tool action—and back to the model.
Inside the AI harness
One illustrative request
YOUR WORKSPACE
Y
Fix the error in this paragraph.
.tex
Active document
main.tex · selected paragraph
✓
≡
Allowed context
Editor + project file access
✓
✳
AI harness
Context · controls · feedback
LocalOllamaCloud
PROJECT TOOLS
01
get_active_document
Read the source
✓
02
edit_selection
Apply an approved edit
✓
03
compile
Return build diagnostics
✓
Ask mode · approval before editing
Tool results return to the model
↳
Available tools follow your access settings.
Source read. The model can inspect the error.
Proposed change:
\sectoin
\section
Example edit accepted. Compile result:
success
.
“The command is corrected and the document compiles.”
05 / 05
The model can answer—or continue.
Your request brings the context.
The model asks to read.
An edit goes through approval.
Tools act and return evidence.
The model can answer—or continue.
The harness supplies allowed context, checks tool availability, and returns tool results to the model.
This example shows an accepted edit in Ask mode. Actual tool sequences vary; a final answer, error,
cancellation, or step limit ends the loop.
03 / Knowledge graph
See what connects your references.
BibTeX provides the papers. Your manuscript provides citation usage. A deterministic graph makes the
relationships visible.
A living map of references
Deterministic relationships
.bib
Your bibliography
Entries → relationships → context
5 entries. A library taking shape.Shared authors connect A–B and B–D.Similar titles connect A–C and B–D.Citation usage adds the manuscript’s context.
5Bibliography entries
3Explainable connections
2Cited in the manuscript
04 / 04
Your citations add context.
A library becomes a map.
Shared authors draw connections.
Title overlap reveals another link.
Your citations add context.
Five illustrative BibTeX entries. Lines represent shared authors or title words; filled nodes are
cited in the example manuscript. The application also supports venue and year relationships. Motion
illustrates the graph; metadata similarity does not establish scientific support.