Skip to content

v0.9.1

Choose a tag to compare

@github-actions github-actions released this 23 Oct 14:29
· 660 commits to main since this release
5123422

中文升级与操作指南

2026-10-23 发布的维护版本。 本版更新任务活动界面、修复独立 Cargo 工程漏检,并维护 TLS 和 macOS 依赖。命令授权规则与受保护路径边界没有放宽;WTeam 的支付、企业身份和数据库不随本版部署。

正式版本与下载 · 完整代码差异 · 首次安装 · CLI 与 MCP 参考

更新内容与影响

更新 对使用者的影响
保留任务的状态与 UI/MCP 来源筛选 快速找到已返回的任务,显示匹配数和保留记录数;不冒充完整进程历史。
工作区、会话、任务绑定的刷新与取消 切换到任务 B 后,任务 A 遗留的按钮不能取消 B;迟到回复和已排队的轮询不能覆盖新选择。
独立嵌套 Cargo workspace 发现 显式 [workspace] 和顶层内联 workspace = {} 都保持独立检查范围,不再仅因语言相同而被父工程吞掉。普通成员仍由所属 workspace 覆盖。
TLS 依赖补丁及 macOS 依赖裁剪 更新锁定的 TLS 验证依赖,关闭菜单栏未使用的 X11/Wayland 默认特性,保留原生窗口句柄支持。
跨平台测试隔离 sandbox 测试在新子进程中建立私有状态目录,避免依赖其他测试的运行顺序;生产环境缺失受保护目录时仍拒绝运行。

已安装用户:升级后还要重新连接

先保存正在进行的工作,确认需要保留的任务状态,再在终端执行:

wcode --version
wcode update
wcode --version

wcode update 使用当前安装位置更新,获取的是执行时的最新正式版本,不是固定版本选择器。要精确安装 v0.9.1,使用上面的固定版本下载页并核对校验和。不要添加并不存在的 wcode update --version ... 参数。

升级完成后,重新连接本机 MCP Host,使它重新启动 wcode mcp-stdio。旧 stdio 会话仍运行原来的进程,磁盘上的文件更新不代表当前会话已经升级。独立 TUI/HTTP 服务也需要操作者在确认任务状态后自行重启;安装器不会替你迁移正在执行的任务。

Windows 的更新辅助程序在当前更新进程退出后才替换文件;看到“准备更新”不等于已经完成。辅助程序结束后再检查版本。新启动的终端命令应报告 wcode 0.9.1,但这仍不能单独证明旧服务已重启。

出现不同版本时,Unix 可用 command -v wcode、PowerShell 可用 Get-Command wcode 检查命中的安装位置,再核对 Host 保存的可执行文件路径。不要通过删除权限状态或重新授权全部目录来处理版本问题。

手动下载与完整性核对

平台 归档
Linux x86_64 wcode-linux-x86_64.tar.gz
macOS Apple Silicon wcode-macos-aarch64.tar.gz
macOS Intel wcode-macos-x86_64.tar.gz
macOS 通用包 wcode-macos-universal.tar.gz
Windows x86_64 wcode-windows-x86_64.zip

从同一 v0.9.1 发布页取得对应归档及 SHA256SUMS,计算文件的 SHA-256,与清单中同名文件的完整值比较。例如:

# Linux
sha256sum wcode-linux-x86_64.tar.gz
# macOS Apple Silicon
shasum -a 256 wcode-macos-aarch64.tar.gz
Get-FileHash .\wcode-windows-x86_64.zip -Algorithm SHA256

只有匹配后才解压使用。不匹配时停止,不跳过校验,也不从其他版本借用校验和。本版没有要求删除 .wcode、清空授权记录或修改项目清单;不要把未提交的开发源码覆盖进安装目录。

Jobs:定位、读取与取消任务

在运行中的 TUI 按 W 打开受保护的 Project Status,选中具体工作区,进入**任务活动(Task activity)**中的任务区域。

  1. 点击刷新保留任务(Refresh retained jobs)。该操作读取已存在的任务,不创建新命令。
  2. 组合使用任务状态和 UI/MCP 来源筛选。筛选只作用于本次返回的有界记录;“没有匹配项”不代表没有后台进程或完整历史为空。
  3. 选择准确的 TASK-… ID,检查来源、状态、命令结果、退出码及 stdout/stderr。输出可能有截断或脱敏标记;completed 只表示任务结束,不等于检查成功,更不等于 Acceptance 通过。
  4. 用**刷新精确任务(Refresh exact task)**重新读取所选任务。它不重跑命令。自动观测因页面隐藏、离开任务页或次数上限而暂停后,可用这个入口继续读取。
  5. 只有当前服务端允许取消的 UI 所属运行任务才显示取消按钮。MCP 来源任务可以查看,但不能借这个页面取得它的取消权限。

取消回执不确定时,先刷新同一个任务 ID确认状态,不能因为页面没有及时更新就重复取消或重新执行。切换工作区或会话后,旧按钮与旧请求失效;重新发现当前范围内的任务即可。

