Skip to content

LoopX v2.1.0

Pre-release
Pre-release

Choose a tag to compare

View all tags
@loopx-agent loopx-agent released this 22 Oct 17:37
· 683 commits to main since this release
v2.1.0
a65c71f
This commit was signed with the committer’s verified signature.
loopx-agent LoopX Agent
SSH Key Fingerprint: aO+8Qrapjn8hOhHKdX+pKOiFIGoSQzOm9P0UMFcsmOw
Verified
Learn about vigilant mode.

LoopX v2.1.0

Preview — stable publication held: the complete packaged browser checks exposed a reproducible task-history restoration regression. Python/PyPI was not published and the source stable ref was not advanced. The immutable source and preview desktop assets remain available for traceability. A normally versioned 2.1.1 fix is being prepared; installation checks alone do not establish application readiness.
预览，稳定发行暂缓： 完整打包浏览器验收发现可复现的任务历史恢复回归。Python/PyPI 尚未发布，源码 stable 未推进；保留原不可变源码和桌面预览资产。正在准备正常升号的 2.1.1 修复版，安装检查通过不等于应用验收通过。

At a Glance

Illustrated release guide: 个人飞书图解指南 (existing document access applies). The versioned public guide covers the same upgrade and capability boundaries without a Feishu account.

Recover work through its original conversation, keep Goal evidence visible, and produce content through explicitly selected providers. An acknowledgement or completed Todo still does not prove that the original requester received a result.

Upgrade

Let active Bot/Agent Turns finish before applying the update: runtime activation restarts managed status/chat services. Inspect original results and effect evidence before continuing any interrupted request.

loopx update check
loopx update plan
loopx update apply
loopx --version
loopx doctor --deep

Keep the existing installation owner. After PyPI publication is independently verified, new users can install loopx==2.1.0; see Install / Update below. CLI and native App versions are separate readbacks.

Highlights

  • Original conversation recovery: resume the saved native profile and source-bound request; uncertain effects retain their recovery path. Check the original result rather than redispatching the receiver. #6934, #6974, #7015.
  • Visible work: use Quick navigation (Cmd+K / Ctrl+K) to find Goals, tasks and previews. Opening an item navigates without executing it. #6996.
  • Content production: prepare a composition in the Goal conversation, then use Results → Content artifacts. Local rendering and cloud generation require the optional provider and explicit effect approval. #6876, #6979.
  • Less repeated browser confirmation: normal skill refresh delivers bounded recovery of a known missing Agent-owned Ego workspace; human control and unknown-effect stops remain. #7034.
  • Optional native memory: an explicitly selected Nano Turn can restore scoped memory through the separate MemT host. This does not change default models or add memory to Codex/Claude. #7028, #7037.

Replan Fixes

  • Planning and recovery can settle without fabricating a delivery Todo; material path changes retain their evidence. #6999, #6940.
  • Required objective revisions retain acceptance guidance and require each Agent's own adoption. #6987, #7023.
  • Unsafe redispatch after provider failures stops instead of treating an unknown outcome as an empty attempt. #6932, #6885.

Contributors

Release Decision

Who should upgrade: No stable-user upgrade is recommended. Stable users should retain their existing installation. This preview is preserved for traceability while the qualified maintenance release is prepared.

What this release solves: Lost native execution context, unsafe recovery assumptions, incomplete visible handoffs, navigation friction and missing optional content-production paths.

Breaking changes: No. There is no additional persisted-state migration from 2.0.0. Its canonical-authority cutoff remains: unpromoted Markdown Goals and retired legacy ownership require the reviewed migration. Optional providers remain explicit and disabled until configured.

How to verify: Expect loopx 2.1.0, a successful installation doctor and the original Goal/request readback. A running process or receipt alone is insufficient to prove business recovery.

Contributors: Maintained by @huangruiteng, with @cuipengcx90, @mikamikasuki, @hhyykk, @JasonBuildAI, @Twiink, @Zhouyang66639, @songoow and @steven-kid; concrete contributions appear above and below.

loopx --version
loopx doctor --deep
loopx extension doctor --all-enabled --execute

State Kernel & Control Plane

Bot recovery preserves original native profiles, verified text-only rich posts and source-bound handoffs. Busy lanes are visible before dispatch, and the steward work surface exposes unfinished incoming/outgoing requests. Read, adoption, execution and final return remain separate. #6934, #6941, #7015, #7018, #7019.

