Skip to content

Build AI methods with your coding agent, then run them anywhere: as an MCP for chatbots, as a webapp for people, or via API for your software.

fix/environment name to pipelex_env

thomashebrard6459f0def6c5
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 0c24c1469..61337ed1e 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,11 @@
# Changelog
+## [Unreleased]
+
+### Changed
+
+- **`RunEnvironment` env var renamed from `ENVIRONMENT` to `PIPELEX_ENV`.** The variable that selects the environment-specific `pipelex_<env>.toml` overlay (and is stamped on OTel spans as `deployment.environment`) is now namespaced to avoid collisions with unrelated `ENVIRONMENT` variables already set in deployment environments. Update any shell, CI, or container config that exported `ENVIRONMENT=...` to export `PIPELEX_ENV=...` instead.
+
## [v0.26.4] - 2026-05-06
### Fixed
diff --git a/pipelex/system/runtime.py b/pipelex/system/runtime.py
index 9cb7761a7..cddb8e4ea 100644
--- a/pipelex/system/runtime.py
+++ b/pipelex/system/runtime.py
@@ -70,7 +70,7 @@ class RunEnvironment(StrEnum):
@classmethod
def get_from_env_var(cls) -> "RunEnvironment":
- return RunEnvironment(get_optional_env("ENVIRONMENT") or RunEnvironment.DEV)
+ return RunEnvironment(get_optional_env("PIPELEX_ENV") or RunEnvironment.DEV)
class ProblemReaction(StrEnum):