cursor
cursor copied to clipboard
getcursor
Copilot inline commands not working
Steps to reproduce:
- Select python class
- Open inline options
- Select Document with copilot
- Error: command 'inlineChat.start' not found
Curious when you'd want to use Copilot inline chat? Assumed that Cursor users weren't interested in using that feature, and so, we turned it off to not have key command collisions.
Happy to consider a change if people want it back on though.
I wanted to test it as I have noticed that option today. Primarly I wanted to try the "Generate documentation" as often times I find the gpt documentation not so great. Secondly having generate documentation button without having to write anything sounds pretty good. Would it be possible to just rebind copilot key commands to None and let user decide ?
Would it be possible to just rebind copilot key commands to None and let user decide
Yep, this sounds like a great solution, will do!
fix this please, not cool to go killing users ability to use paid for extensions.
In my experience, code generated by Copilot inline chat is good as Cursor CMD + K with GPT-4 model, but way quicker than Cursor. Since Copilot cannot specify the scope like Cursor with @, the answer of Copilot Chat is not as correct as Cursor Chat. I also found that after disabling Copilot suggestions, I got a smoother coding experience, only use AI whenever I want.
It's ok to not have Copilot Inline Chat since we have CMD + K already, but I also preferred using Copilot Inline Chat before subscribing the Pro plan.
Experiencing this too with "Quick Fix" => "Fix With Copilot" when hovering an error : "command 'inlineChat.start' not found"
I believe the huge use case is savings with small easy fixes. I got a 50$+ OpenAI bill this month, never had more than 10$ with Plain VSCode & Copilot
For complex problems, Cursor is way better. 100% worth it (even 50+$). But it uses so much context that your OpenAI bill blows up without always being useful.
I got to fix many problems in a old repo, used "AI fix in chat" repeatedly, got a 10$ bill just for that day. There were mainly self contained type inconsistencies so not that hard to fix, I could probably have saved 8$ that day alone.
Update : I just checked, in the same workspace with the same extensions it works with plain VSCode
Both VSCode & Cursor are updated
Please reenable this with no keyboard shortcut mapped (to resolve the collision issue). I need this as well.
@truell20 With VS Code Speech, we can use Copilot Inline Chat to edit by speaking, this is another thing that we cannot do with cmd + K.
We need it back as well. We love the strengths of Cursor, but we need Github Copilot too.
My team's switching back to vscode from Cursor now, but I'll keep testing Cursor and hope one day soon we can switch to Cursor.
Beeing able to choose between cursor and github copilot features would be great. hard-disabling a paid extension feature is not correct imho
What is the solution for the 'inlineChat.start' command not being found?
I have copilot chat installed in Cursor
¿Te interesa saber cuándo usar el chat en línea de Copilot? Supusimos que los usuarios de Cursor no estaban interesados en usar esa función, así que la desactivamos para evitar conflictos de comandos de teclado.
Sin embargo, estaré encantado de considerar un cambio si la gente lo desea.
podria ser util
Curious when you'd want to use Copilot inline chat? Assumed that Cursor users weren't interested in using that feature, and so, we turned it off to not have key command collisions.
Happy to consider a change if people want it back on though.
please do your max , to fix it , thx a lot