AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
securitycritical PriorityID: tauri2-cross-window-ipc-capability-partitioning-production-standard

Tauri 2.0 Cross-Window IPC Capability Partitioning Standard

Enforces strict origin and window-label binding for all Tauri 2.0 IPC commands within multi-webview architectures. Prevents privilege escalation and cross-context contamination by restricting sensitive Rust backend commands through isolated capability definitions and cryptographic webview labeling instead of wildcard window bindings.

Prohibited Anti-Pattern: Wildcard Window Bindings Granting Auxiliary Windows Full Administrative IPC Access

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Tauri 2.0 Cross-Window IPC Capability Partitioning Standard - Enforces strict origin and window-label binding for all Tauri 2.0 IPC commands within multi-webview architectures. Prevents privilege escalation and cross-context contamination by restricting sensitive Rust backend commands through isolated capability definitions and cryptographic webview labeling instead of wildcard window bindings.
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-cross-window-ipc-capability-partitioning-production-standard"
---

# Tauri 2.0 Cross-Window IPC Capability Partitioning Standard

> **Severity**: CRITICAL | **Category**: security
> **Anti-Pattern Warning**: Wildcard Window Bindings Granting Auxiliary Windows Full Administrative IPC Access

## System Constraints
You are a Principal Security Architect enforcing the Tauri 2.0 Cross-Window IPC Capability Partitioning Standard. Multi-webview desktop applications introduce privilege boundary risks where auxiliary windows (e.g., OAuth popups, markdown previewers, document inspectors) may invoke core administrative capabilities if IPC access is not strictly segmented. Mandate granular window-targeted capability definitions in JSON ACLs and explicit window origin validation on all sensitive backend command handlers.

## Strict Guidelines
- Engineers MUST ALWAYS isolate Tauri 2.0 capabilities into dedicated, domain-specific capability files (e.g., `capabilities/main.json`, `capabilities/preview.json`) rather than declaring a monolithic `default.json`.
- Engineers MUST NOT use wildcard window matchers (`"windows": ["*"]`) for capabilities granting access to filesystem operations, shell execution, database mutations, or sensitive core plugins.
- Code MUST explicitly specify exact window labels in each capability configuration file (e.g., `"windows": ["main"]`, `"windows": ["auth-popup"]`).
- Services MUST validate the calling `tauri::WebviewWindow` label within sensitive Rust commands as defense-in-depth, aborting immediately if invoked from an unexpected window context.
- Components NEVER expose privileged invoke wrappers in frontend shared libraries without compile-time window-context checks or type-level capability isolation.

## Bad vs Good Implementations
### Tauri 2.0 Window Capability Configuration and Command Verification

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Using wildcard window bindings ('*') in capabilities exposes all dangerous IPC commands (like filesystem writes and shell execution) to secondary, preview, or third-party webview windows, violating least privilege and enabling remote code execution via compromised sub-windows.
```typescript
// src-tauri/capabilities/default.json
// ANTI-PATTERN: Wildcard window mapping grants untrusted windows full filesystem & shell access
/*
{
  "$schema": "../gen/schemas/desktop-schema.json",
  "identifier": "default-capability",
  "description": "Monolithic capability applied universally",
  "windows": ["*"],
  "permissions": [
    "core:default",
    "fs:allow-write-text-file",
    "fs:allow-read-text-file",
    "shell:allow-execute"
  ]
}
*/

// src/components/PreviewWindow.tsx
// Preview window can execute dangerous shell/FS calls across IPC
import { invoke } from '@tauri-apps/api/core';

export async function exportPreviewDocument(content: string, path: string) {
  return await invoke('export_system_file', { content, path });
}
```

