Skip to content

Baize MCP 0.1.3

Choose a tag to compare

View all tags
@github-actions github-actions released this 16 Aug 03:08
· 18 commits to main since this release
v0.1.3
84763e2

Baize MCP v0.1.3

中文

Baize MCP v0.1.3 增加命令计划审批闭环，让 AI 客户端可以在白泽现有账号权限和审批规则范围内申请、查看并提交审批决定，同时继续保持执行前的独立确认。

主要变化

  • 增加命令计划审批申请、分页列表、详情和通过/驳回决策工具。
  • 审批通过只提交当前账号的后端决策；权限、自审批限制、计划快照、过期时间和审计仍由白泽处理，不会因为 MCP 自动获得权限，也不会自动执行计划。
  • 增加分页继续标记，并为工具目录和结构化结果设置 64 KiB 上限，减少异常响应占用 AI 上下文。
  • 改进跨平台 AI 接入升级流程，覆盖 Linux、macOS 和 Windows。
  • 源码构建最低版本更新为 Go 1.25.13，以使用当前标准库安全修复。

兼容性与升级

  • 最低兼容白泽版本：0.2.1。
  • 传输方式：stdio。
  • 支持 Linux、macOS、Windows 的 amd64 与 arm64 发布包。
  • 已安装用户可从此前获取的 baize 公开入口运行 AI 接入升级器。升级会校验发布归档和可执行文件，并保留本机 profile 与系统凭据；升级前退出正在使用 MCP 的 AI 客户端，完成后重新打开客户端。
  • 审批通过后仍需单独确认执行；白泽要求的风险确认、二次确认或其它审批不得绕过。

完整安装和使用说明见 Baize 公开入口 的 AI 接入与远程任务指南。

English

Baize MCP v0.1.3 adds a command-plan approval workflow. AI clients can request, inspect, and submit approval decisions within the signed-in Baize account's existing permissions and approval rules, while execution remains a separate confirmation.

Highlights

  • Added command-plan approval request, paginated listing, detail, and approve/reject decision tools.
  • Approval decisions are submitted to Baize for backend permission checks. MCP does not grant permission locally, bypass self-approval restrictions, ignore snapshot or expiry checks, or execute a plan automatically.
  • Added pagination continuation markers and 64 KiB limits for the tool catalog and structured results to keep abnormal responses from consuming excessive AI context.
  • Improved cross-platform AI access upgrades across Linux, macOS, and Windows.
  • Raised the minimum Go version for source builds to Go 1.25.13 so builds use the current standard-library security fixes.

Compatibility and upgrade

  • Minimum compatible Baize version: 0.2.1.
  • Transport: stdio.
  • Release archives are available for Linux, macOS, and Windows on amd64 and arm64.
  • Existing users can run the AI access upgrader from the previously obtained baize public entry. The upgrader verifies the release archive and executable, and preserves the local profile and operating-system credential store. Close AI clients using MCP before upgrading, then reopen them afterward.
  • Approval does not execute a plan. Keep separate confirmation for execution and follow any risk, secondary, or additional approval requested by Baize.

See the Baize public entry and its AI Access and Remote Task Guide for complete installation and usage instructions.

Assets 11
Loading