slash commands not working

[harshmittalibm]

Hi Team,

I've noticed that slash commands are not working in granite.code. This functionality was broken in continue.dev version 1.0.5, but fixed in subsequent versions (1.0.6 and later).

Steps to reproduce:

Try invoking any slash command (e.g., /share).

Observe that nothing happens or the expected behaviour does not occur (which is that it should share the chat to a .md file).

Please let me know if any additional info is needed to help debug this. Thanks.

[Jazzcort]

Slash commands now seems to be a way to mention prompts which you can define either in ~/.continue/config.yaml or ~/.continue/prompts/<Whatever name you like>.yaml, or mcp prompts which I'm not pretty sure about the entire mechanism.

The slash commands you mentioned are only valid in a deprecated config format (config.json) which don't have a yaml equivalent. You can see the info here.

Everything that doesn't have a yaml equivalent will eventually become not working when Continue decide to not support config.json as a config file at any points in the future.

In my opinion, the functionality of these slash commands can be easily replaced by using MCP or Context. However, since Granite.Code is currently targeting using local inference (small model), using MCP is not quite practical.

[fbricon]

Basically, built-in slash commands are gone. The /share command could be reimplemented as a prompt for a model capable of using tools, like writing files to the FS. However, granite is not capable of doing that for the moment, and even if it did, like some other models running on ollama (I managed to do it with qwen3 IIRC), it's pretty slow.

My proposal is to expose the share functionality as a button or command directly in VS Code, without requiring a model doing the heavy work. It then works instantly. I got this PoC in the works:

save-chat-as-md.mp4

Next I'll look into exposing this feature as a command, as it'll make it easier for @harshmittalibm to automate.

[fbricon]

I've opened continuedev/continue#6802 upstream. I've checked the vs code command can be invoked using pyautogui, that @harshmittalibm is using, specifically the folder selection.

In case that PR is rejected upstream, we can still apply it to granite-code.