检查嵌套 Rust 工程是否被覆盖

本版修复的是“验证计划是否包含独立工程”,不是让所有 Rust 子目录重复运行检查。根 workspace 的普通成员由根检查覆盖;声明为独立 workspace 的嵌套工程有自己的检查范围。

通过 project_context 或 verification_plan 查看实际发现的检查,核对命令所对应的目录;需要完整验收时让 Agent 调用 verify_project,选择 level: "full"。独立工程应出现对应目录的检查,而不仅是父工程的一条成功结果。清单边界改变后应重新发现和验证,不能继续使用旧计划。

[workspace] 与内联 workspace = {} 都是 Cargo 清单的顶层声明;不要把后一种写进 [package] 表,或为了让检查通过而随意改变实际项目关系。

常见问题

现象 处理方式
升级后界面仍旧 核对安装路径和新进程版本;重新连接 Host。独立服务由操作者确认任务状态后重启。
任务发现不可用 保留错误状态,检查连接/会话,重新读取;不要把错误当作空列表。
任务已完成但验证仍阻塞 查看退出码、失败检查、当前代码版本及 Acceptance 要求;任务生命周期不是验收结论。
找不到某个任务 清除筛选并刷新;记录有保留上限和权限范围,不通过猜 ID 或改变归属来访问。
取消按钮没有出现 核对是否 UI 来源、仍在运行且服务端允许取消;不扩大权限来绕过限制。
检查超时或输出不完整 保留 timed_out、output_incomplete 和任务 ID,先读终态与日志,不能用重复启动代替查询。
独立 Rust 工程未出现在计划中 核对实际 Cargo 清单边界及执行目录,再重新发现;保留失败与遗漏信息,不用历史通过兜底。

发布验证与范围

发布标签固定指向 512342287de4b55a989693b574d50f0c6804ce34。候选的 Build 检查、OSS 独立源码包检查和对抗审计均通过;对抗记录为 300/300,真实 WebKit 为 256/256,布局为 12/12。

正式发布与下载验收的 11 个作业通过,覆盖三平台测试、构建、发布,以及对应平台实际下载归档后的版本、帮助、命令目录和隔离 HTTP 启动。macOS 另检查签名和架构。这里的证据仅对应该标签,不能替后来修改过的源码背书。

开发维护仍要求 cargo test --locked、cargo clippy --locked --all-targets -- -D warnings、在线依赖审计和 Design 检查;行为测试使用 Node 24。编码任务从 agent_context 开始;balanced、fast、light 预设保持原有边界,被动检查使用 --read-only --no-exec --no-semantic。

使用 wcode help-all、wcode help-all setup、wcode help-all --json 查看完整命令,而不启动运行时。WTeam 的开发工作、Stripe 配置、真实客户联调及本地未提交改动不包含在此版;发布成功也不表示你的本机服务已自动升级。


English upgrade and operating guide

Maintenance release published on 2026-10-23. This release improves task activity, fixes discovery of independent Cargo projects, and maintains TLS and macOS dependencies. Command authorization and protected-path boundaries are unchanged. WTeam payments, enterprise identity and databases are not deployed with this release.

Release and downloads · Full code comparison · First installation · CLI and MCP reference

Changes and their practical effects

Change What it means for users
Status and UI/MCP-origin filters for retained jobs Find records already returned by the server, with matching and retained counts. This is not a complete process history.
Workspace-, session- and task-bound refresh and cancellation After selecting task B, a callback left over from task A cannot cancel B. Late replies and queued polls cannot replace the new selection.
Independent nested Cargo workspace discovery Both explicit [workspace] and top-level inline workspace = {} tables preserve an independent verification scope. Ordinary members remain covered by their owning workspace.
TLS patches and macOS dependency pruning Update locked TLS verification dependencies and disable unused X11/Wayland default features while retaining native window-handle support.
Cross-platform regression isolation Sandbox tests initialize private state roots in fresh child processes instead of depending on another test's execution order. Missing protected roots still fail closed in production.

Upgrade an existing installation, then reconnect

Save your work and inspect any tasks whose state you need to preserve before running:

wcode --version
wcode update
wcode --version

wcode update uses the current installation location and fetches the latest stable release available when it runs. It is not a pinned-version selector. For exactly v0.9.1, use the fixed release downloads above and verify checksums. Do not add an unsupported wcode update --version ... argument.

After the update completes, reconnect your local MCP Host so it starts a new wcode mcp-stdio process. Existing stdio sessions continue running the old process; replacing a file on disk does not upgrade a live session. A standalone TUI/HTTP service also needs an operator-controlled restart after inspecting active work. The installer does not migrate running tasks for you.

On Windows, the update helper replaces the executable after the current update process exits. A message saying the update is ready is not completion. Check the version after that helper finishes. A newly launched command should report wcode 0.9.1; this alone does not prove an older service has restarted.

