Thanks — I’m responding to your note about deleting API keys but still seeing the old values in

LIVEKIT_API_KEY

/

LIVEKIT_API_SECRET

. Quick explanation and what you can do now: • Environment variables are injected into running agent containers at deployment time. If an agent was deployed with an old key, it will keep using that value until you update/redeploy the agent. • Update the agent secrets so the containers get the new key and trigger a rolling restart: a. Put the new

LIVEKIT_API_KEY

and

LIVEKIT_API_SECRET

into your local secrets file (e.g.,

.env.local

). b. Run:

lk agent update-secrets --secrets-file .env.local --overwrite

• Verify you didn’t bake old credentials into images or code (check

.env

files in builds; use

.dockerignore

to avoid including them). • Use

lk project list

to confirm the CLI/project configuration is pointed at the correct project. If you want, tell me: • How you deploy agents (LiveKit Cloud agent, Docker, Kubernetes, etc.) • Whether you already ran

lk agent update-secrets

and saw a restart I’ll guide the exact next steps based on your deployment method. Sources: LiveKit CLI project management | LiveKit docs | Secrets management | LiveKit docs | examples/survey | livekit/livekit_composite | DeepWiki