{"version":"2.1.301","anchor":"self-hosted-byoc-remote-environment-detector","canonical_anchor":"claude-code-remote-environment-type-added-to-a-forwarded-o","heading":"Self-hosted remote environments get their own detection","tier":"internal","area":"Self-Hosted Runners","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/self-hosted-byoc-remote-environment-detector","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Self-hosted remote environments get their own detection\n\nClaude Code now recognises self-hosted BYOC remote environments and passes CLAUDE_CODE_REMOTE_ENVIRONMENT_TYPE along with related variables\n\n**What**\n\nAn environment variable is a named value set outside Claude Code that it reads at startup. Claude Code can run in a remote environment, a machine somewhere other than your own computer. It now has a dedicated check for one kind of these, a self-hosted \"bring your own cloud\" (BYOC) environment:\n\n- The check is true only when `CLAUDE_CODE_REMOTE` is set to a true value, `CLAUDE_CODE_ENVIRONMENT_KIND` is `byoc`, and `CLAUDE_CODE_REMOTE_ENVIRONMENT_TYPE` is `self_hosted`.\n\n- `CLAUDE_CODE_REMOTE_ENVIRONMENT_TYPE` is added to a list of variables that already held `CLAUDE_CODE_REMOTE_HERMETIC_MODE`, `CLAUDE_CODE_HOSTED_DESKTOP` and `CLAUDE_CODE_ENVIRONMENT_KIND`. The list appears to control which variables are passed along or allowed.\n\n- Both `CLAUDE_CODE_REMOTE_ENVIRONMENT_TYPE` and `CLAUDE_CODE_ENVIRONMENT_KIND` are now read in more places than before.\n\n**Why**\n\nIf you run Claude Code in a self-hosted remote environment, it can now behave differently from other remote setups, and this setting now travels with the other environment settings.\n\n- Area: Self-Hosted Runners\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: no"}