[KongchangAI]
Product

CellaFlow

A persistent execution engine for multi-agent systems that uses distributed mechanisms such as leases, heartbeats, ownership transfer, and barriers to address repeated side effects and deadlocks following agent crashes, balancing idempotency with recoverability.

Timeline (last 90 days)

Sep 11

CellaFlow's core argument is that Agents themselves are ephemeral, but execution should not be.

Unverified50%
Sep 11

CellaFlow provides a persistent, recoverable execution system built around side effects, so that once ownership is lost, another worker can eventually take over rather than leaving the workflow permanently deadlocked.

Unverified50%
Sep 11

CellaFlow's developer built an open-source, reproducible crash benchmark that compares four approaches—no guard, Postgres advisory lock, Durable claim, and CellaFlow—across multiple failure modes.

Unverified50%
Sep 11

CellaFlow allows idempotency scope to be bound to a business identifier (such as ticket_id), so that regardless of which Agent initiates the call, as long as the business key is the same, it converges to a single execution.

Unverified50%
Sep 11

CellaFlow was built by a developer on Reddit for discussing the crash benchmark problem in AI Agent execution.

Unverified50%

All Facts (5)

Source Articles