agent-trace-triage vs FailTrace
agent-trace-triage is a plugin bundle for AI coding tools published by WasayAbid. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). FailTrace is an MCP server published by LBarimi. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  agent-trace-triage |  FailTrace |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.5.0 Downloads/month (npm): 387 Downloads/week (npm): 89 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | agent-trace-triage | FailTrace |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (failtrace) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/wasayabid/agent-trace-triage | github.com/lbarimi/failtrace |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
agent-trace-triage
Agent Trace Triage is a Claude Code plugin for developers building agentic AI systems (LangGraph, CrewAI, custom tool loops, MCP agents). When an agent run fails, stuck in a loop, wrong tool, or burning tokens. the user runs /agent-trace-triage with a JSON/JSONL trace file. The plugin: • Parses traces (JSONL, OpenAI tool_calls, partial LangSmith/OTEL-style exports) • Detects loops deterministically (identical repeat, ping-pong, retry-without-progress) via bundled Node scripts • Classifies failures into five buckets: tool selection, arguments, execution, orchestration, recovery policy • Writes a markdown triage report with targeted fix recommendations • Scaffolds regression tests (pytest / vitest templates) No MCP servers, no external API calls, no npm dependencies. Requires Node.js 18+ for local scripts only. MIT licensed.
FailTrace
Debugging experiments for coding agents: reproduce failures and verify fixes with test evidence.
How to run each
agent-trace-triage As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install agent-trace-triage@claude-communityFailTrace As a local MCP server: npm package
claude mcp add --transport stdio failtrace -- npx -y failtrace mcp --cwd "<YOUR_CWD>"Requires: --cwd
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: agent-trace-triage · What it can do: FailTrace · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.