diff --git a/README.md b/README.md index 6138564f90..6bc7b2b363 100644 --- a/README.md +++ b/README.md @@ -6,18 +6,18 @@ For enterprise teams, research organizations, and independent builders.
Coordinate agents around complex research goals, preserve decisions and evidence across sessions, inspect outcomes and costs, and carry findings into the next step. Open source and local first, with support for Codex, Claude Code, DeepSeek Harness, and other supported runtimes.
-2.0 development preview · the installation below follows the latest stable release. +TypeScript control plane · evidence-bound research · recoverable agent collaboration -[![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE) [![Release](https://img.shields.io/badge/releases-GitHub-181717)](https://github.com/loopx-project/loopx/releases/latest) [![GitHub contributors](https://img.shields.io/badge/contributors-GitHub-181717)](https://github.com/loopx-project/loopx/graphs/contributors) [![Discord](https://img.shields.io/badge/Discord-Join-5865F2?logo=discord&logoColor=white)](https://discord.gg/XmGgQyCFZd) [![TypeScript core](https://img.shields.io/badge/core-TypeScript-3178C6?logo=typescript&logoColor=white)](docs/architecture/rfcs/typescript-control-plane-migration-v0.md) [![Python](https://img.shields.io/badge/python-3.11%2B-blue.svg)](pyproject.toml) [![Local first](https://img.shields.io/badge/control--plane-local--first-brightgreen.svg)](docs/public-private-boundary.md) [![Loop Agents](https://img.shields.io/badge/status-loop%20agents%20supported-brightgreen.svg)](docs/product/release-readiness.md) +[![Release](https://img.shields.io/github/v/release/loopx-project/loopx?color=181717)](https://github.com/loopx-project/loopx/releases/latest) [![License](https://img.shields.io/badge/license-Apache--2.0-181717)](LICENSE) [![TypeScript core](https://img.shields.io/badge/core-TypeScript-3178C6?logo=typescript&logoColor=white)](docs/architecture/rfcs/typescript-control-plane-migration-v0.md) [![Discord](https://img.shields.io/badge/Discord-Join-5865F2?logo=discord&logoColor=white)](https://discord.gg/XmGgQyCFZd) loopx-project/loopx on Trendshift -[Get started](#try-loopx) · [Workspace](#meet-the-personal-agent-workspace) · [LHTB results](#lhtb-results) · [Docs](https://loopx-project.github.io/loopx/docs/) · [简体中文](README.zh-CN.md) +[Get started](#try-loopx) · [2.0 upgrade guide](docs/product/releases/v2.0.0.md) · [Research workbench](#research-workbench) · [LHTB results](#lhtb-results) · [Docs](https://loopx-project.github.io/loopx/docs/) · [简体中文](README.zh-CN.md) LoopX 2.0, the long-horizon research workbench for enterprise teams, research organizations and independent builders; recorded research history with count ribbons redrawn to scale in a labelled App frame
Watch the research-workbench film · 86s · transcripts, subtitles and sources. Recorded App excerpts, synthetic examples and illustrations are labelled. -**Start in Codex App in two steps.** Install once: +**Start in Codex App in two steps.** Python 3.11+ and Node.js 22.22.3+ are required (Node 24 LTS recommended). Install once: ```bash python3 -m pip install --upgrade loopx && loopx workflow-skills --install @@ -52,6 +52,30 @@ accepted, and when to ask you. | Manage personal projects, schedules and decisions in one place | [Personal Agent Workspace](#meet-the-personal-agent-workspace) | | Let agents collaborate and deliver verifiable results | [Agent collaboration guide](docs/product/use-cases/cross-runtime/README.md) | +## LoopX 2.0 + +| A shared control plane | A long-horizon research workbench | +| --- | --- | +| TypeScript owns the migrated transactions, authority and recovery rules. Python retains real host/provider IO and specialized computation. | Follow a research question through delegated work, Explore history, artifacts, trajectory analysis and the next decision. | +| [Two months of engineering, source history and core statistics](https://loopx-project.github.io/loopx/blog/typescript-control-plane-refactor/) | [Watch the 86-second film](https://github.com/user-attachments/assets/543af0b1-c3d4-4cfb-aedd-a68563a20601) · [Read the analysis contract](docs/reference/trajectory-assessment.md) | + +**Upgrading from 1.x?** 2.0 retires ordinary writes to unpromoted Markdown Goals. +Review the [migration and recovery guide](docs/product/releases/v2.0.0.md) before +continuing those Goals. Installation does not silently convert existing state. + + + +## Research that can continue + +Open a Goal to inspect its work, responsible Agents and recorded Explore history. +Use **Deep analysis** to inspect a registered trajectory, its citations, native +outcome readback and separately measured costs. An Agent prepares the source; +opening a page or reading a result does not start a model call. Explicit analysis +uses the configured host and account. + +Keep supported, refuted and unknown findings visible. Inspect why an approach +changed or continued, then carry the evidence into the next attempt. + ## Meet the Personal Agent Workspace Keep long-horizon goals in one local-first workspace. Goals, attention, @@ -59,7 +83,7 @@ conversations, tasks, files, schedules, and recovery stay durable across days, restarts, and harnesses. Reopen a project, inspect the previous turn’s state and evidence, and continue the next permitted action. -LoopX 1.0 brings these long-horizon control states into the Personal Workspace. It gives you one place to: +LoopX brings these long-horizon control states into the Personal Workspace. It gives you one place to: - see what needs you, what is running, what is being watched, and what is scheduled or stopped; @@ -82,7 +106,7 @@ loopx dashboard ``` `loopx dashboard` is the supported browser/PWA launch path. You can also download -native desktop previews from the [1.0 release](https://github.com/loopx-project/loopx/releases/tag/v1.0.0); +native desktop previews from the [current release](https://github.com/loopx-project/loopx/releases/latest); they reuse the same loopback services and Goal state. Apple Silicon macOS supports signed App updates that pair the shell with its bundled runtime, plus repair and recovery. Python 3.11+ is required; the App is ad-hoc signed, not notarized. @@ -783,7 +807,7 @@ traces, credentials, private logs, or operator artifacts. ## Current Status -LoopX 1.0 is a usable local control plane for long-running agent work and is +LoopX is a usable local control plane for long-running agent work and is entering broader adoption. It is not a full agent platform, an agent runtime, or an autonomous production controller. diff --git a/README.zh-CN.md b/README.zh-CN.md index 5651a74af6..cd0e680552 100644 --- a/README.zh-CN.md +++ b/README.zh-CN.md @@ -6,18 +6,18 @@ 面向企业、研究机构与超级个体。
围绕复杂研究目标，协调多个 Agent 持续推进，跨会话保留研究过程、决策与证据，检查结果和成本，并将发现用于下一步工作。开源、本地优先，连接 Codex、Claude Code、DeepSeek Harness 等已有运行时。
-2.0 开发预览 · 下方安装命令仍跟随最新稳定版。 +TypeScript 控制面 · 有证据的研究 · 可恢复的 Agent 协作 -[![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE) [![Release](https://img.shields.io/badge/releases-GitHub-181717)](https://github.com/loopx-project/loopx/releases/latest) [![GitHub 贡献者](https://img.shields.io/badge/contributors-GitHub-181717)](https://github.com/loopx-project/loopx/graphs/contributors) [![Discord](https://img.shields.io/badge/Discord-Join-5865F2?logo=discord&logoColor=white)](https://discord.gg/XmGgQyCFZd) [![TypeScript core](https://img.shields.io/badge/core-TypeScript-3178C6?logo=typescript&logoColor=white)](docs/architecture/rfcs/typescript-control-plane-migration-v0.zh-CN.md) [![Python](https://img.shields.io/badge/python-3.11%2B-blue.svg)](pyproject.toml) [![Local first](https://img.shields.io/badge/control--plane-local--first-brightgreen.svg)](docs/public-private-boundary.md) [![Loop Agents](https://img.shields.io/badge/status-loop%20agents%20supported-brightgreen.svg)](docs/product/release-readiness.md) +[![Release](https://img.shields.io/github/v/release/loopx-project/loopx?color=181717)](https://github.com/loopx-project/loopx/releases/latest) [![License](https://img.shields.io/badge/license-Apache--2.0-181717)](LICENSE) [![TypeScript core](https://img.shields.io/badge/core-TypeScript-3178C6?logo=typescript&logoColor=white)](docs/architecture/rfcs/typescript-control-plane-migration-v0.zh-CN.md) [![Discord](https://img.shields.io/badge/Discord-Join-5865F2?logo=discord&logoColor=white)](https://discord.gg/XmGgQyCFZd) loopx-project/loopx 在 Trendshift 的趋势排名 -[开始使用](#试用-loopx) · [个人工作区](#认识个人-agent-工作区) · [LHTB 结果](#lhtb-results) · [文档](https://loopx-project.github.io/loopx/docs/) · [English](README.md) +[开始使用](#试用-loopx) · [2.0 升级指南](docs/product/releases/v2.0.0.md#中文指南) · [研究工作台](#research-workbench) · [LHTB 结果](#lhtb-results) · [文档](https://loopx-project.github.io/loopx/docs/) · [English](README.md) LoopX 2.0，面向企业、研究机构与超级个体的长程研究工作台；应用画框内保留真实研究历史与来源范围，状态条按原计数校正比例
观看研究工作台影片 · 86秒 · 双语文字稿、字幕与来源。App 实录、合成示例与机制示意分别标注。 -**两步在 Codex App 里用上 LoopX。** 先安装一次： +**两步在 Codex App 里用上 LoopX。** 需要 Python 3.11+、Node.js 22.22.3+（推荐 Node 24 LTS）。先安装一次： ```bash python3 -m pip install --upgrade loopx && loopx workflow-skills --install @@ -50,13 +50,34 @@ LoopX 管理下一步工作、验收依据，以及什么时候需要你判断 | 在一个入口管理个人项目、定时任务与待决事项 | [个人 Agent 工作区](#认识个人-agent-工作区) | | 让多个 Agent 分工协作，交付可验收的结果 | [Agent 协作指南](docs/product/use-cases/cross-runtime/README.md#中文指南) | +## LoopX 2.0 + +| 共享控制面 | 长程研究工作台 | +| --- | --- | +| 已迁移事务、权威与恢复规则由 TypeScript 统一拥有；Python 保留真实宿主 / provider IO 和专业计算。 | 从研究问题出发，串起任务委派、Explore 历史、产物、轨迹分析与下一轮决策。 | +| [两个月的重构历史、技术细节与核心研发统计](https://loopx-project.github.io/loopx/blog/zh/typescript-control-plane-refactor/) | [86 秒产品影片](https://github.com/user-attachments/assets/543af0b1-c3d4-4cfb-aedd-a68563a20601) · [轨迹分析合同](docs/reference/trajectory-assessment.md) | + +**从 1.x 升级？** 2.0 停止对未迁移 Markdown Goal 的普通写入。 +继续这些 Goal 前先看[迁移与恢复指南](docs/product/releases/v2.0.0.md#中文指南)； +安装新版不会静默转换既有状态。 + + + +## 让研究接得下去 + +打开 Goal 查看任务归属、Agent 与已记录的 Explore 历史。通过 **深度分析 / Deep analysis** +检查已登记轨迹的引用、原生结果读回，以及单独测量的成本。Agent 准备来源； +打开页面、刷新和读取结果不会启动模型，执行分析需要显式操作及已配置的宿主和账号。 + +保留支持、反驳与未知，核对新证据为什么改变了路线，或为什么值得继续，再进入下一轮。 + ## 认识个人 Agent 工作区 把长程目标收进同一个 local-first 工作区。Goal、待关注事项、对话、任务、 文件、定时计划与恢复状态跨天数、跨重启、跨 harness 保持持久。重新打开项目时， 可以检查上一轮的状态与证据，再继续下一项允许执行的工作。 -LoopX 1.0 将这些长程控制状态汇入 Personal Workspace。你可以在一个页面中： +LoopX 将这些长程控制状态汇入 Personal Workspace。你可以在一个页面中： - 看清哪些事项正在等你、执行中、观察中、已安排或已停止； - 配置 Goal 的 Capability，区分机器默认值与 Goal 覆盖，预览变更后再应用； @@ -72,7 +93,7 @@ loopx dashboard ``` `loopx dashboard` 是受支持的浏览器 / PWA 启动方式。也可从 -[1.0 Release](https://github.com/loopx-project/loopx/releases/tag/v1.0.0) 下载桌面预览版， +[最新 Release](https://github.com/loopx-project/loopx/releases/latest) 下载桌面预览版， 复用同一组 loopback 服务与 Goal 状态。Apple Silicon macOS 支持签名 App 更新， 将桌面壳与内置运行时配套升级，并提供修复与恢复入口；需要 Python 3.11+， App 为 ad-hoc 签名，尚未 notarize。Windows 预览版目前手动更新，需单独安装 CLI。 @@ -702,7 +723,7 @@ raw benchmark task/log/trajectory/verifier output、credentials、token、私有 ## 当前状态 -LoopX 1.0 已经是一套可用的长程 Agent 本地控制面，正在进入更广泛的采用阶段。 +LoopX 已经是一套可用的长程 Agent 本地控制面，正在进入更广泛的采用阶段。 LoopX 不是完整 agent platform，不是 agent runtime，也不是自治生产控制器。 目前 LoopX 已交付围绕 goal、typed todo / decision scope、平级 claim / lease、 diff --git a/docs/assets/personal-workspace/research-workbench-hero.webp b/docs/assets/personal-workspace/research-workbench-hero.webp index e307b176fe..8a810f4728 100644 Binary files a/docs/assets/personal-workspace/research-workbench-hero.webp and b/docs/assets/personal-workspace/research-workbench-hero.webp differ diff --git a/docs/assets/personal-workspace/research-workbench-hero.zh-CN.webp b/docs/assets/personal-workspace/research-workbench-hero.zh-CN.webp index f2bc330428..c0838ed06e 100644 Binary files a/docs/assets/personal-workspace/research-workbench-hero.zh-CN.webp and b/docs/assets/personal-workspace/research-workbench-hero.zh-CN.webp differ diff --git a/docs/book/chapters/00-reading-guide.md b/docs/book/chapters/00-reading-guide.md index 3136f7cb60..e4cc9d3f63 100644 --- a/docs/book/chapters/00-reading-guide.md +++ b/docs/book/chapters/00-reading-guide.md @@ -180,7 +180,7 @@ lifecycle 选择，不是所有贡献的默认终点。 ## 版本基线 -当前内容面向 LoopX release `v2.0.0a1`；本地命令示例已按 `loopx 2.0.0a1` 的 +当前内容面向 LoopX release `v2.0.0`；本地命令示例已按 `loopx 2.0.0` 的 公开 CLI 与协议表面复核。该版本要求 Python 3.11+ 与 Node.js 22.22.3+。LoopX 会自动管理 空闲后退出的 TypeScript Effect runtime，用户不需要手工维护 daemon。 diff --git a/docs/book/en/chapters/00-reading-guide.md b/docs/book/en/chapters/00-reading-guide.md index 48616f2b33..bdadb5fc8a 100644 --- a/docs/book/en/chapters/00-reading-guide.md +++ b/docs/book/en/chapters/00-reading-guide.md @@ -199,8 +199,8 @@ Do not bypass a newer permission or lifecycle check just to make an older exampl ## Version baseline -This book targets LoopX release `v2.0.0a1`. Local command examples were checked against -the public `loopx 2.0.0a1` CLI and protocol surface. It requires Python 3.11+ and Node.js 22.22.3+. +This book targets LoopX release `v2.0.0`. Local command examples were checked against +the public `loopx 2.0.0` CLI and protocol surface. It requires Python 3.11+ and Node.js 22.22.3+. LoopX starts and reuses its managed, idle-exiting TypeScript Effect runtime automatically; users do not operate that runtime as a manual daemon. diff --git a/docs/book/en/index.md b/docs/book/en/index.md index 82c59e4846..0b5d9f6eec 100644 --- a/docs/book/en/index.md +++ b/docs/book/en/index.md @@ -79,7 +79,7 @@ versioned or optional functionality, not the default shape of every contribution - Source format: Markdown - Site generator: MkDocs Material - Hosting: GitHub Pages -- LoopX release anchor: `v2.0.0a1` +- LoopX release anchor: `v2.0.0` - Runtime prerequisites: Python 3.11+ and Node.js 22.22.3+ The official public protocols remain authoritative for protocol facts. Commands that change across diff --git a/docs/book/index.md b/docs/book/index.md index abd9ec2fa7..9a9cf1a6dd 100644 --- a/docs/book/index.md +++ b/docs/book/index.md @@ -70,7 +70,7 @@ Extension 只是可独立版本化和交付的一种路径。 - 正文格式：Markdown； - 站点生成器：MkDocs Material； - 在线发布：GitHub Pages； -- LoopX 发布锚点：`v2.0.0a1`； +- LoopX 发布锚点：`v2.0.0`； - 运行时前提：Python 3.11+ 与 Node.js 22.22.3+。 协议解释以 LoopX 官方公开合同为事实源。易变化的命令仍以对应发布物、官方文档和当前 diff --git a/docs/guides/installing-loopx.md b/docs/guides/installing-loopx.md index d82581dcba..a42673aec5 100644 --- a/docs/guides/installing-loopx.md +++ b/docs/guides/installing-loopx.md @@ -39,8 +39,11 @@ the App can render this projection without inventing a second health model. control-plane request. Validate Node before installing or upgrading LoopX. Upgrading from an older Node 22 installation requires restarting the managed runtime with `loopx doctor --restart-runtime` after the new Node is on `PATH`. -SQLite remains opt-in and checks the actual embedded SQLite version before -opening authority state. +New unconfigured Goals use canonical SQLite with hard leases. Explicit choices +and existing Goals retain their own configuration; installing the package does +not migrate their authority. SQLite checks the actual embedded SQLite version +before opening authority state. See the [2.0 upgrade guide](../product/releases/v2.0.0.md) +before updating a Goal that still uses the old Markdown writer. A managed runtime that cannot publish its startup locator returns the existing safe filesystem/lock diagnostic code, such as `mutation_lock_timeout`, diff --git a/docs/product/releases/v2.0.0.md b/docs/product/releases/v2.0.0.md new file mode 100644 index 0000000000..25ac78c30f --- /dev/null +++ b/docs/product/releases/v2.0.0.md @@ -0,0 +1,185 @@ +# LoopX 2.0: TypeScript control plane, long-horizon research workbench + +[中文指南](#中文指南) · [Release and verified assets](https://github.com/loopx-project/loopx/releases/tag/v2.0.0) + +LoopX keeps goals, ownership, decisions and evidence durable while your Agent +host supplies the model and tools. 2.0 connects a two-month control-plane +reconstruction with a workbench for inspecting research across sessions. + +## Choose your upgrade path + +**2.0 is a breaking release for unpromoted Markdown Goals and retired `legacy` +execution policy.** Reading retained history and recovering a supported original +operation remain separate from permission to start a new write. An installation +never silently converts a Goal, changes its provider or releases its leases. + +| Your current state | Before continuing work in 2.0 | +| --- | --- | +| Canonical File/SQLite with `soft_claim` or `hard_lease` | Preserve the selected provider, update through its installation owner and verify package/runtime identity. | +| Unpromoted Markdown Goal | Stop its writers, verify exit, settle leases and pending capture/outbox through their owners, then review and import the original source. | +| Canonical store using `legacy` ownership | Review a claim-preserving ownership-policy migration to `soft_claim` or `hard_lease`; this is separate from storage conversion. | +| Existing target-only settings or explicitly disabled canonical creation | Inspect and explicitly select compatible creation settings before creating a writable Goal; disabled does not mean enabled. | + +If you cannot perform the reviewed migration yet, retain the verified 1.4.2 +installation for those Goals. Do not run two writers against the same state. + +### Install and verify + +Require Python 3.11+ and Node.js 22.22.3+; Node 24 LTS is recommended. Keep one +pip, pipx, uv-tool or archive installation owner. In an appropriate Python +environment, install this exact release: + +```bash +node --version +python3 -m pip install --upgrade 'loopx==2.0.0' +loopx workflow-skills --install +loopx --version +loopx doctor --deep +``` + +Expect `loopx 2.0.0` and a ready packaged TypeScript runtime. Restart the Agent +host after first installing workflow skills. For existing installations, inspect +`loopx update check` and `loopx update plan` before `loopx update apply`. +After updating, read back enabled extensions with +`loopx extension doctor --all-enabled --execute`. + +The browser/PWA entry is `loopx dashboard`. Native desktop downloads remain +preview shells and depend on the complete platform build assets; consult the +[desktop guide](../../../apps/desktop/loopx-control-plane/README.md). A CLI +upgrade and an App upgrade have independent identity readbacks. + +### Import an old Markdown Goal + +Open **Goal settings → Task ownership → Data storage**. Stop the affected +writers and verify process exit, settle retained leases, then use **Back up and +preview import**. Review the complete active/archive inventory and confirm +**Import reviewed Markdown source**. A checkbox cannot bypass an unsettled lease +or changed source. The same transaction is available to an Agent: + +```bash +loopx --format json coordination-shadow prepare-import --goal-id GOAL --operation-id IMPORT \ + --provider sqlite --target-handoff-mode hard_lease +# Review the returned immutable plan and its exact plan_sha256 before applying. +loopx --format json coordination-shadow apply-import --goal-id GOAL --operation-id IMPORT \ + --plan-sha256 SAVED-SHA256 --writers-stopped --execute +``` + +Prepare is not a writer stop or an import. It creates a private scoped authority +archive and plan. That archive is not a complete disaster-recovery backup. +After a lost response, use **Read original preview and current storage**, or +`coordination-shadow recover-import` with the same operation and digest. +Do not replace an ambiguous operation with a fresh import. Replacing the binary +does not remove a committed writer fence or roll state back. Follow the +[full migration and recovery contract](../../reference/local-authority-provider-selection.md#20-compatibility-cutoff-and-release-sequence) +for source verification, File/SQLite alternatives and supported historical input. + +## What changed in the control plane + +The migration began with the August 15 RFC, then moved from leaf helpers to +complete transactions. Effect execution, settlement, canonical authority and +migrated ownership rules share TypeScript owners. Python retains real provider +and Host IO, compatibility codecs and specialized computation. This is not a +claim that every Python module has been rewritten. + +Three engineering details matter when using or extending it: + +- **Check before effects.** Preflight validates the exact operation before a + provider acts; final reduction records its result. Fewer RPCs are not a reason + to move rejection after an irreversible operation. +- **Recover the original result.** An operation receipt can recover committed + work without renewing old execution authority or overwriting later writes. + An uncertain external effect stays uncertain without independent readback. +- **Preserve decision semantics.** The Semantics work traces definition owners, + values, producers and projections. CLI output budgets compare real stdout + and growth while preserving obligations, stop conditions and detail routes. + +Read the [full engineering history and core-only statistics](https://loopx-project.github.io/loopx/blog/typescript-control-plane-refactor/), +including new maintainer [Song](https://github.com/songoow)'s Semantics work and +[Duang777's contributor-led retirement](https://github.com/loopx-project/loopx/pull/6396). +The historical statistics end on October 16; they are not release-tag totals, +unique developer counts, productivity measurements or benchmark gains. + +## Follow a research question through the workbench + +Open a Goal, inspect its Agents and tasks, then follow recorded Explore history +to an experiment, artifact and evidence. **Deep analysis** reads a registered +trajectory with citations, six separate process judgments, coverage and missing +data. Native outcomes and measured solver costs have separate source bindings. +An Agent can prepare the source pack; the owner need not enter private paths. + +Reading pages, refreshing, switching sources and opening citations do not run +analysis. To run it, select an authorized source, review the requested model +operation and explicitly execute it. Missing or changed sources remain visible; +a failed source switch never shows another source's result under the new name. + +- [Research-workbench film, transcript and source boundaries](../../assets/personal-workspace/loopx-research-films.md) +- [Trajectory analysis: preparation, execution, cancellation and readback](../../reference/trajectory-assessment.md) +- [Explore activation and disable path](../../../loopx/capabilities/explore/README.md) + +The film combines labelled recorded excerpts, synthetic examples and illustrations. + +## 中文指南 + +LoopX 2.0 的两条主线是 **TypeScript 控制面重构**与**长程研究工作台**： +让目标、任务归属、决策和证据接续起来，让研究者能追到产物、轨迹与下一步依据。 +模型和工具仍由你选择的 Agent 宿主提供。 + +### 先判断是否需要迁移 + +**这是有兼容性变化的版本。** 未迁移的 Markdown Goal 不再接受普通写入； +`legacy` 也不再授权新的执行。历史可读、原操作可恢复、当前执行获准，是三个独立条件。 +安装新版不会自动迁移 Goal、切换 provider 或释放租约。 + +- 已用 canonical File/SQLite 且为 `soft_claim` / `hard_lease`：保留配置，按原安装渠道更新并核对 runtime。 +- 未迁移 Markdown Goal：先停止相关 writer / Host、确认进程退出、结清租约与 capture/outbox，再预览、备份并导入完整原来源。 +- canonical store 仍用 `legacy`：单独审阅保留 claim 的执行策略迁移；不必因此再次转换存储。 +- 仍用旧目标配置或显式关闭 canonical creation：先明确兼容的新建设置，不将关闭解释为开启。 + +暂时不能迁移的 Goal，可保留已验证的 1.4.2 环境；不要让两个 writer 同时操作同一状态。 + +### 安装、升级与读回 + +需要 Python 3.11+、Node.js 22.22.3+，推荐 Node 24 LTS。在合适的 Python 环境中执行： + +```bash +node --version +python3 -m pip install --upgrade 'loopx==2.0.0' +loopx workflow-skills --install +loopx --version +loopx doctor --deep +``` + +预期版本为 `loopx 2.0.0`，打包 TypeScript runtime 就绪。首次安装 skills 后重启宿主。 +既有安装先执行 `loopx update check`、`loopx update plan`，再按计划执行 `loopx update apply`； +之后运行 `loopx extension doctor --all-enabled --execute` 核对已启用扩展。 +浏览器 / PWA 入口为 `loopx dashboard`；桌面包仍属预览，CLI 与 App 要分别核对版本。 + +旧 Goal 在 **Goal settings → Task ownership → Data storage** 中操作： +停止 writer 并确认退出、结清租约，再选择 **Back up and preview import**， +检查完整 active/archive 清单后确认 **Import reviewed Markdown source**。 +Agent 可复用上方同一组 `coordination-shadow prepare-import / apply-import` 命令。 +预览不会自动停进程或导入；范围内 authority archive 不等于完整灾备。 +响应丢失时读取原预览及当前存储，沿原 operation / digest 恢复。 +不能靠重装旧二进制清除已提交的 writer fence，也不能覆盖后来的写入。 + +### 看懂重构，再使用研究工作台 + +迁移从 8 月 15 日 RFC 开始，经历完整事务、共享权威、真实调用方、存储成本、 +Semantics 与旧 writer 退役。已迁移的领域规则统一由 TS owner 解释； +Python 保留真实宿主和 provider IO、兼容 codec 与专业计算。 +前置准入发生在副作用之前；原回执恢复不续租、不覆盖新写入；CLI 压缩保护决策语义。 + +[中文重构长文与核心统计](https://loopx-project.github.io/loopx/blog/zh/typescript-control-plane-refactor/) +保留新 maintainer [Song](https://github.com/songoow) 的 Semantics 贡献，以及 +[Duang777 主导的收尾](https://github.com/loopx-project/loopx/pull/6396)。 +文中的历史统计截止 10 月 16 日，不能当作本发布 tag 的统计或模型生产率。 + +打开 Goal 追踪任务、Agent 和 Explore 历史，再通过 **深度分析 / Deep analysis** 查看 +登记轨迹、引用、六项过程判断、覆盖与缺失。原生结果、solver 成本与分析器判断各有来源。 +Agent 准备来源，页面不要求用户填写私有路径。打开、刷新、切换来源和读引用都不会启动模型； +运行需要显式选择已有授权来源和模型操作。失败、来源变化与未知不伪装成通过。 + +[影片与双语文字稿](../../assets/personal-workspace/loopx-research-films.zh-CN.md) · +[轨迹分析合同](../../reference/trajectory-assessment.md) + +影片中的实录、合成示例和示意动画各自标注。 diff --git a/examples/public_entry/readme-demo-surface-smoke.py b/examples/public_entry/readme-demo-surface-smoke.py index 8a86687ff4..3127f068c1 100644 --- a/examples/public_entry/readme-demo-surface-smoke.py +++ b/examples/public_entry/readme-demo-surface-smoke.py @@ -60,7 +60,6 @@ def main() -> int: '', '', '', - "LoopX 1.0 is a usable local control plane", "docs/assets/loopx-lark-developer-group.png", "docs/assets/loopx-wechat-contact.png", "WeChat: huangrt00", @@ -78,7 +77,6 @@ def main() -> int: "200+ 小时自然时长", "超过 200 小时的公开贡献轨迹", "经过脱敏的 owner-run showcase", - "LoopX 1.0 已经是一套可用的长程 Agent 本地控制面", "docs/assets/loopx-lark-developer-group.png", "docs/assets/loopx-wechat-contact.png", "微信：huangrt00", diff --git a/loopx/__init__.py b/loopx/__init__.py index 13aa310863..21a05a2037 100644 --- a/loopx/__init__.py +++ b/loopx/__init__.py @@ -2,4 +2,4 @@ __all__ = ["__version__"] -__version__ = "2.0.0a1" +__version__ = "2.0.0" diff --git a/man/loopx.1 b/man/loopx.1 index 773b618e3c..4fb866c2fb 100644 --- a/man/loopx.1 +++ b/man/loopx.1 @@ -1,4 +1,4 @@ -.TH LOOPX 1 "" "LoopX 2.0.0a1" "User Commands" +.TH LOOPX 1 "" "LoopX 2.0.0" "User Commands" .SH NAME loopx \- control-plane helper for long-running agent work .SH SYNOPSIS diff --git a/pyproject.toml b/pyproject.toml index c6123f2965..4078997a83 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta" [project] name = "loopx" -version = "2.0.0a1" +version = "2.0.0" description = "A Loop Engineering control plane for long-running agent goals (requires Node.js 22.22.3+)." readme = "README.md" requires-python = ">=3.11"