Context
CLAUDE.md is explicit that the product/brand name is Extra; agent-engine/agent-manager are only the PyPI package and console-script names, never meant to be user-facing.
Every runtime setting, though, is prefixed AGENT_ — AGENT_DB_BACKEND, AGENT_DB_URL, and now (from #94) the whole AGENT_AUTH_* family (AGENT_AUTH_MODE, AGENT_AUTH_SECRET, AGENT_AUTH_COOKIE, AGENT_AUTH_CLAIM_*, etc.).
Why this is worth fixing
- Brand mismatch. An admin configuring "Extra" will reasonably look for
EXTRA_*, not AGENT_* — the env-var surface leaks an internal package name into the one place customers actually type things.
- Collision risk in enterprise environments. "agent" is a heavily overloaded word in infra (monitoring agents, security agents, etc.).
AGENT_AUTH_MODE sitting next to e.g. DATADOG_AGENT_* in a shared secrets manager or ConfigMap is genuinely easy to misread or collide with.
Why it's not part of #94
#94 only adds new settings; it followed the AGENT_DB_* naming that already shipped rather than introducing a second, inconsistent prefix (EXTRA_AUTH_* next to AGENT_DB_*) inside one PR. A rename is a deliberate, product-wide decision, not something to fold into a feature branch.
Suggested approach
- Introduce
EXTRA_* as the primary name for every setting.
- Keep the old
AGENT_* names working as deprecated aliases for at least one release (warn on use, don't break existing deployments outright), then drop them.
- Update
.env.example, examples/*/.env.example, and the docs (docs/identity.mdx, docs/quickstart.mdx, etc.) in the same pass.
🤖 Generated with Claude Code
Context
CLAUDE.mdis explicit that the product/brand name is Extra;agent-engine/agent-managerare only the PyPI package and console-script names, never meant to be user-facing.Every runtime setting, though, is prefixed
AGENT_—AGENT_DB_BACKEND,AGENT_DB_URL, and now (from #94) the wholeAGENT_AUTH_*family (AGENT_AUTH_MODE,AGENT_AUTH_SECRET,AGENT_AUTH_COOKIE,AGENT_AUTH_CLAIM_*, etc.).Why this is worth fixing
EXTRA_*, notAGENT_*— the env-var surface leaks an internal package name into the one place customers actually type things.AGENT_AUTH_MODEsitting next to e.g.DATADOG_AGENT_*in a shared secrets manager or ConfigMap is genuinely easy to misread or collide with.Why it's not part of #94
#94 only adds new settings; it followed the
AGENT_DB_*naming that already shipped rather than introducing a second, inconsistent prefix (EXTRA_AUTH_*next toAGENT_DB_*) inside one PR. A rename is a deliberate, product-wide decision, not something to fold into a feature branch.Suggested approach
EXTRA_*as the primary name for every setting.AGENT_*names working as deprecated aliases for at least one release (warn on use, don't break existing deployments outright), then drop them..env.example,examples/*/.env.example, and the docs (docs/identity.mdx,docs/quickstart.mdx, etc.) in the same pass.🤖 Generated with Claude Code