Problem
Command palette toggles backed by config.json do not show their current state. Toggles backed by local state do: "Toggle Flat Chat List" shows "Current: Grouped", for example. Two bug-bash explorers (Opus 5.5 and Sonnet 5.5) reported this for the new "Toggle Count AI Calls from Bash Commands" action (#5772). "Toggle Keep Screen Awake" behaves the same way. Running either toggle gives no feedback.
Cause (from source)
src/browser/utils/commands/sources.ts builds the "Current:" subtitles synchronously from persisted local state or props. The config-backed toggles read config.getConfig() only inside run, so the palette has no value to show when it renders.
Expected
Config-backed toggles show "Current: On" or "Current: Off". One way: give the palette sources the loaded app config. Also optional: show a short confirmation after the toggle runs.
Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high • Cost: $53.91
Problem
Command palette toggles backed by
config.jsondo not show their current state. Toggles backed by local state do: "Toggle Flat Chat List" shows "Current: Grouped", for example. Two bug-bash explorers (Opus 5.5 and Sonnet 5.5) reported this for the new "Toggle Count AI Calls from Bash Commands" action (#5772). "Toggle Keep Screen Awake" behaves the same way. Running either toggle gives no feedback.Cause (from source)
src/browser/utils/commands/sources.tsbuilds the "Current:" subtitles synchronously from persisted local state or props. The config-backed toggles readconfig.getConfig()only insiderun, so the palette has no value to show when it renders.Expected
Config-backed toggles show "Current: On" or "Current: Off". One way: give the palette sources the loaded app config. Also optional: show a short confirmation after the toggle runs.
Generated with
xum• Model:anthropic:claude-opus-5-5• Thinking:high• Cost:$53.91