Get a research workspace
Research is turned on per workspace by Orchestra. Write to contact@orchestrahq.ai with your lab’s name and its Orchestra workspace (create one first at app.orchestrahq.ai if you have none). Once it is on, Settings has a Research section that lists what the workspace turns on, and Papers and Findings appear in the sidebar.Hosted or Local
A lab can work in a hosted workspace, on Orchestra Local, or both. What decides it is whether co-authors write papers together.
To write a paper together, use a hosted research workspace. On Orchestra
Local, the Paper tab says that papers stay on that computer. Local suits work
that should never leave the lab’s machines: each person’s sessions,
experiments and drafts. A lab can do both: share findings through Local and
write its papers in the hosted workspace.
Your first steps as the lab’s lead
Setup asks only for the lab’s name. Inviting your lab and bringing in Overleaf are optional, and a research workspace has no GitHub, Linear or repository step. Getting started, at the bottom left of the app, lists what is left:- Start a paper. On Papers, a new lab names its first project (a paper lives in a project, and is as private as it), then starts the paper in it.
- Invite your lab (below).
- Bring in Overleaf (optional). A project on Overleaf comes in as a paper: keep it in sync with your own Overleaf Git token (Overleaf plans with Git), or import its source zip once (any plan). Each person connects their own Overleaf account.
Invite your lab
In Settings, People, enter each person’s email address and choose Invite. Each person signs up from the link in their email (If you were invited). For Local, see Local teams. To skip typing addresses, make an invite link under Invite link on the same page and post it in your lab’s chat. Whoever opens it signs in or creates an account and joins as a member, until the link expires or you turn it off. See Invite links.If you joined a lab
When you sign in for the first time, on the web or in the desktop app, Orchestra welcomes you to your lab’s workspace. There is nothing to configure: whoever runs it already set it up. The welcome shows:- Your lab’s papers and findings. Papers lists every paper you can see. A paper is as private as its project, so if one you expect is missing, ask a co-author to add you to its project, or ask for access from the paper’s link.
- Whether AI will work for you. Ask AI and the claims check run on Orchestra’s keys, or on the workspace’s own. The paper agent needs your own Anthropic key or the workspace’s. You can save your own Anthropic key right there to have it billed to you; where the workspace runs on its own keys and has none, that is a step.
- Your Overleaf papers (optional). Keep a project in sync with your own Overleaf Git token, or import its source zip. To cite from your Zotero library, connect it in Settings, Integrations.
orchestra enable, or the desktop app’s setup), they choose how much to
share, starting from the lab’s defaults:
- What they learn is shared with the lab: findings, decisions and failed experiments, each pointing to the session behind it. Their session transcripts stay on their computer until they share one.
- Share session transcripts with the lab as well.
- Share nothing from this repository.
Papers
Each project has a Paper tab, and Papers lists every paper you can see. Projects and teams covers writing, versions, roles (can edit, can review, can view), comments and suggestions, the References panel, Import from Overleaf, and compiling.- Bring your Overleaf papers in. On Papers, choose Import from Overleaf in the header. Keep one project in sync with your Overleaf Git token, or import zips: one project’s source zip, or every project at once from Overleaf’s project list (tick them, then choose Download). Each becomes a paper, in one project or in a new project of its own. Steps and the file types that come in: Import from Overleaf.
- On Orchestra Local, papers compile on your computer, inside a sandbox, with TeX Live 2025 that Orchestra installs: Compile papers on your computer says what macOS, Linux and Windows need.
- Your own Claude Code can read a paper, propose edits as suggestions and compile it: Edit your paper with Claude Code.
- Ask AI, the paper agent and the claims check run on your own Anthropic key or the workspace’s: Model keys.
- The claims check also finds passages by meaning, so a claim worded differently from the cited paper is still matched. To do that, the citing sentence and the cited paper’s passages are also sent to Orchestra’s embedding provider, as well as to the model on your key. If that is not acceptable for a paper, do not run the claims check on it.