Skip to main content
Agent Inventory is currently in limited beta. Contact Opal support to enable it for your organization.
Agent Inventory keeps one Cursor agent for each person on your Cursor team, so you can see who uses Cursor and what each person’s agent has done. This page explains how Cursor agents get into the inventory, what Opal reads, and what you see. To see and control the tool calls that Cursor makes on your computers, see Cursor Setup. To connect your Cursor organization to Opal, see the Cursor integration.

Requirements

Before you begin, you must:
  • Be an Opal Admin. A read-only admin can’t import agents.
  • Connect your Cursor organization to Opal. See the Cursor integration.

How Cursor agents reach the inventory

There are two ways. Both end with the same result: one agent for each person, named <Name>'s Cursor.

Sync from your Cursor team

An admin runs the sync. Opal creates an agent for each person on your Cursor team whose email matches a person in Opal. Team members with no matching person in Opal are skipped.
  1. Go to Inventory > Agents and select + Agent.
  2. In Add agents, find your Cursor connection and select Add agents.
  3. Select Sync.
Opal imports the agents without a review step, and shows how many it synced. Run the sync again when your Cursor team changes. A person who is missing from Cursor’s list keeps their agent. If Cursor marks a person as removed, the next sync removes their agent. On Cursor Enterprise teams, the sync also imports Grok Bots and routines, and reads MCP usage, from Cursor’s audit logs and analytics. Cursor provides those only to Enterprise teams. Without them, the people still sync.

From tool calls

When tool call governance is set up for Cursor, Opal matches each call to a person. It tries the person’s own sign-in token first, then the emails the computer reports, starting with the email of the account Cursor is signed in with. The call appears on that person’s Cursor agent. A call that matches no agent is unattributed. If the person has no Cursor agent, Opal can create one from their first call. That happens only when your organization has it turned on, and only when the email matches an active person in Opal. Opal doesn’t recreate an agent that an admin deleted. The next sync adopts an agent that a call created, so the person keeps one Cursor agent.

What Opal reads

What you see

Go to Inventory > Agents. Filter by Source or Harness and choose Cursor to list your Cursor agents. The Source column names the connection an agent came from, not the word Cursor. An agent that a tool call created has no connection, so it shows a dash until a sync adopts it. A person’s Cursor agent starts with these values: Open an agent to see its profile. An agent that the sync made for a person also has a Cursor activity tab. It lists each call with When, Tool, and Target, and has three scopes:
  • All shows this agent’s calls together with the unattributed ones.
  • This agent shows only the calls attributed to it.
  • Unattributed shows calls that no agent matched.
Admins and read-only admins can see this tab.

What isn’t covered

  • Computers that send nothing. Calls reach the inventory only from computers where the hook is installed. A computer that sends nothing looks inactive.
  • Who made a call. Opal takes the person from what the computer reports. It’s a label, not proof.
  • Windows and Cursor’s cloud agents. The hook doesn’t cover them yet. Their people still get an agent from the sync. See Cursor Setup.
Last modified on November 17, 2026