Tauri 2.0 Scoped IPC Capabilities & Multi-Webview Isolation Standard

--- description: Tauri 2.0 Scoped IPC Capabilities & Multi-Webview Isolation Standard - Enforces granular IPC capability scoping and strict multi-webview runtime isolation within Tauri 2.0 desktop applications. Guarantees that secondary, untrusted, or multi-tenant webviews cannot invoke native privileged commands or execute cross-origin privilege escalations via shared IPC channels. globs: src-tauri/capabilities/**/*.json, src-tauri/capabilities/**/*.toml, src-tauri/tauri.conf.json, src/**/*.{ts,tsx} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/tauri-v2-ipc-scoped-capability-webview-isolation-standard" --- # Tauri 2.0 Scoped IPC Capabilities & Multi-Webview Isolation Standard > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Wildcard Window Targeting and Unrestricted IPC Exposure Across Multi-Webview Boundaries ## System Constraints You are a Principal Security Architect enforcing the Tauri 2.0 IPC Scoped Capability & Webview Isolation Standard. Mandate that every IPC call, capability definition, and webview initialization adheres to strict capability scoping, principle of least privilege, and context isolation. Never permit wildcard window permissions or untyped IPC invoke calls. ## Strict Guidelines - Engineers MUST ALWAYS assign IPC capabilities to explicit, statically declared window and webview labels rather than wildcard selectors ('*'). - Engineers MUST NOT expose native filesystem, shell, or arbitrary network capabilities to secondary, external, or user-navigated webviews. - Code MUST strictly encapsulate @tauri-apps/api/core 'invoke' calls within domain-specific, typed client modules that validate input schemas with Zod or ArkType prior to IPC transmission. - Services MUST enable the Tauri 2.0 Isolation Pattern using a secure, origin-locked isolation key whenever webviews render dynamic or remote multi-tenant content. - Components NEVER directly bind window.__TAURI_INTERNALS__ or raw window.__TAURI__ globals inside render trees or pass them across iframe boundaries. ## Bad vs Good Implementations ### Tauri 2.0 Window Capability Scoping vs Wildcard Permissions #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Directly calling native plugins from ambiguous contexts without client-side schema verification and pairing with wildcard window capability permissions exposes critical filesystem controls to any rogue webview, compromised third-party script, or child iframe. ```typescript // src/lib/ipc/fs-client.ts import { invoke } from '@tauri-apps/api/core'; // ANTI-PATTERN: Direct, unvalidated invoke vulnerable to privilege escalation. // Often paired with capabilities allowing windows: ["*"] in capabilities/default.json. export async function writeUserData(filename: string, payload: unknown) { // Directly forwarding untyped payload via IPC without local schema validation return await invoke('plugin:fs|write_file', { path: filename, contents: payload }); } ``` #### Production Standard (Correct) > **Standard**: Restricts IPC access through schema-validated domain commands (paired with strict capability definitions targeting only 'main-window' in src-tauri/capabilities/main.json), preventing arbitrary file writes and cross-webview exploitation. ```typescript // src/lib/ipc/fs-client.ts import { invoke } from '@tauri-apps/api/core'; import { z } from 'zod'; const SafeWriteSchema = z.object({ filename: z.string().regex(/^[a-zA-Z0-9_-]+\.json$/), payload: z.record(z.unknown()) }); export type SafeWritePayload = z.infer<typeof SafeWriteSchema>; /** * Strictly scoped IPC client bound to 'main-window' capability scope. * Secondary webviews (e.g., 'preview-webview') are excluded in capability JSON. */ export async function writeUserData(input: SafeWritePayload): Promise<{ success: boolean }> { const validated = SafeWriteSchema.parse(input); return await invoke<{ success: boolean }>('write_user_document', { safeFilename: validated.filename, contents: JSON.stringify(validated.payload) }); } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Tauri 2.0 Scoped IPC Capabilities & Multi-Webview Isolation Standard

Tauri 2.0 Scoped IPC Capabilities & Multi-Webview Isolation Standard defines an industrial-grade behavioral standard for frontend engineering. Enforces granular IPC capability scoping and strict multi-webview runtime isolation within Tauri 2.0 desktop applications. Guarantees that secondary, untrusted, or multi-tenant webviews cannot invoke native privileged commands or execute cross-origin privilege escalations via shared IPC channels. 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: Wildcard Window Targeting and Unrestricted IPC Exposure Across Multi-Webview Boundaries 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	Wildcard Window Targeting and Unrestricted IPC Exposure Across Multi-Webview Boundaries	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 assign IPC capabilities to explicit, statically declared window and 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.