{"version":"2.1.293","anchor":"credential-helper-script-arguments-and-a-windows-specific-he","canonical_anchor":"credential-helper-script-arguments-and-a-windows-specific-he","heading":"Credential helper scripts can take arguments and have a separate Windows path","tier":"use","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/credential-helper-script-arguments-and-a-windows-specific-he","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Credential helper scripts can take arguments and have a separate Windows path\n\nA credential helper script can now be given up to 32 arguments and a separate path to use on Windows\n\n**Unclear.** It is not clear whether these fields affect the command-line Claude Code or only the desktop app.\n\n**What**\n\nA credential helper is a script an administrator provides that Claude runs to get the credentials for model requests. In the managed configuration, it gains two fields:\n\n- `args` (shown as Helper script arguments): up to 32 entries passed to the helper when it runs. Before, the helper was always run with no arguments.\n\n- `commandWindows`: a path to the helper used only on Windows.\n\nSeveral of these fields are marked as applying to the desktop app.\n\n**Why**\n\nAdmins can ship one helper script and change what it does per user through its arguments, and point Windows machines to a different file.\n\n- Area: Managed Settings\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}