WeSearch

AdaMAST: Adaptive Failure Taxonomies for Improving LLM Agents

·9 min read · 0 reactions · 0 comments · 2 views
#machine-learning#llm#agents#taxonomy#research
AdaMAST: Adaptive Failure Taxonomies for Improving LLM Agents
TL;DR · WeSearch summary

AdaMAST introduces an adaptive failure taxonomy that automatically derives named failure modes from an LLM agent’s execution traces. The taxonomy is organized along three fixed axes—system-level, role-specific, and domain-specific—and is validated before use in improvement loops such as best‑of‑N judging, runtime feedback, and mutation feedback. Experiments show notable performance gains across several benchmarks without requiring hand‑crafted codes or human annotation.

Key facts
About this source

Hacker News (AI / LLM) files mainly under ai. We currently carry 3,007 of its stories.

Original article
Github
Read full at Github →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherGithub
Canonical URLhttps://multi-agent-systems-failure-taxonomy.github.io/AdaMAST/blogs/adamast_paper/
Publication timeFri, 31 Jul 2026 06:22:31 +0000
Retrieval time2026-07-31T06:42:50.389Z
Last seen2026-07-31T06:42:50.389Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusterIupwGerunp1s · 1 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

Research blog AdaMAST: Adaptive Failure Taxonomies for Improving LLM Agents Fantastic Adaptive Taxonomies and How to Use Them Mert Cemri1*, Andrei Cojocaru1*, Melissa Pan1, Shu Liu1, Shubham Agarwal1, Alexander Krentsel1, Jay Tang2, Kannan Ramchandran1, Joseph E. Gonzalez1, Matei Zaharia1, Alexandros G. Dimakis1,3, Ion Stoica1 1 UC Berkeley 2 Apple 3 Bespoke Labs · * equal contribution July 2026 🤖 A failure taxonomy is a rubric of an agent system's recurring failure modes. Each mode gets a name, a definition, and evidence quoted from the system's own rollouts. Fixed, hand-built taxonomies such as MAST already work well as debugging aids. But a rubric written before a system exists cannot name the failures specific to that system's roles, harness, or task.

Excerpt limited to ~120 words for fair-use compliance. The full article is at Github.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from Github