Environment Variables
AGILab reads its configuration from environment variables. You can set them globally in
$HOME/.agilab/.env or per-session before launching the web interface / AGI installers. The table below
summarises the supported keys.
Variable |
Default |
Purpose |
|---|---|---|
|
|
Root directory containing app projects; used when selecting the active app. |
|
|
App loaded when no explicit project is provided. |
|
|
Default Python version passed to |
|
unset |
Optional worker-specific Python version override written per host (for example |
|
|
Enables free-threaded Python if both the environment and worker declare support. Either the
string |
|
|
Maximum number of rows shown in web data previews. |
|
|
Sample size used when previewing large tables. |
|
Current OS user |
Username/password pair ( |
|
unset |
API key surfaced to features that rely on OpenAI endpoints. |
|
|
User-facing knob for the shared datasets/outputs root. When cluster mode is enabled, this value is applied to |
|
|
Local datasets/outputs root used when cluster mode is disabled. In cluster mode, AGILab no longer falls back to this path if the shared mount is missing. |
|
|
Default scheduler host for distributed runs. |
|
|
Parent directory for install logs ( |
|
|
Target directory for exported artefacts. |
|
|
Where MLflow tracking data is stored. The PIPELINE page serves the local MLflow UI from this directory and records parent/step run metadata and artefacts there. |
|
|
Location of web page bundles loaded by the Analysis page. |
|
unset |
Optional pointer to the repository checkout containing apps or overrides. |
|
|
Controls the installation mode passed to |
Additional host specific keys are supported for worker provisioning (for example
127.0.0.1_CMD_PREFIX or 127.0.0.1_PYTHON_VERSION). These are written automatically into
$HOME/.agilab/.env when you run installers and can be adjusted manually when one worker host
needs a different Python version or command prefix.
Remember to restart the web interface session after changing $HOME/.agilab/.env so AgiEnv picks
up the new values.
Security note
Prefer environment variables or $HOME/.agilab/.env for secrets such as
OPENAI_API_KEY and CLUSTER_CREDENTIALS. Avoid passing them on the
command line because shell history and process listings can expose them.