Durable Streams

The data primitive for the agent loop.

[Necø @Necmttn]

https://t.co/tkErLGQg9b
built on @EffectTS_, ships with @DurableStreams support

https://t.co/THEuDigRwH

[tonbo @tonboio]

Just open-sourced Ursula: an HTTP event streams server.

Built on @ElectricSQL's Durable Streams Protocol, Ursula keeps a combo we have not seen elsewhere: { Apache 2.0, quorum-replicated, sub-50ms p99, S3 economics }.

https://t.co/ggG70erwRR

[Kyle Mathews @kylemathews]

Agent context needs stored somewhere hence logs and databases

Online agents that react to systems and each other need reactive contect hence sync

[Kyle Mathews @kylemathews]

It's a lot easier to build a coding harness then people think. 2 days in I'd say we're at ~60% of Claude Code / Codex / Open Code.

Models do most of the work. And @DurableStreams and TanStack DB make quick work of building an amazing app around the coding agent.

[James Arthur @thruflo]

Agents on sync? Agents in functions?!

Here's a walkthrough of the thinking behind the new Electric Agents platform.

Full video in the tweet below👇

[Electric @ElectricSQL]

Introducing Electric Agents!

Agents are not compute. Agents are data. Multi-agent is a sync problem. Electric Agents is the first agent platform built on sync.

Use it to build scalable, collaborative, long-lived multi-agent systems: 🧵👇

[Kyle Mathews @kylemathews]

.@DurableStreams + Tanstack DB are great fits for building all sorts of streaming state apps

[Kyle Mathews @kylemathews]

Coding agents turn code from artifact into materialized view.

The base tables are the ideas — algorithms, protocols, semantic contracts. The code is one projection. For decades we treated the artifact as authoritative because regenerating was expensive. It isn't anymore.

[Kyle Mistele 🏴‍☠️ @0xblacklight]

durable streams by @ElectricSQL are really cool btw

[Electric @ElectricSQL]

Can Doom run on @DurableStreams? Absolutely!

The result: live streaming, rewinding, and forking — branch from any point and you're instantly back in the game!

[James Arthur @thruflo]

Or you could use @DurableStreams 🤷

[Kyle Mathews @kylemathews]

.@DurableStreams (reactive append only log) is the *essential* primitive for every AI app and just got even more powerful with native COW forking.

[Sam Willis @samwillis]

Agent sessions need a durable, observable, branchable, append-only log.
Durable Streams from @ElectricSQL give you exactly that - now with instantly forkable sessions. 🚀🥳

[Sam Paton @thesampaton]

Updated my @DurableStreams rust server bin to 0.2 Fixed hierarchical stream names, graceful shutdown that actually drains SSE/long-poll connections 😅 , added proper RFC 9457 error responses and sorted https://t.co/nhoiMW1Gpy

https://t.co/Xltt6JKXHA

[Electric @ElectricSQL]

It's all about the loop.

Agents accumulate state with every step of the loop. This state needs a new data primitive.

That's @DurableStreams 🧵👇

[James Arthur @thruflo]

Break the harness. Wire the loop. This is how agents come online and integrate into operational systems.

[James Arthur @thruflo]

A proper in-depth example of collaboration using @DurableStreams

[Valter Balegas @balegas]

These type of agents can run headless from anywhere. Just give them a @DurableStreams.

[Electric @ElectricSQL]

We built a collaborative editor with an AI agent as a real-time CRDT peer.
It has its own cursor, streams edits into a Yjs rich text document, and resolves conflicts alongside human users automatically.
Built with @DurableStreams, Yjs, and @tan_stack AI.
🔗🧵

[James Arthur @thruflo]

As agentic systems move online, they're going to re-discover the challenges of multi-user collaboration.

With @DurableStreams you can now integrate CRDTs into your prompt and artifact editing, with materialization, compaction, forking etc. all built in.