Build Cloudflare agents for developer operations

Create developer operations agents that connect Cloudflare context to incident response and platform follow-up.

Example outcome

Turn Cloudflare platform context into an incident triage brief with likely causes, evidence, and approval-ready actions.

Agent examples

Workflow guides for Cloudflare

3 guides

Incident response workflow Engineering and infrastructure teams

Create a Cloudflare incident response agent

Build a developer operations assistant that helps teams investigate edge and platform issues safely.

Read workflow guide →

Performance audit workflow Engineering and infrastructure teams

Create a Cloudflare performance audit agent

Build an edge operations assistant that prepares performance recommendations without making unsafe production changes.

Read workflow guide →

Combined plugin workflow Engineering and reliability teams

Create a Cloudflare and Sentry incident fix agent

Build an incident response workflow that connects edge, traffic, and application error evidence before proposing remediation.

Read workflow guide →

Bring edge context into operational workflows

Cloudflare workflows in LatchLoop are strongest when the agent is asked to prepare an investigation or handoff around a real operational outcome. The agent can use available Cloudflare platform context to help teams understand traffic behavior, deployments, configuration, observability signals, or documentation before someone makes a change.

A good Cloudflare agent should stay careful with production systems. It can gather evidence, summarize possible causes, and prepare approval-ready steps, but risky configuration changes should remain visible to a human owner. That approach makes the plugin useful for incident review, worker troubleshooting, performance checks, security follow-up, and deployment readiness.

Use local content to teach the workflow pattern while leaving canonical plugin capabilities in the catalog. Cloudflare also pairs naturally with GitHub, Sentry, Vercel, and documentation tools when an incident spans code, infrastructure, and customer communication.

Start with the incident response workflow below to create an agent that turns platform context into a clear triage brief.

Combine plugins

Build richer agents by pairing Cloudflare with complementary context

Outcome pages can describe combinations: one plugin for source context, another for project tracking, and another for delivery or notifications. Use Cloudflare as one layer in a larger agent workflow when the outcome needs more than one connected app.

Available plugin capabilities

agents-sdkcloudflare-email-servicecloudflaredurable-objectssandbox-sdkweb-perfworkers-best-practiceswrangler

Get Started

Build as fast as you can think.

LatchLoop works where you do to build with you.