Fix: move user cloud API keys out of localStorage into secure storage (Tauri)

[selena731]

Move storage of user-provided cloud API keys (OpenAI, Anthropic, Gemini, OpenRouter) from localStorage to Tauri secure storage APIs (e.g., tauri-plugin-stronghold or invoke('save_key')). Update frontend frontend/src/components/CommandPalette.tsx to use secure storage when running in Tauri; for web builds, provide an encrypted storage or session-only option and document the risk. Add tests and README updates.

Files to change: frontend/src/components/CommandPalette.tsx and relevant storage helpers.

[keldonlyndonjoseph-hub]

Open Jarvis

[gilbert-barajas]

Took a look at implementing this — it appears already done on main:

• Cloud keys (OpenAI/Anthropic/Gemini/OpenRouter) live in the OS credential store via the keyring crate (save_cloud_key / get_cloud_key_status Tauri commands, keyring::Entry set/get/delete).
• Both key UIs (CommandPalette + SettingsPage) write via saveCloudKey(), never localStorage. Web builds refuse ("Cloud API keys can be saved in the desktop app only") rather than storing insecurely.
• There's even legacy migration (migrate_legacy_cloud_keys) moving old keys into the keychain.

So the "out of localStorage → secure storage" goal looks met. Did I miss a remaining piece — the web encrypted/session option, or README docs for the keychain behavior? Happy to add the README note if that's the gap; otherwise this looks closeable.

[ElliotSlusky]

I have solved this. Thank you all.