Skip to Content
Rius

How do I set up tracing for Cursor (beta)?

Rius traces Cursor (beta) through its plugin: import the plugin, run /rius-login, then run /rius-enable-here in a folder and check /rius-status. Each agent chat then arrives as one trace, with its tool calls, subagents, models and timing. If you use OpenHands instead, you need no plugin, only three environment variables. Both routes are covered below, with a check that your first session arrived.

How it works

  • The Rius plugin adds hooks to the Cursor agent (beta), in the editor and in cursor-agent in the terminal. Installing sends nothing, and tracing stays off for every folder until you enable one.
  • /rius-login stores one key for your machine, with permission to send traces only. It is separate from your Claude Code key, so signing out of one does not sign out the other.
  • A folder rule decides what leaves your machine. /rius-enable-here sends structure only: the span tree, models, tool names, error types and timing. /rius-enable-content-here also sends prompts, answers, and tool inputs and outputs, with recognised secrets removed. Redaction is best effort.
  • Cursor’s hooks do not report usage, so Cursor traces carry no token counts and no cost.
  • OpenHands works differently. Its SDK already sends OpenTelemetry, so three environment variables are enough. It always sends prompts and output.

The Coding agents guide compares all four agents side by side.

Set it up

  1. Check the requirements. You need Python 3.9 or later on your PATH, and bash. Use macOS or Linux, because Windows is untested for the Cursor plugin (beta).

  2. Install the plugin. Installation is the same plugin Claude Code and Codex use, and you add it from Cursor’s plugin settings:

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

  3. Sign in. In the agent chat, type /rius-login. In the browser, sign in or sign up, check that the page shows the same code and your machine’s name, choose the workspace this machine sends chats to, and click Connect. Only continue if you started the sign-in yourself. You can type the commands only yourself, because the agent never starts them, and Cursor may ask you to approve the shell command.

  4. Turn tracing on for a folder. In your repo, run /rius-enable-here. Use /rius-enable-content-here instead if you also want prompts, answers and tool output. A folder you disable with /rius-disable-here always beats an enabled parent.

  5. Check the status. Run /rius-status. It says whether the folder is traced and why. If the Reason line says no path rule matches, run /rius-enable-here in that folder. If it says there is no key, run /rius-login.

  6. Check the first session arrives. Work in the agent as usual, then open the trace list at console.rius-glassflow.com. Each chat is one trace. Its spans arrive when the chat starts, after each answer, and every 20 tool calls. Chats also show up as an agent named cursor on the Agents page, and under your sign-in email on the Users page.

  7. Using OpenHands instead? Set these three variables, with your own key in place of ri_..., in the environment that runs the OpenHands SDK:

    export OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=https://ingest.eu.console.rius-glassflow.com/v1/traces
export OTEL_EXPORTER_OTLP_TRACES_PROTOCOL=http/protobuf
export OTEL_EXPORTER_OTLP_TRACES_HEADERS="Authorization=Bearer%20ri_..."

    Run a conversation and look for it in the trace list. OpenHands Cloud is not supported, and web-app conversations carry no tokens or cost because their model calls are streamed.

If nothing arrives from cursor-agent, an older version may be ignoring plugin hooks. The Cursor (beta) guide gives the fix.

What you get

  • Every Cursor chat (beta) as one trace in Rius, with the answer, each tool call, subagents, models, errors and timing. A shell command that exits non-zero shows as an error.
  • Control per folder. You choose structure only or full content, and you can stop tracing a folder at any time.
  • Developers by name. From plugin 0.6.2, each chat carries your sign-in email as the user.
  • A way to ask about your chats from Cursor. The plugin brings the Rius MCP server as rius, with its own second sign-in.
  • For OpenHands, conversations traced with no plugin, with the Tool Loop alert available for stuck agents.

Cursor traces show no token usage and no cost. Cursor’s cloud and background agents and Tab completions are not traced.

When something else fits

  • If you need token counts and cost for your coding sessions, the plugin for Claude Code reports both, and so does Codex (beta). The Cursor (beta) guide explains why Cursor cannot.
  • If you use OpenHands Cloud, Rius cannot receive its traces. Use the OpenHands SDK with the three variables above.

Still stuck? Get help

Last updated on
Quickstart