NodlumeNodlume
Tauri permissions generator

Tauri os permission: os:default

The os plugin (tauri-plugin-os) reports the platform, architecture, OS type and version, locale, hostname and the executable file extension of the machine the app runs on — the details a desktop app uses to pick a keyboard shortcut label, a download URL, or a code path per platform.

os:default grants every read. Nothing here touches user data, but the combination is fingerprintable, so an app that only needs the platform name can grant os:allow-platform alone and keep the rest off.

OS info at a glance

Permission
os:default
Cargo crate
tauri-plugin-os
npm bindings
@tauri-apps/plugin-os
Builder call
.plugin(tauri_plugin_os::init())
What it enables
Platform, architecture and OS version details.
What it widens
Reads platform, architecture and OS version. Fingerprintable, but does not touch user data.

The four files that must agree

Capability file

src-tauri/capabilities/default.json
{
  "$schema": "../gen/schemas/desktop-schema.json",
  "identifier": "default",
  "description": "Capabilities granted to the main window.",
  "windows": [
    "main"
  ],
  "permissions": [
    "core:default",
    "os:default"
  ]
}

core:default is the baseline every window has; the plugin permission is the one line this page adds.

Cargo dependency

src-tauri/Cargo.toml
[dependencies]
tauri = { version = "2", features = [] }
serde = { version = "1", features = ["derive"] }
serde_json = "1"
tauri-plugin-os = "2"

Plugin registration

src-tauri/src/lib.rs
#[cfg_attr(mobile, tauri::mobile_entry_point)]
pub fn run() {
    tauri::Builder::default()
        .plugin(tauri_plugin_os::init())
        .run(tauri::generate_context!())
        .expect("error while running tauri application");
}

A crate that is declared but never registered is dead weight; one registered without its permission is a runtime denial.

Frontend bindings

terminal
npm install @tauri-apps/plugin-os

os:default, answered

The longer version is in the guide Tauri 2 permissions: capabilities without the runtime denials.

What does os:default grant in Tauri 2?
os:default is the default permission set of tauri-plugin-os. It platform, architecture and OS version details. Tauri 2 denies every command that is not listed in a capability file, so without this line the plugin's commands fail at runtime even though the crate compiles and is registered.
Why does my os info call fail with a permission error?
Three files have to agree: tauri-plugin-os in Cargo.toml, .plugin(tauri_plugin_os::init()) in src/lib.rs, and os:default in the capability file under src-tauri/capabilities/. The ACL is checked when a command is invoked, not when the app is built, so a missing permission string compiles cleanly and denies at runtime. The frontend also needs @tauri-apps/plugin-os installed to call it.
Is os:default safe to ship?
Reads platform, architecture and OS version. Fingerprintable, but does not touch user data. Permissions are additive on top of core:default, so the least-privilege shape is to grant only the plugins the app calls, and to prefer the plugin's granular allow-* permissions over the default set wherever a command or path can be named.

Combine it with the rest of your capability file

The Tauri permissions generator builds the whole file from the same catalogue — tick every plugin the app calls, add a custom title bar's window permissions, and copy the capability JSON, Cargo dependencies, builder chain and npm install line together. In the Nodlume workspace the same selection is what the Desktop export writes into src-tauri.

Open the generator

Other Tauri 2 plugin permissions

We'd like to use Google cookies to understand how Nodlume is used and to measure our advertising. Nothing loads until you choose, and declining does not affect anything in the app.