Topic

#cloudflare

Loot, blog posts and adjacent themes connected to this topic. Follow the tag to keep it in your orbit.

#cloudflare

Loot

More from this topic

Explore all loot

Debug Cloudflare Workers locally with traces an AI agent can read

Text: AI-generated

#ai-generated #automated+6

AI-generated · Automatically published by LinkLoot. Cloudflare’s new local tracing flow exposes OpenTelemetry traces, logs, and binding state during local Worker development so agents can inspect failures without a deploy loop. AI-generated: This Loot was created and published automatically by LinkLoot and was not substantively reviewed by a human editor. Cloudflare added local tracing for Workers in wrangler dev and vite dev, with a read-only Local Explorer API that AI agents can query while debugging local failures. What it is wrangler dev and vite dev now automatically capture structured OpenTelemetry traces and correlated console logs during local Worker invocations. When Cloudflare detects an AI agent session, it prints a terminal hint for /cdn-cgi/explorer/api, which exposes an OpenAPI schema and observability endpoints. Who it helps This is useful for developers using coding agents on Cloudflare Workers. Instead of asking an agent to infer failures from terminal logs alone, you can give it a structured local signal: traces, spans, timing, errors, console logs, and binding state. How to evaluate it Run a Worker locally, trigger a failing request, then inspect Local Explorer in the browser or point your agent at the read-only explorer API. Check whether the agent can identify the failing operation, edit the code, rerun the request, and verify the fix without deploying temporary diagnostics. Limits and risks The API is local and read-only, but trace data can still expose request details, environment behavior, or sensitive logs. Review what your Worker logs before handing the endpoint to an agent. This is a developer convenience, not a substitute for production observability or security review. Sources Cloudflare changelog

Free

Review open

@ZachasADMIN

Open loot

Test Cloudflare Browser Run requests before wiring a Worker

Text: AI-generated

#ai-generated #automated+6

AI-generated · Automatically published by LinkLoot. Cloudflare's new Browser Run Playground lets developers trial screenshots, PDFs, extraction, and AI-structured scraping from the dashboard before writing integration code. AI-generated: This Loot was created and published automatically by LinkLoot and was not substantively reviewed by a human editor. What it is Cloudflare Browser Run now has a dashboard Playground for testing Quick Actions against a live browser. You can submit a URL or raw HTML, adjust viewport and page-load settings, preview output, and copy working request code. Who it helps It is useful for developers building browser automation, scraping, QA capture, agent browsing, or document-generation workflows on Cloudflare. It reduces setup time when you need to prove that a page can be captured, parsed, or turned into structured data before creating a Worker. How to evaluate it Start with a non-sensitive URL, test screenshots or Markdown extraction, then compare the copied request against the Browser Run Quick Actions documentation. If you use AI extraction, test with a small JSON schema first so costs and output shape are visible before adding it to a production flow. Limits and risks The Playground is not a free sandbox. Cloudflare says Playground requests incur Browser Run charges, and AI extraction also incurs Workers AI charges. Treat target pages as untrusted input, avoid submitting secrets, and check site terms before automating extraction at scale. Sources Cloudflare changelog

Free

Review open

@ZachasADMIN

Open loot

Find slow Cloudflare Worker startup code from Wrangler

Text: AI-generated

#cloudflare #wrangler+7

AI-generated · Automatically published by LinkLoot. Wrangler 4.116.0 adds wrangler check startup, giving Workers developers local bundle-size and CPU-startup signals before cold starts hurt production latency. AI-generated: This Loot was created and published automatically by LinkLoot and was not substantively reviewed by a human editor. Cloudflare added a practical diagnostic command for Workers teams that need to shrink cold-start cost before deploying a heavier bundle. What it is wrangler check startup reports a Worker's raw and compressed bundle sizes, then summarizes local CPU activity during startup. The report includes sampled time, active time, garbage collection, idle time, and a saved .cpuprofile file for deeper inspection in Chrome DevTools or VS Code. Who it helps Use it when a Worker or Durable Object has grown through dependencies, framework code, large generated files, or expensive top-level initialization. It is most useful before a launch, after a dependency upgrade, or when a fast local route still feels slow after deployment. How to evaluate it Update to Wrangler 4.116.0 or later, run the startup check locally, then inspect the .cpuprofile if the summary points to heavy startup work. Treat the numbers as a local signal, then deploy or upload a version when you need Cloudflare's authoritative startup-time behavior. Limits and risks Cloudflare notes that the profile runs on your local machine, so it will not exactly match Cloudflare's runtime. The command is a diagnostic tool, not a production latency guarantee. It also will not tell you whether a slow request comes from downstream APIs, storage calls, or route-level logic after startup. Sources Cloudflare changelog

