explainx.ai350K+ learn from us
TrendingAI News TodayPathwaysSkills
Pricing
explainx.ai

Upskill in AI — 16 free pathways, live workshops & bootcamps, and 50+ courses from practitioners. Plus the skills, tools, and MCP servers to practice on.

follow us

follow on google

Add explainx.ai as a preferred source

corporate training

support@explainx.ai

get started

Find your pathTake Free Evaluation

community

Join the community

learn

mind: share how you thinkpathways — start freeworkshopsbootcampscoursescompare Explainxcertificationsmock testsexplainx universitycorporate traininglearn skills & mcp

discover

skillsmcp serversexplainx mcpestacktoolsmdx readeragentsllmsdesignsdictionarypeopleagi trackerfelony benchranks

company

aboutvisionmissionteaminstructorsteach on explainxpartnershipscommunityhackathonscareers

content

daily AI newsstate of AI — live resultsblogreleasespromptsgeneratorsresource libraryfor LLMsexplainx.ai kids

solutions

all solutionsdeveloper upskillingmarketing upskillingproduct manager upskillingleadership upskilling

newsletter · weekly

Get AI news, tools, and insights in your inbox.

supportcontactprivacytermsdata rightshow we create contentsubmission guidelines

© 2026 AISOLO Technologies Pvt Ltd

explainx.ai

On this page

  • TL;DR
  • Why Google open-sourced another agent framework
  • Pipeline architecture
  • Installation and environment
  • CLI usage
  • Repository layout for contributors
  • Ethics, authorship, and review risk
  • How it fits the multi-agent research stack
  • Streamlit demo workflow
  • Model provider matrix
  • How this differs from generic "write my paper" prompts
  • Limits and what to test first
  • Agent roles in more detail
  • Templates and conference compliance
  • Autoraters and evaluation gap
  • Relationship to Google's other agent releases
  • Responsible use checklist
  • Future dataset release
  • Security and secrets handling
  • Star velocity and why researchers noticed
  • Integrating PaperOrchestra into a real lab calendar
  • Related reading
← Back to blog

explainx / blog

PaperOrchestra: Google Research's Multi-Agent LaTeX Paper Writing Framework

Google, Research, Multi-Agent, Open Source, LaTeX

Part of Google Gemini and DeepMind

google-research/paper-orchestra turns ideas and experiment logs into LaTeX papers with literature, plotting, and refinement agents. Install and limits.

Nov 16, 2026·8 min read·Yash Thakker
add explainx.ai
go deep
PaperOrchestra: Google Research's Multi-Agent LaTeX Paper Writing Framework

PaperOrchestra is Google Cloud AI Research's open-source multi-agent pipeline that turns experiment logs and bullet-point ideas into conference-formatted LaTeX — with automated literature review, section writing, refinement, and optional plotting. The google-research/paper-orchestra repo listed 1,034 GitHub stars when we fetched it on November 16, 2026, alongside an arXiv:2604.05018 citation in the README.

For ML engineers, it is a concrete reference architecture for decomposing "write the paper" into orchestrated agents — not a substitute for peer review, human authorship ethics, or replication culture.

Daily briefFrom Yash · 350K+ students taught

Catch up on AI

One AI story explained in plain English, plus one thing to try. Every day, free. Unsubscribe anytime.

TL;DR

table · 2 cols
ComponentRole
Outline agentStructure from raw notes
Literature agentSearch, prioritize, integrate citations
Section writersDraft body text per section
Refinement agentIterative polish
Plotting agentOptional code-generated figures
OutputLaTeX under templates/ (e.g., CVPR 2025)

Why Google open-sourced another agent framework

Research teams already use Claude for lattice work and GPT-6 Astra science blogging. The bottleneck shifted to manuscript assembly: related work, consistent notation, figure regeneration after ablations.

PaperOrchestra attacks that last mile with specialists instead of one monolithic prompt — the same pattern as Sakana multi-agent self-supervision but aimed at LaTeX delivery.

The README credits Yiwen Song, Yale Song, Tomas Pfister, and Jinsung Yoon at Google Cloud AI Research. The project site is yiwen-song.github.io/paper_orchestra/.

Pipeline architecture

A large cream ring routes three small green parcels outward — PaperOrchestra's specialized writer, literature, and refinement agentsA large cream ring routes three small green parcels outward — PaperOrchestra's specialized writer, literature, and refinement agents

PaperOrchestra advertises five coordinated stages:

  1. Outline generation from unconstrained pre-writing material.
  2. Literature review with search, prioritization, and integration into prose.
  3. Section writing aligned to the outline.
  4. Content refinement passes.
  5. Plotting (optional) from executable code.

A Streamlit demo lives under frontend/ for interactive runs — useful for lab demos, not production CI.

Compare to TradingAgents' multi-role finance simulators — both show role boundaries beat one chat thread, but PaperOrchestra targets static PDF artifacts.

Installation and environment