Native account handoff exposes quota observation, optional switching, restart and force quit. Force quit targets the verified dedicated GPT client after normal quit fails; unrelated owners continue to block switching. Unknown quota is not exhaustion. #7008.

Known limitation: worker source checks are not atomic with final Task completion. Revocation after the last check can still allow a Task commit before the operation reports revocation. Preserve Task/operation/Host evidence; an authorization error does not establish absence of effects or safe replay. #7016, independent race review.

Capabilities & Workflows

Goal requirements and evidence survive individual Todo completion; objective revision and Agent adoption remain separate decisions. The workbench exposes this state and keyboard navigation without granting execution authority. #6784, #6987, #6996, #7023.

Content artifacts connect Agent-authored composition, local rendering, verified downloads and explicit cloud intents. Full-frame composition retains the complete picture and a source strip. Provider installation, credentials, paid submission and publication remain separate opt-ins. #6876, #6979.

Quality & Testing

Release qualification checks the real packaged seams, native Goal prompt budget, canonical provider fixtures, tool subprocess supervision, truncation and exact Goal lifetimes. The native prompt removes duplicate settlement prose while retaining the unchanged host limit and ambiguity stops. #6927, #6943, #6948, #7037.

Exact release source: a65c71f789459c12b68d6feeec233fbb99f65c91, tree 1595c6dd2c48879d0e9cab8844e9df09b64a7bbe, clean package 2.1.0 / tag v2.1.0. The native exact-source reducer reports 8/8 required qualifications complete, no source mismatches or missing checks. Compact qualification receipt.

  • Full unfiltered root suite: 26,879 tests + 2,242 subtests passed, 686 skipped, zero failures/errors; XML total 29,807. Ruff, strict mypy and the TypeScript build pass. The risk-selected canary has 19 selected checks plus six direct checks with no holds; the complete public sweep is 514/514, zero failures/timeouts. The changed-file public boundary scan covers 99 files with zero findings.
  • Fresh wheel installation and an actual PyPI 2.0.0 → 2.1.0 upgrade preserve Todo/artifact data. The optional MemT workflow passes 232 tests, including the real upstream SDK/client/MCP seam and owned process cleanup. Legacy pending/unfinished/orphaned state is held before provider/MCP IO; new-instance, unrelated-scope, stopped-worker recovery and default-off parity are checked. The matched native prompt is 3,628 characters against the unchanged 4,000-character limit.
  • The operator-authorized DeepSeek Flash/high substitution, with an explicit parallel_tool_calls=false request, passes 22 scenarios × 2 repeats, 44 actor runs, 86 HTTP calls and six contrasts, with zero failures/skips. Actual default-facing packets, repetitions, contrasts, tool caps and semantic oracles stay unchanged. This qualifies that configured sample; it does not change a production Bot profile or establish live native-host qualification or a provider-wide serialization guarantee.

Earlier failures remain evidence: two interrupted full-suite runs are not passes; a 12-worker run hit the original three-second Stop bound. The same four Stop combinations then passed independently and in the complete six-worker run without changing that bound. The first public sweep had two failures; their unchanged-contract diagnosis and the complete 514-check pass are retained. An initial same-source model attempt stopped after 11 HTTP calls when a response returned two tool calls to the single-tool host; its incomplete scenarios and contrasts remain failed/unrun. The configured serial-request qualification above is separate and complete.

The native live Goal regression explicitly skipped with required_executable_unavailable in its isolated runner; it is not a live native Goal pass. An earlier b086 host-prompt decision probe passed 19/20 and remains unqualified; it was not real host execution. The optional Nano workflow has CPU/client/stdio regression coverage; real GPU inference, App/Lark integration, Windows strict tool-tree cleanup and outcome/cost benefit remain unqualified. The separate public intake evaluation on an operator-selected DeepSeek Flash/high profile passed 38/56 attempts and failed 18/56, including envelope/parse and routing failures. That profile is not qualified as a Bot default; no production model switch is implied. Full community/steward golden packs remain unqualified. No benchmark or long-horizon improvement is claimed, so an expensive matched outcome baseline was not required.

Benchmarks & Integrations

Research history retains episodes, source citations and quantitative results independently of model judgment. Explicit source/account selection and the original analysis directory own execution, status and cancellation. #6961, #6966, #6968, #7011.