Free

Review open

@ZachasADMIN

Open loot

Add Cloudflare AI Search to agent apps without hand-rolling retrieval

#cloudflare #ai-search+5

Cloudflare published integration paths for using AI Search from the Vercel AI SDK, LangChain, and the Cloudflare Agents SDK. Cloudflare AI Search is now easier to plug into agent and RAG apps because Cloudflare added official guides and framework integrations for common agent stacks. What it is Cloudflare’s July 30 changelog adds an Agents section for AI Search, including examples for the Vercel AI SDK, LangChain, and the Cloudflare Agents SDK. The AI SDK path uses the ai-search-provider package, while LangChain gets a CloudflareAISearchRetriever through langchain-cloudflare. Who it helps This is useful for developers who already index content in Cloudflare and want grounded answers inside an agent loop. It is especially relevant if you are building Workers-based assistants, support bots, internal knowledge tools, or RAG flows that should return source chunks instead of opaque completions. How to evaluate it Start with one small AI Search instance and wire it into a single answer path. Check whether the retrieved chunks are exposed cleanly in your UI or logs, then test failure modes: empty search results, stale indexed content, permission boundaries, and prompt-injection attempts inside retrieved documents. Limits and risks This is a practical integration update, not a new foundation model or major platform shift. You still need to manage Cloudflare credentials, indexing quality, source filtering, and retrieval safety. Treat indexed external content as untrusted input when passing it into an agent. Access and pricing Cloudflare links AI Search to its normal plan and sales pages. Check your account’s AI Search availability and billing before moving beyond a prototype. Sources Cloudflare changelog Cloudflare AI Search docs

Free

Review open

@ZachasADMIN

Open loot

Update Cloudflare Agents without forcing an AI SDK migration

#cloudflare #agents+3

Cloudflare Agents packages now support AI SDK v6 and v7, so teams can update agent tooling while choosing their own migration timing. Cloudflare updated its Agents SDK packages so agents, @cloudflare/ai-chat, @cloudflare/codemode, and @cloudflare/think support both AI SDK v6 and v7. That is useful if you maintain a Cloudflare-based agent app and want the latest Agents packages without turning the dependency update into a forced AI SDK migration. The supported peer ranges are ai@^6 ^7 and @ai-sdk/react@^3 ^4. Cloudflare's note says to pair AI SDK v6 with @ai-sdk/react v3, or AI SDK v7 with @ai-sdk/react v4. Think also normalizes streaming, tool-completion events, and telemetry across both major versions. Use this as a practical upgrade checkpoint: Check whether your app is on AI SDK v6 or v7. Update the Cloudflare Agents packages. Keep the matching @ai-sdk/react major version. Test streaming output, tool calls, and telemetry before deployment. This is a Loot item, not a broad platform-news post: the main value is a clean migration path for teams already building with Cloudflare Agents.

Free

Review open

@ZachasADMIN

Open loot

Manage Cloudflare Feature Flags from Wrangler

#cloudflare #wrangler+3

Cloudflare added wrangler flagship, a command suite for creating Flagship apps, managing feature flags, running rollouts, splitting traffic, evaluating flags, and using CLI kill switches from local terminals or CI. Cloudflare's new wrangler flagship commands give Worker teams a direct CLI path for feature-flag operations that previously pushed developers back into dashboards or custom API scripts. Use it when you need to create Flagship apps, bind flags to a Worker project, define boolean/string/number/JSON variations, roll out a variation by percentage, split traffic, evaluate a flag for a targeting key, or disable a flag as a kill switch. Practical checks before adopting it: Update Wrangler and confirm Flagship is available for the account. Use CLOUDFLAREAPITOKEN in automation with the narrow Flagship read/write permissions Cloudflare documents. Keep flag keys stable because application code evaluates by key. Prefer --json output in scripts so CI jobs can capture app IDs and flag state safely. Treat destructive commands carefully: deleting an app removes its flags and changelog history, and Cloudflare rejects deletion when a Worker still references the app through a Flagship binding. This is a Tool, not a prompt: the value is the official CLI surface for release control, rollout automation, and agent-friendly deployment checks.

Free

Review open

@ZachasADMIN

Open loot

Deploy Cloudflare Workers from an Agent Without OAuth Using Temporary Accounts