bash
conda create -n paper_orchestra python=3.11
conda activate paper_orchestra
pip install -r requirements.txt

Create .env with keys the README lists:

  • SEMANTIC_SCHOLAR_API_KEY
  • OPENAI_API_KEY and/or GEMINI_API_KEY or Vertex (VERTEX_AI_PROJECT, VERTEX_AI_LOCATION)
  • Optional SMTP fields if the demo emails finished PDFs to you

Dataset gap: README explicitly says evaluation data is not bundled — future release under datasets/. You supply --raw_materials_dir with your own logs.

CLI usage

Bash wrapper:

bash
./paper_writing_cli.sh

Direct Python:

bash
python paper_writing_cli.py \
  --raw_materials_dir /path/to/raw/ \
  --latex_template_dir /path/to/templates/cvpr2025/ \
  --output_dir /path/to/output/ \
  --use_plotting true

Key flags:

  • --writer_model_name — LLM for drafting and literature agents.
  • --reflection_model_name — LLM for critique passes.
  • --use_plotting — enable figure agent (default false).

Templates live under templates/; add a conference by creating a new subfolder with the .sty and skeleton TeX your venue requires.

Repository layout for contributors

table · 2 cols
PathPurpose
methods/Agent logic and orchestration
autoraters/Automated evaluation scripts
utils/PDF helpers, API utilities
templates/CVPR and other conference shells
frontend/Streamlit UI

autoraters/ signals Google intends measurable quality gates — align your internal adoption with Nvidia SkillEvaluator thinking for agent outputs.

Ethics, authorship, and review risk

Automated manuscripts raise venue policy and integrity questions:

  • Disclose LLM assistance per journal and conference rules.
  • Verify citations — retrieval agents can hallucinate papers or misquote abstracts.
  • Do not submit unreviewed LaTeX — treat output as draft zero, not camera-ready.

Our AI-generated code license debate applies doubly when generated text ships in Apache-licensed repos with human names on the byline.

PaperOrchestra is not OpenAI's Orchestra Bio drug agents — naming collision only.

How it fits the multi-agent research stack

table · 2 cols
LayerExample in ecosystem
ExperimentHy4, Qwen, internal baselines (frontier comparison)
BenchmarkVibePrevisBench gaming agents
Write-upPaperOrchestra
ReviewHuman peers + autoraters in repo

Teams building embodied AI criteria benchmarks may feed logs directly into --raw_materials_dir if they standardize markdown experiment diaries.

Streamlit demo workflow

The frontend/ README (linked from the main repo) describes a Streamlit interface for non-CLI users. Typical lab workflow:

  1. Drop markdown experiment notes into raw_materials_dir.
  2. Pick a LaTeX template matching your target venue folder.
  3. Watch agents stream section drafts (API costs accrue per reflection loop).
  4. Download compiled PDF and diff against human baseline.

Streamlit is ideal for PI review; CLI mode fits batch rewrites after ablation sweeps.

Model provider matrix

table · 2 cols
Provider env varAgent stages typically using it
GEMINI_API_KEY / VertexWriter + literature (Google-native retrieval tools)
OPENAI_API_KEYAlternative writer or reflection
SEMANTIC_SCHOLAR_API_KEYCitation search rate limits

You can assign cheaper models to reflection while reserving frontier models for related-work synthesis — but cheap reflection may miss factual errors in methods sections describing novel architectures like MMFlash speculative decoding.

How this differs from generic "write my paper" prompts

Single-shot ChatGPT paper requests collapse structure, citations, and figures into one context window. PaperOrchestra's separation means:

  • Literature agents can restart retrieval without wiping methods drafts.
  • Plotting agents can re-execute matplotlib (or similar) after hyperparameter changes.
  • Refinement agents target section-level tone instead of whole-document rewrites.

That mirrors production agent design in envisioning agentic robotics surveys — specialized roles with orchestration, not one omnibus prompt.

Limits and what to test first

  1. Run without plotting on a toy template to validate TeX compile on your machine.
  2. Swap writer and reflection models — cost and quality trade off sharply on long related-work sections.
  3. Check Semantic Scholar rate limits with your API key tier.
  4. Do not assume CVPR template equals acceptance — formatting ≠ science.

Agent roles in more detail

Three grippers place different green shapes into one shallow tray — outline, literature, and reflection agents handing off LaTeX sectionsThree grippers place different green shapes into one shallow tray — outline, literature, and reflection agents handing off LaTeX sections

Although the public README groups agents coarsely, the implementation under methods/ typically separates:

  • Retrieval planning — what keywords and venues to query (Semantic Scholar API key in .env).
  • Evidence ranking — which papers enter the related-work section versus appendices.
  • Notation normalization — keeping symbols consistent across sections (failure mode in single-thread LLM writes).
  • Reflection — a second model critiques drafts (--reflection_model_name).

Reflection agents mirror Claude team code review patterns: a different model family can catch hedging or missing limitations paragraphs.

Templates and conference compliance

