Cloudflare Agents — Stateful Agents on Durable Objects

Operating Pattern

Fit check

Adoption loop

1. Run the tool on a disposable branch or sandbox project.
2. Capture before/after output so reviewers can see the exact effect.
3. Add the smallest CI or local check that prevents regressions.
4. Document owner, upgrade command, and rollback command in the repo.

Recommended use

Model each durable conversation or job as an agent with its own state. Keep external side effects in explicit tools so retries and wakeups stay predictable.

Guardrails

Design storage boundaries before scale tests. Millions of idle agents are viable only if per-agent state stays small and lifecycle cleanup exists.

Rollout checklist

• Pin the package or release version before using it in CI.
• Keep credentials in environment variables or the platform secret store.
• Add one owner who is responsible for upgrades and breaking-change triage.
• Re-check the GitHub repo before writing docs that mention APIs or install paths.

FAQ

Q: Is this production-ready? A: The repo exists at https://github.com/cloudflare/agents and has 4,898 GitHub stars. Treat the first rollout as a controlled pilot until your team has tested install, rollback, and CI behavior.

Q: Why use it instead of a generic script? A: The value is repeatability: a named package, a documented command, a source repo, and a small verification path that can be reviewed by teammates.

Q: What should I measure first? A: Measure setup time against the 15 minutes target, count how many files or tasks it changes, and record whether the CI command catches the same issue locally.