Keep project papers in a knowledge base, run grounded literature research, and move accepted evidence into citations without switching between disconnected tools.
The product is strongest when it is presented as one evidence workflow. The manuscript, project knowledge base, research agent, and citation path should feel like connected surfaces rather than disconnected tools.
Keep the papers, reports, and chapters that matter to the manuscript inside the same project instead of scattering them across browser tabs and folders.
Start from the current draft or accepted sources, then expand into follow-up papers, counterarguments, and stronger evidence without leaving the project.
Turn strong sources into reusable bibliography entries and citation handoff instead of treating literature review as a separate admin workflow.
Visible Trust
The workflow distinguishes candidate papers from the sources you actually accept into the project.
Research results can be framed around relevance, evidence path, and fit instead of a generic ranked list.
The research flow is designed to keep source-backed evidence separate from AI-written synthesis.
Canonical Docs
Keep the website promise narrow and point to the docs for the exact current state of knowledge-base uploads, research-agent behavior, and citation handoff.
The researcher workflow is strongest when source memory, literature discovery, and citation handoff stay connected to the manuscript.
Keep project PDFs inside the same workspace so the assistant can work from a stable source set instead of one-off uploads.
Run literature discovery beyond uploaded files when the draft needs newer papers, broader coverage, or stronger supporting evidence.
Start from accepted evidence, then branch into follow-up work, related papers, and counterarguments instead of restarting from a blank query.
Turn accepted sources into bibliography-ready records and citation handoff without treating references as a separate cleanup step.
Bring accepted-source memory back into the manuscript so drafting, counterarguments, and support paragraphs stay tied to evidence.
Comments, snapshots, and project history help research teams review literature-backed changes without losing the manuscript trail.
Trust & Status
These notes point to the current public docs for the knowledge base, research agent, citation handoff, and the surrounding manuscript workflow.
Projects can keep uploaded PDF sources and extracted text in a dedicated knowledge-base workspace.
Canonical docsThe research workspace can search beyond uploaded files, expand from accepted sources, and inspect follow-up evidence.
Canonical docsAccepted research sources can move toward bibliography and citation workflows inside the manuscript project.
Canonical docsIn-editor AI requests can generate, rewrite, and proofread selected LaTeX content.
Canonical docsProjects expose version history, labeled milestones, and snapshot restore flows.
Canonical docsTeams can add, reply to, edit, and delete line-linked comments inside a project.
Canonical docsJoin the research community using LaTeX Cloud Studio for their most important work, from breakthrough findings to high-stakes submissions.
Academic pricing • Grant support • Institutional licenses available