Every processed story in chronological order, with the newest coverage first. Filter by tag, source, or score to drill in.
ALMCP consolidates what would otherwise be multiple separate API integrations into a single MCP connection, reducing the setup overhead for agents that need to combine information-gathering and content-processing tools.
The Amp plugin approach reduces specialized agent creation to a small, self-contained configuration that Amp can generate on its own.
The Finder subagent and background compaction together extend how far Deep Search can explore a codebase within a single conversation, directly addressing context window constraints that previously cut sessions short.
An authorization layer for MCP addresses a gap that has been a barrier to enterprise adoption of the protocol for connecting AI agents to tools.
AI DevKit addresses the orchestration gap that emerges when developers run multiple coding agents simultaneously — shared config, memory, messaging, and verification are handled at the control-plane level rather than manually across scattered terminal sessions.
Agent Canvas moving to production readiness marks a shift from experimental to officially supported tooling for running parallel AI agents and automations within the OpenHands ecosystem.
The gateway removes the binary choice enterprises previously faced — either prohibiting AI coding assistants entirely or accepting uncontrolled PII and credential exposure — by inserting a compliant, auditable layer between developer tools and internal data.
Cursor Automations now respond to GitHub events and can operate cloud agents with computer use, expanding the scope of automated workflows the product supports.
The tool closes the context-staleness loop that typically degrades AI output in long-running codebases by pairing a Liquid-templated prompt composer with an MCP server that keeps context blocks current.
EMA replaces thousands of manual, per-user OAuth consent flows with centralized IdP-governed authorization, closing the audit, offboarding, and compliance gaps that standard MCP auth leaves open at enterprise scale.