Signpost AI Logo
WorkersTools

Hitl

📸 Screenshots

Here are visual examples of this section:

Hitl - Worker Configuration Interface Hitl - Worker Configuration Interface

1. Overview and Purpose

The HITL (Human In The Loop) worker enables human intervention points within automated agent workflows. When activated, it pauses the automated flow to allow human review, decision-making, or manual input before continuing execution. This worker is essential for workflows that require human oversight or approval at critical decision points.

2. Configuration Parameters

The Worker accepts the following parameters:

  • enable: Boolean input that triggers human intervention when set to true
  • causes: Array of strings describing the reasons or conditions that triggered the human intervention request

3. Input/Output Handles

  • enable: Input handle - accepts boolean value to activate human intervention
  • causes: Input handle - accepts array of strings describing intervention reasons
  • enabled: Output handle - returns boolean indicating whether HITL mode is currently active

4. Usage Examples with Code

// Enable HITL with specific causes
const hitlWorker = agent.createWorker('hitl');
hitlWorker.fields.enable.value = true;
hitlWorker.fields.causes.value = ['High confidence threshold exceeded', 'Critical decision point'];

// Check if HITL is currently enabled
const isHitlActive = hitlWorker.fields.enabled.value;

5. Integration Examples

The HITL worker integrates seamlessly into decision-making workflows where human oversight is required. It's commonly placed after analysis workers or before critical action workers to ensure human approval of automated decisions.

6. Best Practices

  • Use descriptive causes to help humans understand why intervention was requested
  • Place HITL workers at strategic decision points rather than every step
  • Ensure your application has proper UI handling for HITL activation states
  • Consider timeout mechanisms for HITL requests in production environments

7. Troubleshooting Tips

  • Verify that a valid uid is provided when enabling HITL, as it's required for operation
  • Check that the agent state properly reflects HITL activation status
  • Ensure your frontend can handle and display HITL intervention requests
  • Monitor HITL causes array to debug why interventions are being triggered