# Self hosted cloud agents don't respect model selection

**URL:** <https://forum.cursor.com/t/self-hosted-cloud-agents-dont-respect-model-selection/159529>\
**Category:** Bug Reports\
**Tags:** max-mode, cloud-agents, anthropic\
**Created:** [May 1, 2026, 3:19am UTC](https://forum.cursor.com/t/self-hosted-cloud-agents-dont-respect-model-selection/159529 "2026-05-01T03:19:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jordansimsmith-canva](https://avatars.discourse-cdn.com/v4/letter/j/c4cdca/32.png) [@jordansimsmith-canva](https://forum.cursor.com/u/jordansimsmith-canva)\
**Post date:** [May 1, 2026, 3:19am UTC](https://forum.cursor.com/t/self-hosted-cloud-agents-dont-respect-model-selection/159529/1 "2026-05-01T03:19:11Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

When creating a agent (self hosted cloud agent) from the cursor 3 desktop UI, it does not respect the model that I chose in the dropdown. I selected claude-opus-4-7-thinking-max but from the usage page I can see that it defaulted to “auto”, and from the web ui I can see that it was GPT 5.5 Medium under the hood.

When repeating the steps from the web ui, the model choice is respected.

I have also set my default model preference to Opus 4.7 in the cloud agents settings page.

### Steps to Reproduce

1. Open cursor 3 desktop
2. select self hosted cloud agent mode
3. select model claude-opus-4-7-thinking-max with MAX mode on and AUTO mode off
4. submit prompt
5. check usage page

### Expected Behavior

expected - usage says model is opus 4.7  
actual - usage says model is “auto”

### Screenshots / Screen Recordings

 ![Screenshot 2026-05-01 at 3.18.16 PM.png](https://us1.discourse-cdn.com/cursor1/original/3X/0/8/08217b95e4c9516c02085ee1fc4d1df5349e112c.png)

### Operating System

MacOS

### Version Information

Version: 3.2.16 (Universal)  
VSCode Version: 1.105.1  
Commit: 3e548838cf824b70851dd3ef27d0c6aae371b3f0  
Date: 2026-04-28T21:07:47.682Z  
Layout: glass  
Build Type: Stable  
Release Track: Default  
Electron: 39.8.1  
Chromium: 142.0.7444.265  
Node.js: 22.22.1  
V8: 14.2.231.22-electron.0  
OS: Darwin arm64 25.4.0

### For AI issues: add Request ID with privacy disabled

bc-dfddc317-2833-453a-b73c-a6fbd8979a97

### Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

---

<div class="post-metadata">

**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\
**Post date:** [May 1, 2026, 11:31am UTC](https://forum.cursor.com/t/self-hosted-cloud-agents-dont-respect-model-selection/159529/7 "2026-05-01T11:31:17Z")

</div>

This is a known bug with cloud agents launched from the Cursor desktop (Glass) UI. A fix has been merged to our main branch, but hasn’t landed in the 3.2.x release you’re on. You should see this resolved in a future update.

In the meantime, launching cloud agents from the [web UI](https://cursor.com/) works correctly with model selection, as you’ve already found.

You might also find these related threads from other users helpful:

- [Different models appearing for agent in cloud web vs. desktop](https://forum.cursor.com/t/different-models-appearing-for-agent-in-cloud-web-vs-desktop/158238)

- [Agents Window Agents using incorrect models/modes despite explicit model selection](https://forum.cursor.com/t/agents-window-agents-using-incorrect-models-modes-despite-explicit-model-selection/157476)
