Last week, Cursor quietly rolled out version 3.1, with the key new feature being split-screen multi-Agent functionality. As a user who started using Cursor 3.0 right after its release, I’ve been testing it on and off for a full two weeks. Today, I’m sharing my honest thoughts on what exactly has changed in this highly anticipated Agents Window, and whether average developers should take the time to upgrade.

Let’s Cut to the Chase: The Final Verdict

The most core change in Cursor 3 is a complete overhaul of the IDE’s interaction logic. Previously, opening Cursor would show you nothing more than a file tree, editor, and terminal—nearly identical to VS Code, essentially following a “human-led, AI-assisted” model. Now, simply search for “Agents Window” via the Cmd+Shift+P shortcut, and you’ll see a row of independent Agent cards, each working autonomously in its own workspace without constant supervision.

Put plainly, Cursor’s positioning has shifted from “you write code, AI fills in the gaps” to “you assign tasks, Agents work full-time on your behalf”, delivering an exceptional multi-tasking parallel experience.

Hands-On Impressions of Agents Window: Split-Screen Is the Standout Feature

The layout of Agents Window is straightforward: the left side displays an Agent list clearly showing all running Agents, while the right side is the workspace for the selected Agent, where you can view its operation progress in real time. The split-screen feature added in version 3.1 is incredibly practical. I often open two or three Agents at once, monitoring front-end component development on one side and back-end API coding on the other, with no need to switch windows back and forth—resulting in a remarkable boost in efficiency.

Each Agent has clear status indicators: Thinking, Coding, Awaiting Confirmation, and Completed, making progress easy to grasp at a glance. More importantly, multiple Agents can run simultaneously, working in independent worktrees without interfering with one another—a stark contrast to the previous single-threaded Agent mode, where you had to wait for one task to finish before assigning the next. True multi-tasking parallelism is now achieved, equivalent to having several junior developers working for you at the same time.

Two-Week Test: These 3 Scenarios Work Best

1. Simultaneous Front-End and Back-End Development Doubles Efficiency

I recently worked on a project that required adding a user feedback feature. In the past, I would have to write the back-end API first, debug it, then code the front-end form page—this sequential process took at least 10 minutes. Now I simply launch two Agents with clear task divisions:

• Agent A: Writes the POST /api/feedback API, accepts the content and rating fields, and implements database storage functionality.
• Agent B: Develops the feedback form component, including a text input field and star rating selector, adapted to the overall page style.

The two Agents work in tandem, modifying code in separate worktrees, and finish in just three to four minutes. I only spend one minute reviewing the code and merging branches, wrapping up the entire task in under five minutes—saving more than half the time compared to before.

2. Design Mode UI Annotation Eliminates “Ineffective Communication”

This feature hits the pain point of front-end developers perfectly. Previously, describing UI modification requests to AI required tedious explanations like “the button in the third row of the page” or “the icon on the far right of the navigation bar”, and even after lengthy descriptions, the AI would often modify the wrong element.

Now, enable Design Mode (shortcut ⌘+Shift+D), open the page in a browser, and directly click the element to modify, annotating “change this button to blue” or “reduce spacing by 5px”. The Agent can directly identify the annotated DOM element without extra descriptions, greatly improving modification accuracy. It also supports Shift+drag to select areas and ⌘+L to add elements to the chat box, making operations incredibly smooth.

3. Remote Task Assignment via Mobile Phone Makes the Most of Commute Time

Cursor 3 supports launching Agents from mobile devices, the web, Slack, GitHub, and other channels—a feature I found extremely useful in real use. Last week during my subway commute, I suddenly realized the installation steps in the project README needed updating with Docker deployment instructions, so I assigned the task to an Agent directly on my phone.

When I arrived at the office and opened my computer, the Agent had already submitted the revised content, waiting for my confirmation and merge, with no disruption to my work. Going forward, any code changes I think of during my commute can be assigned to Agents immediately instead of jotting them down in a memo; I can review them right at my desk, making full use of fragmented time.

Frequently Asked Question: Cursor 3 vs. Claude Code—Which to Choose?

This is the question I get asked the most. Based on my two weeks of usage, here’s a practical reference:

Cursor 3 is better suited for developers who prefer working within an IDE, with fast visual feedback. It excels at front-end development, daily small feature development, and team collaboration—especially the split-screen multi-Agent feature, which drastically cuts down waiting time. Claude Code, on the other hand, caters more to terminal users; it has a deeper understanding of codebases and greater autonomy when handling complex projects and cross-file refactoring.

I now use both tools in tandem: Cursor 3 for daily bug fixes and small feature development, as it’s efficient and hassle-free; Claude Code for large-scale code refactoring and cross-file modifications. The combined monthly cost of both tools is $40, which isn’t cheap, but if you code for more than 4 hours a day, the time saved far outweighs the expense.

Pitfall Warnings: 3 Issues to Watch Out For

After two weeks of use, I’ve run into a few pitfalls—here’s a heads-up to avoid them:

1. Multi-Agent Conflicts: Although each Agent works in an independent worktree, conflicts still occur during merging if two Agents modify the same section of the same file. It’s recommended to define clear task boundaries when assigning work, and avoid having two Agents edit the same component or file simultaneously.
2. Rapid Quota Consumption: The Pro plan only includes 20 model quotas per month, and quota usage multiplies when running multiple Agents in parallel. I used up my entire quota in the first week, forcing me to use the free model for the next few days, which significantly worsened the experience.If you regularly use premium models like Claude Opus 4.6 or GPT-5.4, it’s advisable to connect to a third-party API platform to control costs. I personally use ofox.ai, which provides access to over 50 models via a single API with pay-as-you-go pricing, eliminating worries about monthly quota limits. Simply update the API endpoint in Cursor to use it (path: Settings → Models → OpenAI API Base URL → https://4SAPI.COM/v1). Additionally, XINGLIANAPI is another great option, offering low latency, high availability, and multi-model support with no complex configuration. It works seamlessly with multi-Agent parallel workflows, helping developers further manage costs.
3. Occasional Glitches in Design Mode: It relies on a browser extension, and sometimes annotated elements do not match the actual DOM, causing the Agent to modify the wrong part. However, this is a minor issue—refreshing the page and re-annotating usually resolves it.

Final Recommendation: Is It Worth Upgrading?

If you’re currently using Cursor 2.x, the upgrade is completely free—there’s no reason not to give it a try. Agents Window can be switched back to the traditional IDE view at any time without disrupting your existing workflow, essentially giving you an extra efficient tool at no cost.

If you’ve never used Cursor before, now is the perfect time to start. The Agents Window in version 3.0, paired with the split-screen feature in 3.1, delivers a polished multi-Agent parallel development experience that saves you countless hours on repetitive tasks.

Of course, a reminder: AI Agents are not omnipotent, and they will still make errors when handling complex business logic. I treat it as a junior developer capable of handling multiple tasks at once, with myself overseeing the overall process and conducting code reviews. With the right mindset, it’s an incredibly pleasant tool to use.

I’ll continue sharing hands-on experiences with AI coding tools like Claude Code, Cline, and Windsurf in the future. What tools do you use daily? Let’s discuss in the comments! Additionally, if you frequently develop with multiple models, give 4SAPI (4SAPI.COM) a try—its stable API service makes multi-Agent collaboration even smoother.