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

# Requests

> Your central queue for reviewing, responding to, and managing requests from agents that need human input.

## Introduction

Requests is your central queue for handling requests from agents that need human input. When an agent reaches a point where it requires your approval or needs you to answer a question, it sends a request to Requests. You can review, respond to, and manage all of these requests in one place.

## Key Concepts

**Request types:**

* **Approval** — The agent needs you to confirm or reject a decision before it can proceed.
* **Question** — The agent needs you to provide an answer or additional information.

**Statuses:**

* **Pending** — The request is waiting for your response. Your agent is paused until you act.
* **Answered** — You have responded and the agent has continued.

## Where to Find It

Requests is located in the left sidebar under your workspace. A badge on the icon shows the number of pending requests so you can see at a glance when agents need your attention.

## Viewing Requests

The inbox lists all requests with their title, description, the agent that sent them, the request type, and a timestamp. Use the filters at the top to narrow the view:

* **By status** — Show only Pending or Answered requests
* **By type** — Show only Approval or Question requests

Click on any request to open a detail panel on the right side of the screen, which shows the full context of the agent run that generated the request. The header of the detail panel displays the agent name as a link — click it to navigate directly to the specific Run that sent the request.

## Responding to Requests

To respond to a pending request:

<Steps>
  <Step title="Open the request" icon="inbox">
    Click on the request to open the detail panel.
  </Step>

  <Step title="Type your response" icon="keyboard">
    Type your response in the text field.
  </Step>

  <Step title="Submit your answer" icon="send">
    Submit your answer. The agent will resume with your input.
  </Step>
</Steps>

You can also mark a request as responded without providing a text reply if the agent no longer needs the input.

## Bulk Actions

When managing a large number of requests, use the bulk actions available at the top of the inbox:

* **Mark all as responded** — Clears all pending requests at once.
* **Delete all responded** — Removes answered requests from the list.
* **Delete all** — Clears the entire inbox.

## Real-Time Notifications

Requests updates in real time. When a new request arrives:

* A toast notification appears on screen.
* The sidebar badge counter increments.

You do not need to refresh the page to see new requests.

## API Webhook Status

For agent runs triggered via the API, Requests shows the webhook delivery status alongside the request details. This lets you verify whether external systems were notified when a request was created or resolved.

## Related

<CardGroup cols={2}>
  <Card title="Monitor the First Week" href="/user-guide/getting-started/monitor-first-week" icon="calendar-days">
    Using Requests as a daily health signal during the first week after an agent goes live
  </Card>

  <Card title="Designing Human-in-the-Loop Workflows" href="/user-guide/assignment-features/hitl-design" icon="workflow">
    When to add approval gates, escalation patterns, and how to manage exceptions at scale
  </Card>

  <Card title="Human-in-the-Loop" href="/user-guide/assignment-features/human-in-the-loop" icon="user-check">
    How to write AOP approval instructions and respond via Slack or Teams
  </Card>
</CardGroup>