What does this release signal mean?

Cloudflare (Workers AI) published cloudflare/agents @cloudflare/think@0.8.8 (cloudflare/agents). This release signal is evidence of what shipped, changed, or was packaged for users. High-signal details: Release: cloudflare/agents @cloudflare/think@0.8.8 - Repository: cloudflare/agents | Build and deploy AI Agents on Cloudflare | 5K stars | TypeScript - Author:.... onlylabs links this event to 1 captured evidence page and 6 related release signals.

Cloudflare (Workers AI) Release: cloudflare/agents @cloudflare/think@0.8.8

Captured source

source ↗

GitHub/github.com/cloudflare/agents

cloudflare/agents @cloudflare/think@0.8.8

Source ↗

published Jun 8, 2026seen 2dcaptured 12hhttp 200method exa

Release: cloudflare/agents @cloudflare/think@0.8.8

Repository: cloudflare/agents | Build and deploy AI Agents on Cloudflare | 5K stars | TypeScript
Author: [@github-actions[bot]](https://github.com/github-actions[bot])
Created: 2026-06-08T20:47:13Z
Published: 2026-06-08T20:47:15Z

Patch Changes

#1705 `611e8c3` Thanks @threepointone! - Fix Think agents firing an alarm every 30s forever when they don't use workflow notifications (#1703).

alarm() called _startWorkflowNotificationDrain() unconditionally, which wrapped its work in keepAliveWhile(...). Acquiring the keepAlive lease armed the 30s keepAlive heartbeat alarm even though there was nothing to drain, and releasing the lease did not pull the alarm back — so the DO re-scheduled itself every 30s and never hibernated.

_startWorkflowNotificationDrain() now returns early when there are no pending notifications, matching its other call sites. Affected DOs self-heal on their next alarm fire after upgrading: super.alarm() reschedules to the next legitimate task (or clears the alarm entirely) and the drain no longer re-arms the heartbeat.