Gemini Code Assist agent mode doesn’t work in Cursor (works in VS Code / Antigravity)

[JimKarter]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Hi, I’m having an issue where Gemini Code Assist’s agent mode only fails in Cursor, while it works fine in other VS Code–compatible editors.

Steps to Reproduce

1. In Cursor, disabled all extensions.

2. Enabled only the official Gemini Code Assist extension.

3. Tried to start agent mode from the extension UI.
   → Agent mode does not start.

To double-check, I installed the same Gemini Code Assist extension in:

VS Code

Antigravity (a fork of Windsurf, which itself is a fork of VS Code)

In both of these, agent mode works normally with the same settings.

Expected Behavior

Gemini Code Assist’s Agent Mode works perfectly as same as other IDEs.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.50 (user setup)
VSCode Version: 1.105.1
Commit: 56f0a83df8e9eb48585fcc4858a9440db4cc7770
Date: 2025-12-06T23:39:52.834Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

Additional Information

Error in Cursor

On Cursor, when I try to start agent mode, I consistently get this error:

command 'geminicodeassist.startagent' already exists

I do not have Gemini CLI installed on this machine, so (as far as I understand) there shouldn’t be any duplicate command registration coming from a CLI integration.

Also, non-agent features of Gemini Code Assist (normal completions / inline usage) work in Cursor.
Only agent mode is broken.

Related report

I found an existing report that seems to describe the same issue:

Gemini code assist in Cursor doesn't work in agent mode

Thank you for the clarification. This sounds like an issue with the extension itself. We have so far not received similar reports, but it is possible that others experience the same issue. Do you see any errors at Help > Toggle Developer Tools > Console, you can share them here.

From my side, it looks like something specific to Cursor’s extension host or command registration is preventing geminicodeassist.startagent from working, even when Gemini Code Assist is the only enabled extension.

If you need logs or a specific diagnostics command run from Cursor, I’m happy to provide them.

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, thanks for the report. The command geminicodeassist.startagent registers 3 times on extension activation, which causes a conflict.

For final diagnostics, please let me know:

1. Open CTRL+Shift+P > Developer: Show Running Extensions - do you see duplicate Gemini Code Assist entries?
2. Help > Toggle Developer Tools > Console - copy all error messages (a screenshot is fine).
3. Output (bottom panel) > select “Log (Extension Host)” - copy the full log from Cursor startup.
4. Confirm that all other extensions are disabled (except Gemini).

Also try:

• Completely remove the extension
• Restart Cursor
• Reinstall the extension
• Developer: Reload Window

If this doesn’t help, confirm the details above and I’ll pass it to the team.

[JimKarter]

1. No
2. log.zip (6.5 KB)
3. see log.zip
4. created new profile which uninstalls all extensions except laungage pack
5. >Completely remove the extension → see 4., reinstalled gemini code assist, but same “already exists” error
6. >Restart Cursor → no help
7. >Reinstall the extension → no help
8. >Developer: Reload Window → no help

[JimKarter]

new profile log (both developer console and extension host)

new-profile-log.zip (3.5 KB)

[JimKarter]

Did you pass this issue to Cursor engineer team? No replys posted here SO I’m confused.

[JimKarter]

anything progress?

[untoldstory (Garth Cooper)]

I have the same issue, please provide and update

[JimKarter]

Dean Rie, can you share the progress with us? Thanks!

[JimKarter]

so quiet here. come on.

[TigerHead]

It seems that you and I might be the only two people on the entire internet who have encountered this issue. Even AI tools couldn’t resolve it. (Although in my case, it’s VS Code.)

I’m not sure whether this will be helpful to you, but I’ll share my solution anyway.

I ran into this problem after installing a certain version of VS Code. The workaround was to manually execute the command geminicodeassist.startagent, which triggered the error shown in the screenshot.

After investigating, I discovered that in my installation directory, the bin folder was not located inside the hashed subdirectory where it was expected to be, but instead was placed in the program’s root directory. After manually copying the bin folder into the corresponding hashed directory, the issue was resolved and Agent mode started working normally again.

[JimKarter]

How do I run the command ‘geminicodeassist.startagent’ manually? where is it?

[JimKarter]

Oh, it is command palette (Ctrl+Shift+P)

[JimKarter]

[JimKarter]

So I copy and pasted bin folder from C:\Users\UserName\AppData\Local\Programs\Microsoft VS Code to C:\Program Files\cursor and then exexuted restart window command.
And Boom! Agent mode works! Thanks!

[TigerHead]

Haha, I’m glad it helped. There’s another person in this thread, “Garth Cooper,” who seems to be experiencing the same issue as well. I’ll try to @-mention him, though I’m not entirely sure how to do that here.

@untoldstory