Using AI as a Research Assistant: “What You Can Hand Off” and “What You Must Do Yourself”

What Happened

A tool recommended by @Faheem_uh claims to cut a systematic literature review from 4–6 months to 1 hour. The question that followed right away: “It can be done, but will it be a good review?”¹⁵

Meanwhile, the problems are concrete. An AI-assisted physics preprint turned up citations crediting people who don’t exist; even asking the AI to check the citations still produced errors³. In everyday wet-lab work, no LLM has yet proven genuinely helpful for literature searches, and checking the AI’s work takes about as long as doing it yourself⁴. At the journal-review stage, manuscripts that are recognizably AI-written get rejected—not for using AI, but for being badly written⁵.

Common Approaches

1. Use AI only to find and organize. @PhDtoProf tested 12 literature-review tools, and the results fell into two groups: tools that help you “find” and “organize” papers are safer, while those that help you “write” and “synthesize” are high-risk²²⁷. AI is an assistant, not the writer⁸.

2. Define the research question first, then search. Pin down the research question first, let AI handle the mechanical searching, and set a house rule: every citation must be checked against the original⁹.

3. Have AI read the files you provide. To use Cowork as a research assistant, the setup goes like this¹: use the desktop app so the AI can read the paper folder on your computer; keep permissions on manual so it asks before creating, editing, or deleting files, and never choose “Skip all approvals”; use a project tied to your research folder; schedule a weekly check for new papers; and connect PubMed or Zotero only if needed. Also turn off auto-reload so scheduled tasks don’t burn through your credits.

4. For systematic reviews, learn the traditional method first. For a first systematic review, it’s best not to rely on AI—AI for screening and extraction is still experimental, and Zotero or EndNote is enough for deduplication and reference management¹⁰. An ideal tool would also automatically log search terms, databases, and inclusion criteria so others can reproduce the work⁶.

5. Save important content to files. When long conversations get compacted or chat history disappears, the fix is the same: write decisions, rationale, and anything that must be kept verbatim into project files as you go, rather than leaving it only in the conversation¹⁷¹⁸.

Consensus

Open every citation yourself to confirm it exists and that the names and year are correct³⁹.
AI is good at summarizing literature, but lacks the tacit knowledge to spot anomalies and challenge basic assumptions¹⁴.
The research process must be reproducible: record which search terms, databases, and criteria were used⁶.

Disagreements

Is not using AI a form of negligence? One position holds that doing research and writing without the latest AI tools is increasingly close to negligence; rigor lies in thinking and verification, not in who does the typing¹³. The other holds that checking citations is itself part of understanding the literature, and skipping it means skipping the thinking⁴.
Can fully automated research be trusted? Plenty of systems claim to go all the way from literature to hypothesis to experiment automatically¹¹¹²¹⁹, but the papers they produce are scored by the same kind of AI review agent¹¹; under one Japanese write-up, this kind of fully automated pipeline was described as demoting researchers to lab technicians²⁸.
Can data be uploaded? Putting sensitive medical data into AI tools carries security risks²⁰; whether papers uploaded to NotebookLM could be made public also remains an open question⁷.
Can AI find real answers? After an AI-assisted literature search, an Erdős problem turned out to have been solved long ago¹⁶. This use—“finding forgotten old literature”—is also less controversial.

What to Do

Write down your research question and inclusion criteria before you start using AI.
Give the AI only a folder dedicated to papers; don’t connect your whole computer.
Use the prompt below to build a literature table, and spot-check 3 papers for errors.
Look up every paper the AI recommends in a database yourself.
To track new literature, set up a weekly schedule that only produces a list—no automatic downloading or sending.
For unpublished or sensitive data, confirm how the tool stores data before uploading.

General-Purpose Prompt

Research assistant · 14 lines

You are my research assistant for [project name]. The topic is [research question].
Inclusion criteria: [year range, study types, languages].
Use only the files or folder I provide: [location].

1. List every paper in a table: author, year, research question, method, main findings, limitations. For every cell, note the page number in the original.
2. Group the papers by theme, point out where findings contradict each other, and suggest possible reasons.
3. List questions these papers have not yet answered.
4. Recommend [5] more papers to read, with full citations, DOIs, and where you found each one. If you can't confirm a paper exists, write "source not found."
5. Finally, list the search terms and databases you used so I can reproduce the search.

Rules:
- Never cite a page number, figure, or quotation you didn't read in the files.
- Don't write body paragraphs of the review for me unless I explicitly ask.
- Ask me before creating, editing, deleting, or moving any file, or sending anything to anyone.

Replace the [ ] parts with your own details

How Tools Differ

Can it read local files? For Claude Cowork to read folders on your computer, Claude Desktop for macOS or Windows must be open, and access is limited to folders you’ve linked; new tasks on Pro and Max now run in the cloud²². Most other tools require you to upload files or connect cloud storage.
Plans: Cowork is available only on paid plans (Pro, Max, Team, Enterprise)²¹; Grok Bot is included in X Subscription’s Premium, Super, and Ultra²³.
Tracking literature regularly: Cowork has scheduled tasks²²; Grok Bot’s Routines can run on a schedule, and every run consumes usage²⁴. The more schedules you set, the more you need to watch your allowance.
Memory and long-term projects: Grok Bot’s memory stores preferences, role context, and summaries²⁵—it is not a full reference library. Whichever tool you use, literature tables and decision logs should be saved as files¹⁷¹⁸.
Dedicated research tools: Some tools split the work between two models—one generates, the other checks source reliability²⁶. This kind of design reduces errors, but it doesn’t replace checking citations yourself.

References

@MushtaqBilalPhD: Full thread on setting up a research assistant with Cowork ↩
@PhDtoProf: 12 tools ranked by academic risk ↩
r/Physics: Fictitious names in an AI-assisted preprint’s citations ↩ a b
r/labrats: Checking AI takes as long as doing it yourself ↩ a b
r/AcademicPsychology: Reviewers rejecting AI-written manuscripts ↩
Research Rabbit tutorial (YouTube): Comments wishing the search process were logged automatically ↩ a b
Free literature-review tools (YouTube): Comments asking about hallucinations and upload privacy ↩
Grad Coach (YouTube): AI is an assistant, not the writer ↩
Achim I. Czerny (YouTube): Define the research question first; a house rule for checking citations ↩ a b
r/research: Learn traditional methods first for systematic reviews ↩
@HowToPrompt__: Fully automated research systems; comments note the scorer is also AI ↩ a b
@heynavtoor: Open-source academic research automation system ↩
@akoustov: Thesis 25—not using the latest AI tools is increasingly close to negligence ↩
@LocasaleLab: AI is good at summarizing but lacks tacit knowledge ↩
@Faheem_uh: Claims a systematic review in 1 hour; replies question the quality ↩
r/math: AI literature search finds an old solution to an Erdős problem ↩
r/ClaudeAI: Long conversations get compacted; comments suggest writing decisions to files ↩ a b
r/ClaudeCowork: History vanished after an update; comments suggest backing up to files ↩ a b
@L_go_mrk (Japanese): A skill that automates the full research workflow; replies question demoting researchers ↩
@drgto_orthop (Japanese): Changes in research workflows and security risks of medical data ↩
Claude Help: Get started with Cowork ↩
Claude Help: Use Cowork on web, desktop, and mobile ↩ a b
Grok Bot Help: Plans ↩
Grok Bot Help: Routines ↩
Grok Bot docs ↩
@MSFTMechanics: Researcher’s dual-model review mode ↩
@PhDtoProf grouping conclusion: Finding and organizing is safer; writing and synthesizing is high-risk ↩
@manosuke21368 reply (Japanese): Demoting researchers to lab technicians ↩