No more Apply in Ask mode?

for the longest time my workflow has been the following:

i would include some files in the context alongside my chat query while on ask mode, hit enter, the AI thinks and chats then proposes code changes, each file to change would be in its own code block container and each block would have an “apply” button.

now, after i send the query and the response arrives, code blocks don’t have an “apply” button, instead there is an “apply” button at the bottom.

let me start by saying i don’t like this change, i would rather have each block have its own button because sometimes i like certain changes and not others.

but the real problem is that after clicking the “apply” button, i immediately get a cancelled “x” next to each code block:

”reapply above” does nothing

what’s more is that the code block windows are now small, can’t be scrolled inside with the scroll wheel unless you select-scroll (not that you can see anything at this size container).

the last line says “switch to agent mode” but i don’t want that, i liked my workflow, i could review each proposition without having the AI open all the files at once and prompting me for all the changes.

Also i often get “streaming errors”, which crashes the query, very annoying but at least in ask mode i could resend it, if i’m in “agent mode” and this happens mid-changes then it gets really convoluted to take it from there with a new query and explain that some files may have already been changed, again this worked super well in “ask mode” for the last 6 months.

is this a change or a bug ?
i’ve been struggling with this for 2 days.

using Gemini pro 3.0 with my own api key, all of that worked great for the past 6 months.

good question, previously, in my case, it was 50% can apply, 50% cannot apply
I have not seen the option to apply in a while
it could be there are multiple tools, one shows the code, one shows the code and can apply and models just choose the wrong one
or was removed, would be good to know

i get this about every 3 out of 4 times, sometimes in the middle of the agent doing its thing which complicates things a lot… then i hit retry and the agent doesn’t understand why half the code is already changed, does things wrong.

at least in Ask Mode, if that were to happen, i could still reapply as the generated code would be all pre-generated before starting to apply changes.

This error happens because the api key you are using has reached a rate limit. I assume you use a custom api key with cursor and you get 429 which is too many requests from the ai api (outside of cursor)

it wasn’t a problem before with my workflow, which leads me to believe that cursor is internally sending more “bursts” requests, i don’t think we can change that behaviour, i’m mostly including it here to vent and to show how certain issues that we’re ok in ask mode are harder to deal with in agent mode

Hey, thanks for the report.

This is a known issue, and the team is already working on a fix. In a recent update, the Ask mode system instructions were changed so models no longer include file paths in code blocks, and because of that Apply doesn’t work.

Related reports:

About the streaming errors, this is caused by rate limits on the Gemini API side. If you use your own API key, the limits depend on your Google Cloud plan.

Unfortunately, the workaround using formatting rules for code blocks doesn’t work right now because it conflicts with the system instructions. Until a fix is shipped, the only options are to use Agent mode or copy the code manually.

I’m also frustrated with the apply button issue; I feel more in control of my code when I apply it manually.