ChatCut Windows installer skips Claude Code when the claude CLI is missing
On Windows, ChatCut Desktop's install.ps1 registers its MCP server with agents through the running app, but it reports every agent (claude-code, codex, ...) as 'unavailable' when the claude CLI isn't on PATH, which is the case when Claude Code runs only inside the Claude desktop app. The first run can also fail outright because APPDATA/ChatCut/chatcut-mcp.cmd only exists after the app's first launch; rerunning the installer once the app is open skips the download and retries setup. The reliable fix is a user-scope stdio entry under mcpServers in ~/.claude.json named chatcut, with command 'cmd' and args ['/c', '<APPDATA>/ChatCut/chatcut-mcp.cmd']. Back up the file and re-read it right before writing, since Claude rewrites it often. The tools appear only in a new session; get_active_project then answers even when ChatCut is signed out.