Fails to register cursor-agent provider

[jmmaloney4]

Describe the bug

Fails to register cursor-agent provider:

nix shell github:numtide/nix-ai-tools#goose-cli github:numtide/nix-ai-tools#cursor-agent

goose configure

This will update your existing config file
  if you prefer, you can edit it directly at /Users/jack/.config/goose/config.yaml

┌   goose-configure
│
◇  What would you like to configure?
│  Configure Providers
│
◇  Which model provider should we use?
│  Cursor Agent
│
◇  Model fetch complete
│
◇  Enter a model from that provider:
│  gpt-5
│
◇  Request failed: Command failed with exit code: Some(1)
│
└  Failed to configure provider: init chat completion request with tool did not succeed.

My cursor-agent is logged in:

cursor-agent status
 ✓ Login successful! Logged in

To Reproduce
See above.

Expected behavior
No error, or at least a more informative error message.

Screenshots
If applicable, add screenshots to help explain your problem.

Please provide following information:

• OS & Arch: macOS 15.6.1
• Interface: CLI
• Version: 1.7.0 (cursor-agent version 2025.09.04-fc40cd1)
• Extensions enabled: none
• Provider & Model: cursor-agent

Additional context
Add any other context about the problem here.

[cbruyndoncx]

please EDIT fill out the template , not all linux versions are working/supported equally. I am working on provider bugs right now in v1.7.0

[jmmaloney4]

@cbruyndoncx Edited. I'm actually on macOS. Let me know if any other information would be helpful.

[justyns]

I'm running into a similar issue with similar versions on macos as well.

• gpt-5 gives the Failed to configure provider: init chat completion request with tool did not succeed. error in OP
• claude-4-sonnet doesn't give an error, but hangs on Checking your configuration... and never seems to go past that

I also see the "Model fetch complete" message before entering a model, but there's no selection/auto-complete for the model names.

[castilloadrian]

Any update on how to get this working?

[bharmann]

@castilloadrian @justyns @jmmaloney4

Had the same issue - I did several things and not sure which worked, so here's the list:
Verify permissions are: your username:staff in ~/.config/goose

cd ~/.config
ls -al

and also for all the files inside that goose folder, mainly: config.yaml

cd goose
ls -al

I just applied the ownership recursively down:

cd ~/.config
sudo chown -R <yourusername>:staff goose

Probably unnecessary but I added execute permissions as well

chmod -R +x goose

Make sure you have the env variable set for cursor-agent in your ~/.zprofile or ~/.zshrc

export CURSOR_API_KEY="your key"

Quit and reopen your terminal or reload using:

source ~/.zprofile
 or 
source ~/.zshrc

depending on which you edited.

Logout and back into cursor agent using the api-key

cursor-agent logout
cursor-agent --api-key <yourapikey>

Directly edit the goose config file:

open ~/.config/goose/config.yaml

GOOSE_PROVIDER: cursor-agent
GOOSE_MODEL: auto

or gpt-5 or whichever you want

Save

I then wanted to check so I ran:

goose-configurw 
• configure provider

cursor was already selected but model showed gpt-5 (default) so I typed auto again.

It succeeded for me that time.

If you don't have success with any of those ^ I did do one other thing, but I would only do this if it's still not working after trying the above. I still have to go back and reverse all this to see what worked and what isnt necessary, but till I do that:

Go to system preferences -> privacy & security.

You will need your goose app or binary file/location
If you are using the desktop goose, then you will be selecting /Applications/Goose.app`.
If using the goose cli, find the actual binary location:

which goose

Open the path that it displays without the trailing goose
For me it was:

open /opt/homebrew/bin

Then find goose listed which will be an alias and right click to show original.
Keep the folder with the goose binary open, then for the following sections, click + and drag the app or binary into the open dialog window and select open after selecting the file in the correct path.

Full Disk Access
Accessibility
App Management <- I don't think you need this one, but I added it cause I was tired of testing scenarios

With those permissions enabled, try the above again and hopefully something sticks.

Best of luck

[DOsinga]

@roshbhatia I think you contributed the original code here. any thoughts?