The MemT package supplies a separately selected Nano CLI/provider prerequisite through the public Turn-host seam. It does not install upstream code/weights, grant tools or add native memory to another model. Upstream client/inference code is PolyForm Noncommercial 1.0.0; weights have separate terms. Review licensing before installation or commercial use. #7028, #7037.

Documentation & Compatibility

Versioned upgrade, provider lifecycle and RFC status documentation distinguish accepted design from installed or independently accepted results. Ego skill refresh permits one recorded replacement only after successful inventory confirms a known Agent-owned space is absent; login, human intervention and uncertain-effect stops remain. Desktop preview startup/update errors and owned-service cleanup are clearer. #7034, #7037, #7024, #7029.

No new persisted-state migration is introduced relative to 2.0.0. Follow the 2.0 migration boundary for older authority. This release does not silently promote a Markdown Goal or authorize a second writer.

Community Contributors

Attribution is verified against the v2.0.0 to release-source Git range and merged PR metadata, excluding automated dependency and maintainer/bot accounts. No first-time-contributor claim is made.

Optional Capability Activation & Use

Content media

Activation: From a checkout of v2.1.0, install the separate provider and register its manifest. Existing providers require an explicit package upgrade and loopx extension upgrade --manifest packages/loopx-media/extension.toml --execute.
Validation: Run provider doctor, inspect the admitted composition and verify the original render/download result. Doctor alone does not prove generation.
Disable / rollback: Disable new work with the command below; retain existing operation IDs. Remove framing in a new composition revision to restore editorial framing. Observation stop is not remote cancellation.
Authority boundary: Local render, optional Blender and paid Ark submission have separate prerequisites. Cloud submission requires credential/cost/upload review; ambiguous submissions must not be repeated. Artifacts grant no acceptance or publication permission.
Docs: Versioned provider guide.

git checkout v2.1.0
uv tool install ./packages/loopx-media
loopx extension install --manifest packages/loopx-media/extension.toml --execute
loopx extension doctor loopx-media --execute
loopx extension disable loopx-media --execute

MemT Nano Turn host

Activation: Install the separate package and reviewed upstream client; provision Nano independently. Set enabled=true only in an operator-owned profile outside the task workspace, and explicitly select loopx-memt-turn for an admitted generic-cli Turn with an independent validator.
Validation: The command below is local preflight only; it reports network/inference as unchecked. Real GPU and memory quality remain unqualified.
Disable / rollback: Set enabled=false, remove the explicit host selection and restore the previous host. Uninstalling the adapter does not stop the external server or delete snapshots.
Authority boundary: Memory is advisory, scoped to workspace/Goal lifetime/Agent; current authority and evidence still come from LoopX. MCP scope inputs are not authentication. Unknown effects require reconciliation; no automatic replay. Upstream Noncommercial client/inference and separate weight terms apply.
Docs: Versioned Nano install, licensing and recovery.

Legacy recovery: Before provider or MCP IO, the 2.1.0 host holds the old alias cursor lock and rejects pending, unfinished, orphaned or unreadable legacy state. A new Goal lifetime cannot waive unknown effects. Completed legacy records stay preserved without importing memory. Reconcile the exact old session and effects, stop its worker, then explicitly select a new state directory under the existing recovery procedure; keep the evidence and avoid blind replay.

python3 -m venv .venv-memt
. .venv-memt/bin/activate
python -m pip install -e . -e packages/loopx-memt-turn
loopx-memt-turn --config /srv/operator/memt.json --doctor
# After stopping active work and restoring the prior host:
python -m pip uninstall loopx-memt-turn

Ego browser continuation and optional source reader

Activation: Refresh normal workflow skills for an already installed Ego skill. The source reader separately needs an explicit entry in the actual host's MCP configuration; skill refresh does not enable it.
Validation: Inspect the ego_browser refresh/readback result. A replacement needs successful complete inventory, known identity and a recorded attempt; unknown cause stays unknown.
Disable / rollback: Remove the optional reader's MCP entry and reload an idle host. loopx workflow-skills --uninstall restores an unchanged managed Ego copy to the current upstream link while preserving custom edits; it also removes other unchanged LoopX workflow skills.
Authority boundary: No Ego installation, login, takeover, publishing, source-scope expansion or unknown-effect replay is granted. Human control and refused claims remain stops.
Docs: Versioned lifecycle and origin configuration.

loopx workflow-skills --format json
loopx workflow-skills --install --format json
loopx workflow-skills --format json

Native Codex account handoff

