How do I share what I found in my agent traces with a teammate?

Rius lets you click Share on the trace list to create a public, read-only link to a frozen, filtered view of your traces. Your teammate does not need to join the workspace. The link expires after 24 hours, 7 days or 30 days, and it shows summary tiles and trace metadata only, never span content.

How it works

Share works on the list you are looking at, as a snapshot rather than a live page.

• What is frozen. The link captures the time range, the status filter and your filter chips at the moment you click. The page it opens lists the filters it applies, so your teammate can see what they are looking at.
• What is not captured. The search text and the agent selection are not part of a shared view. Express what you want to show as filter chips and a status filter before you click.
• What your teammate sees. Summary tiles and trace metadata. A shared view never includes span content: no input or output previews, end user ids, instance ids, session ids, or the API key that sent a trace.
• How long it lasts. You choose 24 hours, 7 days or 30 days when you create it. 7 days is the default.
• One chance to copy. The link is shown once, at creation. Copy it then.

Because the link is public, treat it like any link you paste into a chat. Choose the shortest expiry that covers the conversation, and revoke it when you are done.

Set it up

1. Make sure your agent is sending traces, so there is something to share. If you have not set this up yet, this is the Python form:

import rius
 
client = rius.init(
    api_key="ri_...",
    service_name="my-agent",
)

2. Open Traces and narrow the list to what you want your teammate to see. Pick a time range (15m, 1h, 1d, 7d, 30d or a custom range), set the status, and use Add filter to build chips. The strip above the list shows the count, error rate, latency percentiles, tokens and cost for the matching traces, which is close to what the summary tiles in the shared view will show.
3. Click Share on the trace list.
4. Optionally give the view a name, so you can recognize it later in your list of shared views.
5. Choose an expiry: 24 hours, 7 days (the default) or 30 days.
6. Create the link and copy it straight away. It is not shown again.
7. Send the link to your teammate. The page it opens lists the filters it applies.
8. When the view is no longer needed, open Settings, find it under shared views and revoke it. That is where all your links are listed.

For the full tour of filters, status values and saved searches, see Exploring traces.

What you get

• A teammate can look at a failure or a pattern without a workspace seat.
• The shared page is read-only and frozen, so what you saw is what they see, even as new traces arrive.
• The filters are listed on the page, so the context travels with the link.
• Sensitive detail stays behind: prompts, replies, tool inputs and outputs, user ids, session ids, instance ids and API key details are not included.
• You stay in control. Every link expires on its own, and you can revoke it earlier from Settings.

If you want a broader picture of what to look for once a teammate has the link, read Monitor AI agents in production.

When something else fits

• If your teammate is already in the workspace, copy the page URL instead. Filters live in the URL, so the link opens the same filtered list. A saved search set to Everyone in this workspace gives the whole team the same list.
• If you need to hand over the detail of one trace for a bug report or a test fixture, use the trace’s Export to download it, or a single span, as JSON, since a shared view never carries span content.

Related