Skip to content

CoreMind v1.2.0 ​

Version: 1.2.0 Tag: v1.2.0 Commit: {{RELEASE_COMMIT}}

简体中文 ​

本说明对应 1.2.0 发布线,纳入未独立发布的 1.1 开发成果;公开用户从 1.0.1 直接升级。公开可安装状态与正式资格以同版本、最终提交及准确制品证据为准。

实现与修复 ​

  • 标准 SKILL.md 通过索引与 load_skill 按需加载。Runtime 创建时冻结所选正文,恢复沿用原快照;加载不增加工具权限,既有技能配置保留。

  • /steer、/follow-up 和 SDK 输入控制具有持久回执;接收、应用、消费、丢弃、重复、冲突与拒绝分别表达,应用不等于消费或完成。

  • 支持显式配置的本地 stdio MCP、受控 HTTP MCP、精确资源读取与凭据引用。显式交互认证支持取消、刷新与退出;认证不代替工具授权,凭据不进入模型上下文。本地服务按宿主进程权限执行;Windows 服务启动前绑定专属 Job,关闭未确认全部后代退出时不报告静止。

  • Config v3 可显式启用中英文工具发现;原 Schema 声明、激活与撤回按执行身份隔离,Child Run 不继承父任务的激活。现有 Config v2 和直接工具路径保留。

  • 终端按实际 Run、Agent、步骤和 Call 展示审批、时长、Effect 与受控 Artifact 引用;保留合并输入、粘贴留稿、凭据显示净化和退出收尾。文档导航及主题标题恢复正常渲染。

  • 同一 Session 的写执行使用覆盖历史读取到最终持久化和取消收尾的租约;重叠执行与失效 holder 在模型或工具执行前拒绝。JSONL 损坏尾部仅截去不可恢复尾段,保留有效前缀及本机硬链接身份;中间损坏不会静默丢弃。

  • 最终工具参数须满足完整解析和原 Schema。畸形、缺失或截断结构不会补齐后执行;完整字符串中的可修复转义仍按解析规则处理。模型可收到参数错误后发起新的合法调用,权限与审批保持原门。

  • 请求装配按 Provider/API/模型身份处理历史思考片段,避免将异模型思考转换为可见正文;普通回答、工具调用配对与原 Session 条目保留。同模型签名的本地请求载荷保真不等于外部服务接受该签名。

  • 两类明确的流内网关暂态错误进入有界重试。当前步骤已开始写入、外部副作用或委派时暂停人工核对,避免整步重放;纯读仍可按原预算重试。委派父回执不能证明子任务无副作用,即使子任务只读也保守暂停。未知、配额和认证错误不因此自动重试。

  • 模型因输出长度上限结束时,返回 failed / model_output_limit,保留部分正文与原始停止原因;不报告成功、自动续写或进入后续验证。默认、顺序、显式 Loop 和仅从历史收敛的路径共享该边界;该响应附带的工具调用不执行、不审批。CLI 打印部分正文并失败退出。

  • 依赖身份检查覆盖全部七个内部运行依赖成员,并单独校验消费者安装后的真实依赖图。Worker manifest 记录实际解析版本、锁文件 integrity 及是否确实进入 bundle;wheel 校验其与冻结构建源码的一致性。这不鉴定安装源码被原地篡改的所有情形。

  • FileRunStore 临时锁文件移除冗余同步;完整 owner 原子发布、关键事实同步与取消静止保证保留。

  • 自定义端点认证: 允许自定义兼容端点明确使用免 key 或仅 Header 认证;显式凭据引用缺失时仍拒绝,不降级匿名。内置 Provider 与原生入口的凭据要求不放宽。

  • 输出背压: CLI 非 Ink 文本输出与 Worker stdio 使用有界编码队列,关键响应交付失败可辨识,并在关闭时等待已接收工作收尾。预算不代表模型生成、瞬间序列化、终端绘制或整个进程内存上限。

  • 重复 Agent/Step/Call 身份在当前 Run 及同 Run 恢复中拒绝再次准入,保留首次事实和绑定;合法的新身份仍可执行。此修复及内部观测错误类型保真已合并并通过双平台 CI。

  • 日志处理成本: 缓存已成功发布的规范关键前缀,仍完整读取并精确比较原文字符串;只减少命中时的历史解析与序列化。完整读取、全量临时文件写入、同步与原子发布保持,不承诺生产速度或百分比收益。

  • Python 通知消费: sync/async drain_notifications() 原子取走并清空全部四类已接收通知。默认保留行为不变;该操作不是服务端确认、不处理工具或验收,也不推进持久事件游标。

  • 项目脚本加载信任: 配置驱动脚本工具 import 前要求宿主显式同意。CLI 非交互运行须显式 opt-in;TypeScript 使用加载决定回调,Python 使用严格布尔参数及匹配 Worker 能力。加载同意与工具授权分离,模块及依赖仍按宿主权限执行。

  • 终端编辑: 支持字素边界上的光标移动、中段编辑与最多 50 条当前界面内的用户输入历史;恢复草稿、审批冻结和整段脱敏保持隔离。历史不持久化,也不是完整编辑器或输入法兼容认证。

  • 黄金示例文档生成器保留验证修复示例的手工定制材料,不再用通用模板覆盖;五示例索引和其余示例的原生成路径保留。

  • 修复正常拒绝项目脚本后的 SDK 关闭:仅对入口检查完成且尚未创建 Runtime 的明确拒绝保留原静止状态;读取或工厂失败,以及此前未静止的执行状态,仍按原保守规则处理。

