Security confirmations

Certain operations that Enkaidu can perform carry risk — modifying files, running shell commands, or other actions you may want to review before they execute. When Enkaidu is about to perform such an operation, it pauses and presents a security confirmation dialog.

What you see

The dialog shows:

• A banner that indicates if the security cordon (sandbox) is enforced or not
• A description of what the operation will do
• A list of the specific subjects (files, commands, targets) it will affect
• Two buttons: Allow and Deny

The dialog blocks the agent. Enkaidu waits for your response before proceeding.

How it works

• Allow — the operation proceeds. The agent continues with its task.
• Deny — the operation is skipped. The agent is notified of the denial and will adapt (typically by explaining what it was going to do, or trying a different approach).

The confirmation appears inline in the conversation flow. After you respond, the transcript continues with whatever the agent produces next.

When do you see these?

Security confirmations are triggered by your configuration. You decide which tools or operations require approval, so you can tune the level of oversight to match your compliance requirements.

The specific triggers are configured in your enkaidu.yaml, via

• the cordon configuration, and
• the shell command tool settings.

Multiple confirmations in one run

If a single task requires multiple approvals (e.g., editing three different files), you’ll see the confirmations sequentially — the agent pauses, you approve, it continues, pauses again for the next approval, and so on. You always know exactly what’s about to happen.