[jinxi97]

Problem

GET /v1/sessions/:id/stream has no server-side EOF. Its loop polls the store until stream.aborted, which needs the hang-up to reach the process. Behind a front end that speaks HTTP/1.1 to the container (Cloud Run's default), it doesn't: the request stays open until the platform's timeout (up to an hour). The loop keeps polling every FUNKY_STREAM_POLL_MS for nobody, and holds one of the instance's concurrency slots the whole time.

Seen on Cloud Run on 2026-10-26: reconnecting clients filled all 240 request slots (3 instances × 80) with orphaned streams. Every request then hung or got 429 Rate exceeded. until a fresh revision was rolled. Request logs showed stream requests completing after >1000s, though their clients had left after 2s.

Fix

• apps/api/src/listen.ts: HTTP/1.1 and h2c on one port, routed by each connection's first bytes (the h2c preface → node:http2, anything else → node:http). A deployment can now turn on end-to-end HTTP/2, where a hang-up arrives as an RST_STREAM. Health probes, curl, compose and the SDKs keep HTTP/1.1; nothing changes for a deployment that never sends h2c.
• Stream route: drops the Transfer-Encoding and Connection headers streamSSE sets. HTTP/2 forbids them: the first fails the response outright, and the second is dropped with a warning. Node sets both itself over HTTP/1.1, so the wire is unchanged there (checked with curl -i --http1.1).

Tests

apps/api/test/listen.test.ts runs the real buildApp over real sockets:

• both protocols answer /health;
• a client hanging up stops the stream's poll loop, via a store that counts polls, over h2c (RST_STREAM) and over HTTP/1.1 (closed connection).

The h2c case fails without the header change (ERR_HTTP2_INVALID_CONNECTION_HEADERS). No @hono/node-server bump is needed: the 2.0 line cancels a started response body on an h2 reset, and a stream's response has always started (checked on 2.0.8). api: 109/109 tests pass; pnpm typecheck and prettier --check are clean.

Deploying behind Cloud Run

Name the container port h2c (Terraform: ports { name = "h2c" }) for end-to-end HTTP/2. Cloud Run's HTTP probes stay on HTTP/1, which this serves on the same port. funkyhq/cloud does this for its gateway in funkyhq/cloud#95 and will set it for the api once this lands.

🤖 Generated with Claude Code

[jinxi97]

Closing: Funky is a batch engine for deferrable tasks, so we're removing /v1/sessions/:id/stream instead of hardening it (clients poll /entries?after=). Replaced by the stream-removal PR.