webui-permission-flow

The WebUI permission flow coordinates permission requests across the Claude Code CLI, a Go backend, and a React frontend using control_request, permission_request, and control_response message formats to manage the lifecycle end-to-end.

To handle cancel and deny paths in a WebSocket permission flow, the system maintains parity with the IM path and uses a pendingInputs cache to preserve tool input, ensuring robust state handling when users reject or cancel permission prompts.

Yes, enabling permission prompts in Claude Code CLI requires the --permission-prompt-tool stdio runtime flag to properly route the WebUI permission flow and maintain communication between the UI and CLI.

The permission lifecycle spans control_request, permission_request, and control_response stages, defining how the Go backend mediates UI-to-CLI communication and manages state for robust frontend-backend integration.

Tool input gets lost during a WebUI permission request when a pendingInputs cache is not maintained, so preserving tool input through the flow requires caching pending inputs to prevent data loss across the CLI and frontend.

Yes, you can use WebSocket communication to manage permission requests by defining UI-to-CLI messaging formats and enforcing required runtime flags to coordinate the flow between the Go backend and React frontend.