升级、限制与回滚 ​

从 1.0.1 直接升级,见中文迁移指南。停止旧进程并备份持久状态;全部 CoreMind npm 包、Python SDK 与随包 Worker 使用同一发布版本。Config v2、Protocol v1/v2 与既有会话保持支持;新能力按能力协商与 v2 Schema 指纹使用,旧 Worker 忽略未知字段不算支持。

Node.js 要求 22.19 或以上,Python 要求 3.10 或以上。Session 租约依赖支持硬链接的本机文件系统,不提供多机分布式锁。项目脚本信任、MCP 认证与技能加载均不放宽既有路径、网络、凭据、Child 或恢复门。不新增托管 API、多租户服务、纯 Python Runtime、durable detach、LSP 或 macOS 正式支持。

回滚时停止全部新进程,将程序、SDK 与 Worker 一起退回 1.0.1,恢复升级前状态备份。不要让新旧程序同时写同一 Session,不盲目重放外部副作用;回滚本地状态不撤销已经发生的外部操作。

发布资格与验证边界 ​

正式发布必须完成绑定同版本、最终提交和准确制品的严格 Provider、Windows/Linux 全量工程与稳定性、覆盖率、真实 PTY、公开下载及安装复验。受控 HTTP/认证/MCP 夹具不替代实际外部服务互通认证。Windows MCP 使用固定 Job 资产及薄启动器,保留原 15 秒调用和 60 秒连接门禁。

实际外部 OAuth/MCP 互通与整体性能尚未认证。

最终资格须绑定最终提交、版本、Runtime/Worker 与准确产物,见对应发布运行、release-manifest.json 和 SHA256SUMS.txt;旧版本证据不能代替。真实依赖与许可证义务继续保留,见目标发布标签的第三方声明和许可证;该标签须在实际发布时存在。

English ​

These notes describe the 1.2.0 release line, including unpublished 1.1 development. Public users upgrade directly from 1.0.1. Public installability and formal qualification require evidence for the same version, final commit, and exact artifacts.