When versions differ, use command -v wcode on Unix or Get-Command wcode in PowerShell to identify the executable, then compare it with the path configured in your Host. Do not delete authority state or broadly grant directory access to resolve a version mismatch.

Manual downloads and integrity checks

Platform Archive
Linux x86_64 wcode-linux-x86_64.tar.gz
macOS Apple Silicon wcode-macos-aarch64.tar.gz
macOS Intel wcode-macos-x86_64.tar.gz
macOS universal wcode-macos-universal.tar.gz
Windows x86_64 wcode-windows-x86_64.zip

Download the archive and SHA256SUMS from the same v0.9.1 release. Compute SHA-256 and compare the entire value with the entry for that exact filename:

# Linux
sha256sum wcode-linux-x86_64.tar.gz
# macOS Apple Silicon
shasum -a 256 wcode-macos-aarch64.tar.gz
Get-FileHash .\wcode-windows-x86_64.zip -Algorithm SHA256

Extract and use the archive only after a match. Stop on a mismatch; do not skip validation or borrow checksums from another version. This release does not require deleting .wcode, clearing authorization records or rewriting project manifests. Do not overwrite an installation with unrelated uncommitted development source.

Jobs: find, inspect and cancel a task

Press W in the running TUI to open the protected Project Status, select the relevant workspace, and open the job area under Task activity.

  1. Select Refresh retained jobs. Discovery reads existing records; it does not start a command.
  2. Combine task-state and UI/MCP-origin filters. They affect only the bounded response already loaded. No matching record does not mean there are no background processes or that a complete history is empty.
  3. Select the exact TASK-… ID and inspect origin, status, command outcome, exit code and stdout/stderr. Observe truncation and redaction markers. completed means the task ended, not that checks or Acceptance passed.
  4. Use Refresh exact task to read the selected task again without rerunning its command. This also resumes observation after it pauses because the page is hidden, you leave the activity view, or its polling budget is exhausted.
  5. Cancellation appears only for a running UI-owned job that the server currently permits you to cancel. Viewing an MCP-origin job does not grant cancellation authority over it.

When cancellation is unconfirmed, refresh that same task ID before attempting another cancellation. Do not rerun the command just because a page is slow to update. Workspace or session changes invalidate old controls and replies; discover tasks again within the current scope.

Check coverage of nested Rust projects

This fix concerns whether an independent project appears in the verification plan. It does not run duplicate checks for every Rust directory. Ordinary workspace members are covered by their owning root; a separately declared nested workspace has its own check scope.

Inspect discovered checks with project_context or verification_plan, including the directory attached to each command. Ask the Agent to call verify_project with level: "full" for complete verification. An independent project should have its directory represented rather than relying solely on a successful parent check. Rediscover and rerun after changing manifest boundaries; an older plan is not current evidence.

Both [workspace] and inline workspace = {} are top-level Cargo declarations. Do not put the inline form inside [package] or change the real project relationship merely to obtain a passing result.

Troubleshooting

Symptom Action
The interface still looks old after updating Check the executable path and the new process version, then reconnect the Host. Restart a standalone service only after inspecting active work.
Job discovery is unavailable Keep the error visible, check connectivity/session, and repeat the read. An error is not an empty task list.
A task completed but verification remains blocked Inspect exit code, failed checks, current revision and Acceptance requirements. Task lifecycle is not an acceptance decision.
A task cannot be found Clear filters and refresh. Retention and access are bounded; do not guess identities or change ownership to reach a record.
No cancellation button Check that the task is UI-owned, still running and server-authorized. Do not broaden permissions to bypass that boundary.
A check timed out or output is incomplete Preserve timed_out, output_incomplete and the task ID. Read its terminal state/logs instead of submitting duplicate work as a polling substitute.
A nested Rust project is missing from the plan Inspect its actual Cargo manifest boundary and command directory, then rediscover. Preserve missing/failed results instead of relying on historical success.

Release verification and scope

The release tag points to 512342287de4b55a989693b574d50f0c6804ce34. Its Build checks, OSS standalone checks, and adversarial audit passed. The recorded audit is 300/300, the native WebKit matrix is 256/256, and layout checks are 12/12.

All 11 jobs in the publication and download-verification workflow passed: platform tests, archive builds, publication, and platform-native downloads exercising version, help, command catalog and isolated HTTP startup. macOS additionally checked signatures and architecture. These observations apply to this exact tag, not to later modified source.

Maintainer gates remain cargo test --locked, cargo clippy --locked --all-targets -- -D warnings, current dependency audit and Design checks. Behavior tests use Node 24. Start coding tasks with agent_context; balanced, fast and light retain their boundaries, and passive inspection uses --read-only --no-exec --no-semantic.

Use wcode help-all, wcode help-all setup and wcode help-all --json to discover commands without starting the runtime. WTeam development, Stripe configuration, real customer integrations and unrelated uncommitted changes are outside this release. Publication does not automatically update or restart your local service.