Hi @mohitjain — confirming this is **not yet fixed on the stable channel** for Windows users, and I think there may be a release-publishing issue worth checking.
**Environment**
OS: Windows 11 (build 10.0.26200)
Terminal: Windows Terminal + PowerShell
`cursor-agent --version` → `2026.05.16-0338208`
Same empty-list symptom as the OP (`Available models` header + `Filter:` render fine, list body is empty).
**Why “update to latest” doesn’t help on Windows yet**
I just re-ran the official Windows install command to try to pick up the fix:
So a fresh install / reinstall on Windows just reinstalls the same broken build. (Side note: on Windows the install also fails partway because `node.exe` and the `*.node` native modules in the existing version directory can’t be replaced while any `cursor-agent` process is running, which leaves the install in a half-broken state until manually repaired.)
Could you double-check whether the fix has actually been promoted to the stable Windows channel, or whether there’s a beta / nightly channel we should opt into in the meantime?
**Other observations that may help narrow down the bug**
`cursor-agent --list-models` (the non-interactive CLI flag) still returns the full model list correctly on the same machine, same account, same broken binary. So the bug is genuinely isolated to the TUI `/model` picker’s data path — server-side model availability and auth are fine.
Even the model marked `(default)` and the one marked `(current)` in `–list-models` are missing from the empty picker, so it doesn’t look like a filter / gating issue — the list really arrives empty.
Workaround confirmed for anyone blocked: launching with `cursor-agent --model ` (e.g. `–model gpt-5.5-medium` or `–model composer-2.5`) bypasses the broken picker and works fine.
I upgraded a few hours ago in my workstation and it was not working either for Windows and Ubuntu (via WSL). I asked hi at cursor dot com and I got a reply that it was a known issue.
I just tried to run agent update and no new version showed up, is there an ETA for the release? The latest version I can get is still 2026.05.16-0338208
Have had the same issue for at least a week now. It’s also impacting the ACP integration with Zed. The list of models is showing as “unknown”. Current version is v2026.05.16-0338208 but I believe it impacted the previous version too.
CLI Version 2026.05.16-0338208
Model Composer 2
Subscription Tier Enterprise
OS darwin (arm64)
Terminal warp
Shell zsh
Thanks for flagging it’s still happening on your end.
Quickest way to unblock yourself right now: launch with the model specified directly, which skips the picker entirely:
cursor-agent --model gpt-5.5-medium
Any model id works there - you can see the valid ones with cursor-agent --list-models.
To pin down what you’re hitting, could you share two things?
Your exact version from cursor-agent --version. The current published build is 2026.06.15-.... If update reports “already up to date” but you’re on an older build, the updater can occasionally get stuck on a stale binary - a clean reinstall via the official script at cursor.com will pull the newest one.
Whether cursor-agent --list-models returns the full list. If it does, the models are reaching you fine and it’s specifically the interactive picker not populating - a case we’re aware of and tracking.
Thanks for the detailed repro. The picker being empty while agent --list-models returns the full list tells us the models are reaching you fine and it’s specifically the interactive /model picker not populating, which is a known issue we’re still tracking (separate from the model list itself).
Two things:
To unblock you right now - launch with the model set directly, which skips the picker entirely:
cursor-agent --model gpt-5.3-codex
Any id from cursor-agent --list-models works there.
To try to get the picker itself working — fully quit cursor-agent, relaunch and wait about 5 seconds (this lets it pull the latest config), then quit and relaunch once more before running /model. This clears it up in a good number of cases.
If it’s still empty after that, let me know - and if you’re on a VPN, corporate network, or SSH session when it happens, mention that too, since a slow connection can also cause the picker to come up empty. That’ll tell us which side to dig into next.
This happens on every launch (15/15 sessions checked). The flat model list fetch succeeds; only the parameterized-models fetch times out at 2s, leaving the /model picker empty.
Startup also has a ~2s pause consistent with this timeout.
Workaround:cursor-agent --model <id> and Ctrl+/ model cycling work.
Suggested fix: increase parameterized fetch timeout, retry on timeout, or fall back to flat availableModels when parameterized fetch fails.
Thanks for the incredibly thorough writeup, your diagnosis is spot on. The /model picker’s catalog comes from a different fetch than cursor-agent models, and when that fetch doesn’t finish inside its short time budget (exactly the fetchAvailableModelsParameterized.timeout you’re seeing), the picker renders empty while the flat list still works.
This is a known issue we’re tracking. Your log evidence is genuinely useful here, especially the fact that it’s firing on every launch rather than intermittently, and I’ve logged your report with it.
Nothing on your end (a config change or update) resolves it right now, so --model <id> and Ctrl+/ cycling, which you’ve already found, remain the best way to work around it for now.
