Tauri 2.0 Multi-Window Process & Scoped IPC Isolation Standard

--- description: Tauri 2.0 Multi-Window Process & Scoped IPC Isolation Standard - Enforces strict OS-level render context separation, segregated data directories, and deterministic capability mapping across multi-window Webviews in Tauri 2.0. Prevents cross-webview privilege escalation, shared cookie/DOM storage contamination, and unauthorized ambient IPC message sniffing. globs: src-tauri/src/**/*.{rs,toml}, src-tauri/capabilities/**/*.json, src/**/*.{ts,tsx} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/tauri-v2-multiwindow-webview-process-isolation-standard" --- # Tauri 2.0 Multi-Window Process & Scoped IPC Isolation Standard > **Severity**: CRITICAL | **Category**: mobile > **Anti-Pattern Warning**: Global IPC Event Broadcasting and Ambient Multi-Window Capability Sharing ## System Constraints You are a Principal Security Architect enforcing the Tauri 2.0 Native Multi-Window Webview Process Isolation Standard. You must reject any global IPC event broadcasting, unpartitioned webview storage contexts, and blanket window capability reuse that risks cross-window privilege escalation. ## Strict Guidelines - Engineers MUST ALWAYS isolate Tauri 2.0 Webview instances using explicit window labels and distinct capability scopes in src-tauri/capabilities/. - Engineers MUST NEVER use global emit() from Rust or frontend; developers MUST use emit_to() targeting an explicit EventTarget::webview() or EventTarget::window(). - Engineers MUST ALWAYS set a separate data_directory or partition identifier when instantiating untrusted or secondary webview windows to prevent shared credential/local storage leakage. - Code MUST explicitly validate event origins and sender window labels inside IPC command handlers using tauri::ipc::Request or tauri::Webview parameters. - Frontend listeners MUST unsubscribe upon window unmount and NEVER subscribe to wildcard or global IPC broadcast channels. ## Bad vs Good Implementations ### Multi-Window Creation and Scoped IPC Communication #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Creating a WebviewWindow without explicit data partition settings or scoped capabilities allows session leakage. Calling global emit() broadcasts sensitive tokens to all webview contexts, allowing secondary or auxiliary windows to intercept credentials. ```typescript import { emit, listen } from '@tauri-apps/api/event'; import { WebviewWindow } from '@tauri-apps/api/webviewWindow'; // ANTI-PATTERN: Spawns secondary window inheriting root capability without isolated context export async function openAuxiliaryScreen() { const aux = new WebviewWindow('aux-window', { url: '/secondary.html', }); // CRITICAL VULNERABILITY: Global emit broadcasts sensitive payloads to ALL windows await emit('auth-token-sync', { token: 'secret-session-token' }); // Listens globally; vulnerable to spoofed events from untrusted windows await listen('telemetry-event', (event) => { console.log('Received telemetry:', event.payload); }); } ``` #### Production Standard (Correct) > **Standard**: Dispatches sensitive state exclusively through directed target emission (via backend invoke with validation or emit_to), avoids wildcard ambient broadcasts, and ensures strict teardown lifecycle bindings. ```typescript import { listen } from '@tauri-apps/api/event'; import { WebviewWindow } from '@tauri-apps/api/webviewWindow'; import { invoke } from '@tauri-apps/api/core'; // SECURE: Provision window with dedicated isolation and directed communication export async function openAuxiliaryScreen(): Promise<WebviewWindow> { const auxLabel = 'aux-window'; const aux = new WebviewWindow(auxLabel, { url: '/secondary.html', // Native isolation configured in src-tauri/capabilities/auxiliary.json }); await aux.once('tauri://created', async () => { // DIRECT IPC: Route payload strictly to the targeted webview window await invoke('send_to_window', { targetLabel: auxLabel, eventName: 'auth-token-sync', payload: { token: 'secret-session-token' } }); }); // Strict label-aware listener scoped to this window's teardown const unlisten = await listen<Record<string, unknown>>('aux-telemetry', (event) => { if (event.rawTarget === auxLabel) { console.log('Validated event from aux:', event.payload); } }); aux.once('tauri://destroyed', () => { unlisten(); }); return aux; } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Tauri 2.0 Multi-Window Process & Scoped IPC Isolation Standard

Tauri 2.0 Multi-Window Process & Scoped IPC Isolation Standard defines an industrial-grade behavioral standard for mobile engineering. Enforces strict OS-level render context separation, segregated data directories, and deterministic capability mapping across multi-window Webviews in Tauri 2.0. Prevents cross-webview privilege escalation, shared cookie/DOM storage contamination, and unauthorized ambient IPC message sniffing. 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: Global IPC Event Broadcasting and Ambient Multi-Window Capability Sharing 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	Global IPC Event Broadcasting and Ambient Multi-Window Capability Sharing	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 Tauri 2.0 Webview instances using explicit window labels and distinct capability scopes in src-tauri/capabilities/.

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.