tauri-syntax-state

Tauri app state is managed safely by wrapping shared data in Mutex or RwLock wrappers and injecting it via tauri::State. This approach enforces thread safety across concurrent commands and background tasks, preventing runtime panics.

You need RwLock for Tauri state injection when multiple background tasks require concurrent read access, whereas Mutex is sufficient for exclusive write access. Choosing the correct wrapper prevents deadlocks and ensures safe state sharing across your application contexts.

Yes, you can access Tauri managed state from background tasks and Webview contexts by passing an AppHandle. This Skill documents safe access patterns for App, AppHandle, Window, and Webview contexts to ensure thread-safe state sharing.

To register and access Mutex-wrapped state in a Tauri 2.x app, you centrally register the state during app startup and inject it into commands using tauri::State. This enforces exact type matching for managed state and provides guarded access.

Tauri commands panic when accessing shared application state if thread safety is not enforced or exact type matching fails. Applying Mutex or RwLock wrappers during centralized registration prevents these state-related pitfalls and runtime errors.