{"version":"2.1.232","anchor":"three-more-variables-can-be-set-from-settings-json","canonical_anchor":"three-more-variables-can-be-set-from-settings-json","heading":"Three more variables can be set from settings.json","tier":"use","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/three-more-variables-can-be-set-from-settings-json","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Three more variables can be set from settings.json\n\nYou can now set OTEL_SERVICE_NAME, OTEL_TRACES_EXPORT_INTERVAL and CLAUDE_CODE_FORK_SUBAGENT in settings.json.\n\n**What**\n\nThe `env` block in settings.json may now set `OTEL_SERVICE_NAME`, `OTEL_TRACES_EXPORT_INTERVAL` and `CLAUDE_CODE_FORK_SUBAGENT`, which previously only took effect from the shell. The first names your service in OpenTelemetry output and the third turns forked subagents off.\n\n**Usage**\n\n`{ \"env\": { \"OTEL_SERVICE_NAME\": \"claude-code-team-a\", \"CLAUDE_CODE_FORK_SUBAGENT\": \"false\" } }` **Evidence** `OTEL_TRACES_EXPORT_INTERVAL`\n\n- Area: Settings\n- Names: `OTEL_SERVICE_NAME`, `OTEL_TRACES_EXPORT_INTERVAL`, `CLAUDE_CODE_FORK_SUBAGENT`, `env`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 3\/5"}