runtime settings changes are ignored unless Preferences is open #118

Closed
opened 2026-08-01 08:37:07 +00:00 by hugo · 1 comment
Owner

SettingsChanged domain events only rehydrate SettingsViewState while a Settings tab exists. Editor, diff, AI, tags, and chat consumers keep stale settings after CLI/server changes until Preferences is opened. Settings must be hydrated and refreshed independently of whether their UI is visible.

SettingsChanged domain events only rehydrate SettingsViewState while a Settings tab exists. Editor, diff, AI, tags, and chat consumers keep stale settings after CLI/server changes until Preferences is opened. Settings must be hydrated and refreshed independently of whether their UI is visible.
hugo added the bugcritical labels 2026-08-01 08:37:07 +00:00
Author
Owner

Implemented in 2fed537. Every relevant SettingsChanged event now rehydrates the complete cached settings state even when Preferences is closed. Airplane mode, which is also cached separately for AI and Git routing, is refreshed through the same runtime applicator used by the status-bar control, including open chat model state. Added red/green regressions for external AI-profile and airplane-mode changes with no Settings tab, updated the Allium client-synchronization obligation and README, and reviewed against bDS2's every-client refresh behavior. Validation: allium check/analyse, cargo fmt, cargo build --workspace, clippy with -D warnings, cargo test --workspace (565 core and 214 UI tests), and cargo bundle-macos all passed.

Implemented in 2fed537. Every relevant SettingsChanged event now rehydrates the complete cached settings state even when Preferences is closed. Airplane mode, which is also cached separately for AI and Git routing, is refreshed through the same runtime applicator used by the status-bar control, including open chat model state. Added red/green regressions for external AI-profile and airplane-mode changes with no Settings tab, updated the Allium client-synchronization obligation and README, and reviewed against bDS2's every-client refresh behavior. Validation: allium check/analyse, cargo fmt, cargo build --workspace, clippy with -D warnings, cargo test --workspace (565 core and 214 UI tests), and cargo bundle-macos all passed.
hugo closed this issue 2026-08-01 08:45:34 +00:00
Sign in to join this conversation.