AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
frontendcritical PriorityID: tauri2-webview-isolation-ipc-scoping-invariant

Tauri 2.0 Ephemeral Webview Isolation & Scoped IPC Guardrail

Enforces strict process, storage, and IPC boundary separation between primary execution contexts and auxiliary or ephemeral renderer windows in Tauri 2.0. Eliminates cross-webview side-channel exfiltration and memory contamination by requiring distinct window labels, explicit capability mapping, and segregated storage partitions.

Prohibited Anti-Pattern: Spawning Auxiliary Renderers with Default Host Capabilities and Shared Memory/Storage Contexts

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Tauri 2.0 Ephemeral Webview Isolation & Scoped IPC Guardrail - Enforces strict process, storage, and IPC boundary separation between primary execution contexts and auxiliary or ephemeral renderer windows in Tauri 2.0. Eliminates cross-webview side-channel exfiltration and memory contamination by requiring distinct window labels, explicit capability mapping, and segregated storage partitions.
globs: src/**/*.{ts,tsx}, src-tauri/tauri.conf.json, src-tauri/capabilities/**/*.json, src-tauri/src/**/*.rs
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/tauri2-webview-isolation-ipc-scoping-invariant"
---

# Tauri 2.0 Ephemeral Webview Isolation & Scoped IPC Guardrail

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Spawning Auxiliary Renderers with Default Host Capabilities and Shared Memory/Storage Contexts

## System Constraints
You are a Principal Engineer enforcing the Tauri 2.0 Webview Process Separation & Memory Scoping Invariant. Mandate that every secondary, auxiliary, or ephemeral webview window operates under a dedicated ACL capability identifier, utilizes a non-shared storage partition, and exposes zero access to core credential or persistence IPC invokes.

## Strict Guidelines
- Engineers MUST ALWAYS isolate auxiliary or preview webview windows under dedicated window labels (e.g., `auxiliary:*`, `preview:*`) with matching restrictive capability files in `src-tauri/capabilities/`.
- Engineers MUST NOT allow auxiliary webviews to inherit the `default` capability group or grant wildcard `core:default` permissions.
- Frontend IPC invokers MUST validate window origin and label before executing sensitive Tauri commands, refusing execution if called from non-main contexts.
- Ephemeral webviews MUST use distinct storage partitions or memory-only browser contexts to prevent IndexedDB and LocalStorage exfiltration across window boundaries.
- Components NEVER instantiate untrusted external URLs or dynamic scripts within windows configured with IPC access; untrusted content MUST use external browser contexts or deep-sandboxed webviews with all Tauri APIs disabled.

## Bad vs Good Implementations
### Ephemeral Webview Window Spawning with IPC and Storage Scoping

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Creating a webview window with default settings grants it the main window's IPC capabilities in Tauri 2.0 (unless explicitly segregated via capability matching) and shares the web storage context (cookies, LocalStorage, IndexedDB), enabling side-channel data exfiltration and unauthorized invoke execution.
```typescript
import { WebviewWindow } from '@tauri-apps/api/webviewWindow';

// ANTI-PATTERN: Spawns preview window with default capabilities and shared context.
// The auxiliary window shares LocalStorage/IndexedDB with main and inherits all backend commands.
export async function spawnPreviewWindow(untrustedUrl: string) {
  const webview = new WebviewWindow('preview', {
    url: untrustedUrl,
    title: 'Document Preview',
    // Inherits main app capability scope implicitly
  });

  await webview.once('tauri://created', () => {
    console.log('Preview window created with full IPC access');
  });
}
```

#### Production Standard (Correct)
> **Standard**: The auxiliary webview uses a globally unique label scoped under the `auxiliary:` namespace, matches a dedicated sandboxed capability JSON configuration, and runs in an isolated incognito context to eliminate shared cache, IndexedDB, and LocalStorage state.
```typescript
import { WebviewWindow } from '@tauri-apps/api/webviewWindow';

// INVARIANT FIX: Strict label scoping tied to Tauri 2.0 capabilities with sandboxed context
export async function spawnPreviewWindow(untrustedContentUrl: string): Promise<WebviewWindow> {
  const windowId = `auxiliary:preview:${crypto.randomUUID()}`;
  
  const webview = new WebviewWindow(windowId, {
    url: untrustedContentUrl,
    title: 'Isolated Preview',
    incognito: true, // Tauri 2.0: isolates web storage and memory
    zoomHotkeysEnabled: false,
    focus: true
  });

  // Window label 'auxiliary:preview:*' is constrained in capabilities/auxiliary.json
  // allowing only zero-trust commands (e.g., window close) and rejecting all storage/keychain invokes.
  await new Promise<void>((resolve, reject) => {
    webview.once('tauri://created', () => resolve());
    webview.once('tauri://error', (e) => reject(new Error(String(e))));
  });

  return webview;
}
```
Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

