// AI Platform Drift

Cloudflare Workers connect() handler now production-ready without experimental flag

Cloudflare developer changelog · published 2026-10-13 22:49 UTC
WORTH KNOWING VERIFY_ONLY API
WHAT CHANGEDCloudflare Workers can now export a connect() handler without enabling the experimental compatibility flag. Previously, this handler required an experimental flag that could not be enabled in production environments. The change was effective 18 August 2026.
WHY IT MATTERSWorkers using connect() handlers for TCP socket communication over service bindings can now run in production. Code previously blocked from production deployment due to the experimental flag requirement is now deployable without modification.
WHAT TO DOIf you have Workers with connect() handlers currently restricted to non-production environments, remove the experimental compatibility flag from your wrangler.toml configuration and deploy to production.
Model-reported confidence 85% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Workers - Connect handler no longer requires an experimental flag
+https://developers.cloudflare.com/changelog/post/2026-08-18-connect-handler/
+Tue, 18 Aug 2026 00:00:00 GMT
+
+Workers can now export a connect() handler without enabling any compatibility flag. Previously, using a connect() handler required the experimental compatibility flag, which cannot be enabled in production.
+A connect() handler lets a Worker accept a TCP connection forwarded from another Worker over a service binding, and read and write raw bytes on it using a Socket object:
+backend-worker.jsjsexport default {
+async connect(socket, env, ctx) {
+const writer = socket.writable.getWriter();
+await writer.write(new TextEncoder().encode("hello"));
+await writer.close();
+},
+};
+Another Worker forwards a connection to it by calling connect() on the service binding:
+frontend-worker.jsjsexport default {
+async fetch(request, env) {
+const socket = env.BACKEND.connect("example.com:1234");
+return new Response(socket.readable);
+},
+};
+On the connect() handler side, socket.opened resolves with localAddress set to the address the caller passed to connect().
+Direct inbound TCP connections remain unsupported at present.
+For more information, refer to the connect handler documentation.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningConnect handler moves from experimental (non-production) to stable production API without flag requirement.
signalsexperimental flag requirement removed · feature graduation to production-ready · breaking change: compatibility flag no longer needed · API execution model change
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)