templates/cvpr2025 ships as an example; you can clone the folder for NeurIPS, ICML, or internal tech reports. PaperOrchestra does not verify you uploaded the latest official style files — maintainers must refresh .sty drops themselves.

Before submission:

  1. Compile with your local TeXLive.
  2. Run venue PDF tests (page limit, anonymization).
  3. Manually inspect bibliography keys — agents love duplicate cites.

Autoraters and evaluation gap

The autoraters/ directory hints at automatic quality scoring, but without the withheld datasets/ folder you cannot reproduce Google Cloud AI Research numbers locally. Treat autoraters as optional dev tooling, not peer review.

When comparing to VibePrevisBench or gaming-agent papers, decide whether automated writing helps camera-ready prose or only internal tech reports — many labs ban the former.

Relationship to Google's other agent releases

PaperOrchestra complements Google Stitch Skills (coding agents) and Gemini Robotics coverage elsewhere on explainx.ai — same company, different surface. None of these repos replace Vertex governance policies on customer data.

Responsible use checklist

  1. Human authorship — list who verified claims and ran experiments.
  2. Citation spot checks — open every DOI the literature agent inserted.
  3. Figure provenance — plotting agents execute code; archive notebooks.
  4. Dual submission policy — automated variants still count as prior work if posted online.
  5. Export controls — unrelated to LaTeX, but relevant if your logs include restricted benchmark numbers from defense-linked evals.

Future dataset release

When Google ships the promised datasets/ drop, rerun PaperOrchestra on their benchmark and compare to your in-house logs — until then, star the repo for architecture reference, not leaderboard scores.

Security and secrets handling

The .env file holds provider keys and optional SMTP credentials for demo email delivery. Treat generated output_dir folders like any research artifact:

  • Scrub API keys from experiment logs before feeding raw_materials_dir.
  • Redact patient identifiers or customer names from traces if your lab works on applied AI such as Apple health AI studies.
  • Do not commit LaTeX outputs with embedded gen-AI watermarks to arXiv without venue policy review.

PaperOrchestra is not a confidential compute enclave — calls go to configured cloud APIs unless you wire local models yourself (not documented as first-class in the README).

Star velocity and why researchers noticed

The repo's +306 stars in a day spike tracks renewed interest in agentic science workflows after Edward Witten's Claude-assisted lattice note and OpenAI lattice science blogging. Teams want pipelines between experiment folder and arXiv source zip without hiring a dedicated technical writer for every ablation grid.

Expect forks that add internal citation styles (IEEE, company tech report templates) under templates/ — upstream encourages custom subfolders.

Integrating PaperOrchestra into a real lab calendar

A pragmatic rollout keeps humans in the loop at three gates: outline approval, related-work spot check, and figure recompilation after final ablations. Schedule the CLI overnight when API rate limits are looser, then let staff edit LaTeX manually the next morning.

Pair with internal git: store output_dir as an artifact, tag the commit hash of code used for results, and block auto-submission hooks from pushing to arXiv until a PI signs off — the same discipline you would apply to Sakana-style multi-agent training logs.

Repository structure and arXiv id match google-research/paper-orchestra README, November 16, 2026.

Related reading

  • OpenAI Orchestra Bio acquisition — different Orchestra
  • Sakana multi-agent self-supervision
  • Envisioning agentic robotics survey
  • Edward Witten Claude Opus lattice paper workflow
  • Google Stitch Skills for coding agents
  • AI-generated code and license debates
Spotted something out of date? Let us know.
Daily briefFrom Yash · 350K+ students taught

Catch up on AI

One AI story explained in plain English, plus one thing to try. Every day, free. Unsubscribe anytime.

  • ✓ Free
  • ✓ One email a day, no spam
  • ✓ Unsubscribe anytime
Yash Thakker

Written by

Yash Thakker

Yash is an AI expert with over 300K learners. Join his workshops →

View Yash Thakker in People in AI →

Related posts

Nov 4, 2026

DeepMind Pluralistic Agents: Code and Data for Scaling Public Input on AI Policy

A new google-deepmind repo, pluralistic_agents, accompanies a 2026 paper on using LLM persona agents to gather public input on AI policy. It ships Apache 2.0 code, about 0.9 GB of generated data and a 746-person human study that stays private.

Oct 21, 2026

Google Harness2: An Open-Source Framework That Rewrites the Agent Around a Frozen Model

Google Research released Harness2, an Apache-2.0 framework that recursively edits the prompts, tools, skills and scripts around an agent instead of retraining the model. Here is how it works, what the reported gains actually measure, and what to check before running it.

Nov 16, 2026

Echelon Optimizer: 10× Faster Muon Steps With a Lean Proof

On November 16, 2026 Evolving Machines released Echelon, an optimizer that approximates Muon polar updates with low-rank work. The post claims 10.5× faster optimizer steps on 70B-class layers, 14% shorter 1.3B training steps with matched validation loss, and large MoE savings on DeepSeek V4.1 Flash—with proofs checked in Lean.