status
Check the status of a running research task by its run ID.
- Queries research task status using the Parallel CLI with JSON output formatting
- Requires the Parallel CLI to be installed; directs users to
/parallel:setupif unavailable - Accepts a run ID as the sole argument to identify which task to monitor
Check Research Status
Run ID: $ARGUMENTS
parallel-cli research status "$ARGUMENTS" --json
If CLI not found, tell user to run /parallel:setup.
More from parallel-web/parallel-agent-skills
parallel-deep-research
ONLY use when user explicitly says 'deep research', 'exhaustive', 'comprehensive report', or 'thorough investigation'. Slower and more expensive than parallel-web-search. For normal research/lookup requests, use parallel-web-search instead. Supports multi-turn: pass --previous-interaction-id from a prior research or enrichment to continue with context.
1.7Kparallel-web-search
DEFAULT for all research and web queries. Use for any lookup, research, investigation, or question needing current info. Fast and cost-effective. Only use parallel-deep-research if user explicitly requests 'deep' or 'exhaustive' research.
1.4Kparallel-web-extract
URL content extraction. Use for fetching any URL - webpages, articles, PDFs, JavaScript-heavy sites. Token-efficient: runs in forked context. Prefer over built-in WebFetch.
1.2Kparallel-data-enrichment
Bulk data enrichment. Adds web-sourced fields (CEO names, funding, contact info) to lists of companies, people, or products. Use for enriching CSV files or inline data. Supports multi-turn: pass --previous-interaction-id from a prior research task to carry context forward.
1.2Ksetup
Set up the Parallel plugin (install CLI)
1.1Kresult
Get completed research task result by run ID
1.1K