This was revealed by the CEO of Duolingo, one of my most frequently used apps, through a company-wide email. (Link) The company will transition to an "AI-first" organization, and AI utilization will be included in hiring and evaluation criteria.
When I first used AI tools that help me as a developer (github copilot, cursor, etc.), my feeling was literally "this can help me." However, in just a few years, these tools have given me the feeling of "this can do work instead of me." And for good reason - I just throw some context and a few lines of code, go to the bathroom, and come back to find it has implemented everything on its own..
While I'm not without fear that AI might replace me, more than that, I want to become a better developer who is needed by my team by utilizing AI better, so I plan to research with more interest than I currently do.
This post is a simple translation and understanding of the cursor 0.50 version changelog that my company started using as a paid service. Including myself, fellow developers are also going back and forth with cursor, oscillating between "it works well" vs "it's stupid," so I want to use it better.
A unified pricing policy has been launched to prevent user confusion.
I didn't know about this since I haven't used max mode or long context mode, but previously there were different billing methods for each model, and additional costs were incurred depending on additional modes, making it difficult for users to accurately understand their usage and costs. (Reddit user who lost $30 by having multiple "edit" requests classified as "premium-tool-call", "claude-3.7-sonnet-max" despite using Agent mode)
Max Mode
- Enables use of all features of the latest AI models
- The biggest difference from normal mode is that Max Mode is optimized to consider as much context as possible at once
- Provides "larger Context Window (the range of context AI can refer to at once)", "200 tool calls", and "ability to read up to 750 lines of code"
Max Mode can now be used with all latest models. Billing is based on the number of tokens used, and when new models are released, they will be immediately provided through Max Mode. (This seems to indicate that the pipeline from model release → service integration with pricing policy is well established)
A new Tab model that suggests changes across multiple files! (The model that enables the feature where you press TAB to apply cursor's suggestions) It enables refactoring, cascading modifications, multi-file editing, and movement between related code.
Cursor agent can now operate in the background. (Settings > Beta > Background Agent)
This allows multiple agents to work in parallel and efficiently handle large-scale tasks. Each agent runs in an independent environment, reducing local resource burden. Also, you can monitor work status in real-time and intervene whenever necessary.
Although it's still a beta feature, the cursor team found it useful for bug fixes, investigations, and drafting (quite long) PRs.
You can add your entire codebase to the model's context using @folders.
(Full folder contents must be enabled)
However, if folders or files are too large, they may not be included.
The UI for Inline Edit (asking and editing directly in code) has been redesigned, and new options have been added.
The agent can now find and change only necessary parts without reading entire files, improving editing speed for long files. Looking at the example video of editing Postgres codebase files, search & edit operations became almost twice as fast. It will be applied to Anthropic models first, then gradually to other models.
This is a feature I'm personally curious about and think will be useful. When I request edits, it finds related code → finds related files → if importing libraries, it reviews those too... and often I don't get the answer I want. I should experience this once.
You can manage multiple codebases in one workspace (!) This can be effectively used when multiple projects are in different folders (!!) It even supports .cursor/rules added to each folder (!!!)
I often need to work on multiple codebases simultaneously and review modifications from various angles, and this is exactly the feature I need most. I haven't actively utilized rules yet, but I should quickly create them, test, and share with my team!!
Sharing in markdown format and duplicating existing chats is now possible.
Duplicating existing chats means it's now possible to keep the path of existing conversations intact while exploring different paths in new conversations. Like Doctor Strange examining all possible futures through the Time Stone.

What I thought was just a simple update note turned out to be very interesting and surprising as I read about how actual developers work being added as features. Of course, other IDEs are probably adding amazing features daily and competing, but I'm excited to see what features cursor will surprise us with in the future.
Side note #1) I need to quickly create cursor/rules for each project. There's significant time consumption every time I start a new conversation. It's like going on a blind date and introducing yourself for the first time..
Side note #2) The cursor blog is really well written. Of course, a blog with technically deep content would be difficult, but in the case of this changelog, it simply describes what the changes are in a plain manner, so it didn't take even two hours to read and understand the article.