> ## Documentation Index
> Fetch the complete documentation index at: https://developer.opus.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Human Decision Agent

> Pause your workflow for a person to make a routing decision when human judgment is needed.

The Human Decision Agent works just like the [Decision Agent](/tasks/agent/decision-agent), but instead of the system evaluating conditions automatically, a real person reviews the situation and decides which path to take. You set a deadline so the person has time to make their decision, then the workflow continues based on their choice.

## Key Capabilities

<CardGroup cols={2}>
  <Card title="Human Judgment" icon="hand">
    Pause your workflow for a real person to make critical decisions.
  </Card>

  <Card title="Deadline Setting" icon="clock">
    Give people a specific timeframe to complete their decision.
  </Card>

  <Card title="Two Modes" icon="list-check">
    Set up decisions using logical rules or natural language.
  </Card>

  <Card title="True/False Output" icon="toggle-on">
    Outputs True or False to send your workflow down different paths.
  </Card>
</CardGroup>

## When to Use It

Use Human Decision Agent when you need a person to make the routing decision instead of automated rules. Common examples:

* A compliance officer needs to approve before proceeding
* Someone needs to judge whether output meets quality standards
* A manager needs to decide how to handle an edge case

<Note>
  **Human Decision Agent vs Decision Agent:** The Decision Agent runs automatically and finishes in real-time. The Human Decision Agent pauses for a person to decide, so you set a deadline to give them time to respond.
</Note>

## Two Ways to Set Conditions

Each condition can be either a logical expression or natural language. You can add multiple conditions and combine them with AND or OR.

<Tabs>
  <Tab title="Logical Expression">
    Build your condition by selecting three things:

    | Field         | What It Does                           |
    | ------------- | -------------------------------------- |
    | **Source**    | The variable you want to check         |
    | **Operation** | How to compare it (see options below)  |
    | **Value**     | The reference value to compare against |

    **Available operations:**

    * Equals / Not Equals
    * Contains / Not Contains
    * Starts With / Ends With
    * Is Empty / Is Not Empty
    * Is Null / Is Not Null

    **Best for:**

    * Important decisions that need to be auditable
    * Precise conditions that must work the same way every time
  </Tab>

  <Tab title="Natural Language">
    Toggle on "Natural Language" and describe your condition in plain English.

    **Examples:**

    * "If the amount is greater than 10000"
    * "If the risk score indicates high risk"
    * "If the document contains sensitive keywords"

    **Best for:**

    * Quick prototyping
    * Simple conditions

    <Warning>
      For important decisions, use Logical Expression instead. Natural language can sometimes be interpreted differently than you expect.
    </Warning>
  </Tab>
</Tabs>

## Output

The Human Decision Agent produces these outputs:

| Output                   | What It Contains                                         |
| ------------------------ | -------------------------------------------------------- |
| **Final Decision**       | True or False—the combined result of all your conditions |
| **Condition 1, 2, etc.** | True or False for each individual condition              |

<Note>
  Make sure you connect both the True and False paths to something. If you leave one unconnected, your workflow might not work correctly.
</Note>

## How to Add a Human Decision Agent

<Steps>
  <Step title="Drop it into your workflow">
    Drag a Human Decision Agent into your workflow.
  </Step>

  <Step title="Choose your mode">
    Pick Logical Expression or Natural Language.
  </Step>

  <Step title="Write your condition">
    Set up what you want the person to evaluate—like "amount greater than 1000" or "status equals approved".
  </Step>

  <Step title="Set a deadline">
    Choose how many hours the person has to make their decision.
  </Step>

  <Step title="Connect both paths">
    Wire the True output to one path and the False output to another. Make sure both are connected.
  </Step>

  <Step title="Test it">
    Run a preview with test data to make sure both paths work as expected.
  </Step>
</Steps>

## Tips for Better Results

<AccordionGroup>
  <Accordion title="Use Logical Expression for important decisions">
    Logical Expression gives you:

    * Clear logic you can audit later
    * Consistent behavior every time
    * Easier troubleshooting when something goes wrong
  </Accordion>

  <Accordion title="Always connect both paths">
    If you leave the True or False path unconnected:

    * Your workflow might get stuck
    * You might get unexpected results
    * Even if one path doesn't need to do anything, connect it to something
  </Accordion>

  <Accordion title="Give people enough time">
    Be realistic about deadlines:

    * Remember people work in different time zones
    * Harder decisions need more time
    * Build in some buffer for busy days
  </Accordion>

  <Accordion title="Write clear instructions">
    People need to understand what they're deciding:

    * Explain what to look for
    * Give examples of when to choose True vs False
    * Include any thresholds or standards to apply
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Decision Agent" icon="code-branch" href="/tasks/agent/decision-agent">
    Have the system make decisions automatically instead of a person.
  </Card>

  <Card title="Human Review" icon="clipboard-check" href="/tasks/review/human-review">
    For simple approve/reject decisions—no routing needed.
  </Card>

  <Card title="Opus Human Task" icon="user-pen" href="/tasks/agent/opus-human-task">
    Collect information from a person instead of routing decisions.
  </Card>

  <Card title="Workflows" icon="diagram-project" href="/guides/workflows">
    Learn how all the pieces fit together.
  </Card>
</CardGroup>