Tauri Process API allowlist discrepancy in production builds

Feature: Process API allowlist

During local development, Tauri’s dev server automatically grants all API permissions, allowing commands such as Command::new("echo", &["Hello"]).output() to run without explicit configuration. When a production bundle is built, the default default allowlist excludes the process API. Consequently, the same command returns a PermissionDenied error unless process is added to the allowlist in tauri.conf.json.

This discrepancy is consistent across Windows, macOS, and Linux, reflecting the identical security model in the bundled application. The documentation notes that developers must opt-in to the process API, but the guidance is not enforced automatically, leading to silent failures in production releases.

The unresolved decision is whether Tauri should enable the process API by default for production builds or require explicit opt-in. This choice has implications for security, developer experience, and cross-platform consistency.

Should Tauri default to enabling the process API in production? What is the recommended strategy to handle this allowlist gap across all supported platforms? How can developers reliably verify that the process API is available in their final bundle?