autoresearchclaw-async-pipeline-pattern-run-id

AutoResearchClaw’s 23-stage pipeline is long-running and must be invoked asynchronously. The researchclaw_run MCP tool returns immediately with a run_id; status is polled via researchclaw_status. All artifact retrieval, gate approvals, and stage outputs are keyed off this run_id. This async pattern is mandatory — synchronous invocation will timeout.

Related

• autoresearchclaw-mcp-server-11-tools-interface-design
• autoresearchclaw-mcp-server-integration-pattern
• researchclaw-mcp-long-running-tool-pattern
• researchclaw-gate-stages-need-dedicated-mcp-tools
• oracle
• researchclaw-async-run-id-polling-pattern-for-long-pipelines