bug: clear() is not persistent

[pfnilsson]

Did you check docs and existing issues?

• I have read all the sidekick.nvim docs
• I have updated the plugin to the latest version before submitting this issue
• I have searched the existing issues of sidekick.nvim
• I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

0.11.4

Operating system/version

MacOS 26.0.1

Describe the bug

When pressing to clear NES, it pop right back. I would expect that it does not reappear until I make some further edit, but I was not able to find anything in the docs that. If it is meant to pop right back up perhaps I am just misunderstanding what the clear feature is supposed to do. Same behaviour if manuall calling .clear() instead of using .

Steps To Reproduce

1. Install sidekick with default settings
2. Trigger a NES
3. Press escape
4. See the suggestion come right back when releasing

Expected Behavior

I would expect the suggestions to not show again until they have a reason to change, e.g. an edit was made.

Repro

Hard to set up isolated because of the copilot dependency, but should work for any working sidekick install I believe

[gennaro-tedesco]

I am experiencing the same problem too, namely after dismissing a NES it tends to re-occur even if I just move around without making further edits. However, this probably depends on the (aggressive) behaviour of the copilot-lsp and sidekick just offers what the lsp passes through.

It would be interesting to see if there are some upstream settings for the lsp that enable to only pass through suggestions of certain relevance (say only when certain parts of the syntax tree are changed).

[folke]

I don't have this, but it's probably triggered by keymaps that don't use <cmd> and so was changing modes from c:n.

Just changed the default triggers to only trigger on mode changes from i:n.

It's also completely user configurable on when nes is updated, so check the docs