I need to change the default mode, it’s really affecting my workflow having to change to ask mode every single time.
26 Likes
What’s not working well in Agent mode that makes you want to switch? This would help me understand if there might be a better solution or if we should look into the settings to change the default
1 Like
I only need Ask Mode. However, when I highlight code and press CTRL + L, it doesn’t start a new chat—it simply brings up an old one. Then I must click the + icon and paste my code into a new chat, which is extremely frustrating.
I’ve already contacted support by email. They said there’s no option to change the default mode in the latest update, so downgrading isn’t possible either.
I’m not interested in Agent Mode. As a developer, I only consult AI when needed; I don’t require it to take over completely.
15 Likes
Just made a new topic regarding this before I saw this; I think the issue is just that the mode defaults to Agent, the most intrusive capability. Additionally, it switches back to Agent from “Ask” whenever code is explicitly added to the context by the user (“Add to Chat”).
I’ve gotten some work done with Agent, but mostly just play projects that can handle loads of spaghetti code.
With my real codebase I like to, and need to, handhold the assistant with very targeted queries and changes; this prevents the frequent and unacknowledged deletions that Cursor likes bundle with actually requested changes.
9 Likes
This is exactly the issue I’m facing.
1 Like
The agent mode is horrible, it starts going off in infinite loops, trying to fix eslint errors, typescript errors, and other non-relevant stuff. The agent mode is perhaps useful for non-technical people who apply everything, or “vibe coding”, but this is not applicable for serious work. I often have to go through several chat iterations before the suggested code is useful, and I don’t want to apply the intermediate steps. Please give us a setting.
12 Likes
Luckily I was able to grab the 0.45.15 version from their official website and I managed to downgrade from 0.46.4. I’m happy now.
3 Likes
spends way too much time caring about typescript and eslint errors and frequently gets stuck in a loop. code is not great, you usually have to massage it in normal mode, sometimes rejecting solutions and iterating on the prompt with additional instructions. it is not smart enough to just do everything on its own for anything serious using already long established codebases. we’re using cli tools like doppler and in mono repos where the commands are not always run in the same location. dont want agent mode at all tbh, have tried it multiple times and every time had to turn it off.
also, it doesnt work with jupyter notebooks at all. so a common thing will be to use chat to handle scripts to paste into jupyter and run them ourselves, and then using composer normal mode in the next tab over to handle building out features outside of notebooks concurrently.
this update completely breaks our workflow. have to revert this
2 Likes
dupe/merge with How can I change default Chat mode as Ask, not Agent
1 Like
Same here, anything that I throw to the chat gets the agent mode… no way man!
Exaaaaactly.
4 Likes
I agree with this completely, came to the forum looking for exactly this. I only like to use ask mode as a software dev. I think agent mode caters better to those that aren’t software devs but rely on AI to generate all of the code IMO. Not trying to sound elitist but I think prof software devs would generally prefer ask mode for the greater flexibility.
3 Likes
I did the same but keeps auto-updating. any solution for that?
The problem with the agent is that it goes into a long sequence of hallucinations and keeps trying things which clearly do not make any sense.
The agent takes “the human” out of the loop. Which is a bit of a blunder tbh.
We need a helping hand, not an AI going on autopilot clobbering changes and clearly going in circles or barking up the wrong tree.
The earlier clear separation of compose vs chat was a nice sweet spot.
Kill The Agent please! Or at least let us configure it ourselves and I’ll happily kill it locally for you 
Nice product btw, keep at it.
8 Likes
Also, to add a bit more.
As someone earlier said, I am in Ask and then later it automatically switches to Agent. Not nice.
One last thing, the Ask (previously chat) had green/red highlighting which was nice. Can we get that back as well please?
4 Likes
I get the frustration with Agent mode switching back automatically - it’s definitely not ideal for many workflows.
Regarding the green/red highlighting in Ask mode - I’ll pass this feedback to the team. There isn’t currently a way to restore this specific feature, but it’s good to know users found it valuable.
The team is aware of the strong preference many developers have for Ask mode, and I’ll make sure this gets proper attention.
8 Likes
Latest client: Wont edit a long python script I originally created with cursor. Seems to be a context issue is my guess. It gets stuck on generating and fails. If I switch to edit mode cursor has no issue.
Whats weird is I swear I created this script with agent mode enabled in the older client. Agent mode in new client doesn’t show the before/after code changes in chat window (what used to be composer). Only way for me to see before/after in chat is edit more now?
How long will it take till it gets proper attention?
3 Likes
Hey, we are ironing out a couple issues with the Agent, mainly due to the usage issues with the Anthropic models, but this should be much better very soon, if not already.
Agent should definitely show a before and after, here’s what it looks like on my end:
1 Like
Regarding the keyboard shortcut, this is a regression here we should have fixed soon.
In the meantime, you can do CMD+L to open the chat window, CMD+N to start a new chat, and then CMD+L again to switch that new chat (which will have defaulted to agent) back to ‘Ask’ again!