Thanks — you're asking how to move your agent to a new region. Quick answers and next steps: • You set the deployment region with the CLI

--region

flag when creating or deploying an agent. Example: ◦

lk agent create --region us-west

• If you already have an agent, create/deploy a new instance in the target region using

lk agent create --region <region>

(or

lk agent deploy

from the agent directory after updating region settings). The CLI uploads, builds, and deploys to the chosen region. • LiveKit Cloud supports several regions (examples:

us-east

,

eu-central

,

ap-south

). If your desired region isn’t supported, you can self-host the agent in your own infrastructure to run in that region. • Note: there isn’t a single “move” command that transparently migrates an existing instance between regions; the practical approach is to deploy a new agent in the target region and switch traffic/IDs as needed. Deployments use rolling updates with graceful draining (old instances may remain handling sessions for up to ~30–60 minutes). Would you like: • Step-by-step commands for creating/deploying to a specific region (tell me which region), or • Help checking whether your target region is available on LiveKit Cloud? Sources: Checklist for Regional Deployments | LiveKit | Understand and Improve Agent Latency | LiveKit | Agents on LiveKit Cloud | Deploy voice AI on global infrastructure | LiveKi... | Deployment reliability on LiveKit Cloud | LiveKit, with interactive elements