#### Production Standard (Correct)
> **Standard**: Divides capability configuration into discrete ACL files with deterministic window matching, denying auxiliary windows access to write/shell plugins while reinforcing security with Rust-level window label checks.
```typescript
// src-tauri/capabilities/main.json
// PRODUCTION FIX: Restrict critical capabilities strictly to the primary administrative window
/*
{
  "$schema": "../gen/schemas/desktop-schema.json",
  "identifier": "main-window-capability",
  "description": "High-privilege capability strictly isolated to the main window",
  "windows": ["main"],
  "permissions": [
    "core:default",
    "fs:allow-write-text-file",
    "fs:allow-read-text-file"
  ]
}
*/

// src-tauri/capabilities/preview.json
/*
{
  "$schema": "../gen/schemas/desktop-schema.json",
  "identifier": "preview-window-capability",
  "description": "Sandboxed capability strictly limited to rendering read-only operations",
  "windows": ["preview-*"],
  "permissions": [
    "core:default"
  ]
}
*/

// src-tauri/src/commands.rs
// Defense-in-depth: Command handler verifies window identity
/*
#[tauri::command]
pub async fn export_system_file(
    window: tauri::WebviewWindow,
    content: String,
    path: std::path::PathBuf,
) -> Result<(), String> {
    if window.label() != "main" {
        return Err("Unauthorized: IPC invocation rejected for window origin".into());
    }
    // Secure write logic
    Ok(())
}
*/

// src/components/MainWindow.tsx
import { invoke } from '@tauri-apps/api/core';
import { getCurrentWebviewWindow } from '@tauri-apps/api/webviewWindow';

export async function exportDocument(content: string, path: string): Promise<void> {
  const currentWindow = getCurrentWebviewWindow();
  if (currentWindow.label !== 'main') {
    throw new Error('Security Error: Document export restricted to main window context.');
  }
  return await invoke<void>('export_system_file', { content, path });
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Tauri Security Auditor MCP
Scans Tauri 2.0 configuration files and capability JSON definitions for permissive window wildcards and insecure ACL configurations.
Recommended Agent Skills (askills.dev)

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

Cargo Audit CLI
Audits Rust dependencies in Tauri applications for security advisories and vulnerable crate versions.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Tauri 2.0 Cross-Window IPC Capability Partitioning Standard

Tauri 2.0 Cross-Window IPC Capability Partitioning Standard defines an industrial-grade behavioral standard for security engineering. Enforces strict origin and window-label binding for all Tauri 2.0 IPC commands within multi-webview architectures. Prevents privilege escalation and cross-context contamination by restricting sensitive Rust backend commands through isolated capability definitions and cryptographic webview labeling instead of wildcard window bindings. 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 Bindings Granting Auxiliary Windows Full Administrative IPC Access 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 DriftWildcard Window Bindings Granting Auxiliary Windows Full Administrative IPC AccessCritical
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 Tauri 2.0 capabilities into dedicated, domain-specific capability files (e.g., `capabilities/main.json`, `capabilities/preview.json`) rather than declaring a monolithic `default.json`.

Engineers MUST ALWAYS isolate Tauri 2.0 capabilities into dedicated, domain-specific capability files (e.g., `capabilities/main.json`, `capabilities/preview.json`) rather than declaring a monolithic `default.json`.

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 use wildcard window matchers (`"windows"

Engineers MUST NOT use wildcard window matchers (`"windows": ["*"]`) for capabilities granting access to filesystem operations, shell execution, database mutations, or sensitive core plugins.

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

Code MUST explicitly specify exact window labels in each capability configuration file (e.g., `"windows"

Code MUST explicitly specify exact window labels in each capability configuration file (e.g., `"windows": ["main"]`, `"windows": ["auth-popup"]`).

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

Services MUST validate the calling `tauri

Services MUST validate the calling `tauri::WebviewWindow` label within sensitive Rust commands as defense-in-depth, aborting immediately if invoked from an unexpected window context.

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 expose privileged invoke wrappers in frontend shared libraries without compile-time window-context checks or type-level capability isolation.

Components NEVER expose privileged invoke wrappers in frontend shared libraries without compile-time window-context checks or type-level capability isolation.

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 Cross-Window IPC Capability Partitioning Standard critical for AI coding assistants?

Enforces strict origin and window-label binding for all Tauri 2.0 IPC commands within multi-webview architectures. Prevents privilege escalation and cross-context contamination by restricting sensitive Rust backend commands through isolated capability definitions and cryptographic webview labeling instead of wildcard window bindings. 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 (Wildcard Window Bindings Granting Auxiliary Windows Full Administrative IPC Access) 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 SECURITY Rules

View all rules →
security
105

OpenFGA Graph Invariants: Cyclic Relation Prevention & Contextual Tuple Hardening

Enforces strict directed acyclic graph (DAG) topology validation during relationship mutation writes and mandates strict server-side schema verification for ephemeral contextual tuples in OpenFGA evaluations. Prohibits persistent storage of ephemeral request attributes and guards against recursive relation loops causing graph expansion denial-of-service.

security
81

WebAuthn Conditional UI Mediation, Nonce Atomicity, and Assertion Cryptographic Verification

Enforces zero-trust cryptographic validation for FIDO2/WebAuthn Passkey authentication with Conditional UI autofill. Requires atomic single-use challenge consumption to eliminate replay attacks, strict RP ID hash and origin binding, authenticatorData flag verification (User Presence and User Verification), and monotonic signature counter enforcement to detect authenticator cloning.

security
111

Enforce Sigstore Keyless OIDC Attestation and Admission Controller Verification

Enforces immutable supply-chain security using Sigstore Cosign keyless signing via ephemeral OIDC tokens issued by Fulcio and verified against the Rekor transparency log. Container workloads must be signed and attested at build time by digest, and admission controllers (such as Kyverno or Sigstore Policy Controller) must strictly validate the OIDC issuer and subject identity before allowing image execution.

1 Rule in Stack

Tauri