Matthew O'Riordan

⚡ Founder/CEO @AblyRealtime | Realtime infrastructure for 2B+ devices | Building the live, interactive internet |

[Matthew O'Riordan @mattheworiordan]

Streaming tokens is easy.

Shipping a continuous AI experience is not 🧵

Here's why we built AI Transport👇

[Matthew O'Riordan @mattheworiordan]

@ikavalerov I thought Hermes was a symbol of showing off one’s wealth :)

[Matthew O'Riordan @mattheworiordan]

@nearestnabors So what’s your take since the deep dive? Back to polling? 😜

[Matthew O'Riordan @mattheworiordan]

@thekitze Snap I created https://t.co/rJt00ETQME 4 months ago and use it to validate hard / controversial decisions.

What’s your use case?

And is it council or counsel :)

[Ably Realtime @ablyrealtime]

The Vercel AI SDK's resumable streams feature is the standard for resumable AI chat.

But it reveals what HTTP/SSE lacks: a native concept of session recovery.

So every team builds the same Redis workaround.

Discover when that pattern runs out, and what comes next 👇

https://t.co/sHF3ACWCf5

[Matthew O'Riordan @mattheworiordan]

Always bet on ShadCN. Watch this space, Shad and @ablyrealtime AIT integration incoming

[Lars Grammel @lgrammel]

Building excellent chatbot and agent UIs just got even easier.

[Matthew O'Riordan @mattheworiordan]

@rauchg @cramforce Agreed. Code is still an asset that needs investment to maintain and evolve. The job of what to do is now harder, not easier, in a world where LLMs get most of that what done.

[Matthew O'Riordan @mattheworiordan]

@nicoalbanese10 @vercel @aisdk Congrats man! Enjoy the magic of marriage

[Matthew O'Riordan @mattheworiordan]

Someone on our team recently needed an answer that a year ago would've been a message to me. They just asked, got it with the data behind it, and I never knew.

Jamie wrote how messy that road was for us: https://t.co/HCNRmmxuv7

How many questions this week needed only you?

[Matthew O'Riordan @mattheworiordan]

If your team keeps coming to you for answers, I've got bad news. You're not indispensable. You're the bottleneck.

I know. I was one for years. The answers lived in my head and I quietly enjoyed being needed.

[Matthew O'Riordan @mattheworiordan]

For a long time "it's all in my head" was fair. Writing it down was slow and went stale instantly.

That excuse is gone. Give AI the right context and access to your real data, and the knowledge answers for itself.

[Matthew O'Riordan @mattheworiordan]

@PitchBook sort yourselves out. Sending me emails I didn't subscribe to is painful, making me go through 8 pages of captchas to unsubscribe is something else. Hard to imagine a more insulting experience really!

[Matthew O'Riordan @mattheworiordan]

@dawncapital Looking good 😎

[Matthew O'Riordan @mattheworiordan]

@sama Companies are not consumers 🙄
You seriously think companies will divert their teams to use codex becuase it’s free for two months?
Sell on value SAM

[Matthew O'Riordan @mattheworiordan]

—> https://t.co/31mZ4q0KC0 (correct new URL), oops

[Matthew O'Riordan @mattheworiordan]

We interviewed 38 companies building AI products at scale.

We evaluated 37 vendors across the AI infra landscape.

Almost every team is hitting the same wall. None of those failures are model failures.

Thread 🧵

[Matthew O'Riordan @mattheworiordan]

4/ Agents fail silently.

33 of 37 vendors have no infra-level health signal. An idle stream looks identical to a dead one. Thinking, stalled, crashed — indistinguishable on screen.

The model is fine. The session is broken.

https://t.co/WkgOHritFo

[Matthew O'Riordan @mattheworiordan]

Eugene Khokhlov kicked off a series on what we've learned. @paddybyers and the team will write more. I'll share why this is one of the quietest, biggest unlocks Ably has.

Part 1: https://t.co/Vo0UdJLtoM

[Matthew O'Riordan @mattheworiordan]

Spec-driven development is having a moment in 2026.

Ably's first spec commit was 28 August 2013.

3,646 commits. 988 of them on the main features file. 55 contributors. 12+ years.

Long before LLMs. Now it's an unfair advantage.

[Matthew O'Riordan @mattheworiordan]

Why specs, not code? Once you ship more than one SDK, behavior is the only thing that can settle disputes across languages, runtimes, and years of change.

Tests verify what you wrote. They don't tell you whether what you wrote was right.