Sticky parameters

[v3ceban]

What's going on

Adding context or an agent to any of the api functions makes them sticky.

-- used in a mapping to open a chat with currently opened buffers
CopilotChat.open {
  selection = CopilotSelection.buffer,
  context = "buffers", -- results in >#buffers being added to chat before my prompt
}

 -- used in a mapping to ask perplexity with no attachement to the codebase
CopilotChat.ask(input, {
  agent = "perplexityai", -- results in >@preplexity being added
  selection = false,
  context = false,
})

  -- part of my config
Dockerfile = {
  prompt = "/COPILOT_INSTRUCTIONS\n\nGenerate a Dockerfile for this application.",
  agent = "docker",
  context = "files:full", -- adds both >@docker and >#files:full
  selection = false,
},

What I tried

Adding the new sticky param to nil or {} didn't help.

The fix for now is to disable agent/context and pass them as the part of the prompt like this

Dockerfile = {
  prompt = "/COPILOT_INSTRUCTIONS\n@docker\n@#files:full\n\nGenerate a Dockerfile for this application.",
  -- agent = "docker",
  -- context = "files:full",
  selection = false,
}

CopilotChat.ask("@perplexityai\n\n" .. input, {
  selection = false,
  context = false,
})

... but it feels a little weird not using the proper params.

Reasoning/background

It is very inconvenient to run these as standalone commands because you have to manually delete the sticky prompts they set when opening a new chat window or executing a new command. I manually set sticky to {} for all default prompts that use it. Before #855, I was rewriting the action prompts without the > before the instructions to remove these side effects, but now they appear when I set agents and context.

Proposed solution

It would be nice to have a way to disable/delete all sticky prompts after chat window is closed.

Deleting the whole chat history is an overkill, plus it's buggy when calling prompt_actions telescope integration in visual mode (it resets the visual selection and acts as if it was called in normal mode).

[deathbeam]

I guess I could add config to shared config to store sticky or not, but at least for opening buffer how this worked before is that the context = buffers config was saved to chat before so even though you did not see the sticky, it was there without easy option to delete it while continuing the chat.

So I added remembering the agent/context/model so its clear that its being reused, but downside is that you cant just replace it with new .ask call while outside of the chat.

[deathbeam]

#912 should solve this i think, added remember_as_sticky shared config that you can pass around (when calling .ask, .open (even though with open its just gonna make the params do nothing for obvious reasons) etc)

[v3ceban]

context = buffers config was saved to chat before so even though you did not see the sticky

It indeed felt that sometimes it didn't reset the context properly between chat sessions, which now makes total sense.

#912 should solve this i think

Will give it a try!

[deathbeam]

I will also add option to clear all stickies as i think its pretty useful thinking about it

[v3ceban]

@deathbeam worked like a charm, thank you so much for the quick fix!