> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/ai-workbench-qore/core-concepts/human-in-the-loop.md).
# Human-in-the-Loop
The points where a person stays in the decision.
An agent that acts on its own is the point. An agent that acts on its own *where it shouldn't* is the risk. In a bank, the difference is usually not whether the agent is capable — it's whether a person is standing in the right place when it commits to something.
Qore's controls fall into two families, and it's worth being precise about which is which:
* **Automated controls** — [Guardrails & Validation](/ai-workbench-qore/core-concepts/guardrails-and-validation.md) such as Sensitive Data Masking and model policy, and [Evals](/ai-workbench-qore/core-concepts/evals.md) scoring live traffic. A machine checks the agent.
* **Human controls** — the subject of this page. A person checks the agent.
## Where a person can stand
### Before the agent commits: Autonomy
[Agent Behavior](/ai-workbench-qore/console/agent-builder/build/agent-behavior.md#autonomy) is a slider — `Low`, `Med`, `High`, defaulting to `Med`. It sets how independently the agent acts without checking back.
* **High** — the agent commits to multi-step plans on its own.
* **Low** — the agent confirms more steps before proceeding.
This is a dial rather than a switch.
### Before a skill runs: Tool Execution Approval
[Tool execution](/ai-workbench-qore/console/agent-builder/deploy/guardrails/tool-execution.md) pauses the agent before it runs selected skills and asks the user whether the call should proceed. **Allow** runs the skill and continues the run. **Deny** blocks the call, and the agent continues without it. Choose the skills one by one, or turn on **Enable for all skills** to cover every current and future skill.
### When an agent needs an answer: questions and Gates
In an Operator conversation, an agent that needs a decision stops and asks. The question appears as a card above the composer. Pick a numbered answer, write your own, attach a file when the agent asks for one, or select **Skip**.
A conversation that ends on a question waits until you answer. It is listed on [Gates](/ai-workbench-qore/console/console-operator/gates.md), in the top bar of Console and of Control Center. Only your requests appear there, and only you can answer them.
### Before a governance change runs: staged actions
The [Governance Operator](/ai-workbench-qore/control-center/governance-operator.md) in Control Center doesn't act on its own. It stages each proposed change, and nothing runs until you approve it. The Console Operator, by contrast, dispatches work as soon as you ask.
### When an evaluator is unsure: Human Review
An evaluator scores each live execution with a rating and a confidence. When the confidence is below the evaluator's threshold and routing to human review is turned on, the result becomes a task in [Human Review](/ai-workbench-qore/control-center/evals/human-review.md), where a reviewer records a verdict. See [Evals](/ai-workbench-qore/core-concepts/evals.md).
### Before the agent learns: learning-case approval
The agent can improve from its own production history — but nothing enters its memory without a person approving it.
{% hint style="warning" %}
**Auto-approval is intentionally disabled,** so a malicious or mistaken input cannot quietly change the agent's behavior.
{% endhint %}
See [Memory & Learning](/ai-workbench-qore/core-concepts/memory-and-learning.md) and [Reinforcement Learnings](/ai-workbench-qore/console/agent-builder/monitor/reinforcement-learnings.md).
### Before code exists: plan review
In [App Builder](/ai-workbench-qore/console/app-builder/plan.md), **Plan Mode** presents a proposed architecture — features, logic, extra ideas — and waits. You click **Start building** to commit, or **Revise plan** to iterate. Nothing is generated until you agree. See [Plan](/ai-workbench-qore/console/app-builder/plan.md).
## Seeing enough to intervene
A person can only stay in the loop if they can see what the agent did:
* **The execution trace** — in the builder, the full record of how the agent read your instructions, which skills it chose, and how long each took. For builders, not end users.
* **The Operator transcript** — each step the Operator took, each question it asked with the answer beneath it, and a card for each agent it handed work to. **Open full run** shows every step that agent took. See [Console Operator](/ai-workbench-qore/console/console-operator.md).
* [Monitor](/ai-workbench-qore/console/agent-builder/monitor.md) **and** [Online-Eval](/ai-workbench-qore/console/agent-builder/monitor/online-eval.md) — what the agent actually did in production, scored.
## The human controls at a glance
| Control | Where it is set | What the person does |
| ----------------------- | ------------------------------------------------------ | --------------------------------------------- |
| Autonomy | Agent Config → Agent Behaviour | Sets how many steps the agent confirms |
| Tool Execution Approval | Agent Config → Guardrails | Allows or denies each selected skill call |
| Questions and Gates | Operator conversations; **Gates** in the top bar | Answers, attaches a file, or skips |
| Staged actions | Governance Operator, in Control Center | Approves a proposed change before it runs |
| Human Review | Control Center → Evals | Records a verdict on a low-confidence score |
| Learning-case approval | Agent Config → Reinforcement Learning → Learning Cases | Approves a correction before it enters memory |
| Plan review | App Builder, Plan Mode | Starts building or revises the plan |
## Where this is configured
* [Agent Behavior](/ai-workbench-qore/console/agent-builder/build/agent-behavior.md) — Autonomy
* [Tool execution](/ai-workbench-qore/console/agent-builder/deploy/guardrails/tool-execution.md) — approval before skills run
* [Gates](/ai-workbench-qore/console/console-operator/gates.md) — conversations waiting for your answer
* [Governance Operator](/ai-workbench-qore/control-center/governance-operator.md) — staged actions
* [Human Review](/ai-workbench-qore/control-center/evals/human-review.md) — reviewing low-confidence scores
* [Reinforcement Learnings](/ai-workbench-qore/console/agent-builder/monitor/reinforcement-learnings.md) — learning-case approval
* [Plan](/ai-workbench-qore/console/app-builder/plan.md) — Plan Mode review, in the App Builder
* [Guardrails & Validation](/ai-workbench-qore/core-concepts/guardrails-and-validation.md) — the automated counterpart
***
{% columns %}
{% column width="83.33333333333334%" %}
Maintained by Abhishek Paul
AI-assisted, human-approved
{% endcolumn %}
{% column width="16.666666666666664%" %}
{% endcolumn %}
{% endcolumns %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.uptiq.ai/ai-workbench-qore/core-concepts/human-in-the-loop.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
