How to Use Claude Deep Research for Cited, Multi-Source Reports

A June 2026 Reddit thread in r/ClaudeCode put it bluntly: "deep research in Claude Code is not the same as in the desktop/web app." The post drew hundreds of upvotes because most users assumed both features worked the same way. They do not, and picking the wrong one wastes time on the wrong kind of output.

Claude.ai Research is a chat-layer feature available on Max, Team, and Enterprise plans. When you toggle it on, Claude conducts multiple searches that build on each other, pulling from the public web and any connected Google Workspace accounts (Gmail, Google Calendar, Google Docs). The output is a conversational answer with inline citations. It runs in the same interface where you already talk to Claude, so there is no setup beyond flipping the toggle.

Claude Code's /deep-research is a bundled workflow, not a chat feature. When you type /deep-research <question>, Claude Code writes a JavaScript orchestration script, spawns parallel subagents that each search independently, cross-checks their findings against each other, and votes on each claim. Claims that do not survive the cross-check get filtered out of the final report. The output is a structured, cited document that lands in your terminal session.

The distinction matters because each tool optimizes for a different failure mode. Claude.ai Research optimizes for breadth and speed across your personal data. Claude Code's /deep-research optimizes for accuracy through adversarial verification. Choosing between them depends on whether you need quick answers backed by your own documents or a thoroughly vetted report you plan to share with a team.

Claude.ai Research is available on the web interface, the desktop app, and the mobile app. Here is the setup and usage flow:

1. Open claude.ai or the Claude desktop app
2. Click the "+" button at the lower left of the chat interface
3. Select "Research" from the menu
4. A blue indicator appears at the bottom of the window confirming Research is active
5. Type your question and send it

Claude then operates agenically. It decides what to search first, reviews the results, identifies gaps or follow-up angles, and runs additional searches that build on what it already found. You do not need to prompt it to keep searching. The system explores different facets of your question automatically and works through open questions methodically.

The output arrives as a thorough answer with inline citations you can click to verify. Research sessions count against your standard rate limits and may consume quota faster than typical conversations because Claude retrieves and processes multiple sources per query.

Connected data sources make this powerful for personal and team research. When you connect Google Workspace, Claude can search your Gmail inbox, Google Calendar events, and Google Docs alongside the public web. A product manager preparing for a quarterly review can ask Claude to research competitive positioning and have it cross-reference public market data with internal strategy documents and meeting notes from the past quarter, all in one query.

Availability: Research is currently available on Max, Team, and Enterprise plans. It requires web search to be enabled in your account settings. If Claude does not activate Research automatically on a query that warrants it, you can prompt it explicitly with "Claude, please use the research tool."

The /deep-research command in Claude Code takes a fundamentally different approach. Instead of one agent running sequential searches, it orchestrates multiple independent agents working in parallel.

Here is how a typical run unfolds:

1. Open Claude Code in your terminal, VS Code, or the desktop app
2. Type /deep-research followed by your question
3. Claude Code asks you to approve the workflow
4. The system writes an orchestration script and spawns parallel subagents
5. Each subagent searches the web from a different angle independently
6. Agents cross-check their findings against each other
7. The system votes on each claim, keeping only those that survive verification
8. A cited report with filtered claims lands in your session

The key difference from Claude.ai Research is the adversarial verification step. Because each subagent searches independently, they surface different sources. When multiple independent agents find the same claim from different sources, that claim gets high confidence. When only one agent finds a claim and others contradict it, the claim gets flagged or filtered out entirely.

You can monitor the run in real time by typing /workflows and selecting the active run. The progress view shows each phase with agent counts, token usage, and elapsed time. You can drill into any phase to see what individual agents found, pause the run, or stop specific agents.

/deep-research requires the WebSearch tool to be available and works on all paid plans (Pro, Max, Team, Enterprise). On Pro plans, you may need to enable Dynamic Workflows in /config first. The workflow runs in the background, so your terminal session stays responsive while agents work.

/deep-research What changed in the Node.js permission model between v20 and v22?

