Cursor 2.4 introduces several new features, including Subagents, image generation, and enhanced agent workflow tooling, designed to assist developers in managing longer tasks across extensive codebases. As an AI code editor within the VS Code ecosystem, Cursor is emphasizing the use of agents as the primary method for researching, planning, and implementing changes both in the editor and through the Cursor CLI.
Cursor now uses subagents to complete parts of a task in parallel.
— Cursor (@cursor_ai) January 22, 2026
Subagents lead to faster overall execution and better context usage. They also let agents work on longer-running tasks.
Also new: Cursor can generate images, ask clarifying questions, and more. pic.twitter.com/LTsxuaYuoU
Subagents are a key feature in this release. These are independent agents that a parent agent delegates to handle specific subtasks in parallel. Each subagent operates with its own context and can be customized with specific prompts, tool access, and model choices. This setup helps maintain a focused main conversation while allowing work to progress on multiple fronts. Cursor provides default subagents for tasks such as codebase research, executing terminal commands, and managing parallel work streams.
Image generation has been integrated into the agent workflow. Users can either describe an image or upload a reference to generate assets using Google Nano Banana Pro. The results are rendered inline and automatically saved into the project’s assets/ folder. This feature is particularly useful for creating UI mockups, product art, and architecture diagrams.
For those on the Enterprise plan, Cursor Blame extends the functionality of git blame by incorporating AI attribution. It distinguishes between Tab completions, agent edits (by model), and human edits, providing per-line links back to the conversation summary. Additionally, agents can ask clarification questions without interrupting their workflow, allowing them to continue reading files, editing, and executing commands while waiting for responses.
Early feedback from the community has highlighted a desire for more control over default subagents and has noted issues with chat history loss in some 2.4.x builds.
