How do I pause Rius tracing in Cursor (beta) for a while?

Rius lets you pause tracing in Cursor (beta) with /rius-off for the current chat, or with /rius-disable-here for a whole folder. Run /rius-on or /rius-enable-here to resume, and /rius-status to confirm whether a folder is traced and why. To stop tracing everywhere at once, set RIUS_CURSOR_ENABLED to false. Pausing keeps your sign-in and your install, so nothing needs setting up again.

How it works

The Rius plugin for Cursor (beta) decides what to trace at three levels. Pick the one that matches how long and how wide the pause should be.

• This chat only. /rius-off turns tracing off for the current chat, and /rius-on turns it back on for that chat. Other chats and your folder rules are not touched.
• One folder. /rius-disable-here stops tracing the folder you are in and everything under it. A disabled folder beats any enabled parent, so a rule set higher up the tree cannot switch it back on.
• Everywhere. The environment variable RIUS_CURSOR_ENABLED set to false turns Cursor tracing off in every folder. Plugin environment variables can only turn things off, so this one never changes your folder rules.

Tracing in Cursor starts off for every folder until you enable one. A pause therefore only changes the folders you had enabled. The commands run only when you type them, and Cursor may ask you to approve the shell command each one runs. If a command cannot find the plugin, start a new chat and try again.

/rius-status is the way to check the result. It reports whether the current folder is traced and gives a Reason line that explains why. After /rius-disable-here, expect it to say the folder is not traced. Before you have enabled a folder at all, the reason is that no path rule matches.

Set it up

1. Check where you are. Open an agent chat in the folder you work in and run the status command. Note the Reason line, so you can compare it after the pause.

   /rius-status

2. Pause the current chat. Use this for a short pause, such as a chat where you paste something you would rather not trace. Resume the same chat with /rius-on.

   /rius-off

3. Pause a folder for longer. Run this in the folder, then run /rius-status again. It should now show the folder as not traced. Every new chat in that folder stays untraced until you enable it again.

   /rius-disable-here

4. Pause every folder at once. Set the plugin’s switch in the environment of the process that runs the Cursor agent. This is useful for a demo or a stretch of work where you do not want any chat traced.

   export RIUS_CURSOR_ENABLED=false

5. Resume. Pick the one that matches how you paused:

   • After /rius-off, run /rius-on in that chat.
   • After /rius-disable-here, run /rius-enable-here in the folder to trace its structure only, or /rius-enable-content-here to also send prompts, answers, and tool input and output with recognised secrets removed. Then run /rius-status to confirm.
   • After setting RIUS_CURSOR_ENABLED, remove the variable from the environment.

Do not use /rius-logout to pause. It revokes the key and deletes it from the machine, so you would have to sign in again with /rius-login. The plugin install, and the full list of Cursor commands, are covered in the Cursor (beta) guide.

What you get

• A pause that matches your need. You choose between one chat, one folder, or every folder, without removing the plugin.
• A clear check. /rius-status tells you whether the current folder is traced and the reason, so you do not have to guess after a pause or a resume.
• No re-setup. Your sign-in and key stay in place, so resuming is a single command.
• Control over what you resume. When you turn a folder back on, you choose structure only with /rius-enable-here, or content as well with /rius-enable-content-here.
• Predictable folder rules. Because a disabled folder wins over an enabled parent, a folder you pause stays paused until you enable that folder again.

Tracing Cursor (beta) never includes token counts or cost, whether you pause or not, because Cursor does not report usage to plugins.

When something else fits

• If you want to stop tracing for good, run /rius-logout and remove the plugin, as described in the Cursor (beta) guide.
• If you only want less content sent, stay traced and use /rius-enable-here for structure only, or set RIUS_CAPTURE_CONTENT to false.
• To pause tracing in another coding agent, each one has its own commands. See Coding agents for the guide to each.

Related