Features and fixes ​

  • Standard SKILL.md files expose an index and on-demand load_skill. Runtime creation freezes selected bodies and recovery uses the original snapshot. Loading grants no tool authority; existing Skill configuration remains supported.

  • /steer, /follow-up, and SDK input controls have durable receipts. Acceptance, application, consumption, discard, duplicate, conflict, and rejection remain distinct; application is not consumption or completion.

  • Support explicitly configured local stdio MCP, controlled HTTP MCP, exact resource reads, and credential references. Explicit interactive authentication supports cancellation, refresh, and logout without replacing tool authorization or exposing credentials to model context. Local servers execute with host process authority. Windows servers join a dedicated Job before execution; unconfirmed descendant cleanup never reports quiescence.

  • Config v3 explicitly enables Chinese and English tool discovery. Original Schema declarations, activations, and withdrawals remain isolated per execution; Child Runs inherit no parent activations. Existing Config v2 and direct tools remain supported.

  • The terminal correlates approvals, durations, Effects, and controlled Artifact references by actual Run, Agent, step, and Call. Coalesced input, paste-as-draft, credential redaction, and exit settlement retain their boundaries. Documentation navigation and theme titles render correctly.

  • Session write execution holds a lease from history reads through final persistence and cancellation settlement. Overlap and stale holders reject before model or tool execution. JSONL tail recovery preserves the valid prefix and local hard-link identity; middle corruption is not silently discarded.

  • Final tool arguments require complete parsing and the original Schema. Malformed, missing, or truncated structure is not completed into an executable call; repairable escapes within complete strings retain the parser's rules. A model may receive the argument error and make a fresh valid call under the original permission and approval gates.

  • Request assembly handles historical thinking by Provider/API/model identity, avoiding conversion of foreign-model thinking into visible text. Ordinary answers, tool-call pairing, and original Session entries remain intact. Same-model signature fidelity in local request payloads does not certify external acceptance of a signature.

  • Two explicit in-stream gateway transient errors use bounded retries. A step that started a write, external effect, or delegation pauses for human reconciliation rather than replaying the whole step. Pure reads retain bounded retry. Parent delegation receipts do not prove that children had no effects; even a read-only child conservatively pauses replay. Unknown, quota, and authentication errors do not gain automatic retries.

  • Model output-length termination returns failed / model_output_limit, retaining partial text and the original stop reason. It does not succeed, continue automatically, or enter follow-up verification. Default, sequential, explicit Loop, and history-only settlement paths share the boundary; tool calls attached to that response are neither executed nor approved. The CLI prints partial text and exits unsuccessfully.

  • Dependency identity checks cover all seven internal runtime dependency members and separately validate a consumer's installed graph. Worker manifests record resolved versions, lockfile integrity, and actual bundle participation; wheel checks compare this metadata with frozen build sources. This does not independently attest to every in-place modification of installed source files.

  • FileRunStore removes redundant temporary-lock synchronization while preserving complete atomic owners, critical Fact synchronization, and cancellation quiescence.

  • Custom endpoint authentication: allow custom compatible endpoints to use no key or Header-only authentication while rejecting missing explicit credential references without anonymous fallback. Built-in and native Provider credential requirements remain intact.

  • Output backpressure: bound encoded queues for non-Ink CLI text output and Worker stdio, identify critical delivery failures, and join accepted work during shutdown. This does not cap model generation, transient serialization, terminal rendering, or total process memory.

  • Repeated complete Agent/Step/Call identities reject readmission within a Run and same-Run recovery, preserving the first facts and binding; valid new identities remain usable. This fix and typed internal-observation failures have merged and passed both-platform CI.

  • Journal processing: cache successfully published canonical critical prefixes while continuing to read and exactly compare the complete text. Hits reduce historical parsing and serialization only; complete reads, full temporary rewrites, synchronization, and atomic publication remain. No production speed or percentage gain is claimed.

  • Python notification consumption: sync/async drain_notifications() atomically takes and clears all four received-notification buckets. Default retention remains unchanged. Draining is not a server acknowledgement, tool or verification response, or durable-cursor advancement.

  • Project script loading trust: require an explicit host decision before configuration-driven script-tool imports. Noninteractive CLI execution opts in explicitly; TypeScript uses a loading decision callback, and Python uses a strict boolean option with matching Worker capability. Loading trust and tool authority stay separate; project modules and dependencies execute with host authority.

  • Terminal editing: move and edit at grapheme boundaries, with at most 50 admitted user entries in the current interface. Draft restoration, approval freezing, and whole-text redaction remain isolated. History is not persisted; this is not a full editor or input-method certification.

  • The golden-example documentation generator preserves the verification-repair example's hand-maintained materials instead of overwriting them with generic templates; the five-example index and other generation paths remain intact.

  • Fix SDK shutdown after an ordinary project-script denial: preserve the prior quiescent state only when entry inspection has completed and the Runtime has not been created. Read or factory failures and a previously unsettled execution state retain conservative handling.

Upgrade, limits, and rollback ​

Upgrade directly from 1.0.1 using the English migration guide. Stop old processes and back up persistent state. Keep all CoreMind npm packages, the Python SDK, and bundled Worker on the same release. Config v2, Protocol v1/v2, and existing Sessions remain supported; new capabilities require negotiation and matching v2 Schema fingerprints. Ignored unknown fields do not establish older Worker support.

Node.js 22.19+ and Python 3.10+ are required. Session leases require a hard-link-capable local filesystem, not a multi-host distributed lock. Script trust, MCP authentication, and Skill loading grant no additional path, network, credential, Child, or recovery authority. This release does not add a hosted API, multi-tenant service, pure Python Runtime, durable detach, LSP, or official macOS support.

To roll back, stop all new processes, restore programs, SDKs, and Worker together to 1.0.1, and restore the pre-upgrade state backup. Never let different versions write the same Session concurrently or blindly replay external effects. Restoring local state does not reverse external operations.

Release qualification and validation boundaries ​

Formal publication requires strict Provider, Windows/Linux full engineering and stability, coverage, real PTY, public download, and reinstall evidence for the same version, final commit, and exact artifacts. Controlled HTTP, authentication, and MCP fixtures do not replace external interoperability certification. Windows MCP uses fixed Job assets and a thin launcher while retaining the original 15-second call and 60-second connection gates.

External OAuth/MCP interoperability and overall performance are not certified.

Final evidence must bind the final commit, version, Runtime/Worker, and exact artifacts. Consult the release runs, release-manifest.json, and SHA256SUMS.txt; older qualification is insufficient. Actual dependency and license obligations remain intact; see the target tag's third-party notices and license. That tag must exist at actual publication.

Last updated:

Released under the MIT License.