Skip to main content
The CLI reads these variables from the shell environment. At startup it also loads the .env file in the current directory into that environment, so any of them can be set there; a variable already set in the shell wins. None of them is sent to the platform. lua status --json reports the credential and URL variables under environment.envOverrides. Verified against lua-cli 3.33.0.

Credentials and URLs

A user session is stored per LUA_API_URL and LUA_AUTH_URL pair. Pointing the CLI at another environment means signing in again there. Two more variables, LUA_FIREBASE_WEB_API_KEY and LUA_POSTHOG_KEY, point the CLI at Lua’s own test environments and have no use outside them.

Output and diagnostics

Workflow push

Local sandbox for lua test

lua test runs your code in a local sandbox with the same module and network policy as the deployed runtime. These variables are read from the CLI’s own environment, not from the variables handed to your code, so a tool cannot widen the allowlist from inside the sandbox. Sandbox policy events print to stderr as [sandbox] {…} JSON lines.

See also