Activation: In Workspace settings → Native Codex accounts, inspect accounts and observed quotas. Explicitly enable automatic switching and, separately, client restart/force quit when wanted.
Validation: Use Check quota and inspect the account/status readback; unknown reads are not exhaustion. Read the running service's identity independently.
Disable / rollback: Turn off Switch automatically when quota runs out; restart and force-quit options can be disabled independently. Retain existing manual account/model selection.
Authority boundary: Force quit targets only the verified dedicated GPT client after normal quit fails. Other CLI/file owners block switching. No credit purchase, reset coupon or submitted-business replay is granted.
Docs: Versioned workspace/account guide.

loopx --version
loopx doctor --deep
loopx dashboard

Research trajectory analysis

Activation: Inspect an authorized source pack and the selected host/account; the command below previews. Add --execute only after reviewing source, model and cost consequences.
Validation: Read status from the original analysis directory and inspect evidence coverage, citations and result boundaries.
Disable / rollback: Leave the preview unexecuted or cancel the original active analysis directory. A failed/uncertain attempt requires original-result readback before explicit retry.
Authority boundary: History/status reads remain model-free. Analysis does not widen source grants, silently switch identity or establish outcome improvement.
Docs: Versioned assessment guide.

loopx benchmark trajectory-assess --input-json evidence-pack.json --output-dir .local/trajectory-analysis --format json
loopx benchmark trajectory-assessment-status --directory .local/trajectory-analysis/KEY --format json
loopx benchmark trajectory-assessment-cancel --directory .local/trajectory-analysis/KEY --format json

Install / Update

Python 3.11+ and Node.js 22.22.3+ are required; Node 24 LTS is recommended. The following pinned install becomes ready after PyPI publication is verified; the build banner above remains authoritative meanwhile.

# v2.1.0 Python/PyPI publication is on hold; retain the current stable install.
loopx workflow-skills --install
loopx --version
loopx doctor --deep

Restart the Agent host after first installing skills. Existing pipx, uv-tool and archive users should keep their installation owner and inspect loopx update check and loopx update plan before loopx update apply. Desktop preview assets and signed-updater artifacts have separate identities. Package checksums and GitHub attestations are acquisition evidence, not a vulnerability-free claim.

中文摘要

图解指南： 个人飞书发布指南沿用当前文档访问权限；无需飞书账号可读公开版本指南。

升级决策

执行升级前，先等活动中的 Bot/Agent Turn 结束：运行时采用会重启受管 status/chat 服务。中断请求须先核对原结果与效果证据，再决定如何继续。

谁需要升级： 暂不建议稳定用户升级。稳定用户保留现有安装；本预览用于保留源码与失败证据，等待修复版完成资格和实际发布。
解决了什么： 保留原生执行上下文、收紧未知效果恢复、显示未回传交办，补齐快速导航和可选内容制作路径。
是否有破坏性变更： 无。从 2.0.0 到本版没有新增持久状态迁移；2.0 的 canonical authority 迁移边界继续有效。可选 provider 不随升级自动启用。
如何验证： 读回 loopx 2.1.0、doctor 和原业务结果；运行中、已读或 Todo done 均不等于原受众收到答复。
贡献者： @huangruiteng 维护；社区贡献来自 @cuipengcx90、@mikamikasuki、@hhyykk、@JasonBuildAI、@Twiink、@Zhouyang66639、@songoow 和 @steven-kid，具体 PR 见社区贡献者。

loopx --version
loopx doctor --deep
loopx extension doctor --all-enabled --execute

状态内核与控制面

原生 profile、富文本原消息和 source-bound 委派保留原上下文；忙碌 lane 与未回传交办可见。自动账号切换、重启、专用客户端强退分别显式启用；额度读取失败不当成耗尽。 #6934、#6941、#7008、#7015、#7018、#7019。

已知限制：最后一次 source 复核后的撤权与 Task 完成不是原子事务，可能先提交 Task，再报告撤权。必须保留 Task、操作与 Host 证据；权限错误不证明没有效果或可安全重放。 #7016、独立竞态审查。

能力与工作流

Goal 要求、证据、目标修订与各 Agent 采用分别保留；无 Todo 的规划可正常结算。快速导航只导航，不执行。Agent 在会话准备分镜，工作台「成果 → 内容作品」制作与查看；大画面保留完整素材和来源栏。provider、付费生成及发布仍分开授权。 #6784、#6987、#6999、#6996、#6876、#6979。

质量与测试

