[loganj]

🤖

Summary

• Settings in .env.local now reach the native desktop build. You can put the federated identity (FI, "sign in with your organization") deployment descriptor there, and plain just desktop produces an FI build. Before this change, you had to put it in front of every just desktop command. A descriptor in .env.local was ignored without a warning, and the result was a non-FI build: Settings → Identity showed no organization sign-in.
• just desktop and just desktop-bundle now add every BUZZ_-prefixed value from the repository-root .env.local to the environment of Tauri, Cargo and the native app. A value set in the shell still wins, including an explicit empty value such as BUZZ_DEV_VIEWER=.

Details

• One helper, launchEnvironment in scripts/desktop-config.mjs, builds the environment for both launchers. It reads .env.local with Node's parseEnv, the same parser as the frontend's Builderlab URL reader: $VAR is never expanded, quoted or not, so a $ in a URL or in the descriptor JSON stays as written. Like the native build, it ignores Vite's .env and mode files (.env.development and similar). Vite's own loader would have expanded $VAR even in single-quoted values and let mode files override .env.local, which would change values the native build already reads today.
• Before this change, desktop-dev.mjs forwarded only BUZZ_DEV_VIEWER. It still passes the frontend's effective pin, from Vite's loader, to native agent starts. An unpinned launch still passes an explicit empty pin.
• The Vite dev server inherits this environment, so in just desktop a .env.local value now also beats the same name in a Vite mode file for the frontend. Frontend and native therefore agree.
• Only BUZZ_ names are loaded, except the release-only BUZZ_UPDATER_* inputs, which stay process-environment only. .env.local can hold unrelated credentials. Agent processes remove only BUZZ_ and NOSTR_ names from the app's environment (src-tauri/src/host_process.rs), so other names would reach them. BUZZ_ values do reach some of the app's child processes, so they must stay public configuration, as the configuration docs already require.
• Direct pnpm tauri build and cargo runs do not change. Release builds still supply their inputs through the process environment.
• docs/configuration.md describes the launch environment. .env.example shows an FI descriptor line.

Example .env.local for the Block deployment:

BUZZ_DEV_VIEWER=
BUZZ_BUILDERLAB_URL=
BUZZ_BUILD_FEDERATED_IDENTITY_CONFIG='{"version":1,"id":"bb-block",...}'

🤖 Generated with Claude Code

[kalvinnchau]

🤖 Reviewed; no actionable defects found. Launcher integration and environment-boundary checks passed, with passing JavaScript/Vitest CI at this head. Native desktop launch, Tauri/Cargo compilation through the launchers, and packaged OS environment inheritance remain unverified.