Current Python transport OpenCode outbound profile + opt-in queue-status SSE #90

New issue

Open

opened 2026-09-20 01:19:23 +00:00 by nsaspy · 0 comments

nsaspy commented

2026-09-20 01:19:23 +00:00

Owner

Reconciles #71/#73 with the current Python transport.

Outbound profile

Implement operator-selected, versioned outbound compatibility/privacy profiles with an OpenCode-style profile as a first-class target.

A profile may normalize allowed application identity headers and strip configured local metadata. It may not alter credentials, routing authority, prompts, tool semantics or quota-group ownership.

Keep original local source-harness provenance separate from egress presentation.

Queue-status SSE

Transparent requests remain ordinary HTTP and either wait within the admission deadline or receive 429.

For explicitly opted-in smart clients, provide a separate queue-status SSE contract:

queued/position/heartbeat events;
admission transition;
final upstream response represented inside the already-committed stream;
timeout/full/cancel typed events.

Acceptance

OpenCode itself plus another supported harness using the OpenCode profile share the same underlying quota group and emit equivalent configured application headers toward a fixture upstream.

Reconciles #71/#73 with the current Python transport. ## Outbound profile Implement operator-selected, versioned outbound compatibility/privacy profiles with an OpenCode-style profile as a first-class target. A profile may normalize allowed application identity headers and strip configured local metadata. It may not alter credentials, routing authority, prompts, tool semantics or quota-group ownership. Keep original local source-harness provenance separate from egress presentation. ## Queue-status SSE Transparent requests remain ordinary HTTP and either wait within the admission deadline or receive 429. For explicitly opted-in smart clients, provide a separate queue-status SSE contract: - queued/position/heartbeat events; - admission transition; - final upstream response represented inside the already-committed stream; - timeout/full/cancel typed events. ## Acceptance OpenCode itself plus another supported harness using the OpenCode profile share the same underlying quota group and emit equivalent configured application headers toward a fixture upstream.