Grok Bot: open cloud-agent cards in the browser and show Grok-launched agents on /agents

Feature request for product/service

– Other –

Describe the request

Product/service: Grok Bot (not in the dropdown list, so selected “-- Other --”)

Current: In Grok Bot chat, a launched cloud agent shows an in-chat card (cursor-agent card; example title like “AssetBuyer no-ledger drift design”, status Running). The card’s “Open in Cursor” button launches the Cursor desktop app. There is no way on that card to open the same running agent in the browser at cursor.com.

Same path: opening https://cursor.com/agents with no filters showed “No agents match filter,” while a Grok-launched agent was live via API and had a working direct URL.
Example: AssetBuyer no-ledger drift design (bc-27b06982-8113-4698-a827-58236ab9df48)
Direct URL that works: https://cursor.com/agents/bc-27b06982-8113-4698-a827-58236ab9df48

Proposed:

  1. Keep Open in Cursor / the desktop path. Add a way to pick Browser (cursor.com) vs Desktop for the same agent (split button, overflow menu, or long-press).
  2. Grok-launched cloud agents should appear on https://cursor.com/agents so the browser path is actually usable.

Who it hurts: Anyone who wants to inspect a running Grok-launched cloud agent in the browser without opening the desktop app (phone, web-only session, or desktop not installed/wantedWhy existing Feature Requests do not already cover this:

Searched Feature Requests (including grok-bot tag and closed) for this Grok Bot card + /agents list ask; no match.).

New signal on the same empty-list path (not a new request):

The agents list is empty on both https://cursor.com/agents (web, no filters: “No agents match filter”) and the Cursor mobile app, even though cloud agents are definitely running.

Earlier today, signed in as John Solly, AssetBuyer no-ledger drift design (bc-27b06982-8113-4698-a827-58236ab9df48) was live via API and opened at https://cursor.com/agents/bc-27b06982-8113-4698-a827-58236ab9df48 — it still did not appear in the /agents sidebar.

Related-at-most (not the same): iOS inbox: Automations source filter shows “No matching agents” despite active automation runs is the iOS inbox Automations source filter, not the main agents list on web + mobile.

Hey @jsolly, thanks for the detailed writeup!

For the card: middle-clicking “Open in Cursor” opens the agent in your browser at cursor.com. A regular click tries the desktop app first and falls back to the browser if it isn’t installed.

For cursor.com/agents: your Grok-launched agents are there, they’re just hidden by the default view. Open the filter menu and enable Source > Grok Bot and they’ll all show up.

We agree the defaults here are confusing, and the team is looking at making this more discoverable. Thanks again for flagging it!