{"version":"2.1.228","anchor":"more-environment-variables-read-through-the-typed-registry","canonical_anchor":"more-environment-variables-read-through-the-typed-registry","heading":"More environment variables read through the typed registry","tier":"internal","area":"Environment Variables","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/more-environment-variables-read-through-the-typed-registry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### More environment variables read through the typed registry\n\nMore environment variables are read through typed declarations; the tool concurrency cap still defaults to ten.\n\n**What**\n\nSeveral hand-written environment variable readers were replaced by typed accessors. `CLAUDE_CODE_MAX_TOOL_USE_CONCURRENCY` still defaults to 10 and is now declared with a minimum of 1, so a non-positive value falls back to the default as before.\n\n**Details**\n\n- The project UUID reader no longer trims its own value, and the Datadog flush interval reader no longer parses the raw string.\n- A messaging token string variable was added to the same registry module, next to the existing messaging socket variable.\n\n**Evidence**\n\n`CLAUDE_CODE_MAX_TOOL_USE_CONCURRENCY`\n\n- Area: Environment Variables\n- Names: `CLAUDE_CODE_MAX_TOOL_USE_CONCURRENCY`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}