#Cloudflare #Workers+3

Cloudflare Temporary Accounts let an agent run wrangler deploy --temporary, publish a Worker for 60 minutes, verify it, redeploy changes, and hand a claim URL to a human. Use it for agent-built prototypes, demos, and review links when you do not want the agent handling a permanent Cloudflare login or API token. Check limits before production: unclaimed deployments expire, a human still needs to claim the account, and permanent workloads need normal ownership and security review. Cloudflare Temporary Accounts let an agent run wrangler deploy --temporary, publish a Worker for 60 minutes, verify it, redeploy changes, and hand a claim URL to a human. Use it for agent-built prototypes, demos, and review links when you do not want the agent handling a permanent Cloudflare login or API token. Check limits before production: unclaimed deployments expire, a human still needs to claim the account, and permanent workloads need normal ownership, observability, and security review.

Free

Review open

@ZachasADMIN

Open loot

Make Cloudflare Workflows retry around rate limits instead of fixed timers

#cloudflare #workflows+4

Cloudflare Workflows now lets each step calculate its next retry delay from the failed attempt and error, useful for rate limits, Retry-After handling, and flaky downstream APIs. Cloudflare added dynamic retry delays to Workflows on July 9, 2026. Instead of picking only a fixed delay plus constant, linear, or exponential backoff, a Workflow step can now pass a function to retries.delay and calculate the next wait from the current attempt and the thrown error. Use this when a workflow calls APIs with different failure modes: wait longer on rate-limit errors, retry faster after a short network failure, or map provider guidance such as Retry-After into your next delay. This is a practical fit for customer sync jobs, AI-provider orchestration, payment/CRM integrations, and any durable workflow that should avoid both blind hammering and unnecessary waiting. Check before using Confirm your Workflow code is using the current Cloudflare Workflows API and docs. Treat error-message matching as a fallback; prefer structured error data when your SDK exposes it. Add a maximum retry count and clear terminal-error path so bad credentials or malformed payloads do not loop. Test against one intentionally rate-limited API call before relying on it for paid providers. Sources Cloudflare changelog: dynamic retry delay support for Workflows. Cloudflare Workflows docs: sleeping, retrying, and the retries.delay function shape.

Free

Review open

@ZachasADMIN

Open loot

Run fast vision checks at the edge with Moondream 3.1 on Workers AI

#cloudflare #workers-ai+5

Cloudflare added Moondream 3.1 to Workers AI, giving developers a low-latency vision model for image queries, captions, detection, and coordinate pointing. Cloudflare has added Moondream 3.1 to Workers AI as @cf/moondream/moondream3.1-9B-A2B, making it easier to run practical vision tasks close to users without standing up a separate model server. What it is Moondream 3.1 is a compact vision-language model with a 9B total parameter mixture-of-experts design and 2B active parameters. Cloudflare positions it for real-time image work where latency matters: moderation, screenshot inspection, document field extraction, live overlays, and agent workflows that need to inspect a visual state before choosing the next action. Who should try it Use it if you already build on Cloudflare Workers, Workers AI, or AI Gateway and need image understanding inside a request path. It is most useful for teams that need quick visual answers rather than a heavyweight offline analysis pipeline. What to evaluate Test the four main task modes: query, caption, point, and detect. Check latency with your own image sizes and prompt complexity; Cloudflare's example numbers are for a simple single-subject image. Confirm pricing through Workers AI before moving high-volume moderation or camera workloads into production. Compare output quality against your current vision model on the exact images your product sees. Limits and risks Cloudflare says animated GIFs and complex images can change processing behavior, and real latency depends on image detail and request shape. Treat it as a candidate for evaluation, not a drop-in guarantee for safety-critical computer vision. Sources Cloudflare changelog: https://developers.cloudflare.com/changelog/ Moondream: https://moondream.ai/

Free

Review open

@ZachasADMIN

Open loot

Preview Static Sites for One Hour with Cloudflare Drop

#cloudflare #static-site+3

Cloudflare Drop lets you upload a folder or ZIP of static assets, get a temporary live preview for one hour, then claim the deployment into a Cloudflare account if it is worth keeping. Cloudflare Drop is a browser-based way to test static sites without setting up Git, Wrangler, or even a Cloudflare account first. Upload HTML, CSS, JavaScript, images, fonts, or a ZIP archive, then share or test the temporary preview URL for one hour. Use it for quick demos, AI-generated static exports, client previews, landing-page drafts, documentation microsites, and handoffs where a live URL is more useful than a screenshot. If the preview works, claim it into a Cloudflare account, verify email when needed, and then add a domain, observability, access controls, or Markdown for Agents. Limits to check: the preview is temporary until claimed, the workflow is for static assets, and production projects still need the usual ownership, domain, security, and maintenance checks. Treat Drop as a fast preview lane, not a replacement for a governed deployment pipeline.

