Skip to content

Widefleet 0.4.13 adds runtime observers for Cloudflare resources

Updated Widefleet

Summary

Installation-owned observers cover storage and workflows, with organization and queue availability controls.

Category
Agent infra
Date
Pricing
Not stated in the sources we cited.

Widefleet 0.4.13 adds runtime observer configuration owned by an installation. The release covers observations for KV, R2, D1 and workflows, giving deployments more explicit infrastructure-level signals to inspect.

Availability and execution controls

Organization HTTP availability is represented in KV. Suspension handling covers cron, connectors and workflow execution, while queue availability publishers can disable deployments. These are controls described by the project; the notes do not demonstrate that every possible suspension or delivery failure is prevented.

Reuse workers and onboard organizations

Workflow workers can be reused. The release also changes email signup and shared-organization onboarding, and makes PostHog configuration adjustable.

This update is relevant to teams operating agent infrastructure on Cloudflare rather than users looking for a new foundation model. Resource access, cloud usage charges and deployment configuration remain separate responsibilities. No operating-cost or performance comparison was measured for this summary.

See the widefleet hub.

More from Widefleet

View all

Questions

What is Widefleet?

Its site describes an open-source platform that lets agents deploy apps and workflows with company login, databases, file storage and controlled access to systems.

Is Widefleet open source?

The GitHub repository reports an MIT license through the GitHub API.

Does Widefleet work with coding agents?

The product site says coding agents can create and manage apps through the Widefleet CLI.

Filed on Agent Radar. Claims in this note are limited to the sources above.