{"version":"2.1.311","anchor":"auth-helper-commands-wrapped-in-a-shared-runner","canonical_anchor":"auth-helper-commands-wrapped-in-a-shared-runner","heading":"Credential and header helper commands now run through one shared runner","tier":"internal","area":"Settings","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/auth-helper-commands-wrapped-in-a-shared-runner","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Credential and header helper commands now run through one shared runner\n\nThe five settings that run your own command for a credential or header now all start that command through one shared runner\n\n**Unclear.** It is not known whether the shared runner changes how or when these helper commands actually run.\n\n**What**\n\nSeveral settings let you name a command of your own that Claude Code runs to fetch a credential or a header. These five now start their command through one shared runner, which is told which helper it is running:\n\n- `apiKeyHelper`\n\n- `awsAuthRefresh`\n\n- `awsCredentialExport`\n\n- `gcpAuthRefresh`\n\n- `otelHeadersHelper`\n\nBefore this change, Claude Code started each of these commands directly.\n\n**Why**\n\nAll five helpers now go through the same step before their command runs. Any later change to how helper commands are started will therefore apply to all five at once.\n\n- Area: Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: no"}