Custom Commands just like in Cody

[19h]

Hey, I would really like to have this feature I use pretty much 95% over entering manual prompts in Cody every day:

These are essentially prompts to do repetitive things like cleanup, certain refactoring, optimizations, etc.

[Robert137498]

This is a great addition, even better if {selected} fills in whatever code is selected on screen, or {current} inputs whatever files is currently selected etc…

[deanrie]

Hi @19h

Thanks for the suggested feature. We’ll definitely consider it. We really appreciate your input

[vaghawan]

Indeed a much needed feature.

[litecode]

Hi @19h ,

You may be interested in the ideas that arose in this topic regarding ‘canned prompts’:

Context Groups: Defining collections of files as a single context for prompting

I wonder if some sort of ‘canned responses’ feature could achieve the desired results, but also be adaptable to other scenarios as well. You know how helpdesk software has canned responses, eg from a quick Google search: https://www.helpdesk.com/help/what-are-canned-responses/ https://www.livechat.com/help/set-canned-responses https://www.customerly.io/canned-response-templates It seems Cursor already has the underlying mechanism for ‘tagging’ specific content through the @ symbols feature,…

Context Groups: Defining collections of files as a single context for prompting

@connor, So as an immediate solution you could either: Create 1 file for each canned prompt: canned_prompt_1 canned_prompt_2 canned_prompt_3 Create 1 file that had all the canned prompts within it canned_prompts And then you could just @ either: the specific canned_prompt file the single canned_prompts file (and reference the relevant entry) Example canned prompt files below. Multiple Canned Prompts File # Canned Prompts This file contains canned prompts designed to …

And also this topic:

Workaround for lack of memory between chats

I guess this is a combo of showcase, workaround & feature request. I’ve been hoping for project memory to eventually be retained between chats, especially as chat length increases and subsequently degrades the quality of responses. Basically I’ve just created a projectContext.md file top-level in my codebase that describes the project / codebase and any current tasks being worked on. Essentially it just contains any information I would want to be persisted between chats. So I can just @project…

And the notion of storing, and writing, local prompt and logging files was expanded upon further in this video:

by echohive, 3 mins

Cursor Composer Auto saves your prompts to a file

Similar ideas about generating markdown files as prompts to keep things relevant and on track are talked about in this video:

by Yaron Been, 17 mins

This HACK WILL CREATE THE PERFECT CODE FOR YOU

The thing I like about all these ideas is that they are trivial to implement, yield powerful results, and let you be as creative as you like with them.