Thanks — you’re asking how to check the environment variables of a deployed agent. I can help with that. Short answer • You can list the names (keys) of secrets configured for an agent with the CLI, but you cannot retrieve the secret values. LiveKit intentionally hides secret values for security. What you can do • List secret keys for an agent:

lk agent secrets --id <agent-id>

This shows the secret names (for example

OPENAI_API_KEY

) but not their values. • Update secrets without redeploying:

lk agent update-secrets --secrets KEY=VALUE --id <agent-id>

This restarts the agent with the new environment variables. • Confirm presence of runtime-injected LiveKit credentials: ◦

LIVEKIT_API_KEY

,

LIVEKIT_API_SECRET

, and

LIVEKIT_URL

are injected automatically and are not exposed in user-configured secret listings. What you cannot do • Retrieve the plaintext values of environment variables/secrets for a deployed agent via the CLI or dashboard. This is by design for security. Safe alternatives to inspect values during development • Log environment values locally during development (avoid logging sensitive values in production). • Run the agent locally with the same secrets to verify values. • If you need to change a value, use

lk agent update-secrets

to replace it. If you want, tell me: • your agent ID (or the

livekit.toml

project context), and • whether you want to list keys or update a particular secret — and I’ll give the exact command(s) and step-by-step for your case. Sources: Agents Framework | livekit/livekit_composite | DeepWiki | Agents (Python) | livekit/livekit_composite | DeepWiki | Server-side | livekit/livekit_composite | DeepWiki