Environment Variables
Combine project settings with provider variables such as JAVA_HOME, ANDROID_HOME and ANDROID_SDK_ROOT.
Manage configured values
env add and env remove edit the local base configuration, or the global base with -g. env list shows merged configured variables; bare env prints shell statements including provider variables and PATH integration. Project aliases/env and .env files require trust.
avm env add NODE_ENV development
avm env add -g EDITOR vim
avm env list
avm env remove NODE_ENV
avm env --shell sh
avm env --shell pwsh
avm env --shell cmdShell refresh and profiles
Activate shell-init to apply the printed environment automatically. Bash and PowerShell refresh at prompts; zsh also refreshes on directory changes. The wrapper refreshes around avm commands. Leaving a project restores the original value or unsets a previously absent variable.
avm env --env production prints exports for that invocation only. Set AVM_ENV in the shell to select the same profile for subsequent commands. cmd.exe has a forwarding avm command but does not provide automatic shell refresh.
Storage and diagnostics
AVM_HOME changes the managed storage root (normally ~/.avm); AVM_PLUGIN_DIR overrides the plugin discovery directory. AVM_DEBUG=1 enables additional diagnostics.
AVM_PLUGIN_INSTALL_TIMEOUT is measured in seconds and defaults to 1800, covering plugin download, verification and extraction. Android has additional timeout controls described in its plugin guide.