Writing loop
Edit, compile, diagnose, preview
Keeps LaTeX source, project navigation, streamed compiler output, line-mapped problems, and bundled PDF.js preview in one focused workspace.
Local-first research workspace ← Software
TeXPilot
A professional LaTeX environment for researchers who want the complete writing loop—source, compilation, diagnostics, PDF review, references, collaboration, and optional AI assistance—without surrendering control of their manuscript workflow.
Research workspace loop
Stay in context from first draft to review
01
WriteProject-aware source editing, search, outline, and revisions
local 02
CompileFive supported LaTeX compiler paths with streamed logs
explicit 03
InspectLine-mapped diagnostics and bundled PDF preview
linked 04
ReviewEvidence-located findings, corrections, and revision comparison
assistive 2Product surfaces
5LaTeX compiler paths
13Review specialists
LocalDefault writing workflow
Research workflow
Tools that follow the manuscript—not the other way around
TeXPilot connects the everyday writing loop with deeper desktop research workflows while keeping feature and privacy boundaries explicit.
Toolchains
Compiler choice without lock-in
Works with latexmk, pdfLaTeX, XeLaTeX, LuaLaTeX, or Tectonic and preserves compiler and target selection as explicit workspace state.
Research library
BibVault on the desktop
Organizes references, source collections, attachments, validation provenance, notes, projects, exports, and integrity-checked SQLite backups.
Paper reading
Evidence stays with the paper
Pairs continuous PDF reading with highlights, page annotations, structured notes, and optional model-assisted summaries or questions.
Publication review
Specialists with source locations
Coordinates 13 review specialties across manuscript structure, methods, evidence, references, reproducibility, language, formatting, and visual integrity.
Collaboration
Revisions remain inspectable
Combines saved revision history, source- or PDF-linked comments, and Git clone, pull, commit, and push operations in the research workspace.
Product surfaces
A clear boundary between editor extension and research desktop
The shared writing experience stays consistent; desktop-only capabilities are named rather than implied.
Work where the source already lives
For researchers who want an integrated LaTeX loop inside VS Code-compatible editors.
- Source editor, project explorer, compile, logs, diagnostics, and PDF preview
- Workspace search, outline, revision history, comments, and Git operations
- Optional Ollama-powered writing assistance
Extend the loop into literature and review
For research workflows that need persistent libraries, paper evidence, and broader manuscript assessment.
- Everything in the core workspace plus BibVault and SQLite persistence
- Attached-paper reading, annotations, notes, and optional Paper AI
- Publication review, scholarly search, comparison, and report exports
End-to-end loop
Move from source to an inspectable revision
01
Author
Edit project files with search, structure, and revision context.
02
Build
Compile through a selected local toolchain and stream diagnostics.
03
Inspect
Review the rendered PDF, references, notes, and source locations.
04
Improve
Apply human-reviewed corrections and compare the next revision.
Engineering signals
What the implementation demonstrates
Desktop security, cross-surface product design, local model integration, durable research data, and evidence-aware AI orchestration.
One workflow, two product surfaces
The VS Code extension focuses on editing, compilation, preview, Git, and the general assistant. The Electron desktop adds BibVault, paper reading, and publication review without misrepresenting feature parity.
Privileged operations stay outside the renderer
The desktop uses context isolation, Chromium sandboxing, a restricted preload bridge, window-scoped IPC authorization, blocked navigation, denied permissions, and canonical project paths.
Local-first with an honest network boundary
Normal editing and compilation need no TeXPilot cloud account. Manuscript context leaves the machine only when a user configures a remote model or enables scholarly research services.
Model output remains assistive
Review synthesis preserves unavailable tools and blocked checks, single-specialist runs remain partial, and the product does not present its assessment as peer review or an acceptance guarantee.
Selected stack
Editor-native and desktop-native where each matters
VS Code APIElectronJavaScriptCodeMirror 6PDF.jsSQLiteLaTeX toolchainsSyncTeXGitOllamaOpenAI-compatible local APIsCrossref / OpenAlex
Build research tools that respect the researcher
Explore TeXPilot’s published extension, inspect the source, or reach out about research-product and developer-tooling roles.