Thanks — you're asking how to spawn a LiveKit agent once and have it handle many sessions. Good question — yes, a single agent server process is designed to stay running and handle many sessions (rooms) over time. What to do (high-level): • Start a long-lived agent server process (e.g., with

cli.run_app(server)

) so it registers with the LiveKit server and remains available. • Use the Agents framework’s

ServerType

to control per-session behavior: ◦

ServerType.ROOM

spawns one job per room (recommended for most cases). ◦

ServerType.PUBLISHER

spawns per publisher if you need per-stream isolation. • The agent server can run multiple jobs concurrently; each job runs in its own process for isolation. • Run multiple agent server replicas to scale; LiveKit automatically balances job dispatch across available servers. If you want, tell me: • which language/framework you’re using (Python/JS/Go), and • whether you want one agent instance per room or per publisher, and I’ll give a concrete example for your setup. Sources: Server lifecycle | LiveKit docs | Agent server options | LiveKit docs | examples/drive-thru | livekit/livekit_composite | DeepWiki