How do I see Cursor (beta) usage across my whole engineering team?

Rius shows Cursor (beta) usage per developer when each developer signs in to one shared workspace through the Rius plugin. The Users page then lists each developer with their traces and failures. Cursor does not give plugins token counts, so Cursor traces carry no token usage and no cost. For cost per developer, the same plugin traces Claude Code, and Codex in beta. See Coding agents for all supported agents.

How it works

• One workspace. Every trace belongs to the workspace chosen at sign-in, so all developers’ chats land in one place.
• One trace per chat. In beta, the plugin turns each Cursor agent chat into a trace. It records the span tree, timing, models, tool calls, subagents and errors. It does not record tokens or cost.
• One identity per developer. With plugin 0.6.2 or later, every span carries user.id, set to the email the developer signed in with at /rius-login. That is what groups chats under a person.
• Opt-in per developer and folder. Installing sends nothing. Tracing stays off for a folder until that developer enables it. Nobody can turn it on for the team from a repo, and the agent cannot turn it on itself.
• Structure by default. /rius-enable-here sends structure only. /rius-enable-content-here also sends prompts, answers, and tool input and output, with recognised secrets removed on a best-effort basis.

Set it up

1. Pick the team workspace. A workspace admin invites teammates under Settings → Organization. Each teammate accepts the invitation first, so the team workspace is available at sign-in.
2. Each developer installs the plugin. Cursor support is in beta and needs plugin 0.6.0 or later, on macOS or Linux, with Python 3.9 or later and bash.

In Cursor's plugin settings, choose Import from Repo and enter glassflow/rius-coding-agents.

3. Each developer signs in. In the agent chat, run /rius-login. In the browser, sign in, check that the code and machine name match, choose the team workspace, and click Connect. This stores a key for that machine that can only send traces.
4. Each developer enables tracing in a repo. Run these in the repo, with /rius-enable-content-here instead if the team agrees to send content:

/rius-enable-here
/rius-status

5. Agree on content as a team. Everyone in the workspace can read what is sent, so decide which repos send prompts and answers.

Tell developers to sign in with /rius-login rather than a shared key. A key stored with use-key carries no user, so its chats land in the anonymous row. Chats from cursor-agent releases before 2026-08-27 need the hooks added by hand, as the Cursor (beta) guide explains.

What you get

• A Users page for the team. Each developer appears by sign-in email, with their traces and failures for the selected time window.
• A trace list with owners. The Sent by column shows whose key sent each chat, so you can filter to one developer and open the chat’s waterfall.
• An agent named cursor. The Agents page shows these chats as one agent. The plugin sends no heartbeat, so chats do not appear under Instances. A chat counts in the agent’s figures once its trace is closed.
• Control over keys. Each developer’s key is listed under Settings → API keys as Cursor: <your email> (<machine>). A workspace admin can revoke it, and removing someone from the organization revokes it too.
• Questions in plain language. Each developer can connect the Rius MCP server from Cursor and ask things like which tools their chats called most this week.

The plugin does not trace Cursor’s cloud and background agents or Tab completions. Cursor (beta) sessions show no cost, so a cost column for them stays empty.

When something else fits

• If you need tokens and cost per developer, Claude Code sessions report both through the same plugin, and so does Codex (beta). Rius prices them at list rates, so the cost is an estimate.
• Cursor tracing is beta, and interactive tool calls and the editor agent are not yet tested, so expect some details to change.

Related