How does AutoGen UserProxyAgent `human_input_mode` change the loop?

Attempt it

Quick reference

TL;DR

NEVER runs fully autonomous, ALWAYS asks the human before every proxy reply, TERMINATE asks only when the loop is about to end so a human can extend it.

Memory aid

Sign in for the mnemonic that makes this stick. See Pro pricing.

Easy to grasp

Picture a self-driving car with a driver in the seat. NEVER mode keeps the human asleep the whole trip, the car drives itself end to end. ALWAYS mode is a nervous driving instructor who grabs the wheel before every single turn. TERMINATE is the sensible middle ground: the car drives itself, but if it is about to stop at what looks like a dead end, it taps the human on the shoulder and asks whether to try a different route. The default is TERMINATE because most teams want autonomy with a safety net, not zero oversight and not a babysitter at every step.

Key concepts

LLM Frameworks Agents

Detailed answer & concept explanation

~4 min read

Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.

Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example.

Sign in for 5 free unlocks/day or go Pro for unlimited. See Pro pricing.

Quick scan · 2–4 min

Everything important, quickly.

Name the three values and their cadences, explain why TERMINATE is the production default, separate `human_input_mode` from termination predicates and tool routing, call out the stdin-blocking gotcha for unattended jobs, and finish with the Slack-override pattern as the senior signal.

Real-world examples

Real products, models, and research that use this idea.

AutoGen documentation ships a code-executor example that pairs `human_input_mode=NEVER` with a Docker `code_execution_config` for fully autonomous Python execution.
Microsoft's AutoGen Studio demos use `human_input_mode=ALWAYS` so the playground UI captures every operator turn through a web prompt.
Production multi-agent pipelines (e.g. teams running AutoGen GroupChat for research assistants) typically run TERMINATE with a custom `get_human_input` override that posts to Slack instead of blocking on stdin.
Academic agent benchmarks like AgentBench use NEVER mode to score fully autonomous trajectories without human intervention contaminating the metric.

Interviewer follow-ups

What an interviewer would ask next. Try answering before peeking at the approach.

QHow would you keep TERMINATE-mode semantics but route the human prompt to Slack instead of stdin?

Sign in or go Pro to see the approach for this follow-up.

QAn agent in NEVER mode is silently looping forever, what config did the team forget?

Sign in or go Pro to see the approach for this follow-up.

QWhen would ALWAYS actually be the right production choice?

Sign in or go Pro to see the approach for this follow-up.

Don't say this

Red flags and common mistakes that signal junior thinking. Click to expand.

Most common mistake

Confusing `human_input_mode` with tool routing or termination conditions. It is purely about when the human is prompted, not about which tools run or what ends the chat.

Sign in or go Pro to see all red flags and common mistakes. See Pro pricing.

60-second cheat sheet

The night-before-the-interview bullets. Scan these on the way to the call.

Sign in for 5 unlocks/day or go Pro for unlimited revision sheets. See Pro pricing.

References

Primary sources. Skim if you want the original framing.