Skip to content

fix: omit transient enabled state from saved presets#4

Merged
leblancfg merged 1 commit into
mainfrom
vi/omit-enabled-from-presets
Jun 26, 2026
Merged

fix: omit transient enabled state from saved presets#4
leblancfg merged 1 commit into
mainfrom
vi/omit-enabled-from-presets

Conversation

@leblancfg

Copy link
Copy Markdown
Owner

Problem

Saved presets currently include enabled, which is transient next-turn state. That means /fusion preset save can accidentally persist whether fusion happened to be armed at the moment the preset was saved.

A preset should describe the fusion configuration: worker count, models, thinking levels, budgets, and planner tool mode. It should not silently turn the next request on or off because of stale UI/session state.

Change

  • Stop writing enabled from snapshotFusionSettings.
  • Keep older presets compatible: if an existing preset already contains enabled, applyFusionPresetSettings still honors it through the normal settings resolver.
  • Add a regression assertion that newly saved presets omit enabled and apply without arming fusion.

Verification

  • pnpm test -- tests/presets.test.ts
  • pnpm run typecheck
  • pnpm run format:check
  • git diff --check

@leblancfg
leblancfg merged commit ce40db5 into main Jun 26, 2026
1 check passed
@leblancfg
leblancfg deleted the vi/omit-enabled-from-presets branch June 26, 2026 00:21
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.

1 participant