The run takes several minutes depending on the complexity of your question. For best results, frame specific, bounded questions rather than vague prompts. "What are the tradeoffs between SQLite WAL mode and rollback journal for write-heavy workloads under 100 concurrent connections?" will produce better output than "Tell me about SQLite."

Keep your research findings where your whole team can find them

Upload Claude research reports to a Fast.io workspace and they are auto-indexed for semantic search and RAG chat, with an MCP endpoint ready for your agents. Starts with a 14-day free trial.

Start 14-Day Trial

Picking the right tool saves you from re-running research that came back in the wrong format or at the wrong depth. Here is a practical framework:

Use Claude.ai Research when:

• You need answers that pull from your personal data (Gmail, Google Docs, Google Calendar)
• The question is exploratory and you want to iterate conversationally
• Speed matters more than adversarial verification
• You are on mobile or want to start research from the web interface
• The output is for your own decision-making, not a shared deliverable

Use Claude Code /deep-research when:

• Accuracy is critical and the output will be shared or published
• You want claims cross-checked across multiple independent sources
• The question is complex enough to benefit from parallel investigation
• You need a structured report rather than a conversational answer
• You are already working in Claude Code and want research inline with your development workflow

Use neither when:

• The question has a simple, factual answer (just ask Claude directly)
• You need real-time data like stock prices or live scores
• The topic requires access to paywalled or authenticated sources neither tool can reach

One pattern that works well for teams: use Claude.ai Research for initial exploration and hypothesis formation, then run /deep-research on the specific claims you plan to act on. The first pass identifies what matters. The second pass verifies it holds up under scrutiny.

Both research tools produce valuable output that disappears when the session ends. Claude.ai Research lives in your chat history. Claude Code /deep-research reports live in your terminal session. Neither format works well for team collaboration or long-term reference.

This is where a persistent workspace becomes useful. Research reports, source documents, and verified claims need a home where teammates (human or AI) can find them later.

Local file storage works for solo developers but breaks down when multiple people or agents need access to the same research. Cloud drives like Google Drive or Dropbox can store the files but do not index them for semantic search, so finding specific claims across dozens of research reports means manual searching.

Fast.io workspaces solve this by combining persistent storage with built-in intelligence. Upload a research report to a workspace and Intelligence Mode auto-indexes it for semantic search and RAG-powered chat. Your team can ask questions about the research in natural language and get answers with citations pointing back to the original report.

For teams running regular research workflows, the Fast.io MCP server lets Claude Code agents write research output directly to a shared workspace. An agent finishes a /deep-research run, uploads the report via MCP, and the workspace indexes it automatically. The next person who needs that research finds it through semantic search or chat rather than digging through Slack threads or shared drives.

Every org starts with a 14-day free trial, with workspaces, monthly credits, and storage scaled to each plan, so you can test this workflow before committing.

After running hundreds of research queries across both tools, a few patterns consistently produce better output.

Frame questions with constraints. "What are the security implications of WebAssembly in server-side runtimes, focusing on sandbox escape vectors documented in CVEs since 2024?" outperforms "Is WebAssembly secure?" The constraints give agents clear boundaries for their searches and reduce the chance of getting generic overview content.

Specify the output format you need. If you want a comparison table, say so. If you want a chronological timeline, say so. Both tools respond well to explicit format requests, and you waste fewer cycles reformatting the output afterward.

Check the citations. Both tools produce citations, but not all citations are equally strong. Blog posts citing other blog posts are weaker than primary sources like official documentation, peer-reviewed papers, or vendor announcements. Skim the cited URLs before treating the research as verified.

Layer your research. Run a broad query first to identify the key subtopics, then run focused queries on each subtopic. This produces deeper coverage than a single comprehensive query because each focused run can dedicate its full context window to one area.

Watch for recency gaps. Both tools search the public web, which means recent developments (last few days) may not be indexed yet. For time-sensitive research, supplement with direct checks of official sources and announcement channels.

For Claude Code, monitor token usage. The /workflows view shows token consumption per agent in real time. If a run is consuming more tokens than expected, you can pause or stop it without losing completed work. Start with a narrow question to gauge the cost before running a broad research sweep.