How do I see Codex (beta) usage across my whole engineering team?

Rius shows Codex (beta) usage and cost per developer when everyone on the team signs in to one shared workspace through the Rius plugin. Each developer installs the plugin, signs in with the team workspace, and turns tracing on for their repos. Each Codex (beta) session then appears as one trace under the developer’s email, and you read usage and cost on the Users page.

How it works

• The plugin traces Codex (beta) CLI sessions, one trace per session, with model calls and their tokens, tool calls and subagents. It needs plugin version 0.6.0 or later.
• When a developer signs in, they pick a workspace. Their machine’s key sends every session to that workspace, so one shared workspace collects the whole team’s usage and cost in one place.
• From plugin 0.6.2, every span carries user.id, set to the email the developer signed in with. That is what groups sessions by developer.
• Sessions sent with a key stored through use-key carry no user and land in the anonymous row. Use the sign-in flow for team reporting.
• Cost comes from token counts at API rates, so it measures usage and is not what a developer pays on a ChatGPT plan.
• Codex (beta) does not tell the plugin when a session ends. A trace closes when the developer starts their next Codex (beta) session on the same key, once the old session has exited and been idle for about an hour. Until then it shows as in progress.

Set it up

1. Pick one workspace for the team. A workspace admin invites teammates under Settings → Organization. Teammates accept the invitation first, then choose the team workspace when they sign in.
2. Each developer installs the plugin. You need Python 3.9 or later on your PATH, and macOS or Linux, because Windows is untested for Codex (beta). Installing sends nothing.

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

3. Trust the hooks. In Codex (beta), open /hooks and trust the five rius hooks. Until you do, nothing is traced and nothing warns you.
4. Sign in. Type $rius:rius-login and approve the sandbox escalation. In the browser, check that the code and machine name match, choose the team workspace, and click Connect.
5. Turn tracing on per folder. Run $rius:rius-enable-here in each repo for structure only. Run $rius:rius-enable-content-here instead to also send prompts, replies and tool output, with recognised secrets removed on a best-effort basis. Each developer runs these themselves. You cannot switch tracing on for the team from one place.
6. Check it. Run $rius:rius-status. Its Hooks: line counts the approved hooks, and its Reason line says why a folder is or is not traced.

Because everyone in the workspace can read what is sent, agree as a team which repos send content. The full flow is in Codex (beta).

What you get

• A row per developer. The Users page lists each developer with their Traces (one per session), Failed traces and Cost for the selected time window. Sort by Cost to see who drives spend, then open a developer to see recent and failed sessions.
• Filtering by owner. The trace list shows one row per session, and its Sent by column names the owner of the key that sent it.
• A team-wide agent view. The Agents page shows Codex (beta) as an agent named codex, with its traces, errors and cost for the window. Each open session is a live instance.
• Session detail. Open a session to see every turn, model call and tool call with tokens and cost. A command that exits non-zero is marked as an error.
• Questions in plain language. Developers can run codex mcp login rius once, then ask Codex (beta) which of their sessions used the most tokens.
• Control over keys. Each key is listed under Settings → API keys with the developer’s email and machine. A workspace admin can revoke it, and removing someone from the organization revokes it too.

The Users and Agents figures count a session once its trace has closed. The trace list shows it while it runs. Sessions started with codex exec --ephemeral are not traced.

When something else fits

• If your team also uses Claude Code, the same plugin covers it with its own sign-in and folder rules. See Track Claude Code usage and cost across a team.
• Cursor (beta) traces carry no token counts or cost, because Cursor’s hooks do not report usage. OpenHands needs no plugin. Both are covered under Coding agents.

Related