Built-in agent reference

TeXRA ships with built-in agents for theory work and the writing around it: deriving and checking results, formalizing proofs, searching the literature, and, in support, polishing prose, fixing errors, creating figures, and converting formats. Pick one from the agent dropdown in the TeXRA UI.

Agent

polish

Tool-use

assistant

prover

research

numerics

review

lean

presenter

latexFixer

latexDiff

setup

creator

Workflow

correct

polish

paper2slide

paper2poster

ocr

transcribe_audio

merge

The agent picker, split by the two agent classes, tool-use (left) and workflow (right), with the selected agent (polish) highlighted.

The same catalog is available from any terminal:

texra agents list

$texra agents list

workflowpolishRewrites and restructures text to improve clarity, flow, and readability.

workflowcorrectFixes typos, grammar, and LaTeX formatting without changing your style.

workflowmergeMerges partial edits back into the full original document.

toolUseassistantGeneral-purpose scientific assistant covering the full research workflow.

toolUseresearchResearch assistant for analytical derivations and numerical programming.

toolUseleanLean 4 proof assistant with VS Code integration and CLI fallback.

One category  name  description row per agent, tab-separated and stable for scripts; --category workflow filters, --all includes hidden agents.

Quick reference

Every built-in agent is one of two execution shapes, a tool-use loop or a workflow pipeline:

Tool-use11 agents

proverAttack open math problems — recon, experiments, proofsresearchAnalytical derivations & numerical programming with WolframreviewMathematical and manuscript verificationnumericsDesign, run, and validate computational experimentsleanLean 4 proof developmentpresenterInteractive presentation and poster builderlatexFixerDiagnose and fix LaTeX compile errors, warnings, bad boxeslatexDiffGenerate a visual latexdiff PDF between two versionscreatorDesign, write, and test new TeXRA agentssetupSetup wizard — diagnose, install, configurechatGeneral assistance & file editing (opt-in)

Workflow7 agents

correctFix errors without style changespolishImprove writing qualitypaper2slideConvert papers to beamer slidespaper2posterCreate academic postersocrExtract text from images / PDFstranscribe_audioTranscribe audio to textmergeIntelligently merge document versions

The two shapes behave differently once they run:

Tool-useloop

Instruction

readeditrun tool

repeat

Done

Converse and call tools in a loop until the task is finished.

Workflowpipeline

Input file Edit Diff

Run a fixed input → edit → diff pipeline; hand back a versioned diff.

Tool-use agents loop: they converse and call tools until done. Workflow agents run a fixed input → edit → diff pipeline and hand back a versioned diff.

Prompts may change

The prompts and specific behaviors of these built-in agents may change slightly between TeXRA versions. If you need precise, unchanging behavior or want to customize the process in depth, create a custom agent based on these examples.

For the structure and execution flow common to all agents, read the agent architecture guide.

Conversational agents

assistant

Opt-in

assistant is not included in any of the built-in teams. Enable it from the Agents tab to use it.

A general-purpose scientific assistant with the broadest toolset of any built-in agent. It can read your project, edit files, run shell commands, search the literature (arXiv, Crossref, web), manage Zotero references, run Wolfram computations, work on Lean 4 proofs, and delegate to specialist agents or external AI coding agents (Codex, Claude Code), all in a back-and-forth conversation.

User story: You just got reviewer comments back. Instead of hunting through a 40-page paper by hand, you open assistant and paste the reviewer's feedback: "Address comment 3 about missing error bars in Table 2: add them and update the caption." The agent reads your files, makes the edits, and shows you a diff to approve.

Best for: General research assistance, literature search, code/LaTeX editing, computations, running compilations

Example instruction:

Review my introduction in paper.tex and suggest improvements for clarity.
Then update the file with your changes.

Problem-solving agents

prover

A research mathematician for open and research-level problems: Erdős problems, conjectures posed at the end of papers, or questions from your own work. It checks the problem's current status in the literature first, computes small cases and hunts for counterexamples, lays out candidate lines of attack, and develops proofs lemma-by-lemma with adversarial self-verification. It reports honestly: SOLVED, DISPROVED, PARTIAL, or OPEN with the exact obstruction. Partial progress (special cases, reductions, improved bounds) is written up as such, never oversold.

