Orchestrate academic research and writing workflows
Researchers use Claude Code as an orchestrator for research workflows and as their main tool for writing papers and theses in LaTeX or Markdown.
What they did
The thread describes people using Claude Code less as a software engineer and more as an orchestrator for research work. One researcher mapped agent roles like PI, operations, interns, grad students, programmer, and QA/fact-checker; another said they built a similar lab scaffold on Dust with defined roles, while a commenter used Claude Code directly in VS Code to write a master's thesis in LaTeX or Markdown instead of Google Docs.
How it went
People in the thread report it works well for structuring research collaboration and speeds up writing, but they also say current tools fight the workflow: model availability changed on Dust, Claude’s context compaction hurt long-form reasoning, other platforms had weak document management, and manual data input remained a problem.
Worth knowing
The main catch is setup and iteration: commenters say most effort is in defining roles, folders, and subagents, then repeatedly testing edge cases until inputs and outputs match the workflow.
Labels
One researcher mapped agent roles like PI, operations, interns, grad students, programmer, and QA/fact-checker
as their main tool for writing papers and theses in LaTeX or Markdown
Researchers use Claude Code as an orchestrator for research workflows and as their main tool for writing papers and theses in LaTeX or Markdown.
another said they built a similar lab scaffold on Dust with defined roles
a commenter used Claude Code directly in VS Code to write a master's thesis in LaTeX or Markdown instead of Google Docs
The “Material” label failed its quality check and is not used for selection.
Details
- Agents
- Claude Code
- Source
- Source date
- Jan 1, 2025
- Accounts
- 1
- In registry since
- Oct 15, 2026