How do I pause Rius tracing in Claude Code for a while?

Rius stops tracing a Claude Code folder when you run /rius:disable-here in it, and you resume by running /rius:enable-here again. To pause only the current session, run /rius:off. Run /rius:status at any point to see whether tracing is on or off and which rule decided it.

How it works

Tracing in the Claude Code plugin is decided by folder rules stored on your machine in ~/.claude/rius/config.json. They apply to every Claude Code session on that machine. You have three ways to pause, and they differ in how long the pause lasts.

• Disable a folder. /rius:disable-here stops tracing that folder and everything under it, including a folder inside an enabled parent. A disabled folder always wins, at any depth.
• Turn off one session. /rius:off stops tracing for the current session only. A new session starts without the override.
• Turn tracing off everywhere. Setting RIUS_CLAUDE_ENABLED to false in the env block of a Claude Code settings file turns tracing off over every folder rule. Only /rius:on beats it, and only for one session.

If a session is open when you disable its folder, nothing that happens afterward is sent. When the session ends, the plugin still closes its trace with the structure of what was open, with no prompts, replies or tool content. That way the trace is complete and counts on the Agents and Users pages. The stop is final for that session: enabling the folder again does not resume it.

/rius:off is final in the same way once the session’s trace has started. /rius:on only helps if you ran /rius:off before your first prompt.

Set it up

1. Pause the folder. In the folder you want to stop tracing, run:

   /rius:disable-here

   Use /rius:off instead if you only want to skip the current session.

2. Check the state. Run /rius:status. The first line reads Rius tracing: off when the session is stopped. A Stopped: line under Reason means tracing was turned off while the session was running, whether by a folder disable, /rius:off or RIUS_CLAUDE_ENABLED=false. After /rius:off, the reason reads off: session override.

   /rius:status

3. Undo /rius:off before you start. If you ran /rius:off and have not sent a prompt yet, run /rius:on to trace the session again. After the first prompt, start a new session instead.

4. Resume the folder later. Run one of these in the folder, depending on how much you want sent:

   /rius:enable-here
   /rius:enable-content-here

   /rius:enable-here sends structure only. /rius:enable-content-here also sends prompts, replies, file contents and command output, with recognized secrets removed. Start a new session after enabling, because a session stopped by a disable stays stopped.

5. Confirm it is back. Run /rius:status in the new session and look for Rius tracing: on. The Reason line then names the path rule that enables the folder.

For the full install and sign-in steps, see the Claude Code plugin guide.

What you get

• A clear stop for one folder, such as a client repository, without touching your other folders or signing out.
• Nothing sent from the paused folder after the command, and a complete, closed trace for any session that was already open.
• A way to verify the pause. /rius:status shows the on or off state, the rule behind it and, for a session that was stopped, the Stopped: line.
• A clean resume. The next session in a re-enabled folder follows the folder rules as usual, with the content setting you chose.
• Your account stays connected. Disabling a folder does not revoke your key or delete traces already sent.

When something else fits

If you want to stop for good and remove access, /rius:logout revokes the key and deletes it from your machine, and you sign in again with /rius:login to resume. To trace every Claude Code folder on the machine less, or only send structure, see the other options on the Coding agents page and in the plugin guide. A signed-out machine has tracing off everywhere, but a session running at that moment stays in progress in the trace list.

Related