autoresearchclaw-gate-stages-hitl-mcp-pattern

AutoResearchClaw has 3 gate stages (5, 9, 20) that require human-in-the-loop approval before the pipeline continues. The MCP server exposes researchclaw_approve_gate and researchclaw_reject_gate tools so ORACLE Hermes can act as the programmatic HITL reviewer. Rejection requires a reason field that feeds back into the next stage. Never leave gate stages unattended — the pipeline blocks indefinitely until a gate decision is made.

Related

• researchclaw-gate-stages-need-dedicated-mcp-tools
• researchclaw-mcp-server-11-tools-interface-design
• oracle
• autoresearchclaw-mcp-server-integration-pattern
• async-mcp-pattern-for-long-running-pipelines
• researchclaw-three-gate-stages-require-hitl-approval-tools
• researchclaw-gate-stages-oracle-hermes-acts-as-hitl-proxy
• 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-hitl-approval