RIVERSIDE — Cursor began as a familiar fork of the Visual Studio Code editor with an unusually capable autocomplete layer. In 2026 it reads more like an operating system for software work: a place where an in-house model can sustain multi-hour tasks, where agents spin up in the cloud with their own virtual machines, and where scheduled workflows can monitor Slack or Stripe without touching a line of source code. The product's own changelog and documentation describe a stack of features dense enough that even devoted users may never flip every toggle—and that breadth is part of what makes the editor distinctive.
The editor you already know—plus an autonomy slider
Cursor's marketing positions the product as a coding agent first and an editor second (Cursor features). Practically, that means three overlapping modes: Tab for inline prediction, targeted edits via keyboard shortcuts, and full agent sessions that can search the codebase, run terminals, edit files, and browse the web (Cursor Agent overview). Andrej Karpathy, quoted on Cursor's site, describes this as an "autonomy slider"—developers choose how much independence to grant the AI on any given task (Cursor features).
Tab remains the entry point many developers feel first. Cursor documents Tab as autocomplete that reads recent edits, surrounding code, and linter errors; it can modify multiple lines, add imports, jump to the next predicted edit location within a file, and even suggest coordinated changes across files through a portal window (Tab completion docs). That cross-file behavior matters when refactors ripple beyond a single buffer.
Composer 2.5: Cursor's own model for long jobs
On May 18, 2026, Cursor shipped Composer 2.5, described in an official announcement as a substantial step up from Composer 2 for sustained work, complex instructions, and day-to-day collaboration (Introducing Composer 2.5). The company says the model builds on the same open-source Kimi K2.5 checkpoint as Composer 2, with training changes that include targeted reinforcement learning with textual feedback, roughly 25 times more synthetic coding tasks, and infrastructure work on optimizers and distributed training (Introducing Composer 2.5).
Pricing published in the changelog lists a Standard tier at $0.50 per million input tokens and $2.50 per million output tokens, plus a faster default variant at $3.00 and $15.00 per million tokens respectively (Cursor changelog). Cursor offered double usage for the first week after launch. For teams weighing model costs, Composer 2.5 is positioned as Cursor's attempt to keep frontier-class agent behavior inside the editor's native picker rather than routing every job to third-party APIs.
Cloud agents: parallel workers with real environments
Cloud agents—formerly called Background Agents—run the same agent fundamentals as local sessions but inside isolated cloud virtual machines with cloned repositories, dependencies, secrets, and network access (Cloud Agents docs). Cursor says users can launch them from the desktop app, the web at cursor.com/agents, Slack, GitHub, Linear, or an API, and run many in parallel without keeping a laptop online (Cloud Agents docs).
The documentation emphasizes environment setup: agents that can write code but cannot run tests or reach services behave like engineers without a workstation. Teams can configure environments via agent-led setup, saved snapshots, or a Dockerfile referenced in .cursor/environment.json (Cloud Agents docs). Finished runs can produce merge-ready pull requests with screenshots, videos, and logs, and reviewers can temporarily take over the agent's remote desktop to validate changes (Cloud Agents docs). Multi-repo support lets one agent reason across separate frontend, backend, or library repositories in a single workspace (Cloud Agents docs).
Automations: scheduled and event-driven agents
Cursor Automations extend cloud agents into background workflows triggered on a schedule or by events from GitHub, GitLab, Slack, webhooks, Linear, Sentry, PagerDuty, and other integrations (Automations docs). Examples in the documentation include reviewing recent pull requests for bugs, triaging Slack messages, and summarizing codebase changes on a cron schedule (Automations docs).
Version 3.5, released May 20, 2026, moved automations into the Agents Window inside the IDE alongside cursor.com/automations (Cursor changelog). Two expansions stand out for teams whose work does not fit a single repository:
- Multi-repo automations attach several codebases so one agent can deliver, test, and verify coordinated changes (Cursor changelog).
- No-repo automations run without cloning code, aimed at monitoring external tools. Cursor added five marketplace templates—for example Slack digests, product analytics from a warehouse, FAQ drafting, Stripe billing reports, and customer health monitoring (Cursor changelog).
Automations always run cloud agents in Max Mode and bill at cloud-agent usage rates (Automations docs).
Fresh UI tools: canvases, /loop, and a cleaner Agents Window
The same May 20 release introduced shared canvases: interactive artifacts such as reports or dashboards that agents create, shareable as live browser snapshots with read-only team access from the Cursor Dashboard on Pro, Teams, and Enterprise plans (Cursor changelog).
The /loop skill lets a local agent repeat a prompt on a schedule, until a defined outcome is met, or until the user stops it—useful for tasks like checking deploy status every few minutes or iterating on a feature until tests pass (Cursor changelog).
Version 3.4, dated May 13, 2026, refined the Agents Window with full-screen tabs that expand files, diffs, canvases, pull requests, browsers, and terminals while collapsing chat into a floating prompt bar, plus compact chat responses with adjustable tool-call density (Cursor changelog).
Hooks into the rest of the stack
Cursor has been pushing agents outside the IDE window. A May 19, 2026 changelog entry adds Jira integration: assign work items to Cursor or mention @Cursor in comments to start a cloud agent scoped to ticket text and repository settings, with completion updates and pull request links returned to Jira (Cursor changelog). The features page also highlights terminal installation, Slack collaboration, and GitHub pull request review (Cursor features).
Together, these integrations frame Cursor less as a standalone text editor and more as a coordination layer—one surface where Tab still feels instantaneous, but where the heavier lifting can be delegated, scheduled, or triggered from the tools teams already live in.
Why the feature pile matters—even if you ignore most of it
Not every developer will configure multi-repo cloud environments, wire PagerDuty triggers, or share agent-built canvases with a product team. Cursor's recent releases nonetheless show a coherent bet: coding assistance is converging on agents that plan, execute, verify, and hand off work across repositories and business systems. The editor remains the home base—keyboard shortcuts, diffs, and file trees included—but the product's center of gravity has shifted toward long-running, tool-using automation you can dial up or down.
For readers evaluating whether Cursor earns its reputation, the practical test may be simpler than adopting every May 2026 feature on day one. Tab and inline edits cover minute-to-minute typing; Composer 2.5 and cloud agents cover the hours-long refactors; automations and Jira hooks cover the workflows that repeat when nobody is watching the screen. Loving the editor, in that framing, is less about using every switch—and more about having them available when the task outgrows autocomplete.
References
Related Articles
Continue reading with these related stories
The Strength We Find in Community
Many of us are more connected online than ever, yet feel increasingly alone. In hard economic times, the community around us—not money or big institutions—may be our greatest strength.
The First two weeks of June and guns deaths in America
From June 1–14, 2026, America logged 23 mass shootings, one school-linked killing, and no new white-supremacist attacks—while daily gun deaths averaged 21.
Newspaper start needs people, businesses and content creators
A new Hartbeespoort news venture on the Crocodile River seeks merchants, marketers, and creators as it enters a local market still dominated by established weeklies such as Kormorant.