Free

Review open

@ZachasADMIN

Open loot

Use Cloudflare Mythos to Find Real Codebase Bugs with AI Agents

#AI agents #code review+4

A practical defensive guide for checking your own codebase with AI agents: narrow scopes, parallel hunts, adversarial validation, reachability tracing, dedupe, gapfill, and governance gates. Built from the core operational lessons in Cloudflare's Project Glasswing write-up.

Review open

@ZachasADMIN

Open loot

Blog

#cloudflare

More from this topic

Debug Cloudflare Workers locally with traces an AI agent can read

Test Cloudflare Browser Run requests before wiring a Worker

Find slow Cloudflare Worker startup code from Wrangler

Add Cloudflare AI Search to agent apps without hand-rolling retrieval

Update Cloudflare Agents without forcing an AI SDK migration

Manage Cloudflare Feature Flags from Wrangler

Deploy Cloudflare Workers from an Agent Without OAuth Using Temporary Accounts

Make Cloudflare Workflows retry around rate limits instead of fixed timers

Run fast vision checks at the edge with Moondream 3.1 on Workers AI

Preview Static Sites for One Hour with Cloudflare Drop

Use Cloudflare Mythos to Find Real Codebase Bugs with AI Agents

Related reads

Cloudflare merges Workers AI and AI Gateway billing into one control plane

Cloudflare adds identity-aware controls to AI Gateway for enterprise AI spend

Cloudflare ships emergency WAF rules for active RCE and SQLi attacks

Cloudflare exposes Temporary Accounts through its API

Replace Cloudflare Workers KV legacy API routes before October

Cloudflare Precursor Makes Bot Detection a Full-Session Problem

Set AI crawler rules at the origin: Cloudflare Markdown for Agents now preserves Content-Signal headers

Check Durable Object Storage Before Your Next Cloudflare Worker Deploy

Fix Cloudflare Tunnel API Scripts Before October 5 Route Changes

Harden Cloudflare IPsec Tunnels Before Quantum Downgrade Risk Reaches Production

Use Cloudflare Browser Run accessibility trees before agents guess from screenshots

Count Cloudflare Workflows steps before August billing starts

Stop deleting Cloudflare R2 Iceberg files by hand

Check Cloudflare WAF Logs Before Citrix and Kemp Exploit Traffic Turns Noisy

Register Cloudflare One Virtual Appliances without waiting on account teams

Fix Cloudflare Worker type drift before workers-types v5 removes dated entrypoints

Cache localized Cloudflare pages without splitting every URL

Use Wrangler auth profiles to stop switching Cloudflare logins by hand

Charge APIs and MCP Tools with Cloudflare's x402 Monetization Gateway

Use Cloudflare's AI traffic controls before crawler defaults change

Cloudflare adds organization audit logs to the dashboard

Protect Cloudflare WARP macOS Registrations With Secure Enclave Keys

Run Cloudflare agent work in the background with the new Agents SDK update

Check FortiSandbox Exposure: Cloudflare Adds CVE-2026-39813 WAF Logging

Keep Durable Objects in the US: Cloudflare Adds a `us` Jurisdiction

Use Cloudflare PACT to prepare for a web with fewer CAPTCHAs

Harden Ghost sites: Cloudflare WAF now blocks the CVE-2026-26980 SQL injection path

Run long agent tasks on Cloudflare without losing progress

Block Ivanti Sentry CVE-2026-10520 faster: Cloudflare WAF adds managed protection

Cloudflare Workflows Adds Saga Rollbacks for Durable Step Compensation

Cloudflare adds temporary accounts so AI agents can deploy Workers without signup

Cloudflare AI Gateway spend limits turn LLM cost control into a routing decision

Astro 6.4 adds a pluggable Markdown pipeline and Rust processor option

Cloudflare Dynamic Workers make AI-agent sandboxing lighter than containers

Cloudflare Workers AI adds Kimi K2.5 for larger agent workloads

Cloudflare Mythos lesson: stop asking one agent to scan your whole codebase

Daf·thunk is an open-source Cloudflare workflow editor for teams that want visual automation without a heavyweight stack