Application Workflow

Main flow

• Open EnvVault.
• Click Add Project.
• Select a local project folder through the macOS folder picker.
• EnvVault imports supported dotenv filenames and mirrors detected files into runtime profiles.
• Review the dashboard, variable table, comparison view, and security alerts.
• Use Re-import Changes after manually editing dotenv files outside EnvVault.
• Use the variable edit popup to update value, note, secret/public type, required flag, or expected value type.
• For runtime profile variables, add review metadata, rotation reminders, or external provider references when needed.
• Review sync diffs and snapshot history after imports, re-imports, and edits.
• Generate .env.example output or export selected env files when needed.

Browser mode versus desktop mode

The browser development mode uses fallbacks for Tauri-only APIs. The macOS Tauri app is the production path for folder dialogs, SQLite persistence, filesystem commands, Keychain commands, and clipboard permissions.

Safe output

• Generate .env.example output with blank values.
• Preview exports before writing.
• Confirm exports before writing dotenv files that may contain secrets.
• Resolve Keychain-backed secrets when exporting values that are intentionally written to disk.