Product / Why agents leave

See why coding agents chose another tool.

See why coding agents choose another tool over yours: DevTune reads what each run did and turns losses with the same cause into one Action.

Losing scenarios

See the scenarios where another tool, or one the agent builds itself, is picked clearly more often than yours. A scenario is one framework, request, agent and model.

Agent Picks · Loss reasons

Agents chose another tool or built their own in 5 of 7 scenarios.

Next.jsAdd an integrationCodexgpt-6.1-sol
Acme picked in 1 of 8 runslost toBuilt its own
ExpressAdd an integrationClaude Codeclaude-sonnet-5-5
Acme picked in 3 of 8 runslevel
ExpressAdd an integrationCodexgpt-6.1-sol
Acme picked in 0 of 8 runslost toPassport
ExpressRecommend a toolCodexgpt-6.1-sol
Acme picked in 5 of 8 runsyou lead
ExpressUse a hosted serviceCodexgpt-6.1-sol
Acme picked in 2 of 8 runslost toAuth0
RailsAdd an integrationClaude Codeclaude-sonnet-5-5
Acme picked in 1 of 8 runslost toBuilt its own
RailsUse a hosted serviceClaude Codeclaude-sonnet-5-5
Acme picked in 1 of 8 runslost toAuth0

Recorded reasons

Losing runs are grouped by what they recorded: your page returned an error, your install failed, they never touched your tool, or they tried it and chose another. Each reason becomes one ranked Action.

Agent Picks · Reasons

01
Fix acme.dev/guides/express-sessions returning 404
2 losing scenarios · returned 404 in 14 runs that didn’t pick Acme · Acme picked in 2 of 16 runs (13%, likely 4–32%)
Steers around 1 locked page
Suggested
ExpressAdd an integrationCodexgpt-6.1-solExpressUse a hosted serviceCodexgpt-6.1-sol14 losing runs
02
Write a guide to using Acme in Rails
2 losing scenarios · Acme picked in 2 of 16 runs (13%, likely 4–32%)
Suggested
RailsAdd an integrationClaude Codeclaude-sonnet-5-5RailsUse a hosted serviceClaude Codeclaude-sonnet-5-514 losing runs
03
Fix the @acme/rails install agents tried in Rails
2 losing scenarios · Acme picked in 2 of 16 runs (13%, likely 4–32%)
Suggested
RailsAdd an integrationClaude Codeclaude-sonnet-5-5RailsUse a hosted serviceClaude Codeclaude-sonnet-5-514 losing runs
04
Check what agents saw after trying Acme in Next.js
1 losing scenario · Acme picked in 1 of 8 runs (13%, likely 3–41%)
Most common trails: searched for Acme, fetched Acme's pages, then built its own (4 runs); searched for Acme, then built its own (2 runs).
Suggested
Next.jsAdd an integrationCodexgpt-6.1-sol7 losing runs

Decision trail

Open a reason to follow one run in order: the sites it fetched with their status codes, the packages it installed and the pick it recorded.

Found your tool

See how often agents found your tool in each losing scenario. A low rate is a discoverability gap; a high one means they found it and still chose another.

Agent Picks · Found your tool

Next.jsAdd an integrationCodexgpt-6.1-sol
Found your tool in 100% of runs, likely 75–100%
ExpressAdd an integrationCodexgpt-6.1-sol
Found your tool in 100% of runs, likely 75–100%
ExpressUse a hosted serviceCodexgpt-6.1-sol
Found your tool in 100% of runs, likely 75–100%
RailsAdd an integrationClaude Codeclaude-sonnet-5-5
Found your tool in 38% of runs, likely 16–65%
RailsUse a hosted serviceClaude Codeclaude-sonnet-5-5
Found your tool in 38% of runs, likely 16–65%

Not found means not seen in the test sandbox. Searches and fetches the model makes on its provider’s side aren’t captured.

Make coding agents reach for you first.