NewsLayer.com
NewsLayer PulseLIVEBTC$78,733-0.72%ETH$2,465-0.68%SOL$97.34-2.31%XRP$1.43-3.73%DOGE$0.0868-4.21%ADA$0.2114-3.70%Total Cap$2.76T-0.97%Layer Index58 Neutral

Diagrid Catalyst 2.0 Adds Durable and Verifiable Execution for AI Agents

Diagrid announced Catalyst 2.0 on 28 July 2026, adding failure recovery and cryptographic verification to agents built with frameworks including LangGraph, Microsoft Agent Framework, Google ADK and Dapr Agents.

infoq.com

Publisher

Aug 26, 2026 at 7:00 AM UTC · Updated há 3 horas · 3 min de leitura

Diagrid Catalyst 2.0 Adds Durable and Verifiable Execution for AI Agents
Image via infoq.com
Traduzindo…

Diagrid announced Catalyst 2.0 on 28 July 2026, adding failure recovery and cryptographic verification to agents built with frameworks including LangGraphMicrosoft Agent FrameworkGoogle ADK and Dapr Agents.

Ten framework integrations ship in the release, also covering LangGraph Deep Agents, AWS Strands, OpenAI Agents SDK, Claude Managed Agents, CrewAI and Pydantic AI.

Developers add a Diagrid package to an existing agent application. Diagrid says Catalyst then represents model and tool calls as durable workflow activities, allowing interrupted runs to resume without repeating completed work.

The failure mode this targets is a familiar one: a long multi-step run fails late in the sequence and, without checkpointing at call granularity, the retry re-pays for every model call already completed. Diagrid says Catalyst runs in cloud, on-premise and air-gapped environments. Durable agents are built with a Python SDK, while Catalyst's documentation lists workflow SDK support for .NET, Go, Java, JavaScript and Python; the open-source Dapr 1.18 SDKs also include Rust.

The verification model comes from Dapr 1.18. Dapr hashes batches of workflow-history events, links each digest to the preceding signature and signs the result using the Dapr sidecar's SPIFFE-based identity. The chain is checked when workflow state is loaded, making deleted, reordered or modified history detectable, and receivers validate each signed chunk against the Dapr Sentry trust anchor, so histories can be verified outside the application that produced them. Dapr groups the work as three capabilities: Workflow History Signing, Workflow History Propagation and Workflow Attestation, the latter two carrying verified execution context across workflow and service boundaries.

Article Intelligence

Topics

Sponsored

Ad
House — Advertise on NewsLayer
NewsLayerLearn more

NewsLayer Premium

Unlock deeper intelligence.

Ad-free reading, exclusive research, and real-time onchain insights.

Go Premium