CC Port v0.5.2 Public Beta
Pre-releaseCC Port v0.5.2 Public Beta
CC Port v0.5.2 增加 Cursor 原生 Prompt 命令支持,并收紧远端快照与文件式
资源的所有权边界。已有自定义平台的 Prompt 目标不会被静默迁移,私有资源仓库的
Prompt 存储路径保持不变。
下载
cc-port_0.5.2_windows_x64_setup.exeSHA256SUMS.txt
下载后请先核对 SHA-256,再运行安装器。不要下载或单独运行需要 sidecar 的
原始桌面 EXE。
主要变化
- Cursor 预设现在把 Prompt 安装为全局自定义命令
~/.cursor/commands/<install-name>.md,并支持扫描、上传、下载和安装别名。 - 平台配置增加
prompts_dir。自定义平台未设置该字段时,继续使用原有的
rules_dir/<install-name>目标,不迁移现有配置。 - 私有资源仓库仍以
prompts/<name>/保存 Prompt。文件式目标只接受单个 Markdown
文件,或目录根级恰好包含一个非符号链接.md文件的载荷;歧义载荷会在计划
阶段阻断。 - CC Port 的内部 Git 工作树关闭宿主
core.autocrlf并重写检出,避免相同的
Cursor Prompt 被错误标记为content-different。仓库自身的.gitattributes
和 clean/smudge filter 仍保持 Git 原生优先级。 - 文件式 Prompt 使用稳定的邻接 ownership sidecar;目标暂时是同名目录或操作失败
时,内容与 sidecar 会纳入同一事务进行验证和回滚。
安全与隐私
- 远端资源快照不再复制或跟随内部格式标记符号链接,格式标记改为同目录原子替换。
- 快照中的
registry.yaml必须是普通非符号链接文件;资源路径规范化后必须仍位于
快照内,且路径组件不得包含符号链接。违反任一条件时会拒绝读取或安装。 - ownership marker 改为同目录原子替换;文件式 Prompt 下载完成前会重新验证完整
resource_keyownership,marker 未持久化时回滚内容与 sidecar。
Public Beta 限制
- 安装器尚未做 Authenticode 签名。Windows SmartScreen 可能显示“未知发布者”;
请核对下载域名和SHA256SUMS.txt后,通过“更多信息”继续。 - 受企业策略管理且禁止运行未签名应用的电脑不在当前支持范围。
- 当前没有自动更新。
- 仅正式提供 Windows 10/11 x64 桌面安装器。
- Windsurf 和 OpenCode 平台预设仍标记为实验性。
升级
关闭正在执行的写操作后,直接运行 v0.5.2 安装器覆盖升级。保留本机状态目录
可以继续使用操作历史、所有权信息和备份。
反馈与安全问题
- 一般 Bug 和功能建议:GitHub Issues
- 安装与同步问题:故障排查
- 安全漏洞:使用仓库 Security 页面的私密漏洞报告,不要创建公开 Issue
CC Port v0.5.2 Public Beta
CC Port v0.5.2 adds native Cursor Prompt commands and tightens ownership
boundaries for remote snapshots and file-style resources. Existing custom
platform Prompt targets are not silently migrated, and Prompt storage in the
private resource repository remains unchanged.
Downloads
cc-port_0.5.2_windows_x64_setup.exeSHA256SUMS.txt
Verify the SHA-256 before running the installer. Do not download or run the raw
desktop executable separately because it requires its packaged sidecar.
Changes
- The Cursor preset now installs Prompts as global custom commands at
~/.cursor/commands/<install-name>.md, with scanning, upload, download, and
install-alias support. - Platform configuration adds
prompts_dir. Custom platforms without this
field continue to use the existingrules_dir/<install-name>target and are
not migrated. - The private resource repository continues to store Prompts under
prompts/<name>/. A file-style target accepts either one Markdown file or a
directory with exactly one non-symlink root-level.mdfile; ambiguous
payloads block the operation plan. - CC Port disables the host
core.autocrlfsetting in internal Git worktrees
and rewrites the checkout, preventing identical Cursor Prompts from being
reported ascontent-different. Repository.gitattributesand clean/smudge
filters keep their native Git precedence. - File-style Prompts use a stable adjacent ownership sidecar. Content and the
sidecar participate in the same verification and rollback transaction when
the target is temporarily a same-name directory or an operation fails.
Security and privacy
- Remote resource snapshots no longer copy or follow a symlink at the reserved
internal format marker, and the marker is replaced atomically in its own
directory. - Snapshot
registry.yamlmust be a regular non-symlink file. Normalized
resource paths must remain inside the snapshot and contain no symlink
components; any violation blocks reading or installation. - Ownership markers are replaced atomically in their own directories.
File-style Prompt downloads revalidate the fullresource_keyownership
before completion and roll back content and the sidecar if the marker is not
persisted.
Public Beta limitations
- The installer is not Authenticode-signed. Windows SmartScreen may show an
unknown-publisher warning; verify the download domain andSHA256SUMS.txt,
then use More info to continue. - Managed enterprise computers that prohibit unsigned applications are outside
the current support scope. - Automatic updates are unavailable.
- Windows 10/11 x64 is the only officially distributed desktop platform.
- Windsurf and OpenCode presets remain experimental.
Upgrade
Finish any active write operation, then run the v0.5.2 installer over the
current installation. Keep the local state directory to preserve operation
history, ownership data, and backups.
Feedback and security
- General bugs and feature requests: GitHub Issues
- Installation and sync help: Troubleshooting
- Security vulnerabilities: use private vulnerability reporting on the
repository's Security page; do not open a public issue.