researchclaw-gate-stages-need-dedicated-mcp-tools
AutoResearchClaw has 3 hard gate stages (stages 5, 9, 20) that halt pipeline execution awaiting human-in-the-loop approval. To enable ORACLE Hermes to act as a programmatic HITL reviewer, the MCP server must expose dedicated researchclaw_approve_gate and researchclaw_reject_gate tools with run_id + stage + optional feedback. Without these, the pipeline blocks indefinitely. Long-running researchclaw_run returns a run_id immediately; status is polled via researchclaw_status — never blocking synchronously.
Related
- autoresearchclaw-mcp-server-11-tools-interface-design
- autoresearchclaw-integrated-as-mcp-server-not-cli-or-acp
- oracle
- oracle-researchclaw-mcp-server-over-cli-or-acp
- autoresearchclaw-integration-architecture-decisions
- autoresearchclaw-mcp-server-integration-pattern
- async-mcp-tool-pattern-for-long-running-pipelines
- researchclaw-mcp-server-11-tools-interface-design
- researchclaw-mcp-long-running-tool-pattern
- autoresearchclaw-async-pipeline-pattern-run-id
- autoresearchclaw-gate-stages-hitl-mcp-pattern
- researchclaw-three-gate-stages-require-hitl-approval-tools
- researchclaw-gate-stages-oracle-hermes-acts-as-hitl-proxy
- researchclaw-mcp-async-pattern-run-id-polling
- researchclaw-gate-stages-require-mcp-approval-tools
- gate-approval-tools-enable-oracle-hermes-as-programmatic-hit
- autoresearchclaw-gate-stages-require-hitl-approval-at-5-9-20
- autoresearchclaw-gate-stages-require-explicit-hitl-approval
- autoresearchclaw-23-stage-paper-pipeline-with-3-gate-stages
- researchclaw-gate-stages-enable-programmatic-hitl-via-mcp