Skip to content

serve server.http routes through the agent data plane - #6918

Draft
theomonnom wants to merge 1 commit into
longc/server-httpfrom
theo/agent-endpoints-sdk
Draft

serve server.http routes through the agent data plane#6918
theomonnom wants to merge 1 commit into
longc/server-httpfrom
theo/agent-endpoints-sdk

Conversation

@theomonnom

Copy link
Copy Markdown
Member
  • server.http routes are served at /agents/{deployment}/{path} through the LiveKit server; no local listener exposes user routes (a health-only listener remains for probes)
  • Route manifest (methods verbatim, per-route public via configure_endpoint) registers on the control connection; the worker dials a fixed pool of wires speaking AgentHttp.Frame
  • Each stream bridges one opaque HTTP/1.1 exchange into the FastAPI app in-process (h11 → ASGI): streaming/SSE pass through, two-level credit flow control, per-wire parameters from the attach response, attach retry + redial within the registration epoch
  • Worker status reports draining/seq for server-side load balancing

Built on #6856 (base branch). Depends on livekit/protocol#1728 — requires a livekit-protocol Python release with the new bindings, so CI fails until that ships and the pin is raised.

User routes declared on server.http are served at /agents/{deployment}/{path}
through the LiveKit server: the worker registers a route manifest on the
control connection and dials a fixed pool of wires speaking AgentHttp.Frame;
each stream bridges one opaque HTTP/1.1 exchange into the FastAPI app
in-process (h11 -> ASGI, two-level credit flow control, per-wire parameters
from the attach response, redial within the epoch). No local listener serves
user routes; a health-only listener remains for probes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant