@tracesdotcom
We've been working on building trace intelligence across all your company sessions. We're building dimensions of trace data especially relevant to the offices of a CTO, CISO, and CFO. You'll be able to answer things like "how often do files in your codebase show up in agent read operations and how much does it cost" (an example visual below)
This is a fun but gnarly data engineering challenge. But IMO the real story is all the software we are creating along the way. We're building internal tools to evaluate schema choices, we use data from our agent to evaluate the types of queries to optimize for (using Jev and Luna to classify), we build visual profiling tools test query performance throughout. Making software now is so much more fun and interesting.
Anyways, I can't wait to show this stuff off. Your agent trace data contains multitudes and you need many ways to look at it. Also, if this is interesting enough that you might want to run a pilot, please DM!View quoted post on X
A few weeks ago, we launched Surfaces on Traces, a new way to visualize your agent sessions.
Today, we're launching a big update - anyone can now create a surface.
Surfaces can be just for your org, or anyone on traces.com - and are super easy to add!View quoted post on X
traces.com The Hub for Your Coding Agents Make every agent session multiplayer & compound your team intelligence. Today we're launching Surfaces on Traces
A new way to visualize your agent session activity, for everything from skills used, token consumption, security issues and much more.
Available for all your sessions on traces.com.View quoted post on X
Introducing the Traces MCP
Anyone in your team can now access information from your past sessions - from every decision to tool call.
A multiplayer team memory, available to any Traces user (individual or org).
Just point your agent to traces.com/docs/mcpView quoted post on X
