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

Rius stops tracing in Codex (beta) for the rest of the current session with $rius:rius-off, and a new session traces again. To stop one folder, run $rius:rius-disable-here there. Run $rius:rius-status at any point to see whether the folder is traced and why.

How it works

The Rius plugin gives you three ways to pause Codex (beta) tracing, from narrowest to widest:

• This session only. $rius:rius-off stops tracing for the rest of the current session. Once the session’s trace has started, the stop is final: $rius:rius-on only helps if you ran $rius:rius-off before your first prompt. Your folder rules and sign-in stay as they are.
• One folder. $rius:rius-disable-here stops tracing the folder you run it in. A disabled folder beats any enabled parent, so a folder you disable stays off even when a folder above it is enabled.
• Everywhere. Setting the environment variable RIUS_CODEX_ENABLED to false turns Codex (beta) tracing off for every folder.

The plugin’s commands are Codex skills. Type $ and pick one. Codex never runs them on its own, so only you start them. The enable and disable skills write to ~/.codex/rius/, so Codex asks you to approve them.

Folder rules apply to every Codex (beta) session on the machine. They are separate from the Claude Code rules, so pausing one agent does not pause the other.

Set it up

Installing the plugin, trusting its hooks and signing in are covered in Codex (beta). The steps below assume tracing already works.

1. Pause the current session. In Codex (beta), type:

   $rius:rius-off

2. Check the state. Run the status skill. It reports whether this folder is traced and why, plus the account, the key and the hooks:

   $rius:rius-status

3. Trace again in a new session. The stopped session stays stopped. Start a new Codex (beta) session, and it follows the folder rules as usual.

4. Pause a folder for longer. Run this inside the folder. It stops tracing there and everything under it. A session open in that folder also stops for good, and re-enabling the folder applies to new sessions:

   $rius:rius-disable-here

   To trace the folder again, run $rius:rius-enable-here for structure only, or $rius:rius-enable-content-here to also send prompts, replies and tool output with recognised secrets removed. Run $rius:rius-status afterward to confirm the folder is traced.

5. Pause everything. Set the variable before you start Codex (beta):

   export RIUS_CODEX_ENABLED=false

   This variable can only turn tracing off. It does not change your sign-in or your folder rules.

What you get

• A pause that matches how long you need it. Use $rius:rius-off for the rest of one session, $rius:rius-disable-here for a folder you want left alone, and RIUS_CODEX_ENABLED for the whole machine.
• A way to confirm the result. $rius:rius-status shows whether the current folder is traced and why. If its Reason line says no path rule matches, run $rius:rius-enable-here in that folder. If it says there is no key, run $rius:rius-login.
• No change to your account. Pausing does not sign you out and does not revoke your key. The key stays stored for this machine, so resuming needs no new sign-in.
• Folder rules that last. A folder you disable stays disabled until you enable it again, whatever its parent folders say.

For how the plugin compares with tracing in other coding agents, see Coding agents.

When something else fits

• To stop tracing for good, run $rius:rius-logout. It revokes the key and deletes it from the machine, and you sign in again with $rius:rius-login to come back.
• To keep tracing but send less, use $rius:rius-enable-here for structure only, or set RIUS_CAPTURE_CONTENT to false to send structure only from every folder.

Related