Tauri Security Inspector MCP
Validates Tauri 2.0 capability definitions, permission sets, and webview window isolation topologies against least-privilege standards.
Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

Tauri 2.0 ACL & Capability Auditor
CLI utility to lint Tauri 2.0 capability files and ensure no cross-window privilege leaks occur between main and auxiliary renderers.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Tauri 2.0 Ephemeral Webview Isolation & Scoped IPC Guardrail

Tauri 2.0 Ephemeral Webview Isolation & Scoped IPC Guardrail defines an industrial-grade behavioral standard for frontend engineering. Enforces strict process, storage, and IPC boundary separation between primary execution contexts and auxiliary or ephemeral renderer windows in Tauri 2.0. Eliminates cross-webview side-channel exfiltration and memory contamination by requiring distinct window labels, explicit capability mapping, and segregated storage partitions. 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: Spawning Auxiliary Renderers with Default Host Capabilities and Shared Memory/Storage Contexts 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 ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftSpawning Auxiliary Renderers with Default Host Capabilities and Shared Memory/Storage ContextsCritical
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 InconsistencyAI 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:

1

Engineers MUST ALWAYS isolate auxiliary or preview webview windows under dedicated window labels (e.g., `auxiliary

Engineers MUST ALWAYS isolate auxiliary or preview webview windows under dedicated window labels (e.g., `auxiliary:*`, `preview:*`) with matching restrictive capability files 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.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
2

Engineers MUST NOT allow auxiliary webviews to inherit the `default` capability group or grant wildcard `core

Engineers MUST NOT allow auxiliary webviews to inherit the `default` capability group or grant wildcard `core:default` permissions.

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.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
3

Frontend IPC invokers MUST validate window origin and label before executing sensitive Tauri commands, refusing execution if called from non-main contexts.

Frontend IPC invokers MUST validate window origin and label before executing sensitive Tauri commands, refusing execution if called from non-main contexts.

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.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
4

Ephemeral webviews MUST use distinct storage partitions or memory-only browser contexts to prevent IndexedDB and LocalStorage exfiltration across window boundaries.

Ephemeral webviews MUST use distinct storage partitions or memory-only browser contexts to prevent IndexedDB and LocalStorage exfiltration across window boundaries.

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.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
5

Components NEVER instantiate untrusted external URLs or dynamic scripts within windows configured with IPC access

Components NEVER instantiate untrusted external URLs or dynamic scripts within windows configured with IPC access; untrusted content MUST use external browser contexts or deep-sandboxed webviews with all Tauri APIs disabled.

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.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is Tauri 2.0 Ephemeral Webview Isolation & Scoped IPC Guardrail critical for AI coding assistants?

Enforces strict process, storage, and IPC boundary separation between primary execution contexts and auxiliary or ephemeral renderer windows in Tauri 2.0. Eliminates cross-webview side-channel exfiltration and memory contamination by requiring distinct window labels, explicit capability mapping, and segregated storage partitions. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (Spawning Auxiliary Renderers with Default Host Capabilities and Shared Memory/Storage Contexts) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related FRONTEND Rules

View all rules →
frontend
119

SolidStart 1.0 Server Functions & Async Boundaries Production Standard

SolidStart 1.0 relies on the Vinxi bundler to split `server$` closures into independent HTTP POST RPC endpoints. Direct lexical closure over client signals within `server$` scopes or failure to demarcate async boundaries with `<Suspense>` causes silent serialization failures, client-bundle secret leaks, and SSR hydration mismatches. Enforcing strict parameter passing, runtime input validation, and Solid async primitives maintains security and fine-grained reactivity across network boundaries.

frontend
119

Astro 5 Actions & Content Layer Production Standard

Enforces strict type safety and architectural correctness for Astro 5 Server Actions and the zero-waterfall Content Layer API. Prevents runtime contract mismatches, hydration mismatches, and unhandled mutation exceptions across dynamic and prerendered boundaries. Failure to follow these patterns leads to silent data fetching waterfalls, build-time cache corruptions, and unhandled server action exceptions.

frontend
51

Nuxt 4 Nitro Server Engine & Shared Directory Production Standard

Nuxt 4 enforces strict boundary segregation between client UI in the app/ directory, backend endpoints in server/, and universal contracts in shared/. Violating cross-boundary isolation or maintaining module-scoped state in Nitro server handlers causes catastrophic cross-request data corruption and hydration mismatches under concurrent production traffic. Architects must enforce request-isolated H3 event contexts, universal serialization schemas, and strict path-alias boundaries.

1 Rule in Stack

Tauri