Summary
The Wave Config (Settings) sidebar always shows a deprecated AI Presets entry pointing at presets/ai.json. There's no way to dismiss or hide it. Per the docs at https://docs.waveterm.dev/ai-presets, this surface has been deprecated in favor of waveai.json (Wave AI Modes). For users who never used AI presets, or who have migrated to Wave AI Modes, the entry is permanent visual noise in the sidebar.
Current behavior
In frontend/app/view/waveconfig/waveconfig-model.ts, getDeprecatedConfigFiles() already filters the other deprecated entry (presets.json) so it's only shown when the file actually exists on disk. The presets/ai.json entry has no equivalent gate and is always rendered, regardless of whether the file exists or whether the user has any AI preset config at all.
Request
Please provide a way to hide the deprecated AI Presets entry — for example, an opt-in setting, or auto-hide when the file doesn't exist (matching the existing presets.json behavior). Either approach would address the noise.
Summary
The Wave Config (Settings) sidebar always shows a deprecated AI Presets entry pointing at
presets/ai.json. There's no way to dismiss or hide it. Per the docs at https://docs.waveterm.dev/ai-presets, this surface has been deprecated in favor ofwaveai.json(Wave AI Modes). For users who never used AI presets, or who have migrated to Wave AI Modes, the entry is permanent visual noise in the sidebar.Current behavior
In
frontend/app/view/waveconfig/waveconfig-model.ts,getDeprecatedConfigFiles()already filters the other deprecated entry (presets.json) so it's only shown when the file actually exists on disk. Thepresets/ai.jsonentry has no equivalent gate and is always rendered, regardless of whether the file exists or whether the user has any AI preset config at all.Request
Please provide a way to hide the deprecated AI Presets entry — for example, an opt-in setting, or auto-hide when the file doesn't exist (matching the existing
presets.jsonbehavior). Either approach would address the noise.