CodeGate chat commands don't work with file in context, or clients that prefix messages

[danbarr]

Describe the issue

Copilot automatically includes the file that's active in the VS Code editor as context. When this happens, codegate version commands are not correctly handled.

Possibly related to issues I used to see with the task-oriented tools like Cline/Kodu, codegate commands where they only worked if they are the first prompt in the task? This seems to have been fixed at least for Cline.

Also maybe related to the avante.nvim issue stacklok/codegate-ui#346

Steps to Reproduce

Open a file in VS Code. In the Copilot chat, see that it's currently included in the current file context. Enter codegate version into the chat and observe the results.

Operating System

MacOS (Arm)

IDE and Version

VS Code 1.97.2

Extension and Version

Copilot 1.272.0

Provider

GitHub Copilot

Model

Claude 3.5 Sonnet

Codegate version

v0.1.24

Logs

No response

Additional Context

No response

[kantord]

There is a very similar issue with avante.nvim: stacklok/codegate-docs#89 (comment)

Seems like the underlying cause is that the client prefixes the message that the user typed, thus it's no longer recognized by codegate as a command: https://discord.com/channels/1184987096302239844/1342432974817198114/1342442136439881783

But I suppose the underlying cause is the same: some clients will add additional text prefixing/postfixing the message, which sabotages the current logic for recognizing codegate commands 🤔

[alex-mcgovern]

Duplicate of #1061

[danbarr]

Doh! I thought we had one on this but couldn't find it. Thanks.