How do I trace Cursor (beta) in only one repository?

Rius traces Cursor (beta) only in the folders you enable, so run /rius-enable-here inside that repository and every other folder stays untraced. Installing the plugin and signing in send nothing by themselves. Start the agent from the enabled repository, work as usual, and each agent chat appears as a trace in Rius. Details are on the Cursor (beta) guide.

How it works

Tracing for the Rius plugin is off everywhere until you turn it on for a folder. That is what limits it to one repository.

• Folder rules. /rius-enable-here traces the folder you run it in and everything under it. A repository you never enable sends nothing.
• Where the agent starts matters. The agent is traced when it runs in an enabled folder, so open the enabled repository in Cursor (beta), or start cursor-agent from it.
• Disabling wins. /rius-disable-here stops tracing a folder, and a disabled folder beats any enabled parent folder. You can enable a repository and still switch off one subfolder.
• Structure by default. /rius-enable-here sends the span tree, timing, model names, tool names and error types. It sends no prompts, answers or tool output.
• One chat is one trace. Each Cursor (beta) agent chat becomes a trace, with a span for each answer, tool call and subagent.

The commands run only when you type them. Each runs a script through the agent’s shell tool, so Cursor may ask you to approve it.

Set it up

1. Install the plugin once per machine. In Cursor’s plugin settings, choose Import from Repo and enter the repository below. Installing sends nothing, and tracing stays off for every folder.

   glassflow/rius-coding-agents

2. Sign in once. In the agent chat, run /rius-login, pick a workspace in the browser and click Connect. The plugin stores a key for this machine, and you do not repeat this per repository.

3. Open the one repository. Open that repository’s folder in Cursor (beta), or start cursor-agent from it. This is the folder you enable next.

4. Enable it and check. In the agent chat, run these two commands:

   /rius-enable-here
   /rius-status

   /rius-status shows whether the folder is traced and why. If the Reason line says no path rule matches, run /rius-enable-here again in this folder. If it says there is no key, run /rius-login.

5. Work as usual. Find the chat in the trace list at console.rius-glassflow.com.

6. Add content only if you want it. To also send prompts, answers, and tool input and output, run /rius-enable-content-here in the same folder instead. The plugin replaces the secrets it recognizes before sending, which is best effort.

7. Pause or undo. /rius-off turns tracing off for the current chat only, and /rius-on turns it back on. /rius-disable-here stops the folder for good.

If a command cannot find the plugin, start a new chat and try again. To stop tracing from every folder on a machine, set RIUS_CURSOR_ENABLED to false.

What you get

• Traces from the one repository you enabled, and none from your other projects.
• Each chat as a trace with its span tree, timing, models, tools, errors and subagents.
• Your developer identity: from plugin 0.6.2, chats appear under the email you signed in with on the Users page.
• A clear check at any time, because /rius-status tells you whether a folder is traced and why.
• Control over content, since structure only is the default and /rius-enable-content-here is a separate choice per folder.

Cursor (beta) traces carry no token counts and no cost, because Cursor’s hooks do not report usage. Cursor support needs plugin 0.6.0 or later and runs on macOS or Linux, and Windows is untested. It is tested mostly against headless runs, so some details of the editor agent may change.

When something else fits

• To trace every project under a parent folder, run /rius-enable-here in that parent, since it covers everything below it.
• If you need token counts and cost per session, Claude Code and Codex (beta) report them, and you can compare all four agents on the Coding agents page.
• If you want to use Rius without the plugin for a different agent, the same page covers the other ways to connect.

Related