Datasets:
issue_id stringlengths 8 8 | framework stringclasses 23
values | date stringlengths 4 7 | short_url stringlengths 2 6 | title stringlengths 13 129 | prevented_at_compile_time float64 | user_dollar_loss stringclasses 10
values | notes stringlengths 17 4.22k | label stringclasses 12
values | primary_cluster stringclasses 8
values |
|---|---|---|---|---|---|---|---|---|---|
LANG-001 | langgraph | 2026-01 | #6731 | Agent infinite looping until recursion limit | null | null | paper:bu; text-to-SQL retry; reproduced in Section 5.3 | bu | M-retry-loop |
LANG-002 | langchain | 2024-01 | #16251 | load_summarize_chain hits infinite loop due to small token_max | null | null | paper:bf; description corrected in v7 from "rec_limit fix" to "summarize-chain loop" | bf | M-retry-loop |
LANG-003 | langchain | 2023-04 | #2548 | Cost getting too high | null | null | SKIPPED for paper. 2023 Q&A thread: reporter @vishnu1991 misunderstood chunked retrieval mechanics (asking why a 2k-token document costs 2k tokens per query). Community members @Qualzz and @kartikbhardwaj2000 explained correctly. Not a failure incident. Auto-closed not-planned by dosubot Sep 26 2023. | SKIPPED | null |
LANG-004 | langchain | 2025-02 | #29779 | Reasoning tokens not in cost calculation | null | null | paper:bu; closed not-planned by dosubot stale-bot May 22 2025. Reporter @dbuos provided langchain_community/callbacks/openai_info.py code with comment line "## reasoning_tokens are not used in the cost calculation below" -- the source code itself acknowledges the gap. Affects o3-mini, o1, and variants. User @roryeckel ... | bu | M-cost-observability |
LANG-005 | langchain | 2025-04 | #30795 | Total cost calculation possible bug with o3-mini | null | null | paper:bf; closed completed Apr 13 2025 by @ccurme via PR #30807, fixed in commit f005988. Reporter @tdahar provided minimal repro showing o3-mini total_cost calc returned $0.012 instead of expected ~$0.05 (4x undercount). Bug was in standardize_model_name not recognizing o3 as completion-priced model. Fixed in 2 days. ... | bf | M-cost-observability |
LANG-006 | langsmith | 2025-10 | #2085 | Token count and cost incorrectly display as 0 | null | null | paper:mf; closed completed Oct 30 2025 by @angus-langchain with "this has been released for a week." LangSmith silently deprecated server-side token tokenization, breaking cost displays for all gpt-4.1, gpt-4o, o3-mini traces from Oct 23 2025. Multiple users affected. Resolution shifted cost-counting responsibility fro... | mf | M-cost-observability |
LANG-007 | langsmith | 2025-09 | #2024 | Cost showing up as 0 despite having tokens | null | null | paper:bu; OPEN as of Dec 2025. Reporter @ryanlohyr documents OpenAI gpt-4o calls via Responses API showing $0 cost in LangSmith despite token usage. Maintainer @angus-langchain self-assigned then confirmed: "Confirmed I can repro. This is related to the Responses API which we are working on supporting better." Three mo... | bu | M-cost-observability |
LANG-008 | langchain | 2024-02 | #19120 | OpenAI Tokens and Cost are inaccurate | null | null | paper:bu; closed not-planned by dosubot stale-bot Jul 4 2024 with no fix. Reporter @ArslanKAS documents get_openai_callback returning 815 tokens and $0.00134 USD for a gpt-3.5-turbo request that llm.get_num_tokens cross-check showed should be ~13K tokens (~16x undercount). One community confirmation @axiangcoding "Same... | bu | M-cost-observability |
LANG-009 | deepagentsjs | 2025-12 | #82 | Agent infinite loop with large tool results | null | null | paper:bf; flagship deepagentsjs entry. Reporter @KDKHD documents three-way interaction between toolTokenLimitBeforeEvict, filesystem-eviction, and read_file line limit causing infinite eviction/read loop. LangSmith trace at https://smith.langchain.com/public/5ccfa3e5-07f0-4572-b205-22ae3d3d5689/r Fixed in PR #172 by @c... | bf | M-retry-loop |
LANG-010 | langchain | 2024-02 | #18212 | get_openai_callback returns 0 for create_openai_functions_agent | null | null | paper:bf; closed completed Mar 15 2024 by @eyurtsev as duplicate of #16798, patch released in PR #18761 (langchain 0.1.12). Reporter @lamparelli documents the langchain-recommended create_openai_functions_agent constructor silently breaks get_openai_callback (returns 0 tokens, $0 cost) while the deprecated OpenAIFuncti... | bf | M-cost-observability |
LANG-011 | langchain | 2023-10 | #11347 | Conversational Chain Error 429 | null | null | SKIPPED for paper after URL verification (S6 rate-limit-not-budget). Filed Oct 3 2023 by @harchyboy; auto-stale-closed by dosubot Feb 10 2024 with no fix. Reporter hits OpenAI 10KTPM rate limit when using ConversationChain but not bare LLMChain. Contributor @sudranga speculates memory-type summarization may make additi... | S6 | null |
LANG-012 | langchain | 2024-05 | #22241 | 429 Resource Exhausted with gemini-1.5-pro | null | null | paper:bu; closed completed Nov 11 2025 by @mdrxy after 18-month thread; partial fix later in PR by @IrakliGLD Dec 10 2025 ("Reduce LangChain retry attempts from 6 to 2 to prevent quota exhaustion"). Filed May 28 2024 by @sidagarwal04 against gemini-1.5-pro. Reporter saw retry attempts every 2/4/8/16/32 seconds when API... | bu | M-retry-loop |
LANG-013 | langgraph | 2025-08 | #6027 | Node Retry Policies not respected on ValidationError | null | null | paper:bu; closed by @casparb Sep 9 2025 with documentation pointer rather than framework fix. Subtle silent failure: RetryPolicy() does NOT retry on Pydantic ValidationError (which is a ValueError subclass) by default. Workaround requires explicit RetryPolicy(retry_on=ValidationError). Default behavior unchanged. Follo... | bu | M-retry-loop |
LANG-014 | langchain | 2023-08 | #9717 | Langchain QA over large documents results in Rate limit errors | null | null | paper:bu; closed by reporter @gourao Aug 29 2023 with "Found a different way to accomplish this" -- never shared the workaround despite multiple followup requests from @Wesleystormrage and @afedotov-align. Issue references 5+ related rate-limit issues (#11155, #11500, #11657, #11907, #12712, #12986). Documents 2023-era... | bu | M-retry-loop |
LANG-015 | langgraph | 2025-06 | #4927 | Agent timeout causes error | null | null | SKIPPED for paper after URL verification (S1 wrong-failure-class). Filed Jun 3 2025 by @JiayuChen02; closed Jun 4 2025 (next day) by @nfcampos via PR #4950. Bug: setting supervisor_agent.step_timeout=180 in multi-agent LangGraph supervisor causes ParentCommand/GraphInterrupt exceptions to bubble up incorrectly through ... | S1 | null |
LANG-016 | langchain | 2024-08 | #25309 | No notification when exceeding Anthropic rate limit | null | null | paper:bu; auto-stale-closed by dosubot Dec 6 2024 with no fix. Filed Aug 12 2024 by @albint3r against ChatAnthropic. Reporter documents the application silently hangs (no exception, no timeout) after exceeding Anthropic 40k tokens/minute limit, requiring server restart. Reproduces locally, ruled out NGINX. Collaborator... | bu | M-retry-loop |
ATGN-001 | autogen | 2023-10 | #108 | Infinite loops with gpt4, OpenAI rate limit triggered | null | null | SKIPPED for paper after URL verification (S2 duplicate-of-existing). Filed Oct 5 2023 by @adriangalilea; closed Oct 9 2023 by @LittleLittleCloud after providing workaround. Same root mechanism as paper-tagged ATGN-002: termination-check failure causing default-auto-reply loop with rate limit consequences. Root cause: i... | S2 | null |
ATGN-002 | autogen | 2025-02 | #5317 | Infinite loop in quick start sample with additional agent | null | null | paper:bu; closed by reporter Feb 4 2025. Maintainer ekzhu response: "Interesting attempt to break the example :)" classified the cascading-message behavior as inherent to default subscriptions, provided documentation workaround using separate topics; framework was NOT patched. First AutoGen entry in catalog. | bu | M-retry-loop |
ATGN-003 | autogen | 2025-03 | #5831 | Infinite loop in swarm with human dialogue | null | null | paper:mf; converted to discussion #5869 by @ekzhu Mar 7 2025 (effectively closed without fix). Maintainer response to swarm infinite-loop: "It is because the model could not generate a tool call for handing off to the user [...] No magic here." Multiple users (@toughnoah) report the same with gpt-4o and qwen-max. Stren... | mf | M-retry-loop |
ATGN-004 | autogen | 2023-10 | #198 | Token limit and rate per minute limit errors in framework demo notebooks | null | null | paper:bu; UPGRADED from SKIPPED in v22-batch-24 revision per codebook section 10. Original triage skipped as S6 (rate-limit-not-budget) but new cross-reference evidence from ATGN-018 (#1070) recharacterizes the rate-limit and context-overflow errors as concrete user-impact of the architectural cost amplification mechan... | S6 | null |
ATGN-005 | autogen | 2023-10 | #156 | Roadmap for handling context overflow | null | null | paper:fr; closed completed Mar 14 2024 by @yiranwu0 when several PRs (#131, #421, #443, #497) merged. 2023-era AutoGen roadmap parallel to AGPT-001/002. Documentation pointer (microsoft.github.io/autogen/docs/topics/long_contexts) cited Apr 2024 by @ekzhu became 404 by Sep 2025 after AutoGen v0.4 rewrite, with user @re... | fr | M-context-amplification |
ATGN-006 | autogen | 2024-12 | #4719 | Token usage and latency metrics in TaskResult | null | null | paper:fr; OPEN as of Feb 2025. Filed Dec 16 2024 by lead maintainer @ekzhu himself. Documents specific cost-observability gap in autogen-agentchat 0.4 architecture: "Console is currently using agents inner messages to keep track of the total token usage -- this is inaccurate. As agents may not emit inner messages, and ... | fr | M-cost-observability |
ATGN-007 | autogen | 2023-10 | #175 | We Need a Token Count | null | null | paper:fr; closed completed Oct 12 2023 by @qingyun-wu via PR #179 by @yiranwu0. Filed Oct 10 2023 by @aiInvader: "This is a super crucial feature. When finished executing, we need the token count." Reporter pushed back when @qingyun-wu pointed to existing logging (which only logged cost in USD, not token count). Mainta... | fr | M-cost-observability |
ATGN-008 | autogen | 2025-02 | #5400 | Token counting issues with smaller models | null | null | paper:bu; OPEN as of Feb 2025. Filed Feb 6 2025 by Member @afourney (Microsoft Research). Documents KeyError llama3.3:latest from _MODEL_TOKEN_LIMITS[resolved_model] in autogen-ext openai client when using local Ollama models. remaining_tokens() and get_token_limit() crash; multimodal_web_surfer breakage. Console flood... | bu | M-cost-observability |
CRAI-001 | crewai | 2023-12 | #6 | AgentExecutor chain loop stucked, will break OpenAI budget | null | null | paper:bf; first crewai loop incident | bf | M-delegation-fanout |
CRAI-002 | crewai | 2024-09 | #1355 | Agents getting stuck in loop since move to LiteLLM | null | null | paper:bf; LiteLLM-introduced regression, same-day patch | bf | M-retry-loop |
CRAI-003 | crewai | 2024-06 | #738 | Loop in crew execution | null | null | SKIPPED for paper. Bare 2-sentence bug report by @Ai-ENGINEER-s with no code, no logs, no repro. Asked for details by @mangalprada on Jun 8, no follow-up. Auto-closed by github-actions stale-bot Aug 22 2024. | SKIPPED | null |
CRAI-004 | crewai | 2024-01 | #183 | Looping tasks | null | null | SKIPPED for paper after URL verification (S4 qa-not-incident). Filed Jan 25 2024 by @chriscamacho as a workflow-design question (4-line body): how to chain programming-agent and testing-agent tasks with feedback loop. No incident, no mechanism, no cost evidence. @Biancamazzi (bot tag) pointed to Discord; community user... | S4 | null |
CRAI-005 | crewai | 2025-08 | #3299 | Thinking budget parameter for gemini models | null | null | SKIPPED for paper. Resolved same-day by reporter @Vamshi3130 after user @mouramax pointed to existing LiteLLM thinking_budget passthrough. Not a real failure incident. Closed Aug 9 2025. | SKIPPED | null |
AGPT-001 | autogpt | 2023-04 | #6 | Make Auto-GPT aware of running cost | null | null | paper:fr; first runaway-cost feature request | fr | M-budget-primitive-missing |
AGPT-002 | autogpt | 2023-04 | #393 | Set budget per session with soft/hard cap | null | null | paper:fr; "set budget for each session with soft and hard cap" | fr | M-budget-primitive-missing |
AGPT-003 | autogpt | 2024-06 | #7216 | Optimally productive per dollar of LLM expense; risk of infinite recursion | null | null | SKIPPED for paper. Roadmap/SWOT meta-issue from maintainer @Pwuts; mentions infinite-recursion as a "Threat" but no production incident, no dollar amount. Closed not-planned as duplicate of #6964 by Pwuts on Jun 14 2024. CSV title misleading. | SKIPPED | null |
AGPT-004 | autogpt | 2023-04 | #2726 | auto-gpt stuck in a loop of thinking | null | null | SKIPPED for paper after URL verification (S5 user-found-existing-feature). Filed Apr 21 2023 by @MikeWIseX0; closed same-day by reporter after community member @90stm pointed out the issue was lack of paid OpenAI billing account ("Setup a paid account here... it wasnt until I did this that those same issues disappeared... | S5 | null |
AIDR-001 | aider | 2024-09 | #1842 | Loop ran up $13 in charges rapidly | null | 13.55 | paper:bf; fixed same day in commit f2e1e17 | bf | M-retry-loop |
AIDR-002 | aider | 2024-09 | #1841 | Loop trying to answer a question, tokens 22k->313k | null | 0.43 | SKIPPED for paper (duplicate of AIDR-001 root cause): same fix commit f2e1e17. Comments link to #1842. Note user 0-sv reports separate $11.64 loop in deleted folder Nov 2024. | SKIPPED | null |
AIDR-003 | aider | 2024-11 | #2491 | Enormous token counts and costs from rate limit retries | null | 83 | paper:bu; auto-closed by github-actions stale-bot Dec 27 2024 with no fix. Reporter @tom-doerr documents $83 in a single day. Other user @etewiah reports same call sending 114k tokens then 915k tokens after rate-limit retries ($2.75 message). Maintainer @paul-gauthier framed as display-layer issue ("the provider should... | bu | M-retry-loop |
AIDR-004 | aider | 2024-07 | #863 | Tokens leak: 11k tokens for small change | null | null | paper:mf; closed by maintainer @paul-gauthier Aug 6 2024. Reporter @ErykCh observed 11k tokens consumed for /tokens displayed 1.8k context (6.1x amplification). Maintainer initially confirmed bug ("not showing the tokens used by the repo-map. I will get this fixed") then walked back over multiple comments: "The --map-t... | mf | M-context-amplification |
AIDR-005 | aider | 2024-10 | #1919 | Costly message $4.99 with token limits breach | null | 4.99 | paper:bu; closed not-planned by github-actions stale-bot Oct 29 2024 with no maintainer fix. Issue body shows "$4.99 message, $9.68 session" verbatim; oversize-msg breach (1.66M tokens vs 200k limit). Distinct failure mode from AIDR-001 retry loop. | bu | M-retry-loop |
AIDR-006 | aider | 2025-04 | #3803 | DeepSeek R1 thinking in thousands of tokens, cannot limit | null | null | paper:bu; OPEN. New failure subclass: reasoning-model hidden-token consumption. Reporter @GeorgeFlorian: DeepSeek-R1 thinks in thousands of tokens before response; aider thinking-tokens setting does not take effect. Workaround reasoning.exclude:true suppresses visibility but not consumption. Adds reasoning-model subcla... | bu | M-context-amplification |
AIDR-007 | aider | 2024-01 | #458 | /tokens pricing calculations bug | null | null | SKIPPED for paper after URL verification (S3 weak-evidence-stub). Filed Jan 27 2024 by @transcendr; same-day fix by @paul-gauthier in commit 35f8128 closing Feb 10 2024. The bug is a pricing-table lookup error (gpt-4-turbo-preview displayed at base gpt-4 pricing, ~2-3x overstated) not a silent-zero or mechanistic under... | S3 | null |
LLMI-001 | llamaindex | 2024-05 | #13278 | RateLimitError: Error code 429 quota exceeded | null | null | SKIPPED for paper after URL verification (S5 user-found-existing-feature). Filed May 6 2024 by @craigjurs; closed-completed by reporter May 7 2024 (one day later) with self-resolution: "After some investigation Ive found that indeed its my lack of attention about the refresh on the openai account which caused the api k... | S5 | null |
LLMI-002 | llamaindex | 2024-08 | #15083 | Tool calling broken when LLM responds with both text and tool calls | null | null | SKIPPED for paper. Streaming/tool-calling correctness bug not budget overrun. When GPT-4o returns text+tool_calls in same message, stream_chat ignores tool_call and chat stalls. Fixed by maintainer @logan-markewich Apr 10 2025 via new agent-workflows API. | SKIPPED | null |
LLMI-003 | llamaindex | 2023-04 | #1070 | Cost of building and querying each index TODO | null | null | paper:fr; closed completed Jul 26 2023 by @Disiok with documentation pointer to TokenCountingHandler. Earliest documented cost-tracking gap in LlamaIndex (cited "TODO" from reference docs). Same era as AGPT-001/002. Adds LlamaIndex (run-llama/llama_index) to the catalog. Maintainer @logan-markewich answered followup qu... | fr | M-cost-observability |
LLMI-004 | llamaindex | 2025-08 | #19722 | Storing tool's raw result from agent's tool calling | null | null | SKIPPED for paper after URL verification (S1 wrong-failure-class). Filed Aug 22 2025 by @bzr1 as a workflow-design question: how to capture raw tool outputs from agent.run() given that the default return is LLM-processed not raw. Collaborator @logan-markewich engaged with technical clarification about Context-typed too... | S1 | null |
CCDE-001 | claude-code | 2025-10 | #9579 | Autocompacting Loop Causing Massive Token Usage Spikes | null | 235 | paper:bf; quoted by maintainer @bcherny; closed by commit Oct 17, 2025 | bf | M-retry-loop |
CCDE-002 | claude-code | 2025-08 | #6461 | [Bug] [Has Workaround] Auto-Compact Resetting Context Limit To 4-6% Causing Frequent Compaction Loop | null | null | paper:bu; closed not-planned by github-actions bot Jan 4 2026 after 60-day inactivity. Filed Aug 24 2025 by @Codewow. Same compaction-loop signature as CCDE-001. Bot itself flagged three duplicates at filing (#6004, #6315, #6232) and the activity log references at least seven additional sibling issues filed Aug-Dec 202... | bu | M-retry-loop |
CCDE-005 | claude-code | 2025-10 | #8838 | [Bug] Auto-Compact Loses Track of Active Commands During Cleanup | null | null | SKIPPED for paper after URL verification. Closed as duplicate of #3321 (.mcp.json not read) by github-actions bot Oct 7 2025. Filed Oct 3 2025 by @eliasstepanik. Underlying root cause is MCP JSON parsing failure plus Cloudflare 525 SSL handshake errors, not a budget overrun. Bot flagged duplicates of unrelated issues (... | SKIPPED | null |
GPTE-001 | gpt-engineer | 2023-07 | #551 | Rate limit reached for 10KTPM-200RPM | null | null | SKIPPED for paper after URL verification (S6 rate-limit-not-budget). Filed Jul 23 2023 by @pdavis68; closed by owner @AntonOsika Sep 2 2023 with upstream classification: "Doesn't seem like an issue with gpt-engineer but openai, happy to hear suggestions will close otherwise." Reporter wrote a 150-line prompt + answers ... | S6 | null |
GPTE-002 | gpt-engineer | 2023-06 | #114 | Specifications repeating, consuming many tokens | null | null | paper:bf; first gpt-engineer entry. Owner @AntonOsika initially classified spec-repetition as "part of the introspection process" (mf framing) but reduced excessive specs and closed Jun 21 2023. Concrete reproduction: simple "write a 2D car racing game" prompt produces doubled spec output, hits "Aborted" without comple... | bf | M-context-amplification |
GPTE-003 | gpt-engineer | 2023-06 | #322 | Track and log token usage | null | null | paper:fr; closed completed Jul 5 2023 by @AntonOsika (project owner) via PR #438 merged by @UmerHA. Filed Jun 22 2023 by @AntonOsika himself: "Print and store how many tokens were used in memory/logs. In this way, we can also store this to benchmark results. A huge increase in tokens will not be worth a minor improveme... | fr | M-storage-amplification |
DNSW-001 | danswer | 2024 | PR1569 | Word of warning: 2k euros spent in a few days | null | ~2150 (2000 EUR) | paper:bu; multi-day onyx deployment loss | bu | M-budget-primitive-missing |
OCLW-001 | openclaw | 2026-02 | #5960 | Agent session 123 Opus calls in 16min, $4.85, no cap | null | 4.85 | paper:bu; WONTFIX | bu | M-delegation-fanout |
NANO-001 | nanobot | 2026-03 | #2318 | Tool-loop cost roadmap; max_iterations doesn't cap spend | null | 2.70 | paper:fr; max_cost_per_message proposal | fr | M-retry-loop |
PCLP-001 | paperclipai | 2026-03 | #390 | Agent circuit breaker; #1 pain point across all multi-agent tools | null | null | paper:mf; "#1 pain point across all multi-agent tools" | mf | M-retry-loop |
CDXL-001 | codex | 2026-04 | #18335 | Agent spawn slots leak across turns in persistent sessions | null | null | paper:mf; closed "by design" by maintainer jif-oai. Reporter documents 24 spawns / 14 closes across 9 rounds; spawn permanently blocked from round 4 onward. Follow-up issue #19197 (persistent orphaned subagents) opened by user vzd3v: "It is hard for me to understand why this issue was closed." | mf | M-delegation-fanout |
AGNO-001 | agno | 2024-10 | #1284 | Ollama setup requiring openai-api key? | null | null | SKIPPED for paper after URL verification (S1 wrong-failure-class). Filed Oct 21 2024 against phidata 2.5.9 (pre-rename to agno) by @gitmurawka; closed same day by @jacobweiss2305 after pointing out user used deprecated llm= parameter instead of model=, which caused phidata to fall back to OpenAI default and fail with a... | S1 | null |
AGNO-002 | agno | 2025-02 | #2156 | Fix Agentic Chunking | null | null | SKIPPED for paper after URL verification (S1 wrong-failure-class). PR merged Feb 17 2025 by @dirkbrnd, authored by @manthanguptaa. Bug: agentic-chunking module hardcoded OpenAI as a dependency even when user configured a different model. Same shape as AGNO-001: misconfiguration/hardcoded-OpenAI-dependency bug, not a co... | S1 | null |
AGNO-004 | agno | 2025-05 | #3421 | Pass filters for traditional RAG | null | null | SKIPPED for paper after URL verification (S1 wrong-failure-class). PR merged Jun 2 2025 by @dirkbrnd, authored by @kausmeows. Bug: add_references=True (traditional RAG path) was not threading knowledge_filters through to vector search, while the agentic-RAG path did. RAG filtering correctness bug, not a cost mechanism.... | S1 | null |
ATGN-009 | autogen | 2024-11 | #4172 | Logging metrics for agents | null | null | paper:bf; closed completed Jun 14 2025 by @victordibia citing model_usage and OTEL support as the resolution. Filed Nov 14 2024 by @fniedtner (Microsoft, AutoGen team member) documenting v0.4 cost-observability regression vs v0.2: lost client.total_usage_summary and planner.client.actual_usage_summary fields, plus 5 ot... | bf | M-cost-observability |
ATGN-010 | autogen | 2024-12 | #4835 | Model Costs and Cached Tokens | null | null | paper:bu; OPEN as of Mar 2026. Filed Dec 27 2024 by @Leon0402 (Contributor) documenting that v0.4 RequestUsage dataclass lacks cost and cached-tokens fields that v0.2 had. @ekzhu engaged immediately: "yes, it is important. We are planning to address this after the 0.4.0. For now, lets targeting 0.4.1 for this one. #476... | bu | M-cost-observability |
ATGN-011 | autogen | 2025-02 | #5620 | Observability (epic/parent issue) | null | null | SKIPPED for paper after URL verification (S7 roadmap-doc-not-incident). Filed Feb 19 2025 by @jackgerrits as an epic/parent issue: "There are a number of related issues around this overall topic, using this as the parent issue. We need to improve the tracking of usage and cost of models." Lists 4 sub-issues including #... | S7 | null |
ATGN-012 | autogen | 2025-02 | #5590 | Outputs in docs are outdated as summary is not printed out by default | null | null | SKIPPED for paper after URL verification (S1 wrong-failure-class). Filed Feb 18 2025 by @thinkall (Collaborator); closed via PR #5720 by @victordibia Feb 26 2025. Bug: documented Console output shows token-usage summary by default but in scripts/notebooks the summary requires output_stats=True. @ekzhu acknowledged: "Th... | S1 | null |
ATGN-013 | autogen | 2024-12 | #4750 | Define AgentEvent, rename tool call messages to events | null | null | SKIPPED for paper after URL verification (S1 wrong-failure-class). PR merged Dec 19 2024 by @ekzhu, resolves #4533. Pure type-system refactor: introduces AgentEvent type, renames tool-call messages to events. Referenced in ATGN-006 thread as adjacent architectural change but its own scope is naming/structure only. No c... | S1 | null |
ATGN-014 | autogen | 2024-12 | #4768 | Fix tracking SelectorGroupChat tokens with new Message type | null | null | SKIPPED for paper after URL verification (S2 duplicate-of-existing). Exploratory PR by @gziz Dec 20 2024, closed by author same day to consolidate discussion in #4771 (ATGN-015). Author body: "The below changes are not meant to be merged but rather are here to open a discussion about how to correctly track the token us... | S2 | null |
ATGN-015 | autogen | 2024-12 | #4771 | Track SelectorGroupChat token usage with new Message type | null | null | SKIPPED for paper after URL verification (S2 duplicate-of-existing). Exploratory PR by @gziz Dec 20 2024 proposing UsageEvent message type; closed without merge by @jackgerrits Feb 26 2025: "I am going to go ahead and close this as I think we need to take a holistic look at cost tracking and will overhaul it." Discussi... | S2 | null |
ATGN-016 | autogen | 2025-03 | #6000 | BaseGroupChat ignore_unhandled_exceptions kwarg mismatch | null | null | SKIPPED for paper after URL verification (S1 wrong-failure-class). GitHub Discussion (not Issue) filed Mar 19 2025 by @yaoyanglee documenting API/version-skew bug: BaseGroupChat passes ignore_unhandled_exceptions=False to SingleThreadedAgentRuntime.__init__ but user runtime version does not accept that kwarg. @ekzhu re... | S1 | null |
ATGN-017 | autogen | 2025-03 | #5800 | Save/Load in .NET AgentChat | null | null | SKIPPED for paper after URL verification (S1 wrong-failure-class). Filed Mar 4 2025 by @lokitoth (Member); closed Mar 14 2025 via PRs #5841 and #5855. .NET feature implementation issue for save/load APIs in AgentChat.NET. No cost mechanism, no incident, no documented spend or amplification. | S1 | null |
AIDR-008 | aider | 2025-01 | #2842 | Feature request: search the web via searx google and/or jina ai | null | null | SKIPPED for paper after URL verification (S1 wrong-failure-class). Web-search feature request by @KUKARAF Jan 12 2025: requesting /search action to query searx/google/jina. Not budget-related. Issue OPEN, low engagement, no maintainer response on cost angle. | S1 | null |
AIDR-009 | aider | 2025-03 | #3471 | claude code /compact command | null | null | paper:fr; OPEN as of Sep 2025. Filed Mar 9 2025 by @kanishkaverma requesting Aider implement claude-code /compact command. Maintainer @paul-gauthier initial response (Mar 11 2025): "Aider already automatically compacts/summarizes the conversation periodically" - a "by-design"-style framing. Community pushed back: @para... | fr | M-context-amplification |
AIDR-011 | aider | 2025-05 | #4012 | fix: base coder not ignoring gitignore if --file is used | null | null | SKIPPED for paper after URL verification (S1 wrong-failure-class). PR by @ujisati May 13 2025, closed by author same day. Fixes base_coder gitignore handling when --file flag is used. Not cost-related. | S1 | null |
AIDR-012 | aider | 2025-01 | #2934 | Does Aider support removing the thinking content of previous replies | null | null | SKIPPED for paper after URL verification (S2 duplicate-of-existing). Filed Jan 21 2025 by @Mushoz; closed Jan 27 2025 by @paul-gauthier as duplicate of #3008: "This looks like a dup of #3008." Same M-reasoning-token-leak mechanism as paper-tagged AIDR-006 (DeepSeek-R1 hidden-token consumption); maintainer-confirmed dup... | S2 | null |
AIDR-013 | aider | 2025-02 | #3245 | refactor: Update editor discovery to handle environment variables | null | null | SKIPPED for paper after URL verification (S1 wrong-failure-class). PR by @devriesd Feb 14 2025, closed unmerged same day. Refactor to handle EDITOR/VISUAL environment variables for the /editor command. Not cost-related. | S1 | null |
AIDR-014 | aider | 2024-09 | #1789 | Uncaught AttributeError in sendchat.py line 30 | null | null | SKIPPED for paper after URL verification (S2 duplicate-of-existing; also S1 wrong-failure-class). Filed Sep 28 2024 by @faroucksc; closed same day by @paul-gauthier as duplicate of #1414. Stack trace shows AttributeError in retry decorator: module litellm.llms.anthropic has no attribute AnthropicError - pure litellm ve... | S2 | null |
AIDR-015 | aider | 2024-12 | #2567 | Fixed /chat-mode architect no description | null | null | SKIPPED for paper after URL verification (S1 wrong-failure-class). PR by @reecelikesramen Dec 9 2024, closed unmerged Dec 10 2024 by @paul-gauthier ("I will fix this up with different text, thanks"). Fixes display of "No description" text for editor-diff and editor-whole modes in /chat-mode listing. UI text fix, not co... | S1 | null |
AIDR-016 | aider | 2025-03 | #3678 | Uncaught UnboundLocalError in repo.py line 302 | null | null | SKIPPED for paper after URL verification (S1 wrong-failure-class). Filed Mar 30 2025 by @cristibctr; closed Mar 31 2025 by @paul-gauthier with same-day fix tagged priority. UnboundLocalError in repo.py line 302 caused by upstream IndexError in git tree-walking (gitpython library). Pure git-handling bug, not cost mechan... | S1 | null |
AIDR-017 | aider | 2025-09 | #4500 | Uncaught LookupError in core.py line 305 | null | null | SKIPPED for paper after URL verification (S1 wrong-failure-class). Filed Sep 3 2025 by @jhf. Stack trace: LookupError "unknown encoding: hex" in codecs.encode(os.urandom(16), "hex") inside diskcache library used for repomap caching. Python compatibility bug (hex codec removed); not cost mechanism. Issue OPEN as of Sep ... | S1 | null |
CCDE-003 | claude-code | 2025-06 | #2546 | False Capability Claims and Immediate Self-Contradiction | null | null | SKIPPED for paper after URL verification (S1 wrong-failure-class; also S2 duplicate-of-existing). Filed Jun 24 2025 by @SDS-Mike; closed Aug 21 2025 by github-actions bot as duplicate of #1360. Documents Claude Code making confident false statements about own capabilities (file access, conversation history). Self-knowl... | S1 | null |
CCDE-004 | claude-code | 2025-07 | #3287 | Memory Insertion Corrupts Entire claude.md File Content | null | null | SKIPPED for paper after URL verification (S1 wrong-failure-class). Filed Jul 10 2025 by @mkamrans; auto-closed Jan 5 2026 as not planned. Claude Codes # annotation feature for adding memory deletes the rest of CLAUDE.md content and replaces with "[remaining content has not changed]" placeholder. Real bug with multiple ... | S1 | null |
CCDE-006 | claude-code | 2025-07 | #2891 | Hooks not executing despite following documentation | null | null | SKIPPED for paper after URL verification (S1 wrong-failure-class). Filed Jul 3 2025 by @grahama1970; closed Jan 15 2026 by @dicksontsai with workaround pointing to CLAUDE_PROJECT_DIR docs. Long thread Jul 2025 -> Jan 2026 with sibling issues #5093, #5307, #5648, #6403, #6876, #7905, #8388, #10098, #12172, #13572. PreTo... | S1 | null |
CCDE-007 | claude-code | 2025-07 | #3672 | PreToolUse hooks not executing at all in Claude Code | null | null | SKIPPED for paper after URL verification (S1 wrong-failure-class). Filed Jul 17 2025 by @cobach; closed same day by @dicksontsai with config-format correction (matcher should be string not object). User-error/config-format issue, same shape as CCDE-006. | S1 | null |
CCDE-009 | claude-code | 2025-07 | #4156 | Image Paste Functionality Broken in CLI Interface | null | null | SKIPPED for paper after URL verification (S1 wrong-failure-class). Filed Jul 23 2025 by @boscorp on Windows; self-closed Jul 31 2025 ("I do not know when, but now it works"). Image paste broken on Windows due to ENOENT error trying to read C:\proc\version. Pure platform/UI bug, not cost. | S1 | null |
CCDE-010 | claude-code | 2025-07 | #4823 | Display Current Model and Add a Shortcut for Model Switching | null | null | SKIPPED for paper after URL verification (S5 user-found-existing-feature). Filed Jul 31 2025 by @arrrggghhh; auto-closed Feb 9 2026 as not planned. Quotable cost-framing in body: "Opus has much stricter usage limits than Sonnet. While it would be ideal to use Opus continuously, in practice, my workflow involves using S... | S5 | null |
CCDE-011 | claude-code | 2025-07 | #3941 | Terminal Rendering Glitch on Warp with Long Conversation Context | null | null | SKIPPED for paper after URL verification (S1 wrong-failure-class; also S2). Filed Jul 18 2025 by @zubenelakrab; closed Aug 20 2025 as duplicate of #5224. Mouse-event/terminal rendering glitch on Warp terminal with long conversation context. UI bug, not cost mechanism. | S1 | null |
CCDE-012 | claude-code | 2025-07 | #4502 | request (voice support for visually impaired users) | null | null | SKIPPED for paper after URL verification (S1 wrong-failure-class; also S2). Filed Jul 26 2025 by @Aaronminer1; closed Aug 15 2025 as duplicate of #2189. Voice-support accessibility feature request. Not cost-related. | S1 | null |
LITE-001 | litellm | 2025-02 | #8423 | automated nesting when using litellm sdk within langfuse observe() decorated function | null | null | SKIPPED for paper after URL verification (S1 wrong-failure-class). Filed Feb 9 2025 by @marcklingen (Langfuse contributor); closed Aug 6 2025 as not planned. Feature request to auto-detect langfuse_context and set existing_trace_id/parent_observation_id automatically when LiteLLM SDK is called from inside @observe()-de... | S1 | null |
LITE-002 | litellm | 2024-11 | #6789 | Number of golden records in output is not the same as requested in input during synthesis | null | null | SKIPPED for paper after URL verification (S1 wrong-failure-class). Filed Nov 18 2024 by @nalin-programmer in wrong repo (issue is about deepeval golden-records synthesis, not LiteLLM). Closed same-day by @ishaan-jaff: "you are on the wrong repo." Not relevant to any cost mechanism. | S1 | null |
LITE-004 | litellm | 2024-12 | #7234 | (UI QA) - stop making expensive UI queries when 1M+ spendLogs in DB | null | null | SKIPPED for paper after URL verification (S1 wrong-failure-class). PR merged Dec 15 2024 by @ishaan-jaff. UI performance fix for spendLogs DB queries (avoid expensive queries when >1M rows). Internal UI optimization, not cost mechanism in the framework-budget-overrun sense. | S1 | null |
LITE-005 | litellm | 2024-09 | #5891 | Add a (strict) lint check either before or during runtime for litellm config.yaml | null | null | SKIPPED for paper after URL verification (S1 wrong-failure-class). Filed Sep 25 2024 by @ishaan-jaff (maintainer); auto-closed May 7 2025 as not planned. Feature request for config.yaml lint check on startup. Config validation, not cost mechanism. | S1 | null |
LITE-006 | litellm | 2025-04 | #10245 | Suspected logic bug in get_optional_params | null | null | SKIPPED for paper after URL verification (S1 wrong-failure-class). PR by @peteski22 Apr 24 2025; auto-closed Aug 26 2025 as stale. Refactors get_optional_params function-call/tools handling logic and adjusts ollama special-case. Refs issue #10244. Internal refactor, not cost mechanism. | S1 | null |
LITE-008 | litellm | 2024-10 | #6512 | (prod stable branch) Oct 28th | null | null | SKIPPED for paper after URL verification (S1 wrong-failure-class). Production stable branch merge PR by @ishaan-jaff Oct 30 2024; closed by author same day after consolidation. 1201 line additions across 74 files; not a single-issue cost mechanism. | S1 | null |
LITE-009 | litellm | 2025-03 | #8967 | (UI) Fixes to session token handling | null | null | SKIPPED for paper after URL verification (S1 wrong-failure-class). PR by @ishaan-jaff Mar 4 2025; closed by author same day. Cookie/session-token UI handling fixes (stop storing userID in URL, use cookie utils). Auth/UI bug, not cost mechanism. | S1 | null |
LITE-010 | litellm | 2025-01 | #7678 | heroku additions - initial test | null | null | SKIPPED for paper after URL verification (S1 wrong-failure-class). PR by @hillarysanders Jan 11 2025; closed Jan 17 2025 by author (deleted head repository). Initial WIP for Heroku LLM provider integration. Provider integration, not cost mechanism. | S1 | null |
MAST-001 | mastra | 2025-07 | #5850 | [BUG] Upstash for storage is getting ridiculously expensive | null | 100 | paper:bu; closed Aug 9 2025 via PR #6672 (docs warning, NOT code fix). Reporter @MaryOfLA documents +$100 USD spent in development phase ("Just 20 or 30 conversations testing the agent setup") with claude-sonnet-4-20250514 + Upstash Redis storage; three-word agent question generated huge entry. Second user @leo-paz (Ju... | bu | M-storage-amplification |
MAST-002 | mastra | 2025-07 | #5703 | Token / Cost Usage Tracking? | null | null | paper:fr; closed completed Jul 30 2025 by Member @wardpeet citing https://mastra.ai/blog/nested-streaming-support and forthcoming docs. Filed by Member @abhiaiyer91 himself on behalf of Discord user. Quotable: "Pre Mastra, I built a basic cost logger that tracked the token usage results from OpenAI calls. Would be grea... | fr | M-cost-observability |
MAST-003 | mastra | 2025-10 | #9016 | [FEATURE] Track token usage across agent network iterations | null | null | paper:fr; closed completed Nov 3 2025 by @taofeeq-deru via PR #9649 (commit 1521d71). Filed by Contributor @rase- on Oct 20 2025. Body: "Currently, the individual steps in an agent network have their usages reported through nested events. However, there is no overarching usage tracking. Add usage data into existing age... | fr | M-cost-observability |
MAST-004 | mastra | 2025-06 | #5490 | [BUG] memory processor only run the 1st time agent is called | null | null | paper:mf; closed by Member @abhiaiyer91 Jul 11 2025: "Closing as is by design for now!" -- direct by-design closure quotable. Filed by @vikyw89 Jun 26 2025 documenting TokenLimiter(127000) memory processor only running at memory-retrieval step, not per-LLM-call inside agentic loop. Quotable user concern: "Some model on... | mf | M-context-amplification |
MAST-005 | mastra | 2025-12 | #11273 | maxOutputTokens quits agentic loop if max output tokens reached at a particular step | null | null | paper:fr; UPGRADED from SKIPPED in v22-batch-26 revision per codebook section 10. Original triage skipped as S5 (user-found-existing-feature) but new evidence-deepening (Discord-source verbatim quotes, trace evidence, primitive-exists-but-only-via-callback-closure sub-mechanism framing) recharacterizes as fr-shape M-bu... | S5 | null |
MAST-006 | mastra | 2025-09 | #8162 | [BUG] Langfuse exporter not capturing output tokens from LLM calls | null | null | paper:bf; closed completed Oct 14 2025 by Member @epinzur via PR #8790 (preceded by reporter-filed PR #8417). Filed Sep 25 2025 by @rmarquet21 against @mastra/langfuse 0.0.8 + @ai-sdk/anthropic 2.0.17 with thinking.budgetTokens 12000 enabled. Tagged bug + p:high + Observability (AI Telemetry). Documented gap: "LLM trac... | bf | M-cost-observability |
MAST-007 | mastra | 2025-10 | #8351 | Mastra Server not handling rate limit error for anthropic provider | null | null | paper:bf; closed completed Oct 7 2025 (6-day resolution) via PR #8567 by @LekoArts (Member). Filed Oct 1 2025 by Contributor @wardpeet on behalf of Discord user @meghdip-fenrir. Documented mechanism: Anthropic API returns 429 with "This request would exceed the rate limit for your organization of 30,000 input tokens pe... | bf | M-retry-loop |
MAST-008 | mastra | 2026-01 | #12014 | [FEATURE] Expose provider response headers in agent.generate() and agent.stream() | null | null | SKIPPED for paper after URL verification (S5 user-found-existing-feature). Filed Jan 16 2026 by @tomaskupka requesting response.headers be added to agent.generate() and agent.stream() return values to enable rate-limit-aware batch processing. Tagged enhancement + impact:high + effort:medium + Agents. Body has strong co... | S5 | null |
Token Budgets — Empirical catalogue and inter-rater reliability data
Data for:
Token Budgets: An Empirical Catalog of 63 LLM-Agent Budget-Overrun Incidents, with an Affine-Typed Rust Mitigation as a Case Study. Sajjad Khan, 2026. arXiv:2606.04056 — preprint.
This dataset bundles three artefacts referenced in the paper:
catalogue— the harvested catalogue of LLM-agent budget-overrun incidents across 21 orchestration frameworks (2023–2026), 167 rows total. The IRR-included primary corpus is the 110 rows labelledbf/bu/mf/frin thelabelcolumn; the remaining 57 rows are supplementary structural entries (S1–S7) orSKIPPED.irr_four_class— the 113-row paired re-annotation by an independent human rater under the four-class scheme, used to compute the paper's headline IRR figure (Cohen's κ=0.837, 95% CI [0.745, 0.919]).irr_cluster— the 110-row paired re-annotation under the eight-cluster mechanism partition. Exploratory only per paper abstract: Cohen's κ=0.44, 95% CI [0.34, 0.55], with cost-observability (κ=0.78) and multimodal-cost-amplification (κ=0.65) the two reliably-identified mechanisms; other clusters are not reliably reproducible from issue-body text and the cluster partition is reported as exploratory rather than validated.
Quick load
from datasets import load_dataset
catalogue = load_dataset("sajjadanwar0/token-budgets-catalog",
"catalogue", split="train")
print(catalogue)
# Dataset({features: ['issue_id', 'framework', 'date', 'short_url', 'title',
# 'prevented_at_compile_time', 'user_dollar_loss',
# 'notes', 'label', 'primary_cluster'],
# num_rows: 167})
irr_four = load_dataset("sajjadanwar0/token-budgets-catalog",
"irr_four_class", split="train")
print(irr_four)
# Dataset({features: ['issue_id', 'framework', 'date', 'short_url', 'title',
# 'notes_redacted', 'rater_a_tag', 'rater_b_tag',
# 'phase', 'rater_b_notes'],
# num_rows: 113})
irr_cluster = load_dataset("sajjadanwar0/token-budgets-catalog",
"irr_cluster", split="train")
print(irr_cluster)
# Dataset({features: ['issue_id', 'rater_a_cluster', 'rater_b_cluster'],
# num_rows: 110})
catalogue config
Schema (10 columns)
| Column | Type | Description |
|---|---|---|
issue_id |
string | Catalogue-internal identifier (e.g. LANG-001, CRAI-006) |
framework |
string | Framework name (e.g. langchain, langgraph, crewai, autogen, mastra, pydantic-ai) |
date |
string | Year-month the issue was opened (YYYY-MM) |
short_url |
string | GitHub issue/PR reference (#NNNN) within framework's repo |
title |
string | Original issue title verbatim |
prevented_at_compile_time |
string | Whether the Token Budgets affine type system would have prevented the bug at compile time (yes, no, or empty) |
user_dollar_loss |
string | Reported user-side dollar loss when stated in the issue (else empty) |
notes |
string | Curator notes, may include paper:XX marker mirroring label for backward compatibility with earlier IRR scripts |
label |
string | One of bf, bu, mf, fr (IRR-included primary corpus); S1–S7 (supplementary structural entries); or SKIPPED (excluded) |
primary_cluster |
string | One of the eight mechanism clusters (see irr_cluster config below), or empty for supplementary/skipped rows |
Coverage
| Subset | Row count |
|---|---|
| Total catalogue | 167 |
Primary corpus (IRR-included): label ∈ {bf, bu, mf, fr} |
110 |
Supplementary structural (S1–S7): documents the budget-primitive-missing condition but not a user-reported overrun incident |
50 |
SKIPPED: excluded from analysis (out-of-scope or duplicate) |
7 |
| Distinct frameworks (primary corpus) | 21 |
| Date range | Jan 2024 – Jan 2026 |
Primary corpus label distribution
The paper's Table I groups these 110 rows analytically as 63 confirmed production incidents + 28 maintainer-acknowledged gaps + 14 feature requests + 5 borderline. The mapping between the analytic groups and the raw four-class labels is documented in the paper §2.4. The raw label column reports the four-class scheme directly:
label |
Meaning | Count |
|---|---|---|
bf |
bug fixed by framework (linked PR or commit shipped) | 27 |
bu |
bug unfixed (acknowledged but no released fix) | 55 |
mf |
maintainer framing (failure characterised as inherent / by-design) | 7 |
fr |
feature request (budget primitive missing, no overrun incident) | 21 |
| Primary total | 110 |
Mechanism cluster column (primary_cluster)
Eight mechanism clusters, populated for the 110-row primary corpus.
The cluster assignment is the paper's exploratory partition;
inter-rater reliability is reported in the irr_cluster config
(κ=0.44 overall) — see that config's documentation below for the
honest scope discussion.
| Cluster | Primary-corpus count |
|---|---|
M-retry-loop |
27 |
M-cost-observability |
22 |
M-context-amplification |
13 |
M-storage-amplification |
13 |
M-budget-primitive-missing |
12 |
M-delegation-fanout |
11 |
M-multimodal-cost-amplification |
6 |
providerOptions-silently-dropped |
6 |
| Total | 110 |
irr_four_class config
Schema (10 columns)
| Column | Type | Description |
|---|---|---|
issue_id |
string | Matches catalogue config |
framework |
string | Framework name |
date |
string | Year-month |
short_url |
string | Issue reference |
title |
string | Issue title |
notes_redacted |
string | Issue-body excerpt with rater A's label markers stripped (rater B was blinded) |
rater_a_tag |
string | Rater A's label (one of bf, bu, mf, fr); Sajjad Khan |
rater_b_tag |
string | Rater B's independent label; Zahid Hussain (Mindgigs Ltd.) |
phase |
int | IRR phase: 1 = main 109-row study, 2 = 4-row supplementary top-up |
rater_b_notes |
string | Rater B's per-case rationale (may be empty) |
Headline IRR statistics
Computed by
irr_scaffold.py
on the 113-row paired sample:
| Statistic | Value |
|---|---|
| Overall Cohen's κ | 0.837 |
| Bootstrap 95% CI | [0.745, 0.919] |
| Observed agreement | 0.894 |
κ on bf (one-vs-rest) |
0.858 |
κ on bu (one-vs-rest) |
0.876 |
κ on mf (one-vs-rest) |
0.918 |
κ on fr (one-vs-rest) |
0.727 ← weakest seam |
Confirmed-subset sub-result reported in paper abstract: κ=0.943 on the n=79 rows both raters independently marked as confirmed (i.e. the subset where both agreed the failure was a real production incident rather than a gap, request, or borderline).
The fr/bu boundary
κ=0.727 on fr is the codebook's weakest seam. The paper reports this
honestly as the empirical reproducibility ceiling on bug-vs-request
adjudication at the issue-body-excerpt length the catalogue ships. The
catalogue's downstream claims depend on the union
bf ∪ bu ∪ mf ∪ fr being 110 budget-primitive-missing issues across 21
frameworks, which is invariant under the bu/fr cut.
Reproducing this kappa
git clone https://github.com/sajjadanwar0/token-budgets-formals.git
cd token-budgets-formals/irr/
python3 irr_scaffold.py compute --input independent_second_human_annotator_113.csv
# Expected: Cohen's kappa: 0.837
irr_cluster config — EXPLORATORY
Schema (3 columns)
| Column | Type | Description |
|---|---|---|
issue_id |
string | Matches catalogue.primary_cluster rows |
rater_a_cluster |
string | Rater A's cluster assignment (Sajjad Khan); one of the eight clusters listed below |
rater_b_cluster |
string | Rater B's blinded re-assignment (Zahid Hussain); same eight-cluster vocabulary |
Exploratory status
This config supports a paper claim that is explicitly labelled "exploratory" in the abstract (paper §2 / Table I):
"We treat the eight-way mechanism partition as exploratory: independent cluster-assignment agreement is moderate (Cohen's κ=0.44, 95% CI [0.34, 0.55], N=110, two raters), with cost-observability (κ=0.78) and multimodal-cost-amplification (κ=0.65) the two reliably-identified mechanisms."
Headline figure: κ=0.44 on N=110. This is below conventional "substantial agreement" thresholds (κ≥0.6) and is reported as such. The cluster partition is not a validated label scheme; it is a post-hoc analytic grouping that helps organize the catalogue's mechanism discussion but should not be used as ground-truth labels for downstream classification work.
Per-cluster κ (one-vs-rest)
| Cluster | κ | Observed agreement | Rater-A support |
|---|---|---|---|
M-cost-observability |
0.778 | 0.918 | 22 |
M-multimodal-cost-amplification |
0.647 | 0.964 | 6 |
M-storage-amplification |
0.529 | 0.918 | 13 |
M-context-amplification |
0.370 | 0.882 | 13 |
M-retry-loop |
0.328 | 0.773 | 27 |
providerOptions-silently-dropped |
0.309 | 0.873 | 6 |
M-delegation-fanout |
0.254 | 0.909 | 11 |
M-budget-primitive-missing |
0.184 | 0.818 | 12 |
The two clusters with κ above 0.6 are the ones the paper identifies as reliably-identified mechanisms. The remaining six should be treated as analytic suggestions, not classification labels.
Reproducing this kappa
git clone https://github.com/sajjadanwar0/token-budgets-formals.git
cd token-budgets-formals/irr/cluster/
python3 compute_cluster_kappa.py \
cluster_irr_rater_a_frozen.csv \
cluster_irr_rater_b_frozen.csv
# Expected: Overall (8-cluster) Cohen's kappa: 0.4440
# 95% bootstrap CI [0.337, 0.547]
# observed agreement 0.5273
# N=110
The two _frozen.csv files in the GitHub repository are committed,
byte-stable snapshots; the paired CSV in this HF config is built from
those two files via (rater_a, rater_b) JOIN ON issue_id.
Companion artefacts
sajjadanwar0/token-budgets— the Rust crate with theBudget<T>affine type andBudgetMintauthority gate (the "case study mitigation" of the paper title).sajjadanwar0/token-budgets-formals— Coq, Dafny, TLA+, Verus mechanised proofs, plus the IRR working directory (this dataset's source).sajjadanwar0/token-budgets-experiments— Python and Rust experimental harnesses for the Anthropic estimator validation, forgetful-operator experiment (Conditions A–E), and multi-runtime sweeps.
A single-script reproduction covering all paper-backing artefact
claims (catalogue row count, both IRR figures, Rust crate build,
trybuild, Coq/Dafny verification, loom interleavings, microbenchmark,
forgetful-operator Condition E) is available at
sajjadanwar0/token-budgets/reproduce.sh.
Citation
@misc{khan2026tokenbudgets,
author = {Khan, Sajjad},
title = {Token Budgets: An Empirical Catalog of 63 {LLM}-Agent
Budget-Overrun Incidents, with an Affine-Typed {Rust}
Mitigation as a Case Study},
year = {2026},
eprint = {2606.04056},
archivePrefix = {arXiv},
primaryClass = {cs.SE},
url = {https://arxiv.org/abs/2606.04056}
}
@misc{khan2026tokenbudgetscatalog,
author = {Khan, Sajjad},
title = {{token-budgets-catalog}: Empirical catalogue and IRR
data for the Token Budgets paper},
year = {2026},
publisher = {Hugging Face},
howpublished = {\url{https://huggingface.co/datasets/sajjadanwar0/token-budgets-catalog}}
}
License
MIT (matching upstream repositories). The catalogue is derived from public GitHub issue threads under the original repos' licenses; framework maintainers and reporters retain authorship of their issue text.
Limitations and scope notes
- Convenience sample. The catalogue is a convenience sample of public English-language GitHub issues across 21 open-source frameworks. Closed-source agent platforms (Cursor, Replit Agent, Devin, etc.) are not represented. The paper makes a recurrence claim (the failure class occurs across independently-developed projects), not a prevalence estimate.
- Selection on the dependent variable. Issues were located by searching for budget-overrun-suggestive terms in issue trackers; the sampling frame is therefore conditioned on the failure occurring and being publicly reported. Prevalence claims would require an unconditional sample of agent deployments, which this catalogue does not provide.
- Single curator at initial labelling. Rater A (Sajjad Khan) authored the initial four-class labels. The IRR study with rater B (Zahid Hussain) addresses the rater-independence threat for the four-class scheme (κ=0.837) but does not eliminate possible curator- selection bias at the issue-discovery stage.
- The eight-cluster mechanism partition is exploratory. See the
irr_clusterconfig above. κ=0.44 is below conventional substantial-agreement thresholds and is reported as such in the paper abstract. OnlyM-cost-observabilityandM-multimodal-cost-amplificationexceed κ=0.6 individually. - Failure modes, not framework rankings. Higher row counts for langchain, mastra, etc. reflect issue-traffic volume from these frameworks' larger user bases, not relative engineering quality.
- Catalogue mutability. The catalogue is a research artefact expected to grow as new incidents are reported in the wild. The paper's headline counts (110 rows, 63 confirmed) are pegged to the arXiv v1 snapshot; downstream replicators should clone the GitHub repo at the corresponding commit tag if exact reproducibility is required.
- Downloads last month
- 4