Every processed story in chronological order, with the newest coverage first. Filter by tag, source, or score to drill in.
Spanly fills a gap left by generic APM and SDK-based MCP monitors by operating at the protocol level as a language-agnostic proxy, making silent agent failures and tool-level errors visible without requiring code changes or a supported runtime.
MCP Bridge removes the terminal and JSON config barrier to MCP server installation, replacing a multi-step manual process with a single browser click.
Iris replaces the agent's need to interpret a browser snapshot with a direct pass/fail verdict from inside the live app, addressing the failure mode where agents incorrectly self-report completion without confirming actual runtime behavior.
WebMCP, if adopted as a web standard, replaces the fragile, token-intensive DOM-scraping approach agents currently use with direct, structured tool calls — reducing the work agents must do to complete actions on existing websites.
The bridge offloads file-reading and git-archaeology work to Gemini so that only answers — not raw file contents or log output — enter Claude's context, extending how long Claude Code can operate before its context fills up.
The overnight decode of a complete 1989 DOS executable — verified bit-for-bit — compresses what previously took weeks of work per system with earlier models into a single session, demonstrating a concrete step-change in AI-assisted reverse engineering of legacy software.
The proxy delivers simultaneous token cost reduction and accuracy improvement over plain JSON — without requiring any changes to existing MCP servers — by replacing a format that causes LLM comprehension failures at scale with one that scores 90.7% vs. JSON's 53.6% on the same data.
The rebuilt scoring model replaces a system that compressed 85.7% of tools into a single grade, giving the ecosystem its first meaningful quality differentiation signal for identifying which MCP servers are actually discoverable by AI agents.
The tool directly addresses a concrete bottleneck in agentic coding loops — context budgets consumed by redundant file re-reads — by fitting entire repositories into context that previously only held a fraction of the codebase.
The conference program shows that the AI coding stack debate has shifted from "should we do context engineering" to harder second-order problems — skill sprawl, supply chain security, and harness design — marking a concrete maturation in how the industry frames agentic development.