Find and fix friction across your agent network.

Agents keep hitting friction that other teammates have already solved. Agent Experience finds and fixes agent friction using the best solution from across the agent network.

Start a team trial

Permission prompts3 agents

Agents ask to run npm test on each task instead of using an allowlist.

Humans collaborate to solve problems. Why shouldn't agents?

Agents work at machine speed, but improving how they work still happens at human speed. Fixes wait on human intervention, leading to lost time and wasted tokens.

Quotient surfaces friction and fixes it using your team's agent network.

Babysitting costs time and tokens

Each time an agent stalls, an engineer stops to unblock it while the agent burns tokens retrying.

Redundant solutions
to the same problem

Engineers solve the same problem separately, even when a teammate already has the fix.

No visibility of the human/agent system

The team's shared picture stays at the operator level. Agent setups and best practices stay scattered across individual engineers.

How it works

From a stuck agent to a fix the whole team can use.

AgEx runs inside Claude Code as the Quotient plugin.

Find and apply the best fix from across the team

After each task, AgEx asks the agent what slowed it down and shows fixes teammates' agents already found. Pick one, and your agent makes the change.

Claude Code with the Quotient pane open. A friction, lint fails in CI after passing on commit, is listed with two fixes from teammates; running ESLint from the repo root in the pre-commit hook is marked recommended.

Surface the top frictions and improvements across the team

Get one view of the frictions your team's agents hit and the fixes that resolved them, so the team knows what to tackle first.

Friction inventory

AllOpenFix availableFixed

FrictionSeverityStatus

Integration tests skip without a local databasepayments-api · 4 agents▲ high2 fixes to try

Agent retries lint instead of reading the configpayments-api · 3 agents▲ highOpen

MCP config written to the wrong pathweb-app · 2 agents◆ mediumFixed

Create a unified view of the human/agent network

Get a view of how agents are working within the network, alongside the engineers who run them.

Agent ExperienceYour team's engineers and agents, in one view

Engineers6of 8 on the team

Frictions found24across 2 repos

Frictions fixed9by shared fixes

Top areas of friction

Context

Tools and environment

Tests and checks

Handoffs

Value

Solve a bottleneck once, and the team's agents get it.

Without AgEx Agents work in silos

With AgEx Agents share what they learn

Less babysitting of individual agents

Agents pick up fixes a teammate's agent already found, so engineers step in less.

Your best solutions, shared

What works in one engineer's setup reaches the rest of the team's agents.

Improvement at agent speed

Fixes spread after each task, without waiting on someone to update a shared file.

How AgEx is different

Fixes that move at agent speed.

Agent Experience adds the agent-speed layer to your team's improvement stack.

	Shared rules files	Team learning sessions	Sharing in Slack	Agent Experience (AgEx)
Best for	Writing down conventions the whole team should follow.	Agreeing on bigger changes to how the team works with agents.	Getting help on one problem from whoever sees the thread.	Identifying and solving agent frictions after each session.
Frequency	Human speedWhen the file gets updated, which can lag behind how the team works.	Human speedOnce per meeting, often weeks apart.	Human speedWhen someone asks, one thread at a time.	Agent speedDaily, as new frictions are found and fixed.

Questions

Before you start

What is Agent Experience?

Agent Experience (AgEx) is a Quotient plugin for Claude Code. It finds the friction slowing your team's coding agents and applies fixes that already worked for a teammate's agent, so improvements spread across the team.

Which coding agents does it work with?

Claude Code today. Support for more coding agents is on the way.

How do we get started?

Each engineer installs the Quotient plugin and runs /quotient:setup. Setup reviews the last two weeks of agent sessions and lists what it finds. Fixes from teammates start once two or more people on the team are connected.

What does AgEx change in our setup?

Engineers pick a fix and their agent makes the change, such as an update to a hook, a config file, or CLAUDE.md. AgEx doesn't apply a fix the engineer hasn't chosen.

How is our data protected?

Quotient is SOC 2 Type 2 and GDPR compliant, and supports SSO and SCIM.

What are some examples of how it unlocks the engineering process?

Priya's agent finishes a task, but lint passes on commit and fails in CI. AgEx flags the friction and finds that Jordan's agent already solved it by running ESLint from the repo root in the pre-commit hook. When Priya starts her next session, Quotient offers Jordan's fix. She picks it, her agent updates the hook, and lint passes in both places from then on.

Get started

Start with one team.

Install AgEx on your team's Claude Code setup and see what your agents report in the first week.

Start a 7-day team trial