发布验收覆盖安装包公共 seam、原生 Goal 提示长度、canonical fixture、工具进程监督、截断和 Goal lifetime。提示仅删除重复结算文本，原长度上限和未知效果停止规则保留。 #6927、#6943、#7037。

发行源码固定为 a65c71f789459c12b68d6feeec233fbb99f65c91，tree 1595c6dd2c48879d0e9cab8844e9df09b64a7bbe，clean 2.1.0 / v2.1.0；原生精确版本 reducer 确认 8/8 必需资格完成，无源码不匹配或缺项。紧凑资格回执。

  • 完整根测试 26,879 项及 2,242 子测试通过，686 跳过，0 失败/错误；XML 共 29,807 条。Ruff、strict mypy、TypeScript build 通过；风险 canary 为 19 项加 6 个直接检查、无 hold；公开全扫 514/514、无失败/超时；99 个改动文件无公开边界命中。
  • 新 wheel 安装与真实 PyPI 2.0.0 → 2.1.0 升级保留 Todo 和产物；可选 MemT 专用工作流 232 项通过，含真实上游 SDK/client/MCP、进程清理、旧状态调用前阻断、新生命周期/无关 scope/停 worker 恢复及默认关闭一致性。相同输入的原生 prompt 为 3,628 字符，4,000 硬上限未放宽。
  • 本人已授权的 DeepSeek Flash/high 替代 profile，显式请求 parallel_tool_calls=false，完成 22 题各 2 次、44 actor、86 HTTP 调用及 6 组对照，0 失败/跳过；默认-facing packet、重复次数、对照、工具上限和语义 oracle 未变。它只证明该配置下本次完整样本，不切换生产 Bot profile，不算 live 原生宿主资格，也不假定 provider 全局保证串行。

历史失败保留：两次被中断的全量不算通过；12-worker 运行曾触发原三秒 Stop 上限，同一四组合后经独立检查及完整六 worker 全量通过，上限未改。首轮公开 sweep 的两项失败、原标准诊断和完整 514 通过均保留。同源码首轮模型在第 11 个 HTTP 调用返回双工具、触发单工具宿主拒绝，其未完成题和对照继续记为失败/未跑；上方串行请求资格是另一份完整结果。

原生 live Goal 回归在隔离 runner 中因 required_executable_unavailable 明确 skipped，不算原生 Goal 实跑通过；较早 b086 的 host-prompt 决策 probe 为 19/20，仍未资格化，也不是真实宿主执行。单独的 operator DeepSeek Flash/high intake 实测 56 次，38 通过、18 失败，含 envelope/解析和路由问题；该 profile 未获 Bot 默认资格，也未据此切换生产模型。完整社区/管家 golden pack、真实 GPU、MemT App/飞书入口、Windows 严格工具树清理及收益仍未资格化。本版不声明 benchmark 或长程收益，未要求昂贵的匹配 outcome baseline。

基准与集成

研究历程展示原始 episode、引用和定量结果；模型判断不替代原证据。执行/取消沿原分析目录及已选 source/account。MemT 只交付显式选择 Nano 的独立 CLI/provider 前置层，不给 Codex/Claude 加原生记忆，不自动安装上游代码/权重。上游客户端/推理代码采用 PolyForm Noncommercial 1.0.0，权重另有许可，使用前需审阅。 #6961、#6966、#6968、#7028、#7037。

文档与兼容性

Ego 的正常 skill 刷新沉淀一次性丢失恢复：成功 inventory 确认已知自有工作区不存在后可记录一次替代；真人接管、登录、拒绝 claim、未知效果仍停止。桌面更新传输/签名失败和自有服务清理分别可见。2.0 到本版无新增持久状态迁移，旧 authority 仍需原迁移路径，不启动第二 writer。 #7034、#7024、#7029、#7037。

社区贡献者

名单基于 v2.0.0 到本次发布源码及已合并 PR 核验，不声明首次贡献，不把依赖机器人或维护者列为社区贡献者。

可选能力启用与使用

Content media

启用： 在 v2.1.0 checkout 安装独立 provider 并注册 manifest；旧 provider 先升级包，再执行 extension upgrade。
验证： 运行 doctor，读回原分镜、制作结果与校验下载；doctor 不证明生成成功。
停用 / 回退： disable 阻止新工作，旧操作保留原 ID；新修订移除 framing 可恢复原构图。停止观察不等于云端取消。
权限边界： Blender extra 与云凭据独立安装；付费生成先看来源上传、价格和用量，不重放未知提交。产物不授予验收或发布权。
文档： 版本化 provider 指南。

