Thanks — I hear your concern about seeing different API keys in the deployed app than the ones you put in

env.local

. I’m responding about why

LIVEKIT_API_KEY

/

LIVEKIT_API_SECRET

can differ between local files and a cloud deployment, and what you can do. What’s happening • LiveKit Cloud does not upload or use the

LIVEKIT_API_KEY

,

LIVEKIT_API_SECRET

, and

LIVEKIT_URL

values from local env files during deployment. • The platform auto-injects system-managed credentials for your project into the running environment. That’s why

os.getenv("LIVEKIT_API_KEY")

/

LIVEKIT_API_SECRET")

in the deployed app show a different pair — they are the platform-provisioned keys, not the ones in your local

env.local

. What this means for you • The keys printed by your deployed process are valid for that deployment even if they don’t match local files or what you expect to see in the console. • This behavior is intentional to keep agent credentials secure and consistent across deployments. If you want to verify or change credentials • If you need to use specific credentials or inspect project credentials, tell me whether you want to: ◦ confirm which project/agent is running (I can walk you through checks to identify the project/agent), ◦ use different credentials for local testing vs cloud (I can show safe ways to do that), or ◦ rotate/regenerate keys for the project (I can outline the steps). Which of those would you like to do, or share whether you’re running in development vs a cloud deployment so I can give precise steps. Sources: Examples | livekit/livekit_composite | DeepWiki | Agents Framework | livekit/livekit_composite | DeepWiki