Tauri v2 Desktop & Mobile Security Standard

--- description: Tauri v2 Desktop & Mobile Security Standard - Guardrails for Tauri v2 cross-platform desktop & mobile apps: command capability security ACLs, safe IPC serialization, and isolation of OS native permissions. globs: src-tauri/**/*.rs, src-tauri/capabilities/**/*.json alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/tauri-v2-desktop" --- # Tauri v2 Desktop & Mobile Security Standard > **Severity**: CRITICAL | **Category**: mobile > **Anti-Pattern Warning**: AI enables wildcard permissions ('*') in Tauri capabilities or passes unsanitized filesystem paths over IPC. ## System Constraints You are a Tauri v2 security engineer. In Tauri v2, permissions are strictly governed by capability JSON files. Never grant wildcard permissions ('fs:*'). Every frontend IPC invocation via invoke() must validate parameters inside the Rust command before executing. ## Strict Guidelines - Scope permissions tightly in src-tauri/capabilities/default.json; avoid broad wildcard rules. - Validate and canonicalize all file paths in Rust before performing disk I/O. - Ensure the Tauri isolation pattern or Content Security Policy (CSP) is active in production builds. ## Bad vs Good Implementations ### Tauri v2 Scoped IPC Command with Path Canonicalization #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Unsanitized paths allow frontend attackers or malicious dependencies to read arbitrary system files. ```rust // Anti-pattern: Path traversal vulnerability over IPC #[tauri::command] fn read_user_file(path: String) -> Result<String, String> { // Dangerous: User can supply "../../../etc/passwd" std::fs::read_to_string(path).map_err(|e| e.to_string()) } ``` #### Production Standard (Correct) > **Standard**: Safely scopes file access to the sandboxed application directory and blocks path traversal attacks. ```rust // Production Standard: Scoped directory validation use std::path::{Path, PathBuf}; #[tauri::command] fn read_app_file(app: tauri::AppHandle, relative_path: String) -> Result<String, String> { let base_dir = app.path().app_data_dir().map_err(|e| e.to_string())?; let safe_path = base_dir.join(&relative_path); // Ensure path cannot escape the sandboxed app data directory if !safe_path.starts_with(&base_dir) { return Err("Path traversal attempt detected".into()); } std::fs::read_to_string(safe_path).map_err(|e| e.to_string()) } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Tauri v2 Desktop & Mobile Security Standard

Tauri v2 Desktop & Mobile Security Standard defines an industrial-grade behavioral standard for mobile engineering. Guardrails for Tauri v2 cross-platform desktop & mobile apps: command capability security ACLs, safe IPC serialization, and isolation of OS native permissions. 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: AI enables wildcard permissions ('*') in Tauri capabilities or passes unsanitized filesystem paths over IPC. 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	AI enables wildcard permissions ('*') in Tauri capabilities or passes unsanitized filesystem paths over IPC.	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:

Scope permissions tightly in src-tauri/capabilities/default.json

Scope permissions tightly in src-tauri/capabilities/default.json; avoid broad wildcard rules.

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.

Validate and canonicalize all file paths in Rust before performing disk I/O.

Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.

Ensure the Tauri isolation pattern or Content Security Policy (CSP) is active in production builds.

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 v2 Desktop & Mobile Security Standard critical for AI coding assistants?

Guardrails for Tauri v2 cross-platform desktop & mobile apps: command capability security ACLs, safe IPC serialization, and isolation of OS native permissions. 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 (AI enables wildcard permissions ('*') in Tauri capabilities or passes unsanitized filesystem paths over IPC.) 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.