Hey, thanks for the report. What you’re seeing is how Multitask works right now, even though it’s not obvious.
Turning on Multitask changes how a single prompt runs. The agent offloads work to background subagents. It does not make every new message start its own parallel task. If you send a second message while the first turn is still running, it follows the New Messages setting. With Queue, it waits in line. With Interrupt, it stops the current run and replaces it.
To run things in parallel:
In the Agents Window, open Settings → Agents → Conversation and set New Messages to Queue, not Interrupt. That way a quick follow-up won’t stop the current task.
When a message is sitting in the queue, click Start Multitasking on the queue. This moves the current task to a background subagent and frees up the agent for the next message. You can also start a message with /multitask.
One more thing. You’re on 3.17.8, and that version has a separate issue where the chat can keep queueing messages even when the agent is idle. Please update to the latest version, currently 3.18.25, and let me know if the queue behavior still looks odd. Ideally include a screenshot of the New Messages setting.
Thanks for the screenshots. I can see the queue with the option 1 chip and a running task, that’s the exact queue behavior I mentioned.
But the settings screenshot you shared is from a different section Run Mode, File/External Protection, Web Search, etc. The setting that controls queue behavior is here:
Settings > Agents > Conversation > New Messages
Set it to Queue, not Interrupt. With Interrupt, a new message stops the current task, which looks like what you’re seeing. Please send a screenshot of that specific setting so I can double check.
One more thing: you’re still on 3.17.8, and that version has a separate issue where the chat can keep adding messages to the queue even when the agent is idle. Update to the latest version, it’s 3.18.25 right now, then test again.
To actually run things in parallel: when a message is in the queue, click Start Multitasking on it. That moves the current task into a background subagent, and the agent takes the next message. You can also start your message with /multitask.
Let me know how it goes after updating and switching the setting to Queue.
Open the menu via the gear icon Settings in the top right, or go to Help → Check for Updates. Cursor will download the update and ask you to restart.
If it does not show an update, download the latest version from https://cursor.com and run the installer over your current install. Your settings and data will stay, it will just update the version.
After updating to 3.18.25, check that in Settings > Agents > Conversation the New Messages value is set to Queue, not Interrupt, then test Multitask again. If the queue behavior still looks weird, send a screenshot of that exact setting and I will take a look.
3.18.25 (user setup) i have this and is still continue the same problem i change my parameter ! and is still do the same i cant send 2 task in the sametime without interruption
Thanks, I can see from the screenshots that you updated to 3.18.25 and switched New Messages to Queue, that’s correct.
One important detail that’s easy to miss: switching to Queue alone isn’t enough to make tasks run in parallel. Multitask changes how a single prompt runs, it doesn’t automatically make each new message start as a separate parallel task. To actually run two tasks at the same time:
Send the first task.
While it’s running, send the second one. With Queue enabled, it will wait in the queue and won’t interrupt the first.
On the queued message, click Start Multitasking. This moves the current task into a background subagent and frees the agent to take the next message. Alternatively, start the message with /multitask.
Quick check: are you clicking Start Multitasking on the queued message? If yes, and the second task still interrupts the first with Queue enabled, please send the Request ID for that session right top corner of the chat > Copy Request ID. With that, I can share the exact case with the team to investigate.