uv tool install ./packages/loopx-media
loopx extension install --manifest packages/loopx-media/extension.toml --execute
loopx extension doctor loopx-media --execute
loopx extension disable loopx-media --execute

MemT Nano Turn host

启用： 独立安装适配包、审阅许可后安装上游客户端，并另行部署 Nano。workspace 外 operator profile 设 enabled=true；只有显式 generic-cli host 选择与独立 validator 才进入该 Turn。
验证： doctor 仅本地前置，明确不检查网络/推理；真实 GPU、记忆质量与收益未资格化。
停用 / 回退： 设 enabled=false，移除后续 host 选择并恢复原 host；卸载不停止外部服务或删除快照。
权限边界： 记忆按 workspace、Goal lifetime、Agent 隔离，仍属未验建议；当前权和证据从 LoopX 读回。MCP 字段不当认证，未知效果先对账。上游客户端/推理 Noncommercial、权重单独许可。
文档： 版本化 Nano 安装、许可和恢复。

旧状态恢复： 2.1.0 在 provider/MCP 调用前持有旧 alias 游标锁，拒绝 pending、未完成、孤立或不可读的旧状态；换 Goal 生命周期也不能绕过未知效果。已完成旧记录保留但不导入记忆。先核对原会话与真实效果、停止原 worker，再按原恢复流程显式选择新状态目录；保留证据，不盲目重放。

python3 -m venv .venv-memt
. .venv-memt/bin/activate
python -m pip install -e . -e packages/loopx-memt-turn
loopx-memt-turn --config /srv/operator/memt.json --doctor

Ego browser continuation and optional source reader

启用： 正常刷新已有 Ego skill；可选 source reader 需在真实 host 的 MCP 配置另行显式添加，技能刷新不会启用 reader。
验证： 读回 ego_browser 状态；替代需完整成功 inventory、已知身份和持久尝试记录，未知原因保持未知。
停用 / 回退： 移除 reader MCP 项并在空闲时重载。workflow-skills --uninstall 会移除未修改的 LoopX skills，并将未修改的受管 Ego 副本恢复到当前上游链接，保留定制内容。
权限边界： 不安装 Ego、不登录/接管、不扩来源或发布权、不重放未知效果；真人控制和 claim 拒绝仍停止。
文档： 版本化生命周期和 origin 配置。

loopx workflow-skills --format json
loopx workflow-skills --install --format json
loopx workflow-skills --format json

Native Codex account handoff

启用： 工作区设置 → 原生 Codex 账号，先检查账号与额度；自动切换、重启、强退分别显式启用。
验证： 点击检查额度并读回账号/状态；读取失败不是耗尽，运行服务身份独立核验。
停用 / 回退： 关闭额度耗尽时自动切换；重启和强退选项可分别关闭，保留原手动账号/模型选择。
权限边界： 正常退出失败后仅强退已核验的专用 GPT 实例，其他 CLI/文件占用仍阻断。不能购买额度、消费重置券或重放已提交业务。
文档： 版本化工作区/账号指南。

loopx --version
loopx doctor --deep
loopx dashboard

Research trajectory analysis

启用： 核验 source pack、所选 host/account 与成本后，先 preview；明确执行才加 --execute。
验证： 沿原分析目录读 status、引用、覆盖与结果边界。
停用 / 回退： 不执行 preview，或取消原目录的活动分析；失败/未知结果先读回，不能静默切身份重试。
权限边界： 历史和状态读取不调用模型，分析不扩大 source grant，也不证明长程收益。
文档： 版本化轨迹分析指南。

loopx benchmark trajectory-assess --input-json evidence-pack.json --output-dir .local/trajectory-analysis --format json
loopx benchmark trajectory-assessment-status --directory .local/trajectory-analysis/KEY --format json
loopx benchmark trajectory-assessment-cancel --directory .local/trajectory-analysis/KEY --format json

发布验证

最终源码、测试和产物身份见上方 Quality & Testing。固定版本 v2.1.0；更新后分别核验 CLI、宿主、原服务和启用扩展。原生桌面仍属预览，构建资产不等于真实 Windows 执行、GPU 或公证资格。历史积压是否自动完成，必须以原 Bot 执行与原消息实际回传为准。

Contributors

hhyykk, huangruiteng, and 7 other contributors
Assets 11
Loading