Tauri 2.0 Multi-Window Webview IPC Channel Origin-Binding Guardrail

--- description: Tauri 2.0 Multi-Window Webview IPC Channel Origin-Binding Guardrail - Enforces explicit webview context validation and capability partitioning in Tauri 2.0 multi-window applications. Restricts high-privilege IPC command execution strictly to authorized webview labels, preventing capability escalation from secondary popups, OAuth windows, or auxiliary webviews. globs: src/**/*.{ts,tsx}, src-tauri/src/**/*.rs, src-tauri/capabilities/**/*.json alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/tauri-v2-multiwindow-webview-ipc-origin-binding" --- # Tauri 2.0 Multi-Window Webview IPC Channel Origin-Binding Guardrail > **Severity**: CRITICAL | **Category**: mobile > **Anti-Pattern Warning**: Ambient IPC Execution Permitting Secondary Webviews to Invoke Privileged Core Commands ## System Constraints You are a Principal Security Architect enforcing Tauri 2.0 Multi-Window Webview IPC Channel Origin-Binding Guardrails. You mandate zero ambient authority in multi-webview architectures. You ensure that capability definitions in Tauri 2.0 ACLs explicitly restrict privileged commands to designated window labels and that all IPC invocation wrappers assert matching window origin contexts before dispatching commands across the bridge. ## Strict Guidelines - Engineers MUST ALWAYS isolate privileged commands to explicit window labels using Tauri 2.0 capability configuration files (e.g., `windows: ["main"]`). - Engineers MUST NOT configure wildcard windows (`windows: ["*"]`) or broad ambient permissions across multi-window webview topologies. - Rust command handlers MUST validate the calling webview label via `tauri::WebviewWindow` or `tauri::Webview` when executing sensitive operations. - Frontend IPC client layers MUST verify their `getCurrentWebviewWindow().label` against an authorized window manifest before calling `@tauri-apps/api/core::invoke`. - Secondary webviews (e.g., OAuth modals, external URL renderers, help dialogs) MUST have isolated, minimal-privilege capability files that explicitly deny core business logic commands. ## Bad vs Good Implementations ### Secure Window Origin Verification in Tauri IPC Client Wrapper #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: The client blindly dispatches high-privilege IPC invocations without asserting current webview identity, allowing compromised or auxiliary secondary webviews (e.g., popup dialogs or OAuth frames) to trigger destructive native operations. ```typescript import { invoke } from '@tauri-apps/api/core'; // ANTI-PATTERN: Ambient invoke allowing any window context (including popups) to execute critical commands export async function deleteUserAccount(userId: string): Promise<void> { return await invoke('delete_user_account', { userId }); } ``` #### Production Standard (Correct) > **Standard**: The wrapper asserts that the executing webview matches an explicit set of privileged window labels before crossing the native IPC boundary, preventing capability escalation from secondary windows. ```typescript import { invoke } from '@tauri-apps/api/core'; import { getCurrentWebviewWindow } from '@tauri-apps/api/webviewWindow'; const PRIVILEGED_WINDOW_LABELS = new Set(['main', 'secure-settings']); export async function deleteUserAccount(userId: string): Promise<void> { const currentWindow = getCurrentWebviewWindow(); if (!PRIVILEGED_WINDOW_LABELS.has(currentWindow.label)) { throw new Error( `SecurityException: Capability escalation blocked. Window '${currentWindow.label}' is unauthorized to invoke 'delete_user_account'.` ); } return await invoke('delete_user_account', { userId }); } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Tauri 2.0 Multi-Window Webview IPC Channel Origin-Binding Guardrail

Tauri 2.0 Multi-Window Webview IPC Channel Origin-Binding Guardrail defines an industrial-grade behavioral standard for mobile engineering. Enforces explicit webview context validation and capability partitioning in Tauri 2.0 multi-window applications. Restricts high-privilege IPC command execution strictly to authorized webview labels, preventing capability escalation from secondary popups, OAuth windows, or auxiliary webviews. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Ambient IPC Execution Permitting Secondary Webviews to Invoke Privileged Core Commands Without an explicit system instruction file, developers spend hours debugging silent failures.

Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure Mode	AI Symptom (The Anti-Pattern)	Severity	Production Impact & Remedy
AI Hallucination & Deprecation Drift	Ambient IPC Execution Permitting Secondary Webviews to Invoke Privileged Core Commands	Critical	Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production. Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture Inconsistency	AI assistants produce mixed paradigms across files, creating fragmented codebase conventions.	Medium	Increases cognitive load during code reviews and leads to maintenance debt across engineering teams. Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.

Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

Engineers MUST ALWAYS isolate privileged commands to explicit window labels using Tauri 2.0 capability configuration files (e.g., `windows

Engineers MUST ALWAYS isolate privileged commands to explicit window labels using Tauri 2.0 capability configuration files (e.g., `windows: ["main"]`).

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.