What a Human Input Popup (HIP) is and when it appears

A Human Input Popup (HIP) is HIIE's single human-in-the-loop primitive. Any time a human must do work an agent cannot do on its own — adding keys or context, approving an action, or intervening in a decision — a HIP is raised so you stay in control.

When a HIP appears

HIPs surface during a Camelia run whenever the work reaches a point that needs your input rather than just more model thinking. Camelia raises an approval HIP by streaming a directive into the chat; the client strips that directive from the displayed text and opens the popup for you. The user-facing answer remains Camelia's prose only — actions, gates, and directives are pulled out of what you read.

The kinds of moments that trigger one

There are three HIP actions in HIIE: approving a document deletion, approving an external integration write action, and approving a capacity top-up when a request would exceed your monthly limit. Each is a discrete moment where Camelia pauses and hands the decision to you.

Why it exists

The HIP keeps Camelia's autonomy bounded by human judgment. She can read your project data, write documents, run flows, and call read-only integrations directly, but deletions, external writes, and cost-bearing requests are routed through a HIP first. This makes her behavior transparent: you see what she intends to do and decide whether it happens.

HIPs are queued and shown one at a time, so even a busy run never buries you in stacked dialogs — you handle each decision in order.