Repository navigation
v0.3.3
v0.3.3
这一版修复了 cct 在「claude 以脚本形态安装」的电脑上启动失败的问题。当 claude 是 npm 装的
.cmd/.ps1包装脚本、或没有扩展名的 POSIX 脚本时,启动器此前会直接把这些脚本当程序执行而失败(报「%1 不是有效的 Win32 应用程序」)。现在 cct 会先识别 claude 的真实安装形态,再选对启动方式,各种安装方式都能正常进入会话。
This release fixes cct failing to launch on machines where claude is installed as a script. When claude comes as an npm
.cmd/.ps1wrapper script, or as an extensionless POSIX shim, the launcher used to execute the script file directly and fail with "%1 is not a valid Win32 application". cct now detects how claude is actually installed and picks the right runner, so every install shape starts a session correctly.
修复与优化
Fixes and improvements
-
支持 claude 的脚本安装形态:启动器按
claude命令的实际解析结果自动选择启动方式——npm/常见安装的.cmd/.bat经cmd.exe包装执行,.ps1(如claude.ps1)经pwsh执行,.exe保持直接启动以保留交互式终端;找不到配套脚本时回退让命令解析器按扩展名检索。Script-form claude is now supported: the launcher follows how
claudeactually resolves and picks the right runner — npm/common.cmd/.batshims run throughcmd.exe,.ps1(likeclaude.ps1) runs throughpwsh, and.exestays a direct launch to preserve the interactive terminal; when no companion script is found it falls back to letting the command resolver search by extension. -
保留原有交互式终端语义:原生
.exe形态仍直接启动(不经解释器包装),不改变已有的无管道直启(TTY 保持)设计,脚本形态仅做最小必要包装。The original interactive-terminal behavior is preserved: native
.exebuilds are still launched directly (no interpreter wrapper), keeping the existing pipe-free direct-launch (TTY-preserving) design; script shapes only get the minimal wrapper they need.
安装与更新
Installation and update
从 PowerShell Gallery 安装或更新到最新版:
Install or update to the latest version from the PowerShell Gallery:
# 全新安装
# Fresh install
Install-Module -Name ClaudeCodeTask -Scope CurrentUser
# 更新到 0.3.3
# Update to 0.3.3
Update-Module -Name ClaudeCodeTask -Scope CurrentUser -Force更新后若 cct 已在本会话加载,需重开终端(或先
Remove-Module ClaudeCodeTask)再输入cct才会生效。
If cct is already loaded in the session, reopen the terminal (or
Remove-Module ClaudeCodeTask) before typingcctfor the update to take effect.
更多用法见 README 或 cct -h。
More usage details in the README or cct -h.