Cursor Agents Can Now Run on Your Own Machine — and Drive a Browser While They're There

Cursor’s changelog entry for 2026-09-02 introduces Self-hosted machines. In one line: agents that used to run only on Cursor’s cloud can now run on hardware you own. Verified 2026-09-08.

On the surface this is an enterprise feature — keeping tool execution inside your own infrastructure. It also quietly solves two problems solo developers have had for a while.

1. What shipped

2. The fourth item is the interesting one

The first three are infrastructure. The fourth changes behaviour.

Agents could already edit your files and run your commands, but they could not see a screen. With computer use, one can open a browser, click, and look at the result. That makes a category of task possible that was not before:

• After a front-end change, the agent opens the page and checks whether it broke, rather than only running unit tests.
• Admin flows that require a login can be walked end to end and reported back.
• Cross-application chores — moving an artifact from one tool into another — finally have hands.

Note the scope: Cursor lists Linux and Mac only. Windows is not on the list. That is explicit in the entry, and Windows users are still waiting.

3. What you gain, what you pay

Gained:

• Data stays in. Tool execution happens inside your environment — the headline point, and a hard requirement for teams with compliance constraints.
• The environment is the one you know. Cloud sandboxes are irritating precisely because of missing packages, credentials and network permissions. Your own box has none of that.
• Idle hibernation, so a team pool is not burning resources all day.

Paid:

• You now operate the machine. If it dies, you have no worker. That is your problem, not Cursor’s.
• The agent’s permissions became real. Misclicking in a sandbox destroys a disposable container. Misclicking on your laptop touches real files and real logged-in sessions. Decide what lives on that machine before enabling computer use.

No official figures exist for this trade-off — it is judgement, not data, but it deserves thinking about before the feature list does.

4. Why it matters

Working solo: you have a new use for an old laptop. Park it as a worker and long-running agent tasks stop competing with the machine you are actually typing on.

Working in a team: the notable part is that Cursor opened the execution layer to eight third-party platforms. That positions Cursor as an orchestration layer rather than a product welded to its own cloud — a point in its favour if lock-in worries you.

The changelog says nothing about plan restrictions or price impact. Cursor’s pricing page does not publish quota numbers at all, which we covered separately.

What Cursor’s pricing page does and does not say: Cursor publishes no quota numbers. Free versus paid: Cursor free vs Pro.

Source read directly on 2026-09-08: the Self-hosted machines entry dated 2026-09-02 in the official Cursor changelog. My Machines, Team pools, the eight execution platforms and Linux/Mac computer use support are all as published. Cursor does not state plan restrictions or pricing impact for this feature, and we do not estimate them. Section 3’s costs are our assessment, not Cursor’s.