Best for: Attacking open problems, counterexample searches, turning conjectures into verified partial results

Example instruction:

Attack the open problem stated in problem.tex. Check its current status on
erdosproblems.com and arXiv first, compute small cases, then either prove it,
disprove it, or report the strongest partial result you can rigorously verify.

Research & discovery agents

research

A hands-on research agent that can edit your files and verify mathematics computationally. Use it when you need to check a derivation or run a symbolic calculation alongside your writing.

Best for: Mathematical derivations, computational verification, multi-step research

Example instruction:

Derive the variational equations for the Lagrangian in equations.tex.
Verify each step computationally and update the file with results.

numerics

A numerical-experiments agent that designs, implements, and validates computational experiments following the scientific method. Use it when a claim needs to be backed by code and reproducible results rather than symbolic derivation alone.

Best for: Convergence studies, benchmarking, simulation-backed results, sanity-checking numerics

Example instruction:

Implement and run a convergence study for the solver in solver.py.
Sweep the step size, plot the error, and report the observed order of accuracy.

Verification agents

review

A scientific auditor that verifies your research manuscript. It checks mathematical correctness, derivation soundness, notation consistency, code-manuscript agreement, and goal achievement, using Wolfram for computational verification.

Best for: Pre-submission audits, mathematical verification, notation consistency checks

Example instruction:

Audit this manuscript: verify every derivation step-by-step, check notation
consistency across all sections, and confirm that every stated goal in the
abstract is actually delivered in the paper.

Formal methods agents

lean

Helps you write and debug Lean 4 proofs. It reads compiler diagnostics, inspects proof state, and iterates until the proof compiles.

Best for: Formalizing proofs, Lean 4 development, Mathlib projects

Example instruction:

Formalize the proof of the theorem in Proofs/GroupTheory.lean. Start with an
informal outline, then produce Lean code and iterate until it compiles.

Presentation & simplification agents

presenter

Creates LaTeX Beamer presentations from research papers. Point it at your paper and it reads through your work, extracts figures, bibliography entries, and TikZ diagrams, writes the deck from the bundled slide template, and refines individual slides with edit_file. For posters, use the paper2poster workflow agent instead.

Best for: Conference talks, seminar presentations, lightning talks

Example instruction:

Create a 15-slide Beamer presentation from this project. Cover motivation, the core
algorithm, key results, and future work. Use the metropolis theme and include TikZ
diagrams for the architecture.

Correction & polishing agents

correct

The correct agent fixes errors without changing the style or content of your document.

Purpose: Fix typos, grammatical errors, and LaTeX syntax issues.

Best for:

• Final proofreading before submission
• Fixing errors in collaborative documents
• Ensuring consistent formatting and notation

Example instruction:

Fix grammatical errors, typos, and LaTeX syntax issues throughout the document.
Ensure consistent notation for mathematical symbols and equations.
Don't change the technical content or writing style.

polish

The polish agent improves the writing quality of your document while preserving essential technical content and meaning.

User story: Your draft is technically solid but the writing is rough. Select polish, tell it "Improve clarity for a CVPR audience: keep all equations and citations intact," and in a couple of minutes you have a version that reads like it went through a professional copyedit. Review the colour-coded diff to accept or reject each change.

Use it for drafts that are technically sound but need language improvements before submission.

Example output

Run polish on the sample document to see a colour-coded diff showing exactly what changed. The agent produces versioned output files with latexdiff highlighting additions in blue and deletions in red.

View example

Content generation & transformation agents

paper2slide

The paper2slide agent converts research papers into LaTeX beamer presentations.

Purpose: Create presentation slides from academic content.

Best for:

• Preparing conference presentations
• Converting papers for teaching purposes
• Creating seminar materials

Example instruction:

Convert this paper into a beamer presentation with approximately 15-20 slides.
Include a title slide, outline, introduction, methodology, results, and conclusion.
Use bullet points for clarity and add slide titles. Include the key figures and tables.

