When it comes to updating a LiveKit agent, you'll need to redeploy the entire agent rather than just specific files. This is because the deployment process creates a fresh container image from your code and uses a rolling deployment approach. This way, your service stays up and running smoothly—any sessions already in progress will finish on the old version, while new sessions will automatically connect to the updated version. If you have any questions about this process, I'm here to help! Sources: cmd/lk/agent.go | Deploying to production | LiveKit Docs