Add a way to hide the deprecated "AI Presets" entry from the Wave Config sidebar

Open Beginner friendly

#3,282 opened on May 4, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 2/5
Estimated time: 1-3 hours
Newbie friendliness: 70/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Quiet
Tech stack: typescript
Domain: frontend

Research direction

Start in frontend/app/view/waveconfig/waveconfig-model.ts and inspect getDeprecatedConfigFiles(), comparing its existing presets.json file check with the unconditional presets/ai.json entry. Review the AI Presets documentation and choose one of the requested hiding behaviors; done means the deprecated entry is no longer shown when its configuration is absent or the chosen dismissal setting is active.

Written by the indexing model from the issue text.

Description

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.

Dominant language: Go
Stars: 22.3k
Forks: 1.1k
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

GrafeasNote is a duplicate resource of ContainerAnalysisNote Open

Difficulty 1/5 Under an hour Newbie friendliness 84/100

GoogleCloudPlatform/k8s-config-connector#13349 · Opened Sep 21, 2026
[receiver/receiverhelper] skip WithLinks when the parent span context is invalid Open

enhancement needs triage

Difficulty 2/5 1-3 hours Newbie friendliness 68/100

open-telemetry/opentelemetry-collector#15998 · Opened Sep 21, 2026
🧹 Use PodSet wrappers in DRA tests Open

kind/cleanup

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

kubernetes-sigs/kueue#15947 · Opened Sep 21, 2026
Custom provider credential is written as `PROVIDER_API_KEY` (apiserver) but the AgentRun controller injects only allowlisted keys, so every custom provider fails with HTTP 401 Open

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

sympozium-ai/sympozium#627 · Opened Sep 21, 2026
A recording that opens with an all-zero last_throw emits a zeroed discThrown at frame 0 Open

Difficulty 2/5 1-3 hours Newbie friendliness 86/100

EchoTools/tape#60 · Opened Sep 21, 2026

More Go issues