How approval prompts are queued and shown one at a time
HIIE handles approvals through Human Input Popups (HIPs), and a deliberate part of their design is that they are queued and shown one at a time. You never face a pile of stacked dialogs competing for your attention.
Why one at a time
A single Camelia run can reach several decision points — for example proposing a document deletion, then wanting to make an external integration write, then hitting a capacity limit. Rather than throwing all of these at you at once, HIIE queues them and presents each as its own clear gate. You resolve one, and the next appears.
What this means in practice
Every approval is a distinct, focused decision. Because the popups are presented sequentially, you always know exactly which action you're approving — which document is about to be deleted, which external write is about to run, or whether you're adding capacity. There's no ambiguity about which "yes" applies to what.
How they're raised
Camelia raises each approval by streaming a directive into the chat. The client strips that directive out of the displayed text and opens the corresponding true-gate popup, so your readable answer stays clean prose while the gates are handled separately and in order.
The benefit
This queuing model keeps even a busy, multi-step run manageable. Camelia can do a lot of work autonomously, but each moment that genuinely needs your judgment is isolated and surfaced deliberately — one decision, fully understood, before the next.