Skip to main content
In a research workspace, Claude Code on your own machine can work on a paper the way a co-author does: read every file, propose changes, compile, read the errors and try again. It runs on your own Claude Code subscription or key. Orchestra gives it the paper and keeps the record. Nothing it writes goes into the paper directly. Each edit lands as a suggestion in the paper’s review mode, word by word, credited to Claude Code and to you, for someone who can edit the paper to accept or reject.

Set it up

  1. Install the Orchestra CLI and sign in to your research workspace, if you have not: see Install the CLI. If it is installed already, update it so it has the paper tools (see Updating).
  2. Register Orchestra with your agents:
    This adds Orchestra’s MCP server to Claude Code for every project (see Orchestra in your agents). In a research workspace the paper tools are on by default.
  3. Start Claude Code anywhere and ask it about your paper, by its title:
  4. Open the paper in Orchestra. The changes wait in Review, marked as Claude Code’s, with your request beside them. Accept or reject each one, or a whole turn at once.
If you set mcp.tools yourself, add papers to it to keep these tools (see Turn on more tools).

What Claude Code can do

Who can do what

The paper’s roles apply to Claude Code exactly as they apply to you:
  • Can edit and can review: Claude Code reads, compiles, proposes changes and checks claims.
  • Can view: Claude Code reads and compiles, and is told it cannot propose changes or check claims.
  • A paper you cannot see does not exist for Claude Code either.
Only someone who can edit the paper accepts a suggestion.

When the paper changed meanwhile

Claude Code proposes each change against the revision it read. If someone changed the same words since, the change is refused, and Claude Code reads the file again and proposes on the text as it is now. A whole-file change is refused whenever the file changed after Claude Code read it, so it never undoes someone else’s edit.

Where the work shows

Your Claude Code session is captured as usual. Each suggestion it makes is linked to that session, so:
  • the paper’s Sessions list shows the session, with who ran it, what it changed and how many of its suggestions were accepted or rejected;
  • Who wrote this names the session behind every passage it wrote that was accepted, and opens it.
Anyone who opens the session sees it only if they can see the session itself.