{"version":"2.1.300","anchor":"desktop-claudecodeprocesswrapperenabled-now-also-supported-f","canonical_anchor":"desktop-claudecodeprocesswrapperenabled-now-also-supported-f","heading":"Desktop process-wrapper setting now also applies to first-party sign-ins","tier":"use","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/desktop-claudecodeprocesswrapperenabled-now-also-supported-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Desktop process-wrapper setting now also applies to first-party sign-ins\n\n`claudeCodeProcessWrapperEnabled` now covers the 1p scope from desktop version 2.16120.0, not only the 3p scope\n\n**What**\n\nThe desktop app setting `claudeCodeProcessWrapperEnabled` now lists support for the 1p scope from desktop version 2.16120.0. Before, it was supported only for the 3p scope, from version 2.7032.0.\n\nThe desktop app also now tells Claude Code at launch whether it is running on a self-hosted runner.\n\n**Why**\n\nMore desktop setups can now be made to start Claude Code through a launcher.\n\n- Area: Managed Settings\n- Names: `claudeCodeProcessWrapperEnabled`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}