Repository navigation
Looper v2.14.168
Looper v2.14.168
This is the patch release v2.14.168, a hotfix line in which each merged change ships at once. It documents one change: #1306 (Dashboard follow-ups).
Release Decision
Who should upgrade: Installations that use the dashboard's agent history, LLM-request export, project deletion or Cursor login status, or that run TTADK profiles. Others need not upgrade for behavior.
What this release solves: #1306 fixes the listed valid items of the review follow-ups #1076, #1127, #1132 and #1140 (fixes #1140, #1127, #1076, part of #1132): agent history refreshes its Model requests, the dashboard export has a size limit, a TTADK sign-in check that could not finish is shown, project deletion shows its impact first, and the Cursor login status refreshes.
Breaking changes: No. There is no migration or database schema change. One additive API change: a new read operation project_admin.preview_delete, and an optional refreshing field on a provider's login. The bridge boundary is unchanged: upgrade to v2.13.165 first if the installation is older.
How to verify: Check the installed version.
looper --version # looper 2.14.168Contributors: Maintainer @foolzzz authored #1306; no community contribution was included in this release.
Upgrading
The bridge boundary is unchanged: an installation older than v2.13.165 must upgrade to v2.13.165 first (upgrade to v2.13.165 first) and be started once; see the Upgrading section of the v2.14.0 release for the steps and rollback. An installation on v2.14.0 to v2.14.167 upgrades directly. There is no database schema change.
Behavior changes
The pull request states that its behavior changes follow the triage notes' fixes (maintainer decision, intended). Read in the code of #1306:
- Agent history (
web/src/pages/agent-history.tsx). Opening the Model requests section re-fetches its rows. A run card shows a warning, "TTADK sign-in check before this run started", when the run's launch record carries attadk_checknote. - TTADK launch note (
looper/agents/runtimes/ttadk.py). For an inconclusive check the note recorded in the launch record is now "timed out or failed; the run started anyway" instead of "could not finish (…)". The check itself is unchanged. - LLM-request export (
web/src/lib/api.ts). The dashboard export fails with an error once it would exceed 256 MiB, pointing toloopercli llm-requests exportfor larger exports. Smaller exports are unchanged. - Project deletion (
looper/agents/v1_domains/projects.py,web/src/components/project-settings.tsx). The new read operationproject_admin.preview_deletereturns the same impact text that deletion confirms with, changing nothing. The dashboard's Delete button now calls it and shows that impact instead of a generic "cannot be undone" line; Cancel takes focus, and a delete or preview error is shown next to the button. Deleting itself is unchanged. - Cursor login status (
looper/agents/runtimes/cursor_login.py,looper/agents/v1_domains/registry.py,web/src/lib/use-registry.ts). While a background probe runs, the login view carriesrefreshing: truenext to the last known state, and the dashboard re-polls every second while any login is checking or refreshing. The field is optional in the schema. - Model-visible changes: None to prompts or tool descriptions for Planner, Worker or Reviewer. The new operation's description ("Preview deleting a project and its Manager-scope impact without changing anything.") appears in the v1 operation catalog that API clients read.
Optional Capability Activation & Use
No new optional capability activation is introduced in this release.
Validation
Reported by the pull request: #1306 lists the tests that cover the change (Python tests for Cursor login, the v1 registry and projects, and web tests for the registry hook, LLM export, agent history, project settings and the projects API), automated reviews, and CI before the merge. It does not report a local full suite.
CI: CI runs after the release is drafted; its result is not recorded here.
Not tested for this draft: a local full suite and the built wheel. The release documentation gate checks the body only.
中文摘要
本版本是 patch release v2.14.168(热修线,每个合并的改动立即发布),说明一项改动:#1306(Dashboard 后续修复)。
升级决策
**谁需要升级:**使用 dashboard 的 agent 历史、LLM 请求导出、项目删除或 Cursor 登录状态,或运行 TTADK profile 的安装。其他安装没有行为上的升级需求。
解决了什么:#1306 修复评审后续 #1076、#1127、#1132 和 #1140 中列出的有效项(修复 #1140、#1127、#1076,属于 #1132):agent 历史会刷新 Model requests,dashboard 导出有大小上限,未能完成的 TTADK 登录检查会显示出来,删除项目前先显示影响,Cursor 登录状态会刷新。
**是否有破坏性变更:**否。没有迁移或数据库结构变更。有一处增量 API 变更:新增只读操作 project_admin.preview_delete,以及 provider 登录上的可选字段 refreshing。桥接边界不变:早于 v2.13.165 的安装须先升级到 v2.13.165。
**如何验证:**核对版本为 2.14.168。
**贡献者:**维护者 @foolzzz 提交 #1306;本版本无社区贡献。
looper --version # looper 2.14.168升级
桥接边界不变:早于 v2.13.165 的安装必须先升级到 v2.13.165 并启动一次(upgrade to v2.13.165 first 即先升级到 v2.13.165),步骤与回退见 v2.14.0 发布说明的升级一节。v2.14.0 至 v2.14.167 上的安装可直接升级。数据库没有结构变更。
行为变化与入口
该 PR 声明行为变化遵循分诊记录中的修复(维护者决定,符合预期)。#1306 在代码中可见:
- Agent 历史(
web/src/pages/agent-history.tsx)。展开 Model requests 时会重新获取其行。启动记录带有ttadk_check说明时,运行卡片显示 “TTADK sign-in check before this run started” 警告。 - TTADK 启动说明(
looper/agents/runtimes/ttadk.py)。检查未得出结论时,启动记录中的说明由 “could not finish (…)” 改为 “timed out or failed; the run started anyway”。检查本身不变。 - LLM 请求导出(
web/src/lib/api.ts)。dashboard 导出超过 256 MiB 时报错,并指向loopercli llm-requests export做更大的导出。较小的导出不变。 - 项目删除(
looper/agents/v1_domains/projects.py、web/src/components/project-settings.tsx)。新增只读操作project_admin.preview_delete,返回删除确认所用的同一影响文本,不做任何改动。dashboard 的删除按钮现在调用它并显示该影响,而不再是通用的“无法撤销”提示;焦点落在取消按钮,删除或预览的错误显示在按钮旁。删除本身不变。 - Cursor 登录状态(
looper/agents/runtimes/cursor_login.py、looper/agents/v1_domains/registry.py、web/src/lib/use-registry.ts)。后台探测运行期间,登录视图在最近已知状态之外带有refreshing: true,dashboard 在有登录处于 checking 或 refreshing 时每秒重新拉取。该字段在 schema 中是可选的。 - **面向模型的变化:**Planner、Worker、Reviewer 的提示词和工具描述没有变化。新操作的描述(“Preview deleting a project and its Manager-scope impact without changing anything.”)会出现在 API 客户端读取的 v1 操作目录中。
可选能力启用与使用
本版本未新增可选能力启用入口。
验证
PR 报告的:#1306 列出覆盖该改动的测试(Cursor 登录、v1 registry 与 projects 的 Python 测试,以及 registry hook、LLM 导出、agent 历史、项目设置和 projects API 的 web 测试)、自动评审,以及合并前的 CI。它未报告本地完整套件。
**CI:**发布草稿后 CI 会运行,其结果未在此记录。
**本次草稿未测试:**本地完整套件以及构建出的 wheel。发布文档 gate 只检查正文。