Why Long-Running AI Agents Break on HTTP, and How Ably's Durable Sessions Fix It

May 21, 2026 · 8:37 AM UTC ·6 min read · 0 reactions · 0 comments · 31 views

TL;DR · WeSearch summary

Long-running AI agents often encounter issues with HTTP due to its request-response cycle, which is not designed for prolonged exchanges. These agents can break connections during lengthy operations, leading to lost data and increased costs. Ably's durable session model addresses these challenges by separating the session from the connection, allowing for continuous operation even when connections are interrupted.

Key facts

▪Long-running AI agents can exceed the idle time limits of HTTP connections, causing them to break.
▪Traditional HTTP connections close after a short period, which is problematic for agents that take longer to process requests.
▪Ably's durable session model allows sessions to persist independently of the connection, enabling reliable communication.

How this story was covered

2 outlets in our directory ran this story, first to last over 21 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.

Centre · 1

▪ Why multi-agent AI breaks in prod and how Yugabyte's Meko is trying to fix it — Tessl

About this source

DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.

All DEV.to (Top) coverage →

Original article

DEV.to (Top)

Read full at DEV.to (Top) →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	DEV.to (Top)
Canonical URL	https://dev.to/pickuma/why-long-running-ai-agents-break-on-http-and-how-ablys-durable-sessions-fix-it-4f9m
Publication time	Thu, 21 May 2026 08:37:35 +0000
Retrieval time	2026-05-21T08:51:10.385Z
Last seen	2026-05-21T08:51:10.385Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	sQD1RttXMka7 · 2 stories
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3926669) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } pickuma Posted on May 21 • Originally published at pickuma.com Why Long-Running AI Agents Break on HTTP, and How Ably's Durable Sessions Fix It #webdev #devops #cloud #astro Indie Infrastructure (17 Part Series) 1 Debugging Occasional ECONNRESET Errors in Node.js: Root Causes and Fixes 2 The Self-Hosting Guide on GitHub: What It Gets Right About Local LLMs and Home Servers ... 13 more parts...

…

Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).

Anonymous · no account needed

Discussion

0 comments