Roles & confirmations

Roles

• Pick the JWT claim that holds the role (for example role or realm_access.roles) and a default role for users without one.
• New projects start with claim role, default role member, and admin allowed every operation (*).
• For each role, choose the operations it may call.

Operations a role can’t use never appear in search, and calling one is rejected, on every surface: AI apps, the CLI and the widget.

Confirmations

Operations marked needs confirmation first return a confirm_token. The call runs only when the client calls again with the same arguments plus that single-use token, after the user agrees.

// 1st call_write_operation
{ "operation_id": "deleteTask", "arguments": { "id": "42" } }
// → needs confirmation, with a confirm_token; the AI asks the user

// 2nd call_write_operation, only if the user agreed
{ "operation_id": "deleteTask", "arguments": { "id": "42" }, "confirm_token": "<token>" }