When to use this skill
ALWAYS use this skill when the user mentions:
- Persisting plugin scopes across app restarts
- Remembering file access permissions between sessions
- Scope expiration or revocation flows
Trigger phrases include:
- "persisted scope", "remember access", "scope persistence", "re-authorization", "scope expiration"
How to use this skill
- Install the persisted-scope plugin:
cargo add tauri-plugin-persisted-scope - Register the plugin in your Tauri builder:
tauri::Builder::default() .plugin(tauri_plugin_persisted_scope::init()) - Configure capabilities in
src-tauri/capabilities/default.json:{ "permissions": ["persisted-scope:allow-save", "persisted-scope:allow-load"] } - How it works: When the user grants file access (e.g., via a dialog picker), the persisted-scope plugin automatically saves those scope entries to disk and restores them on next launch
- Implement expiration by periodically checking saved scopes and removing stale entries
- Add revocation UI to let users manage which persistent access grants remain active
- Avoid permanent over-privilege by reviewing persisted scopes during app startup
Outputs
- Persisted scope plugin setup for cross-session access retention
- Expiration and revocation flow patterns
- Scope audit guidance to prevent over-privilege
References
- https://v2.tauri.app/plugin/persisted-scope/
Keywords
tauri persisted scope, scope persistence, file access, re-authorization, expiration