agents & frameworks
Independent comparisons of agent stacks and multi-agent designs, tracking the gap between framework marketing and the failure modes that show up under real workloads.
- Why Deep Research Agents Abandon the Plan Mid-Search
- MCP vs Function Calling: Who Should Own Your Agent's Tool Layer?
- Qwen-Agent Stretches 8k to 1M Context: Do You Need a Long-Context Model?
- Can AI Agents Do Root Cause Analysis? What Cloud-OpsBench Measures
- Which AI Agents Behave Badly: Cloudflare's Agentic Internet Data
- Compressing LLM Agent History: Pixel Rendering vs Summarization
- Anthropic A/B Tests Claude Code Effort Levels: Your Agent Is the Control Group
- Self-Hosted Coding Agents: The Safety Burden You Inherit
- Claude Code Weekly Limits Promo Ends in August 2026: Budgeting for Agent Teams
- Vibe Coding vs Control: How Developers Actually Used AI Coding Agents
- Multi-Agent or Single-Agent LLM: What Skill Distillation Actually Costs
- Multi-Agent LLM Systems Drift Into Misaligned Communication Over Long Horizons
- Sizing Agent Memory: A Capacity Planning Rubric for Long-Horizon LLMs
- When Spec-First Agents Dismantle Invariants: A Governance Case Study
- Cloudflare Kitesurf: V8 Isolates vs Containers for Agent Browsing
- Claude Code Skills vs Model Weights: Where Should Agent Skills Live?
- Cloudflare Precursor: Behavioral Detection for AI Agents
- Why Multi-Agent LLM Delegation Concentrates Risk
- Harness vs Scaffold: Why Claude Code and LangGraph Are Not Interchangeable
- MCP Tool Discovery Moves From Hardcoded Config to Runtime Agent Search
- Code-as-Action Agents Beat GAIA But Require Runtime Sandboxing
- Why Agent Security Tests Must Audit Full Trajectories, Not Single Turns
- x402 Per-Call Payments: Agent Wallet Custody and Replay Risks
- CodeRabbit Review Study: 56% Rejection Rate Demands Targeted Scoping
- LLM Agents Ignore Mid-Flight Halt Signals: 0 of 40 Trials Stopped
- Agent-First CLIs: Why GitHub, npm, and PyPI Must Publish Machine-Readable Contracts
- MCP and AGENTS.md Standardize Context, Not Agent Coordination
- Cursor's Swarm Math: When Cheap Agents Save Money and When They Fail
- Runtime monitoring beats alignment for agent-to-agent coercion
- Cloudflare's Agent Stack: Edge Trust, Identity, and Metering
- LM Studio Bionic vs Claude Code: Local-First vs Cloud Agent Tradeoffs
- Can a Malicious AGENTS.md File Compromise Your Coding Agent? A Threat Model
- How GitHub Projects Actually Adopt Coding Agents: New Empirical Data
- Why CLI Coding Agents Derail Mid-Run, Not at the First Mistake
- Test-Time Scaling Cost Falls as PRMs Reuse Generator KV-Cache
- Claude Code Skills vs Cursor Rules vs MCP: How Agent Skill Systems Compare
- TTHE: Test-Time Harness Evolution Changes the Test-Code Contract for Coding Agents
- Git-for-Data for Agentic Lakehouses: Why Agents Need Versioned State
- Game Theory Can Cut Multi-Agent LLM Hallucination, But Only If Payoffs Align
- WebSwarm: Recursive Multi-Agent Search vs Flat Orchestration
- Do Coding Agents Memorize Their Benchmarks? DeepSWE Tests on Unseen Tasks
- Can a 4B Model Run a Coding Agent? Terminus-4B vs Claude and GPT-4o
- Can You Prove a Governed AI Agent Actually Ran the Action You Authorized?
- AgentTether Repairs LLM Agent Failures with a Runtime Graph
- Can Multi-Agent LLM Negotiation Protocols Trust Their Own Samplers?
- Why Your AI Travel Agent Would Book a Bullfight
- Can Multi-Agent RAG Run Air-Gapped? A Forensics System Shows How
- Can You Prove an Agentic Trading Pipeline Has No Look-Ahead Bias?
- How Far Ahead Can a Coding Agent Plan? The Horizon Bottleneck
- Symbolic Inference Forces Agent Frameworks to Expose Intermediate State
Agent frameworks ship faster than the rigor operators need to run them. Vendor docs promise orchestration, memory, and tool use; academic benchmarks and production post-mortems keep exposing the same structural gaps: diversity collapse in multi-agent ideation, hallucination amplification across consensus topologies, missing per-step rationale traces, role-based retry losing to graph-state failure isolation on long tasks, and configuration surfaces that punish static templates. This beat covers that delta.
The second through-line is governance and trust. Skill registries, tool-use protocols, and capability manifests are accumulating faster than auditable contracts for them. Trust schemas, contractual skill specs, and information-flow controls are arriving as bolt-ons rather than primitives, while the infrastructure layer — sandbox execution, private networking, agent memory — keeps absorbing functionality the framework layer used to own. The question of where the agent stack actually lives, and who is liable when it misbehaves, stays unresolved.
Coverage is comparative and opinionated. When a benchmark or paper exposes a gap that a major framework cannot close without redesign, that gets named. When a vendor ships governance theater rather than enforcement, that gets named too. The goal is help readers pick stacks that survive contact with production, not a taxonomy of every framework release.
