Computer Use is useful when explicitly needed, but exposing its MCP tools by default creates unnecessary desktop-control surface for users who want coding-only sessions. This adds a shared disable path for CLI flags, environment, and desktop settings while keeping preauthorized app state in one config file. The same change also preserves Windows and WSL shell startup behavior by applying the MSYS argument-conversion guard only on WSL-bound launches. Constraint: Computer Use MCP must not be exposed to the Coding Agent when disabled Constraint: Desktop settings and CLI sessions need to read the same persisted Computer Use config Rejected: Environment-only disable switch | desktop users need a persistent Settings control Rejected: Remove Computer Use setup entirely | enabled sessions still need the existing built-in MCP path Confidence: high Scope-risk: moderate Directive: Keep every new Computer Use entrypoint wired through loadStoredComputerUseConfig or the CLI disable flag before adding MCP tools Tested: bun test src/utils/computerUse/gates.test.ts src/utils/computerUse/preauthorizedConfig.test.ts src/server/__tests__/computer-use-api.test.ts src/utils/shell/wslInterop.test.ts desktop/src/pages/ComputerUseSettings.test.tsx Tested: bun run check:server; bun run check:desktop; bun run check:docs; bun run check:policy; bun run check:native; git diff --check Tested: SKIP_INSTALL=1 ./desktop/scripts/build-macos-arm64.sh; codesign verify; hdiutil verify; built CLI Computer Use E2E exposure and disable checks Not-tested: Full screenshot/control action after granting macOS Screen Recording permission on this machine
1.7 KiB
Global Usage (Run from Any Directory)
If you want to run claude-haha directly from any project directory, set up one of the following. Once configured, claude-haha will automatically recognize your current working directory.
macOS / Linux
Add to ~/.bashrc or ~/.zshrc:
# Option 1: Add to PATH (recommended)
export PATH="$HOME/path/to/claude-code-haha/bin:$PATH"
# Option 2: Alias
alias claude-haha="$HOME/path/to/claude-code-haha/bin/claude-haha"
Then reload the config:
source ~/.bashrc # or source ~/.zshrc
Windows (Git Bash)
Add to ~/.bashrc:
export PATH="$HOME/path/to/claude-code-haha/bin:$PATH"
Windows + WSL Toolchains
If claude-haha runs on Windows / Git Bash but tools such as Node, Python, uv, or bun are installed inside WSL, call them through WSL explicitly:
wsl -e bash -lc 'node --version && python3 --version'
When cc-haha detects wsl / wsl.exe, it automatically sets MSYS2_ARG_CONV_EXCL=* so Git Bash does not rewrite WSL paths such as /home/... into C:/Program Files/Git/home/....
To route Bash tool commands through WSL by default, set this before startup:
export CLAUDE_CODE_SHELL_PREFIX='wsl -e bash -lc'
Computer Use still controls Windows desktop apps. CLI tools running inside WSL do not need to be added to computer-use-config.json. If you only need the WSL toolchain and do not need desktop control, disable Computer Use with --no-computer-use or the Settings > Computer Use switch.
Verify
After setup, navigate to any project directory and test:
cd ~/your-other-project
claude-haha
# Ask "What is the current directory?" — it should show ~/your-other-project