Got an email from LiveKit saying the following: Your project AI_MODERATOR_SECOND_VERSION has recently reached or surpassed 5 concurrent cloud agent jobs, which is the limit set on your project. To avoid service disruption for your users, please review your options in the settings page for your project.

Thanks for reaching out, Ganesh. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.

How do I kill these sessions in the terminal right now?

Thanks — I see you want to immediately kill the running agent sessions for project AI_MODERATOR_SECOND_VERSION. Short answer: there is no documented terminal command to forcibly kill individual LiveKit Cloud agent sessions. However you can end sessions now using one of these actions: • Restart the agent deployment (graceful drain): run

lk agent restart

for the agent serving that project. This stops new jobs and waits for jobs to finish (honors drain timeout). • Delete the agent deployment:

lk agent delete

— removes the agent and will stop sessions as the deployment is removed. • Delete the room via the Server API to immediately disconnect participants and end the session. Example (Python):

await api_client.room.delete_room(api.DeleteRoomRequest(room=ctx.job.room.name))

• If you self-host agents, send SIGTERM to the agent process to trigger drain mode (not an immediate force-kill). If you’d like, tell me which option you prefer and whether you’re using LiveKit Cloud or a self-hosted agent, and I’ll give the exact

lk

commands or the API call details you need. Sources: Agents Framework | livekit/livekit_composite | DeepWiki | examples/drive-thru | livekit/livekit_composite | DeepWiki | Deployment reliability on LiveKit Cloud | LiveKit | Job lifecycle | LiveKit Documentation, with interactive elements