Answer: CLAUDE_CODE_PROCESS_WRAPPER wraps Claude Code's own processes and passes the command through as separate argv tokens for the launcher to exec, while CLAUDE_CODE_SHELL_PREFIX wraps the shell commands Claude runs on your behalf, such as Bash tool calls, hooks, and the commands that start stdio MCP servers, and passes each one as a single shell-quoted string in $1 for the wrapper to re-evaluate. Status: Confirmed Entry: tool/claude-code/admin-and-enterprise/process-wrapper-vs-shell-prefix Revision: 1 Digest: sha256:d49c32b16381dfbc (changes whenever the content changes) Timeline: Created: 2026-11-13T12:09:40Z Last changed: 2026-11-13T12:09:40Z Last verified: 2026-11-20T12:19:52Z Next check: 2026-11-21T12:19:52Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of PROCESS_WRAPPER behavior | wraps Claude Code's own processes and passes the command through as separate argv tokens for the launcher to `exec` | [1] | 2026-11-20 SHELL_PREFIX behavior | wraps the shell commands Claude runs on your behalf, such as Bash tool calls, hooks, and the commands that start stdio MCP servers | [1] | 2026-11-20 SHELL_PREFIX argument format | passes each one as a single shell-quoted string in `$1` for the wrapper to re-evaluate | [1] | 2026-11-20 compatibility | A launcher written for one doesn't work as the other. | [1] | 2026-11-20 Sources: [1] Anthropic. "Run Claude Code behind a corporate launcher". https://code.claude.com/docs/en/corporate-launcher.md Role: primary. Accessed: 2026-11-20T12:19:52Z Quote: "`CLAUDE_CODE_PROCESS_WRAPPER` wraps Claude Code's own processes and passes the command through as separate argv tokens for the launcher to `exec`." (Supports: PROCESS_WRAPPER behavior) Quote: "wraps the shell commands Claude runs on your behalf, such as Bash tool calls, hooks, and the commands that start stdio MCP servers" (Supports: SHELL_PREFIX behavior) Quote: "passes each one as a single shell-quoted string in `$1` for the wrapper to re-evaluate" (Supports: SHELL_PREFIX argument format) Quote: "A launcher written for one doesn't work as the other." (Supports: compatibility) Published: 2026-11-20T04:35:55Z Snapshot SHA-256: bb8d1a8d8d9056a04a34ea228cba21dd3cf8d2d3b00dff5947d74f274cf9ea0f (captured 2026-11-15T12:19:41Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T12:09:40Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:19:52Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:19:52Z Last attempt: 2026-11-20T12:19:52Z Notes and limitations: Extracted automatically from a single official source (section "Relationship to `CLAUDE_CODE_SHELL_PREFIX`"). Related: https://latestn.com/tool/claude-code/admin-and-enterprise/provide-mcp-servers-managed-settings How do I provide MCP servers to every user through managed settings in Claude Code? https://latestn.com/tool/claude-code/admin-and-enterprise/rename-plugin-renames-map How do I rename a plugin in a Claude Code marketplace without breaking existing installs? https://latestn.com/tool/claude-code/admin-and-enterprise/restrict-login-organization How do I restrict Claude Code login to my organization? https://latestn.com/tool/claude-code/admin-and-enterprise/pr-attribution How does Claude Code attribute pull requests to users in analytics? https://latestn.com/tool/claude-code/admin-and-enterprise/preinstall-require-plugins How do I pre-install and require plugins for my organization in Claude Code? https://latestn.com/tool/claude-code/admin-and-enterprise/private-marketplace-access How do I grant access to a private Claude Code plugin marketplace for users without a git-host account? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T12:09:40Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-code/admin-and-enterprise/process-wrapper-vs-shell-prefix/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/claude-code/admin-and-enterprise/process-wrapper-vs-shell-prefix POST: https://latestn.com/dispute/tool/claude-code/admin-and-enterprise/process-wrapper-vs-shell-prefix with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-code/admin-and-enterprise/process-wrapper-vs-shell-prefix?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How does CLAUDE_CODE_PROCESS_WRAPPER differ from CLAUDE_CODE_SHELL_PREFIX in Claude Code? Revision 1, last verified 2026-11-20T12:19:52Z. https://latestn.com/tool/claude-code/admin-and-enterprise/process-wrapper-vs-shell-prefix (accessed 2026-11-21T09:55:08Z). @misc{LatestN_tool_claude_code_admin_and_enterprise_process_wrapper_vs_shell_prefix_r1, title = {How does CLAUDE_CODE_PROCESS_WRAPPER differ from CLAUDE_CODE_SHELL_PREFIX in Claude Code?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-code/admin-and-enterprise/process-wrapper-vs-shell-prefix}}, note = {Revision 1; digest sha256:d49c32b16381dfbc; last verified 2026-11-20T12:19:52Z; accessed 2026-11-21T09:55:08Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/claude-code/admin-and-enterprise/process-wrapper-vs-shell-prefix