TIL: You can use the human-in-the-loop to approve costly actions before they run.

I was setting up a new multi-agent workflow in AutoGen yesterday and had a bit of a scare. I configured a `UserProxyAgent` with code execution enabled, and the `AssistantAgent` almost ran a `terraform apply` that would have spun up several expensive EC2 instances I didn't need. It was a good reminder of a powerful, sometimes overlooked, safety feature.

You can enforce a human approval step for any code execution, especially for commands with potential cost or security impact. It's done by setting `human_input_mode` to "ALWAYS" on your `UserProxyAgent`. This forces the agent to ask for confirmation before running *any* code block it receives.

Here's a quick snippet from my Terraform-focused setup:

```python
from autogen import UserProxyAgent, AssistantAgent

user_proxy = UserProxyAgent(
name="UserProxy",
human_input_mode="ALWAYS", # This is the key
code_execution_config={"work_dir": "terraform"},
is_termination_msg=lambda x: x.get("content", "").rstrip().endswith("TERMINATE")
)

terraform_assistant = AssistantAgent(
name="TerraformAssistant",
system_message="You are a Terraform expert. Provide code but do not run it unless the human approves.",
llm_config={"config_list": config_list},
)
```

With this, the workflow pauses and presents the proposed code in the console, waiting for a 'y' or 'n' input. For cost control, you can get more granular by implementing custom validation logic, but starting with "ALWAYS" is a great way to avoid surprises.

It's a simple setting, but it turns AutoGen from a potential runaway train into a collaborative tool. I now use it by default for any agent that might touch infrastructure or production data. It adds a minor delay but saves so much anxiety.

-- Amy