Tauri 2.0 Dynamic Webview Origin-Scoped IPC Capability Partitioning

--- description: Tauri 2.0 Dynamic Webview Origin-Scoped IPC Capability Partitioning - Enforces strict origin-scoped permission capabilities and label-based isolation across dynamic secondary webviews in Tauri 2.0 mobile and desktop applications. Prevents auxiliary frames and untrusted webview instances from inheriting root IPC command privileges, mitigating lateral privilege escalation via compromised dynamic contexts. globs: src-tauri/capabilities/**/*.json, src-tauri/tauri.conf.json, src-tauri/src/**/*.rs, src/**/*.{ts,tsx} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/tauri2-multi-webview-sandbox-partitioning" --- # Tauri 2.0 Dynamic Webview Origin-Scoped IPC Capability Partitioning > **Severity**: CRITICAL | **Category**: mobile > **Anti-Pattern Warning**: Assigning global wildcard capabilities or inheriting root IPC privileges in secondary webview instances ## System Constraints You are a Principal Security Architect enforcing strict IPC sandbox partitioning for Tauri 2.0 multi-webview architectures. You must ensure auxiliary and dynamic webviews operate under zero-trust capability profiles. Disallow wildcard window targets in capability manifests and verify all dynamic webviews enforce unique labels mapped to restricted permission boundaries. ## Strict Guidelines - Engineers MUST ALWAYS isolate dynamic secondary webviews to dedicated capability manifests in `src-tauri/capabilities/` using explicit webview labels rather than wildcard `*` selectors. - Engineers MUST NOT grant core shell, filesystem, or sensitive plugin invoke permissions to webviews loading external, dynamic, or federated third-party origins. - Dynamic webview constructors MUST assign an immutable, cryptographically unpredictable or explicitly scoped label prefixed with a recognized partition identifier (e.g., `sandbox-aux-*`). - Rust IPC command handlers SHOULD validate the invoking webview label and origin using `tauri::ipc::Request` or `tauri::Webview` context when executing state-modifying operations. - Security manifests NEVER permit `core:default` or high-privilege capabilities across windows that render untrusted remote resources. ## Bad vs Good Implementations ### Tauri 2.0 Webview Creation and Capability Scoping #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Creating a webview with a generic identifier where the underlying capability manifest targets `"windows": ["*"]` allows untrusted external URLs to access all registered Tauri commands and plugins, facilitating full sandbox escape. ```typescript import { WebviewWindow } from '@tauri-apps/api/webviewWindow'; // Flaw: Spawns secondary auxiliary window with arbitrary label that inherits // ambient privileges defined by permissive wildcard capability files. export async function openAuxiliaryPortal(untrustedTargetUrl: string) { const auxView = new WebviewWindow('portal-frame', { url: untrustedTargetUrl, // Inherits wildcard permissions from default capability set }); await auxView.once('tauri://error', (err) => { console.error('Failed to initialize aux webview', err); }); } ``` #### Production Standard (Correct) > **Standard**: The webview label conforms to a scoped partition schema (`isolated-aux-*`) backed by an explicit capability configuration file that explicitly denies default core permissions and binds only zero-privilege or read-only plugins. ```typescript import { WebviewWindow } from '@tauri-apps/api/webviewWindow'; // Fixed: Assigns an explicitly partitioned sandbox label with matching // minimal-permission capability JSON and disables ambient root IPC injection. export async function openAuxiliaryPortal(untrustedTargetUrl: string) { const secureLabel = `isolated-aux-${crypto.randomUUID()}`; const auxView = new WebviewWindow(secureLabel, { url: untrustedTargetUrl, incognito: true, // Restrict standard window manipulation APIs focus: true, }); // IPC capability matching 'isolated-aux-*' in src-tauri/capabilities/auxiliary.json // explicitly restricts permissions to empty sets or dedicated read-only plugins. await auxView.once('tauri://error', (err) => { console.error(`Failed to initialize secure webview ${secureLabel}`, err); }); } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Tauri 2.0 Dynamic Webview Origin-Scoped IPC Capability Partitioning

Tauri 2.0 Dynamic Webview Origin-Scoped IPC Capability Partitioning defines an industrial-grade behavioral standard for mobile engineering. Enforces strict origin-scoped permission capabilities and label-based isolation across dynamic secondary webviews in Tauri 2.0 mobile and desktop applications. Prevents auxiliary frames and untrusted webview instances from inheriting root IPC command privileges, mitigating lateral privilege escalation via compromised dynamic contexts. 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: Assigning global wildcard capabilities or inheriting root IPC privileges in secondary webview instances 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	Assigning global wildcard capabilities or inheriting root IPC privileges in secondary webview instances	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 dynamic secondary webviews to dedicated capability manifests in `src-tauri/capabilities/` using explicit webview labels rather than wildcard `*` selectors.

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.