How do I record the full prompts and replies of Cursor (beta) sessions?

Rius records full prompts and replies from Cursor (beta) chats when you run /rius-enable-content-here in a folder. The command adds your prompts, the agent’s answers, and tool inputs and outputs to each chat’s trace, with recognised secrets removed first. Removal is best effort, so agree as a team which repos send content.

How it works

Tracing is off until each developer turns it on for a folder. The Rius plugin offers two levels for a folder and everything under it:

• /rius-enable-here sends structure only: the span tree, timing, model names, tool names, error types and subagents.
• /rius-enable-content-here sends the same, plus your prompts, the agent’s answers, and tool inputs and outputs.

Before anything is sent, the plugin replaces the secrets it recognises, such as cloud and API keys, tokens and private keys, with a marker. It also caps each captured value at 32 KB. This is best effort: a secret in a format the plugin does not know is sent.

Each event is first written to a local file under ~/.cursor/rius/spool/, readable only by you. With content off, no content is written there.

Content does not change what Cursor (beta) reports about usage. Cursor traces carry no token counts and no cost, with or without content, because Cursor’s hooks do not report usage.

Set it up

1. Install the plugin and sign in, if you have not yet. In Cursor’s (beta) plugin settings, choose Import from Repo and enter the repo below, then run /rius-login in the agent chat and pick a workspace in the browser. The Cursor guide covers install and sign-in in full.

   glassflow/rius-coding-agents

2. In the repo where you want prompts and replies recorded, run the content command in the agent chat. It applies to that folder and everything under it.

   /rius-enable-content-here

3. Run /rius-status to see whether the folder is traced, and why. If the reason says no path rule matches, the command has not been applied to this folder yet.

4. Work as usual, then open the chat in the trace list at console.rius-glassflow.com. Each chat is one trace, and its spans arrive while you work: when the chat starts, after each answer, and every 20 tool calls.

5. To stop sending content but keep tracing, run /rius-enable-here in the folder, which sets it back to structure only. To stop tracing the folder entirely, run /rius-disable-here. A disabled folder beats any enabled parent, so a sensitive subfolder stays off even when its parent sends content.

To cap content for one machine regardless of folder rules, set RIUS_CAPTURE_CONTENT to false. That sends structure only from every folder. Setting RIUS_CURSOR_MAX_ATTR_BYTES lowers the 32 KB cap on each captured value.

What you get

• The full text of your prompts and the agent’s answers on each turn of the chat’s trace, next to the model name, timing and status.
• Tool inputs and outputs on each tool call, so you can see what a failed call was given and what it returned.
• The same span tree you get in structure-only mode, including subagents under the call that started them.
• Secrets the plugin recognises replaced with a marker before they leave your machine.

Everyone in the workspace can read what is sent, so content mode is a team decision, not only a personal one. Because tracing is opt-in per developer and per folder, no repo can switch it on for the team. Each developer runs the command themselves, which makes a written agreement the way to keep it consistent. A simple one lists the repos where content is allowed, names the repos that stay structure-only or off, and asks everyone to check /rius-status after enabling a folder.

The Track Claude Code usage and cost across a team guide describes the same team pattern for Claude Code, and the Coding agents page compares what each agent sends.

When something else fits

• If you only need to see what the agent did, use /rius-enable-here: you keep the span tree, models, tools and errors without any prompt or reply text.
• If a repo holds material you cannot risk sending, because best-effort secret removal may miss an unfamiliar format, use /rius-disable-here there.
• If you need token counts and cost for coding sessions, the plugin reports them for Claude Code and Codex (beta), not for Cursor (beta).

Related