parallel-deep-research
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseDeep Research
深度研究
Research topic: $ARGUMENTS
研究主题:$ARGUMENTS
When to use (vs parallel-web-search)
适用场景(对比parallel-web-search)
ONLY use this skill when the user explicitly requests deep/exhaustive research. Deep research is 10-100x slower and more expensive than parallel-web-search. For normal "research X" requests, quick lookups, or fact-checking, use parallel-web-search instead.
仅当用户明确要求深度/详尽研究时,才可使用该技能。深度研究的速度比parallel-web-search慢10-100倍,成本也更高。对于普通的“研究X”请求、快速查询或事实核查,请改用parallel-web-search。
Step 1: Start the research
步骤1:启动研究
bash
parallel-cli research run "$ARGUMENTS" --processor pro-fast --no-wait --jsonThis returns instantly. Do NOT omit — without it the command blocks for minutes and will time out.
--no-waitProcessor options (choose based on user request):
| Processor | Expected latency | Use when |
|---|---|---|
| 30s – 5 min | Default — good balance of depth and speed |
| 1 – 10 min | Deeper analysis, more sources (~2x cost) |
| 5 – 25 min | Maximum depth, only when explicitly requested (~3x cost) |
Parse the JSON output to extract the and monitoring URL. Immediately tell the user:
run_id- Deep research has been kicked off
- The expected latency for the processor tier chosen (from the table above)
- The monitoring URL where they can track progress
Tell them they can background the polling step to continue working while it runs.
bash
parallel-cli research run "$ARGUMENTS" --processor pro-fast --no-wait --json此命令会立即返回结果。请勿省略参数——如果省略,命令会阻塞数分钟并超时。
--no-wait处理器选项(根据用户请求选择):
| 处理器 | 预期延迟 | 使用场景 |
|---|---|---|
| 30秒 – 5分钟 | 默认选项——在深度和速度之间取得良好平衡 |
| 1 – 10分钟 | 更深入的分析,更多来源(约2倍成本) |
| 5 – 25分钟 | 最大深度,仅在用户明确要求时使用(约3倍成本) |
解析JSON输出以提取和监控URL。立即告知用户:
run_id- 深度研究已启动
- 所选处理器层级的预期延迟(参考上表)
- 可跟踪进度的监控URL
告知用户可以将轮询步骤置于后台,在研究运行期间继续其他工作。
Step 2: Poll for results
步骤2:轮询结果
Choose a descriptive filename based on the topic (e.g., , ). Use lowercase with hyphens, no spaces.
ai-chip-market-2026react-vs-vue-comparisonbash
parallel-cli research poll "$RUN_ID" -o "$FILENAME" --timeout 540Important:
- Use (9 minutes) to stay within tool execution limits
--timeout 540 - Do NOT pass — the full output is large and will flood context. The
--jsonflag writes results to files instead.-o - The flag generates two output files:
-o- — metadata and basis
$FILENAME.json - — formatted markdown report
$FILENAME.md
根据研究主题选择一个描述性文件名(例如、)。使用小写字母和连字符,不要有空格。
ai-chip-market-2026react-vs-vue-comparisonbash
parallel-cli research poll "$RUN_ID" -o "$FILENAME" --timeout 540注意事项:
- 使用(9分钟)以确保在工具执行限制内完成
--timeout 540 - 请勿添加参数——完整输出内容过大,会占用大量上下文。
--json参数会将结果写入文件。-o - 参数会生成两个输出文件:
-o- ——元数据和研究依据
$FILENAME.json - ——格式化的Markdown报告
$FILENAME.md
If the poll times out
若轮询超时
Higher processor tiers can take longer than 9 minutes. If the poll exits without completing:
- Tell the user the research is still running server-side
- Re-run the same command to continue waiting
parallel-cli research poll
更高层级的处理器可能需要超过9分钟的时间。如果轮询未完成就退出:
- 告知用户研究仍在服务器端运行
- 重新运行相同的命令以继续等待
parallel-cli research poll
Response format
回复格式
After step 1: Share the monitoring URL (for tracking progress only — it is not the final report).
After step 2: Tell the user the two generated file paths:
- — formatted markdown report
$FILENAME.md - — metadata and basis
$FILENAME.json
Do NOT re-share the monitoring URL after completion — the results are in the files, not at that link.
Ask the user if they would like to read through the files now. Do NOT read the file contents into context unless the user asks.
步骤1完成后: 分享监控URL(仅用于跟踪进度——并非最终报告)。
步骤2完成后: 告知用户生成的两个文件路径:
- ——格式化的Markdown报告
$FILENAME.md - ——元数据和研究依据
$FILENAME.json
完成后请勿再次分享监控URL——结果已在文件中,而非该链接。
询问用户是否需要立即查看文件内容。除非用户要求,否则不要将文件内容读入上下文。
Setup
安装配置
If is not found, install and authenticate:
parallel-clibash
curl -fsSL https://parallel.ai/install.sh | bash
parallel-cli loginOr set an API key:
export PARALLEL_API_KEY="your-key"如果未找到,请安装并认证:
parallel-clibash
curl -fsSL https://parallel.ai/install.sh | bash
parallel-cli login或者设置API密钥:
export PARALLEL_API_KEY="your-key"