Skip to content

Keep synthesis disabled for new profiles - #155

Merged
calvintvu merged 1 commit into
mainfrom
cvu/disable-synthesis
Sep 4, 2026
Merged

Keep synthesis disabled for new profiles#155
calvintvu merged 1 commit into
mainfrom
cvu/disable-synthesis

Conversation

@calvintvu

@calvintvu calvintvu commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Context

New profiles should not automatically enable synthesis merely because a supported backend is detected. Keep the available backend and model preselected so users can opt in without extra setup.

Changes

  • Leave synthesis disabled when initializing unpersisted settings.
  • Preserve automatic selection of an available backend and its default model.
  • Add regression coverage for new-profile initialization.

Test

  • npm test — passed, 80 tests
  • npm run build — passed
  • npm run lint — passed with existing warnings
  • npm run format:check — passed
  • git diff --check — passed

Screenshots

  • Fresh profile settings — AI synthesis is disabled while a backend and model remain preselected
Screenshot 2026-09-04 at 11 03 41

@calvintvu calvintvu added the bug Something isn't working label Sep 4, 2026
@calvintvu
calvintvu merged commit ef151e9 into main Sep 4, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants