[FEATURE] Configurable user local binary path
Resolved 💬 3 comments Opened Apr 1, 2026 by deese Closed May 22, 2026
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
On systems with strict AppLocker policies, execution from the default installation directory %USERPROFILE%/.local/bin is frequently blocked by path-based rules. Currently, claude-code defaults to this location, preventing the tool from starting in enterprise or hardened environments.
Proposed Solution
Provide an environment variable (e.g., CLAUDE_BIN_DIR) or a configuration in the settings.json to specify a custom, pre-approved directory that is whitelisted by AppLocker (e.g., /opt/bin or a specific signed path).
Alternative Solutions
_No response_
Priority
Medium - Would be very helpful
Feature Category
Configuration and settings
Use Case Example
- Set an applocker policy that blocks execution from the user home directory
- Run the claude update
- Attempt to run claude from the terminal
- System returns Permission denied or Program cannot be executed due to group policy.
Additional Context
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