Every session starts from zero
One engineer’s agent fixes a bug. The next engineer’s agent never hears about it, and the same bug comes back.
XTrace gives every engineer’s coding agent the context your team has already built, and turns what one session learns into shared knowledge and rules every agent follows. Those rules run on the same control plane as your security policies, and your agents keep improving on their own, session after session.
The problem
One engineer’s agent fixes a bug. The next engineer’s agent never hears about it, and the same bug comes back.
An agent copies a flawed pattern from the codebase, and the next session copies it again.
Every decision gets added to the file. Agents still skip parts of it, and nobody can say how often.
How it works
Each session starts from what the team knows, and adds what it learns.
How a lesson travels: from one session, into shared context and team rules, and into every engineer’s next session.
Brains
A Brain is shared memory for a project or team: the lessons, decisions and proven fixes your people and agents have built up, each kept with its source.
Context is shared across people, agents and tools, and kept current as the work happens.
The reasoning behind a decision travels with it, traceable to the session or document it came from.
One engineer’s fix reaches the whole team.
Rules
A rule is a team standard drawn from your own history, placed in the agent’s workflow so it applies in every session for every engineer.
Example rule
When an agent adds an environment variable, it logs it in the team’s release Brain.
Rules come from your own bugs, review comments and skipped instructions. None are generic best practice.
The XTrace plugin enforces each rule through the coding agent’s hooks, before the work goes through, so nobody has to repeat the correction.
Every rule traces back to the work it came from, with a record of where it applied.
XTrace keeps finding new mistakes and turns them into rules on its own. Teams that want a look first can review rules before they go live.
Sessions
Sessions are your team’s AI coding work, captured where it happens: what the agent did and where a person stepped in. They are the record lessons come from, and the evidence that rules hold.
Where sessions stall, loop or need a person to step in, by repo and team.
Which rules applied, how often and where.
The session behind any rule or lesson, one click away.
The learning loop
When a lesson lands in a team Brain or rule, the XTrace plugin brings it into every engineer’s next session. XTrace keeps finding new lessons as your code, models and team change, so the setup keeps improving without anyone maintaining it.
In the session
Add the new payout limit and ship it.
Added PAYOUT_LIMIT_MAX to the payout config. Committing.
git commit -am "Add payout limit"BlockedNew environment variables go in the release Brain.
This change adds PAYOUT_LIMIT_MAX. Log it so the person deploying knows it’s needed.
a production incidentApplies in every engineer’s sessionsLogging the variable to the release Brain, then committing.
git commit -am "Add payout limit"DoneFor the whole team
The XTrace plugin inside a coding agent: a team rule applied in the session, and the result saved to the shared Brain.
Getting started
We connect XTrace to the AI tools and coding agents your teams already use.
XTrace reviews your past sessions and existing instruction files and finds the mistakes that keep repeating.
Rules and shared Brains reach every engineer’s agent through the XTrace plugin, and keep growing as new lessons come in.
Add-on
Move faster with expert help.
Hands-on workshops and expert support to get your engineers working with shared Brains and team rules sooner.
Privacy & security
XTrace reports at team level by default. Your data is encrypted in transit and at rest, access runs through SSO, and every setting is configurable to your policies.
FAQ
An instruction in a file depends on the agent noticing and following it. A rule sits in the agent’s workflow: the XTrace plugin enforces it through the agent’s hooks, in the session, before the work goes through.
We’ll show you how XTrace turns it into a rule every engineer’s agent follows, and what your sessions say about the next one.