Skip to content

Improved API key persistence and config recovery - #7

Merged
karamouche merged 4 commits into
mainfrom
fix/api-key-persistence
Sep 2, 2026
Merged

Improved API key persistence and config recovery#7
karamouche merged 4 commits into
mainfrom
fix/api-key-persistence

Conversation

@karamouche

Copy link
Copy Markdown
Collaborator

Summary

  • Fail safely when the existing config cannot be read or parsed, preventing API keys and other settings from being overwritten by defaults.
  • Surface config-load failures separately from a missing API key and provide Retry and Open logs actions.
  • Add an explicit two-step settings reset that keeps a timestamped backup, refuses readable configs, and restores the original if reset fails.
  • Add redacted config diagnostics without logging API key contents.

Test plan

  • npm run test
  • cargo clippy --manifest-path src-tauri/Cargo.toml --all-targets -- -D warnings
  • npm run build
  • Manually verify a saved API key survives a full quit and relaunch.
  • Manually corrupt config.json and verify Retry/Cancel do not reset it, then confirm Reset all settings creates defaults and retains a timestamped backup.

@karamouche karamouche changed the title Fix API key persistence and config recovery Improved API key persistence and config recovery Aug 31, 2026
@karamouche
karamouche merged commit 23ec72f into main Sep 2, 2026
6 checks passed
@karamouche
karamouche deleted the fix/api-key-persistence branch September 2, 2026 21:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants