The same day Cursor got bought for $60B by SpaceX, they shipped something arguably bigger: Cursor on web and mobile.
Until today, Cursor was a desktop IDE, a VS Code fork you had to be sitting at to use. Now the company is launching agents that run in any browser, on any phone, and respond to @Cursor mentions in Slack. The acquisition is the headline. The product is the story.
What launched today
Cursor’s blog post dropped this morning with four major features.
Agents on web and mobile. Full Cursor Agent experience in any browser, including tablets and phones. The same agent that works alongside you in the IDE, accessible from anywhere.
PWA install on iOS and Android. Visit the URL, install as a Progressive Web App, get a native-feeling app on your phone without going through the App Store.
Background task execution. Launch bug fixes, build new features, or ask complex codebase questions. The agent runs while you’re away from your desk.
Slack integration. Get notifications when tasks complete. Trigger agents with @Cursor in Slack conversations. Route work to Cursor from anywhere your team is already talking.
Plus team collaboration features (review diffs, create pull requests from the web interface) and rich context support (images, follow-up instructions, parallel agents).
It’s live now at cursor.com/agents.
The “run agents while you’re away” use case
This is the feature that actually changes your day.
You’re at lunch. You pull out your phone. You open the Cursor PWA. You describe a bug fix, attach a screenshot of the error, and hit go. The agent spins up, digs into your codebase, makes the change, and runs the tests.
You finish your sandwich. Slack pings you. The agent is done. You open the diff in your browser, review the change, and either approve or send it back with a follow-up instruction.
When you’re back at your laptop, you open Cursor and pick up the agent’s work right where the web session left off. No context loss, no “where was I.”
That’s the workflow. That’s what the mobile app actually buys you. It turns the agent from “tool I use at my desk” into “background worker I delegate to from anywhere.”
@Cursor in Slack (the team angle)
The Slack integration is the feature that makes Cursor feel like a teammate, not a tool.
Code review, bug fixes, feature requests, codebase questions. All routable through Slack. Your team is already in Slack talking about work. Now Cursor is in there too.
For solo devs, the use case is “delegate from anywhere.” For small teams, it’s “treat Cursor as an on-call engineer.” For larger orgs, it’s “let non-engineers (PMs, designers, support) file Cursor tasks in the same place they file human tasks.”
The setup is at cursor.com/docs/slack if you want to wire it up.
Cursor just became a platform, not an IDE
The strategic read matters here.
Cursor was a desktop IDE. You installed it, opened a repo, and used the agent inside the IDE. The whole product lived inside that desktop window.
Today Cursor is a platform. The agent can be invoked from a browser, a phone, a Slack channel. The desktop IDE is still there for the heavy work, but the entry points have multiplied.
This is the moment Cursor stopped being a tool and started being infrastructure. For developers who don’t live in their IDE (or who want to delegate from anywhere), there’s now a real path to Cursor that doesn’t require installing anything.
It’s also the move that makes Cursor competitive with the AI coding tools I’ve been tracking. The vibe-coding workflow is about being able to direct AI from wherever you are. Cursor just made that workflow first-class.
The Codex comparison
Same week, OpenAI Codex is pushing in the same direction, but with a different bet.
Codex just rolled out Computer Use (letting the agent drive your desktop on macOS, with EU/UK expansion in progress per OpenAI’s announcement) and a Chrome extension that lets the agent browse the web for you on macOS and Windows.
Different strategies, same target.
Cursor’s bet: agents as background workers you Slack at and review in a browser. Mobile-first, IDE-optional.
Codex’s bet: agents as desktop operators that drive your computer. Desktop-first, mobile TBD.
Both companies are racing past the “AI autocomplete in your editor” stage. The next phase is “AI that does the work while you live your life.” Cursor shipped today. Codex is shipping. The next 12 months will tell us which bet pays off.
Same day as the SpaceX deal
I covered the SpaceX $60B acquisition of Cursor separately this morning. The deal mechanics, the xAI failure narrative, the MANGOS context: that’s all in the other piece.
What’s worth noting here: the same-day timing is striking. Cursor was acquired for $60B hours earlier. They shipped a major product feature the same day.
The product velocity says something. The acquisition didn’t slow Cursor down. If anything, it looks like the team used the moment to push the launch they had been planning. Watch the next 30 days for more product moves. SpaceX just gave Cursor a runway, and Cursor seems ready to use it.
Bottom line
Cursor just had the biggest day in its history.
$60B acquisition. A mobile app. A Slack integration. Background task execution. Same day, same announcement cycle.
For users: install the PWA, set up the Slack integration, try the background workflow. See if it actually changes how you work, or if it’s just a nicer place to launch the same prompts.
For watchers: this is the moment Cursor stopped being a tool and started being a platform. The question now is whether the product can keep up with the valuation. The answer, as of today, is: at least they’re shipping.
