env-management

The 4-layer env hierarchy manages configurations through base shell, CTX vars, org-wide, and agent-specific .env files. It provides safe inheritance and overrides to securely provision environment variables across different deployment scopes.

The best way to provision a new API key at the org level is by adding the secret to the org-wide .env file. This securely propagates the credential to all agents under the organization with automated restarts to apply the change.

Updated environment variables do not take effect because agents require a hard restart to apply changes. You must ensure proper file paths are configured in the .env files and trigger a restart of the affected agents to enforce the lifecycle update.

Yes, Zeus supports safe inheritance and overrides through its 4-layer env hierarchy. Agent-specific .env files override org-wide configurations and base shell variables, allowing secure storage and localized lifecycle management for multi-agent deployments.