Bridge Transport v1 vs v2
- Entity ID:
ent-20260420-bridgev1v2a01 - Type:
concept - Scope:
shared - Status:
active - Aliases: env-based bridge, env-less bridge, ReplBridgeTransport
Description
Two transport generations in the bridge layer. v1 is env-based (WebSocket reads via Session-Ingress, HTTP POST writes, negotiated through the Environments API poll/ack/dispatch lifecycle). v2 is env-less (SSE stream via SSETransport reads, CCRClient writes to /worker/* endpoints, negotiated via direct POST /v1/code/sessions/{id}/bridge returning a worker JWT). Both are wrapped behind the ReplBridgeTransport interface in replBridgeTransport.ts.
Key claims
- Bridge entitlement requires OAuth + GrowthBook gate
- Bridge session has a six-step lifecycle
- Bridge has two transport generations
- Session-Ingress JWTs are sk-ant-si- prefixed
Relations
- Bridge System --[contains]--> Bridge Transport v1 vs v2
- Bridge Transport v1 vs v2 --[uses]--> WorkSecret Payload
- Bridge Transport v1 vs v2 --[uses]--> HybridTransport (v1 Bridge)
- Bridge Transport v1 vs v2 --[uses]--> CCRClient
- Bridge Transport v1 vs v2 --[uses]--> SSETransport