Topic

#workers

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

#workers

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

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

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

Blog

#workers

More from this topic

Debug Cloudflare Workers locally with traces an AI agent can read

Find slow Cloudflare Worker startup code from Wrangler

Manage Cloudflare Feature Flags from Wrangler

Deploy Cloudflare Workers from an Agent Without OAuth Using Temporary Accounts

Related reads

Cloudflare Access now protects Workers at the app and account level

Cloudflare exposes Temporary Accounts through its API

Check Durable Object Storage Before Your Next Cloudflare Worker Deploy

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

Use Wrangler auth profiles to stop switching Cloudflare logins by hand

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

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

Run long agent tasks on Cloudflare without losing progress

Cloudflare Dynamic Workers make AI-agent sandboxing lighter than containers