paper2poster

The paper2poster agent converts papers into academic conference posters.

Purpose: Create well-structured academic posters.

Best for:

• Conference poster preparation
• Visual research summaries
• Academic showcases

Example instruction:

Convert this paper into an academic poster using the baposter template.
Include sections for Introduction, Methodology, Results, and Conclusions.
Highlight key figures and tables. Make it visually appealing with appropriate columns.

Creating figures

There is no longer a dedicated draw agent. To generate or improve TikZ figures, use a tool-use agent (research or presenter) and describe the figure. The agent writes compilable TikZ, compiles it, and visually verifies the result. Read Working with figures and TikZ figures.

LaTeX & build agents

latexFixer

Diagnoses and fixes LaTeX compilation errors, warnings, and bad boxes. Point it at a project that does not compile (or compiles with overfull boxes) and it reads the build log, locates the cause, and iterates until the document is clean.

Best for: Resolving build failures, clearing warnings, fixing overfull/underfull boxes

Example instruction:

This project fails to compile. Read the latexmk log, fix the underlying errors,
and rebuild until it produces a clean PDF.

latexDiff

Generates a visual diff PDF between two LaTeX versions using latexdiff, so you can see exactly what changed between drafts.

Best for: Reviewing changes between versions, preparing "changes marked" PDFs for co-authors or referees

Example instruction:

Produce a latexdiff PDF comparing the submitted version (v1/main.tex) with the
current revision (main.tex), highlighting additions and deletions.

Figure & media agents

ocr

The ocr agent converts handwritten mathematical content from images into LaTeX.

Purpose: Turn handwritten equations and notes into LaTeX code that matches your document's notation and style.

Best for:

• Converting handwritten derivations or lecture-board photos into LaTeX
• Digitizing handwritten mathematical notes across multiple images
• Keeping converted notation consistent with the existing document

Example instruction:

Convert the handwritten derivation in [notes.png] into LaTeX, matching the notation used in the attached document.

transcribe_audio

The transcribe_audio agent converts audio files (like lectures, podcasts, or personal notes) into text transcripts. It requires native audio support; read Working with figures.

Purpose: Create searchable text versions of spoken audio content.

Best for:

• Transcribing recorded lectures or talks
• Converting podcast episodes to text
• Transcribing personal voice memos or notes

Example instruction:

Transcribe the provided lecture audio file [lecture.mp3]. Provide the output as plain text, identifying different speakers if possible (e.g., Lecturer, Questioner 1).

Merge agent

merge

Takes an AI-edited document and merges the improvements back into your original, keeping the best of both. It understands context, so it does not overwrite your careful phrasing with generic rewrites.

Best for: Applying AI-suggested edits from output files, incorporating reviewer suggestions, combining different drafts

Example instruction:

Merge changes from the edited file into the original document. Prioritize substantive
improvements in clarity while maintaining the original's technical precision.
Preserve mathematical notation and citations from the original.

Read Intelligent merge for details on the merge workflow.

Software engineering agents

These agents make up the Software Engineer team for the code that accompanies a project: simulations, numerics, data pipelines, scripts, and small libraries. The Computer Scientist team also includes coder and testEngineer for implementing and pinning down experiment code.

engineer

The team lead. Turns a coding goal into focused tasks, delegates each to the right specialist, reviews their work, and keeps the codebase coherent.

Best for: Multi-step coding goals you want planned, delegated, and verified end to end

Example instruction:

Speed up scripts/simulate.py without changing its results. Profile it first,
then optimize the hot loops, and make sure the regression tests still pass.

coder

Implements features, makes focused edits, and fixes bugs, then verifies the change builds and passes the project's checks.

Best for: Implementation, focused edits, bug fixes

codeReviewer

Reviews a diff or file for correctness, clarity, security, and convention fit, and reports prioritized findings. It is read-only and does not edit.

Best for: Pre-merge review, auditing generated code

changeReviewer

Reviews the working tree's diff against the main branch, verifies each suspicion with repository tools and language-server diagnostics, and reports confirmed findings to the Agent Review (Find Issues) panel in Source Control. It is read-only, does not edit, and has no bash tool by design.

