[Bug] Update 1.1.7714 broke Claude Code desktop app — ccd-cli passes --allow-dangerously-skip-permissions as root + Hyper-V not initializing on Windows

Environment

| | |
|---|---|
| Desktop app version | 1.1.7714 |
| Claude Code CLI | v2.1.81 |
| Machines affected | Mac mini + Windows 11 |
| Remote server | Proxmox (SSH, running as root) |
| Working directory | /tank/proxmox-data/code/nero |

---

Summary

After updating the Claude desktop app to 1.1.7714, Claude Code stopped working entirely on both Mac and Windows. Two completely separate root causes were found.

---

Bug 1 — ccd-cli passes --allow-dangerously-skip-permissions when running as root (Mac + SSH)

Symptoms

• Claude Code appears to connect but never becomes interactive — just hangs silently
• No error shown in the desktop app UI
• Claude Code CLI works perfectly when run directly from terminal on the same server
• Logs show the session starting and immediately dying

Root Cause

The desktop app deploys its own ccd-cli binary to /root/.claude/remote/ccd-cli on the remote server. The bundled binary (v2.1.78 shipped with 1.1.7714) invokes Claude with the flag:

--allow-dangerously-skip-permissions

Claude Code explicitly refuses to start with this flag when running as root — it is a security guardrail. Since the remote server runs as root, every session silently exits immediately after launch.

This is a regression. The previous version of ccd-cli did not pass this flag.

Workaround Applied

Replaced /root/.claude/remote/ccd-cli with a bash wrapper that strips the bad flags before passing arguments to the real Claude script:

#!/bin/bash
export PATH=/root/.nvm/versions/node/v24.14.0/bin:$PATH
ARGS=()
for arg in "$@"; do
    [[ "$arg" == "--dangerously-skip-permissions" ]] && continue
    [[ "$arg" == "--allow-dangerously-skip-permissions" ]] && continue
    ARGS+=("$arg")
done
exec /root/.nvm/versions/node/v24.14.0/bin/node /root/.claude/remote/ccd-cli.js "${ARGS[@]}"

Additionally applied chattr +i to prevent the app from overwriting the wrapper on reconnect — since the app auto-redeploys ccd-cli on each connection and would otherwise restore the broken binary.

---

Bug 2 — HCS operation failed: HRESULT 0x80070005 (Access Denied) on Windows

Symptoms

Hard error immediately when attempting to open any Claude Code session on Windows:

HCS operation failed: HRESULT 0x80070005 (Access Denied)

Root Cause

The desktop app attempts to spin up a local Hyper-V virtual machine to run Claude Code. Hyper-V and Windows Hypervisor Platform were not enabled on the machine.

It is unclear whether update 1.1.7714 introduced a new dependency on Hyper-V, or whether this was always required and not previously documented. There was no error or warning prior to this update.

Fix Applied

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All -NoRestart
Enable-WindowsOptionalFeature -Online -FeatureName HypervisorPlatform -NoRestart
# Reboot required

Claude Code on Windows worked immediately after reboot.

---

What We Tried (Chronological)

1. Restarting the desktop app and reconnecting — no effect
2. Verified Claude Code CLI works directly from terminal on Proxmox — confirmed the CLI itself is not broken
3. Inspected the deployed ccd-cli binary — discovered it was passing --allow-dangerously-skip-permissions
4. Tested running ccd-cli manually without the bad flag — Claude Code launched successfully, confirming the flag as the culprit
5. Tried updating ccd-cli-version file to force a re-download — app re-downloaded the same broken binary
6. Replaced ccd-cli with a bash wrapper stripping the bad flags — this worked
7. Diagnosed Windows 0x80070005 error — traced to Hyper-V not being enabled
8. Enabled Hyper-V features and rebooted — Windows fixed
9. Applied chattr +i to lock the wrapper and prevent it being overwritten on reconnect

---

Requested Fix

1. Bug 1: Remove --allow-dangerously-skip-permissions / --dangerously-skip-permissions from the flags passed by ccd-cli when the remote user is root — or handle the root case explicitly
2. Bug 2: Surface a clear error message (or setup guide) when Hyper-V is not enabled on Windows, rather than a raw HCS HRESULT error with no context

---

Full Detailed Report

A complete HTML report with full timeline, all attempted fixes, backup locations, and step-by-step recovery procedures is available here:
https://irishman19.github.io/claude-code-bug-fix/

---

Reproduced and debugged across two machines (Mac mini + Windows 11) with a shared Proxmox remote server. Happy to provide additional logs or information if helpful.