Self hosted runner not eligible in macOS app, works in web

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Cursor CLI + Cursor Agent Window on macOS

Describe the Bug

When using a self-hosted agent in macOS app (Cursor Glass), no new thread can be started, always leading to a stuck “Setting up environment” step with the error “No matching self-hosted worker is eligible”.

When starting the agent with the same settings in cursor.com/agents, everything works as expected, even when taking over the agent session in the macOS app after creation in the web ui.

Steps to Reproduce

  • Login using Cursor CLI using agent login
  • Start worker in git repo agent worker start
  • In macOS App in agent window start a new agent and select the worker in the “Machines” menu item
  • Start a prompt

Expected Behavior

Agent session properly started from macOS app using the self hosted agent.

Screenshots / Screen Recordings

file-cdd546c32ab883a22fdc8f897d6c56b6.png
file-cdd546c32ab883a22fdc8f897d6c56b6.png1820×298 21.2 KB

Operating System

MacOS

Version Information

IDE: 3.6.31 (also did not work on nightly)
CLI: 2026.06.02-8c11d9f

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

7

This is a known bug - self-hosted workers started via agent worker start don’t get properly routed when you select them from the Machines submenu in the macOS app. The web UI at cursor.com/agents handles the routing differently, which is why it works there.

Two workarounds:

  1. Start from the web - launch the session at cursor.com/agents, then take it over in the macOS app (which you’ve already found)

  2. Use pool mode - start your worker with agent worker start --pool instead. This makes it visible to Glass directly, though only one agent session can claim it at a time.

Our team is aware of this and tracking it.