Where does the bug appear (feature/product)?
Cursor CLI
Describe the Bug
I am user of the PRO Account of Cursor and leveraging Cursor CLI in Windows WSL. It appears that when I login to cursor CLI it does not pick up my Pro Account.
Steps to Reproduce
Here’s the step to Reproduce:
It’s still defaulting to openai:gpt-4o-mini because something on your system is pinning that model (an alias, env var, or a config file that the agent actually reads). Let’s nuke whatever is forcing it and hard-set GPT-5.
Do this in your Ubuntu (WSL) terminal
- Find what’s forcing 4o-mini
Is there an alias or function shadowing it?
type -a cursor-agent
alias cursor-agent || true
Any env vars telling it which model to use?
env | grep -iE ‘cursor|model’ || true
Any config files containing 4o-mini (Linux home + current folder + Windows home)
grep -Rni ‘4o-mini’ ~/.config ~/.cursor . /mnt/c/Users/ADMIN 2>/dev/null | head -n 50
If you see hits, delete or edit those files/lines. For example, remove any alias lines from ~/.bashrc, and delete configs that mention 4o-mini.
- Remove all possible configs and caches
Linux side
rm -rf ~/.cursor
rm -f ~/.config/cursor/config.json
rm -f ~/.cursor/config.json
Windows side (sometimes Cursor picks these up if you start in a Windows path)
rm -rf /mnt/c/Users/ADMIN/.cursor
rm -rf /mnt/c/Users/ADMIN/.config/cursor
-
Recreate a clean default (GPT-5) in both expected locations
mkdir -p ~/.config/cursor ~/.cursor
printf ‘{ “defaultModel”: “gpt-5” }\n’ > ~/.config/cursor/config.json
printf ‘{ “defaultModel”: “gpt-5” }\n’ > ~/.cursor/config.json -
Make a hard override alias (bulletproof)
remove any old alias lines
sed -i ‘/alias cursor-agent=/d’ ~/.bashrc
add a forced-model alias
echo “alias agent=‘cursor-agent --model gpt-5’” >> ~/.bashrc
source ~/.bashrc
- Re-auth fresh and test
cursor-agent logout || true
agent # this runs cursor-agent with --model gpt-5
Error: You’ve hit your usage limit for GPT-5
Get Cursor Pro for more Agents use, unlimited Tab, and more.
fallbackModel: default
spendLimitHit: false
chatMessage: You’ve hit your free requests limit. Upgrade to Pro for more usage, frontier models, Background Agents, and more. Your usage limits will reset
when your monthly cycle ends on 9/18/2025.
Expected Behavior
I should be able to use Cursor CLI with the capabilities of my cursor pro account.
Screenshots / Screen Recordings
Operating System
Linux
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.4.5 (user setup)
VSCode Version: 1.99.3
Commit: af58d92614edb1f72bdd756615d131bf8dfa5290
Date: 2025-08-13T02:08:56.371Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100
Does this stop you from using Cursor
No - Cursor works, but with this issue
