Open StructByLightning opened 2 weeks ago
@StructByLightning I've just realized that our new documentation for this didn't make it through build, so hasn't been updated, but here is the new page: https://github.com/continuedev/continue/blob/main/docs/docs/customize/deep-dives/prompt-files.md
We just shipped a v2 of prompt files with the following updates:
~/.continue/prompts
for global, and .continue/prompts
for per-workspace promptsSorry about the miscommunication, and would love to hear your thoughts on the new format! We definitely understand that there is still work to do and will be able to patch any holes pretty quickly from initial feedback
hey @sestinj
The global prompts are still not documented on the GH doc you linked. That said, using ~/.continue/prompts
and @ instead of / works for me.
Thanks!
Hype! This is awesome! I thought I was going to have to wait a few days for a bugfix and instead there are new features. Context providers in prompt files!
(And yeah I was able to get the global prompt location working, same as @madrover)
After having used the new prompts some more, I really don't like the change from slash command to @ commands.
There are a lot more possible results for an @ command, so it makes it harder to select the prompt. For example, with the prompt name jest
, I could type /je
and then it would autocomplete it for me because the only other prompt that started with j
was jsdocs
. But with @ commands... @je
doesn't even show the jest prompt on the first page.
In fact, typing out the full prompt name still doesn't put it as the first one!
I am not sure how anyone thinks this would be better from a usability stand point as @StructByLightning shows. But it's free so can't really say more than that.
Before submitting your bug report
Relevant environment info
Description
This morning, I discovered that Continue no longer loads prompt files. Things I tried:
/home/raven/.continue/.prompts
.prompts
experimental.promptPath
field to/home/raven/.continue/.prompts
experimental.promptPath
field to/home/raven/prompts/build
experimental.promptPath
field toprompts
experimental.promptPath
field to.prompts
In all cases I was unable to get any of my prompt files to appear as slash commands. Needless to say, this almost completely breaks Continue for me, as most of my prompts are stored as files.
To reproduce
.prompts
experimental.promptPath
and folder locationsLog output