SQLR-70 — Desktop playground: in-app Settings for Anthropic API key

[joaoh82]

What & why

The SQL playground (sqlrite-desktop) read its ask config exclusively from SQLRITE_LLM_API_KEY in the environment. Launched from Finder / the Dock — which don't inherit a shell's env — the Ask… button just errored. This ports the in-app settings pattern we shipped for the journal example app (SQLR-41 / #145) into the playground, so a user can paste a key in a ⚙ dialog and it persists across restarts. Env var still works as a fallback for existing dev workflows.

Changes

Rust (desktop/src-tauri/)

• src/settings.rs (new) — AskSettings persisted as JSON to $APP_DATA/com.sqlrite.desktop/settings.json; scrubbed AskSettingsDto (has_api_key: bool — the raw key never crosses to the webview); three-valued AskSettingsUpdate; build_ask_config() (prefers saved key, falls back to SQLRITE_LLM_API_KEY); settings_path(). 5 unit tests.
• src/main.rs — AppState gains settings_path (resolved from app_data_dir() in setup); ask_sql builds config from saved settings instead of AskConfig::from_env(); new get_ask_settings / update_ask_settings commands registered.

Frontend (desktop/src/)

• lib/SettingsPanel.svelte (new) — gear-modal, rewritten in the playground's plain-CSS idiom (the playground uses global app.css vars, not Tailwind like the journal). Password field, model, max-tokens, "Clear saved key", status line, Esc-to-close, security note.
• lib/api.ts (new) — getAskSettings / updateAskSettings wrappers with null→absent normalisation.
• App.svelte — ⚙ header button mounts the panel. app.css — .settings-button rule.

desktop/README.md (new) — "Configuring ask" section + security note (no README existed).

Deviations from the journal port

• build_ask_config is unconditional — the desktop crate has no ask feature gate and always builds the engine with ask on (matching the existing unconditional ask_sql). So all 5 tests always run.
• tempdir() in tests uses a process-wide AtomicU64 counter instead of subsec_nanos() — the journal's version has a latent parallel-run collision that surfaced here (fixed; see follow-up).

Test plan — all green locally

• npm install + npm run build (vite) + npm run check (svelte-check: 0 errors/warnings)
• cargo test -p sqlrite-desktop → 5/5 pass, stable across 3 runs
• cargo build -p sqlrite-desktop --all-targets, cargo fmt --check, cargo clippy → new code has 0 warnings (remaining clippy hits are pre-existing)

Not verified: live end-to-end LLM call (needs a real key + network) and the literal Finder-launch scenario (headless run). Both are covered indirectly by unit tests + the binary compiling against the embedded dist/.

Follow-up

The journal app's examples/desktop-journal/src-tauri/src/settings.rs has the identical flaky tempdir() — worth a small ticket to port this fix back.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
rust-sqlite	Ready	Preview, Comment	May 30, 2026 10:44pm