Cursor 0.51.1: Small Version, Big Update!
Cursor 0.51.1 update, a small version brings big changes! The interface function is fully upgraded, and the experience is greatly improved!
Core content:
1. A new model drop-down menu is added to the chat window, and the setting interface is fully reconstructed
2. Added independent Rules setting panel and memory function, and the relevance is enhanced
3. Asynchronous programming of background tasks in the cloud, and the background management page is updated
Today, Cursor 0.51.1 was officially released. Although it is a small version, it has many updates from the interface to the functions.
In the chat window, a new order list for adding models is added to the model drop-down menu.
The new settings interface has been completely reconstructed with configuration options. The interface is divided into blocks, making settings more convenient.
Added an independent Rules settings panel and a new memory function, which is only available when the privacy mode is turned off. This function can automatically generate relevant rules based on the conversation. This means that as our project iterates, it will automatically create corresponding rules.
After a new conversation is started, the relevance to the old conversation is enhanced, and it will not start from the beginning again, which greatly improves the overall experience.
After the 0.51.1 update, background tasks are available. Background tasks are a new cloud-based asynchronous programming service launched by Cursor. In a word, you can push your existing code tasks to the cloud virtual host for editing.
However, the use of background tasks has strict requirements. For Cursor 0.51 version of Background Mode, the privacy mode must be turned off, the access rights to the code base must be enabled, and the max model (charged by Token) must be used.
Although the fee is charged according to the amount of tokens used, it is currently based on the price of an opus4. In addition, the process is completely unreliable and there is a high probability that a problem will cost you more than a dozen dollars. It is recommended to use it only when things are particularly difficult.
The general process of background management tasks (Background Mode) is as follows: start a remote cloud development container, work in it, and submit a branch after completion.
The corresponding official backend management page has been updated, and the usage records will be displayed in the form of charts, which can effectively count the usage within a fixed time period.
So overall, although this is a small version update, there have been significant improvements and upgrades from content to functions to interface to background management!
