Skip to Content
Rius

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

Rius traces Codex (beta) only in folders you enable, so you trace one repository by running $rius:rius-enable-here inside it. Tracing is off everywhere until you do that, so every other repository stays untraced. Run the command from the repository’s folder and start Codex (beta) there, and the sessions you run in it appear as traces in Rius.

How it works

  • Installing the Rius plugin sends nothing. Tracing stays off for every folder until you enable one.
  • $rius:rius-enable-here adds a rule for the folder you run it in. The rule covers that folder and everything under it, so a repository with sub-folders is traced as a whole.
  • The command writes to ~/.codex/rius/, so Codex (beta) asks you to approve it.
  • Folders with no rule are not traced. A folder you disable with $rius:rius-disable-here is never traced, even when a parent folder is enabled.
  • The folder rules apply to every Codex (beta) session on the machine. They are separate from the Claude Code rules, so enabling a repository for one agent does not enable it for the other.
  • By default the command sends structure only: the span tree, model names, tokens, cost, timing, tool names and error types. It sends no prompts, replies or tool output.

Set it up

  1. Do the one-time setup if you have not yet: install the plugin, trust its five rius hooks in /hooks, and sign in with $rius:rius-login. Until the hooks are trusted, nothing is traced. Codex (beta) walks through each part.

    codex plugin marketplace add glassflow/rius-coding-agents
codex plugin add rius@rius-coding-agents

  2. Open a terminal in the repository you want to trace and start Codex (beta) from that folder, so the folder you enable is the one you work in.

  3. Type the enable skill, then the status skill, and approve the prompt when Codex (beta) asks to write to ~/.codex/rius/:

    $rius:rius-enable-here
$rius:rius-status

  4. Read the output of $rius:rius-status. It shows whether this folder is traced and why, the account, the key, and how many hooks are approved. The Hooks: line should show all five.

  5. Work as usual. Open the trace list in the Rius console, and the session from this repository appears there as one trace.

  6. If you want prompts, replies and tool output from this repository too, run $rius:rius-enable-content-here instead of step 3. It adds those fields and removes secrets it recognizes before anything is sent. This is best effort, so a secret in a format it does not know is sent.

To stop tracing the repository later, run $rius:rius-disable-here in it. To stop tracing for the rest of one session, use $rius:rius-off. Once the session has started tracing the stop is final, so start a new session to trace again.

If the repository does not show up, check the Reason line of $rius:rius-status:

  • If it says no path rule matches, run $rius:rius-enable-here in this folder.
  • If it says there is no key, run $rius:rius-login.
  • If the Hooks: line shows fewer than five approved, open /hooks and trust the rius hooks.

What you get

  • Traces from one repository only. Work in your other repositories never reaches Rius.
  • One trace per Codex (beta) session, with your prompts when you enable content, every model call with its tokens and cost, every tool call, and the subagents Codex (beta) started.
  • Resuming a session with codex resume or codex exec resume continues the same trace.
  • A trace closes after the old session’s process has exited and it has been idle for about an hour, when you start your next session. Until then it shows as in progress.
  • Sessions from codex exec --ephemeral are not traced.
  • Sessions appear under your sign-in email on the Users page, and under an agent named codex on the Agents page.
  • Cost is worked out from token counts at API rates, so on a ChatGPT plan it measures usage, not what you pay.
  • A global off switch: setting RIUS_CODEX_ENABLED to false turns Codex (beta) tracing off everywhere, over every folder rule.

When something else fits

  • If you want every repository traced, run $rius:rius-enable-here in a parent folder such as ~/code. It covers every folder under it.
  • If you also use Claude Code, Cursor (beta) or OpenHands, the Coding agents page compares how each one is connected and what each one sends.

Still stuck? Get help

Last updated on
Quickstart