Module permission_interaction 

The shapes one permission interaction is made of - PermissionRequest (what the agent surfaces when the CLI asks for tool approval), the options it offers, and PermissionOutcome (what a person picks).

Not a view’s shapes, and the name says so: the request and its options are what the dispatcher reads to build the decision on submit, so the dock a view draws is a rendering of one set rather than a copy of it. Distinct from the wire-side decision types in crate::permissions, which talk to the SDK’s can_use_tool callback.

Re-exports

use serde::Deserialize; 🔒

use serde::Deserialize; 🔒

use serde::Serialize; 🔒

use serde::Serialize; 🔒

use crate::permissions::PermissionUpdate; 🔒

use crate::session_update::ToolCall; 🔒

Structs

PermissionDisplay

PermissionOption

PermissionRequest

Enums

PermissionAction

Typed wire-side response routing for a permission option. Each PermissionOption constructed by forge-agent carries an action; the dispatcher reads it to build the right PermissionDecision on submit.

PermissionOptionKind

Display style for a permission option - drives icon + color in the prompt widget.

PermissionOutcome