Best for: Reviewing uncommitted changes before you commit

testEngineer

Writes and maintains tests: pins down existing behaviour, covers new code and edge cases, and keeps the suite fast and reliable.

Best for: Adding coverage, characterization tests, keeping suites healthy

codeSimplifier

Refactors working code for clarity, reuse, and efficiency without changing its behaviour, then confirms the tests still pass. It works on quality only and does not hunt for bugs.

Best for: Behaviour-preserving cleanup of research code

Setup & meta agents

setup

A setup wizard that diagnoses your environment, installs missing dependencies, configures TeXRA, and orchestrates your first task. If you are new to TeXRA or moving to a new machine, start with this agent.

Best for: First-time setup, diagnosing missing dependencies, getting unblocked

Example instruction:

Check whether my environment has everything TeXRA needs, install anything missing,
and help me run my first agent on this project.

creator

Designs, writes, and tests new TeXRA agents through conversation. Describe the behavior you want and creator drafts the agent YAML, then helps you refine and validate it.

Best for: Building custom agents without hand-writing YAML from scratch

Example instruction:

Help me build a custom agent that rewrites abstracts to a 150-word limit while
preserving every numerical result. Draft the YAML and walk me through testing it.

Remote agents

The following agents are available as remote agents. Sign in to TeXRA to access them.

search

Finds papers and web content for you. Give it a topic and it comes back with relevant preprints, published articles, and web resources. It is read-only and does not change your files.

Best for: Literature reviews, finding citations, fact-checking

Example instruction:

Find recent papers on transformer architectures for scientific document understanding.
Focus on papers from 2023-2024 that address mathematical equation handling.

simplifier

Removes complexity from your code and writing: duplicated logic across files, over-abstract wrappers, or LLM-generated filler prose. simplifier cleans them up while preserving correctness.

Best for: Refactoring research code, tightening manuscript prose, cleaning up verbose AI-generated text

Example instruction:

Simplify the numerical solver in solver.py. Look for duplicated code, inline any
single-use helper functions, and remove dead code. Run existing tests after each change.

orchestrator

Coordinates multi-agent work on LaTeX research projects. It reads project context, turns broad goals into focused tasks, routes each task to the right specialist, tracks results, reviews generated files, and keeps follow-up work organized. The lead agent for the Physicist, Mathematician, and Computer Scientist teams.

Best for: Multi-step research goals that span several specialists

progressCheck

An end-of-session reviewer. It looks at what was just done and, when the session changed files or depends on wider project context, the project's standing goal and git/PR state. For self-contained read-only work, it stays with the request and the named agent reports. It is read-only: it advises, but does not edit or delegate. Bundled with every team except Software Engineer.

Best for: Auditing what a team run actually delivered versus the goal

TIP

Additional remote agents may be available depending on your access level. In the VS Code extension, run TeXRA: Show Agents from the Command Palette for the full list. Read Remote agents to sign in and sync them.

Built-in teams

Teams are predefined collections of agents for a discipline. Pick one from the Teams tab in the Dashboard, or run one from the CLI with texra multi-agent run <team>:

Team	For	Lead agent
Lean Project	Lean 4 projects: theorem search, tactic simplification, and blueprints	leanOrchestrator
Physicist	Physics papers: derivations, numerical experiments, literature search, slides, and review	orchestrator
Mathematician	Math research: attacking open problems, proofs, Lean 4 formalization, and LaTeX correction	orchestrator
Computer Scientist	CS papers: algorithm design, code-driven experiments and ablations, tests, and review	orchestrator
Software Engineer	A project's code: implementation, review, debugging, and testing across specialists	engineer

Every team except Software Engineer bundles the progressCheck audit helper and latexFixer. The Software Engineer lead and its specialists run locally; some specialists in other teams are remote agents that sync after you sign in. Every lead can also run its specialists in parallel as a multi-agent workflow.

Next steps

• Agent architecture: how agents work internally
• Research tools: literature discovery and web tools
• Custom agents: create your own agents
• Models: AI model selection