Add opt-in streaming queue-status protocol for smart clients #70

New issue

Open

opened 2026-09-12 19:54:49 +00:00 by nsaspy · 0 comments

nsaspy commented

2026-09-12 19:54:49 +00:00

Owner

Goal

Give queue-aware clients a way to hold a request open and receive queue/status heartbeats without compromising the transparent proxy path.

Why this is separate

A transparent HTTP proxy cannot emit SSE response-body bytes while a request is queued and then later preserve the upstream status line and headers: sending the SSE response commits the downstream HTTP response first.

Scope

Define an explicit opt-in queue-aware protocol/header or endpoint.
For opted-in streaming clients, emit queue/heartbeat events while waiting.
On admission, bridge the upstream streaming response into the already-established downstream stream.
Define how upstream non-2xx responses are represented after the downstream stream is committed.
Preserve the normal transparent path for clients that do not opt in; those clients receive bounded waiting or 429 + Retry-After from #70.
Integrate Agent Zero in #72 once this contract exists if the streaming path is useful.

Tests

heartbeat while queued;
admission transition;
cancellation while queued;
queue timeout/full error event;
upstream non-2xx mapping;
no interference with transparent HTTP behavior.

## Goal Give queue-aware clients a way to hold a request open and receive queue/status heartbeats without compromising the transparent proxy path. ## Why this is separate A transparent HTTP proxy cannot emit SSE response-body bytes while a request is queued and then later preserve the upstream status line and headers: sending the SSE response commits the downstream HTTP response first. ## Scope - Define an explicit opt-in queue-aware protocol/header or endpoint. - For opted-in streaming clients, emit queue/heartbeat events while waiting. - On admission, bridge the upstream streaming response into the already-established downstream stream. - Define how upstream non-2xx responses are represented after the downstream stream is committed. - Preserve the normal transparent path for clients that do not opt in; those clients receive bounded waiting or `429 + Retry-After` from #70. - Integrate Agent Zero in #72 once this contract exists if the streaming path is useful. ## Tests - heartbeat while queued; - admission transition; - cancellation while queued; - queue timeout/full error event; - upstream non-2xx mapping; - no interference with transparent HTTP behavior.

nsaspy referenced this issue

2026-09-12 19:54:49 +00:00

Add smart-client retry/queue integration for Agent Zero #71

nsaspy referenced this issue

2026-09-12 19:54:49 +00:00

Versioned outbound privacy/compatibility profiles for Hermes, OpenClaw and Agent Zero #72

nsaspy referenced this issue from a pull request that will close it,

2026-09-12 20:08:46 +00:00

Add provider-wide request scheduling and 429 backpressure #74

nsaspy referenced this issue

2026-09-12 23:06:24 +00:00

Rate admission: enforce time-based quotas shared across client/provider aliases #75