Skip to content

LoopX v0.4.1

Latest

Choose a tag to compare

@huangruiteng huangruiteng released this 04 Aug 04:06
eadacca

LoopX v0.4.1

LoopX v0.4.1 is a focused control-plane release for longer-running agent work. It strengthens durable work selection, Goal-host continuation, bounded scheduling, agent-scoped recall, and provider-neutral operations while keeping external effects behind explicit authority.

State Kernel & Control Plane

  • Persist capability-admitted Todo routes so later turns can resume the same domain work without re-inferring intent (#2728).
  • Add a typed Goal continuation contract and retain selected-Todo continuation context across host turns (#2731, #2738).
  • Preserve delivery across neutral refreshes, reject watch-only spend, retain blocked-successor acknowledgements, and reload unchanged monitor writeback state (#2729, #2733, #2739, #2754).
  • Wake Goal hosts at the earliest material frontier transition instead of relying on broad polling (#2737).

Capabilities & Workflows

  • Materialize grouped Issue Fix PR monitors and require explicit capability-route selection, preventing unrelated URLs or later Todos from silently changing the workflow (#2725, #2747, #2749).
  • Add default-off Agent Turn Recall with agent, goal, project, Todo, turn-instance, freshness, and authority scoping (#2740, #2743).
  • Add provider-neutral Content Ops item lifecycle records for revision-bound approval, delivery receipts, readback, and supersession without storing draft bodies or credentials (#2746).
  • Settle material-intake ranking disposition into a bounded lifecycle rather than leaving source choices in prompt memory (#2741).

Quality & Testing

  • Keep status and monitor-poll packets within bounded output budgets, and refresh Full Public fixtures against the compact contracts (#2726, #2732, #2735).
  • Decouple release promotion readiness from project-specific goal state and restore the v0.4.1 release/full-public qualification smokes (#2727, #2750, #2752).
  • Keep bounded monitor and replan fixtures fresh so failures reflect product behavior rather than expired test data (#2744).
  • Speed up loopx --version without importing the full command surface (#2751).

Benchmarks & Integrations

  • Refresh and observe published integration source heads without resetting reviewed local plans (#2736, #2745).
  • Update the OpenCode Goal bridge pin to opencode-goal-plugin 0.7.0 (#2753).
  • This release makes no benchmark-score, leaderboard, or long-horizon outcome-uplift claim.

Documentation & Compatibility

  • Reorganize documentation into product, capability, integration, development, concept, and reference paths, and add a public-safe RFC for Agent IM, LoopX, and OpenViking collaboration (#2742).
  • Refresh the public developer-group QR code and contributor task board (#2757, #2764).
  • v0.4.1 remains compatible with the documented local install/update paths and named-version contract.

Community Contributors

  • @Ray0907 fixed blocked-Todo counts in the global summary and added the fast --version path (#2748, #2751).
  • @elegracer updated the OpenCode Goal bridge to the 0.7.0 plugin contract (#2753).

Optional Capability Activation & Use

Agent Turn Recall

Activation: Explicitly enable Reward Memory for the goal and configure the agent_workflow.turn_admission surface, then invoke recall after quota/Todo selection with --execute.

Validation: Run the same command without --execute; it previews the bounded situation and query without provider access.

Disable / rollback: Remove the goal's turn-admission recall configuration or stop invoking agent-turn-recall. Provider failure already fails open to an empty context.

Authority boundary: Recalled guidance is private read-only context, not action authority. Current Todo, interaction, capability, write-scope, and user gates remain authoritative.

Docs: https://github.com/huangruiteng/loopx/blob/main/docs/capabilities/agent-turn-recall/README.md

loopx agent-turn-recall \
  --goal-id <goal-id> \
  --agent-id <agent-id> \
  --turn-instance-id <iso-turn-id> \
  --quota-decision-json .local/turn-quota.json \
  --format json

Content Ops Item Lifecycle

Activation: No persistent switch is required. Create an item explicitly through loopx content-ops item-create; persistence remains caller-owned.

Validation: Inspect the returned content_ops_item_v0 and transition receipt, then use item-transition with caller-owned event JSON.

Disable / rollback: Stop invoking the lifecycle or supersede/skip the local item. No provider state is mutated by the lifecycle helper.

Authority boundary: Approval references and provider effects remain external authority. LoopX validates revision/digest lineage but does not publish, store draft bodies, or hold credentials.

Docs: https://github.com/huangruiteng/loopx/blob/main/docs/reference/protocols/content-ops-item-lifecycle-v0.md

loopx content-ops item-create \
  --item-id launch-post-v1 \
  --item-kind post \
  --channel x \
  --content-digest sha256:0000000000000000000000000000000000000000000000000000000000000000 \
  --content-ref draft:launch-post-v1 \
  --created-at 2026-08-04T00:00:00Z \
  --format json

中文摘要

状态内核与控制面

  • 将 capability 准入后的 Todo 路由持久化,并通过 typed Goal continuation 与 selected-Todo 上下文让后续 turn 稳定续接。
  • 收紧 watch-only spend、neutral refresh、blocked successor acknowledgement 与 unchanged monitor writeback 语义。
  • Goal host 按最早 material frontier transition 唤醒,减少宽泛轮询。

能力与工作流

  • Issue Fix 现在会生成分组 PR monitor,并要求显式 capability route,避免 URL 或后续 Todo 隐式改路由。
  • 新增默认关闭、严格按 agent/goal/project/Todo/turn scope 约束的 Agent Turn Recall。
  • 新增 provider-neutral Content Ops item lifecycle,覆盖 revision-bound approval、delivery/readback receipt 与 supersession,同时不保存正文或凭据。
  • Material intake 的 ranking disposition 进入有界生命周期,不再只存在于 prompt 记忆中。

质量与测试

  • 收紧 status、monitor-poll 输出预算,并让 Full Public fixtures 对齐 compact contract。
  • release promotion readiness 不再依赖项目私有 goal state;v0.4.1 release 与 full-public qualification smoke 已恢复。
  • 修正过期 monitor/replan fixture,并加速 loopx --version

基准与集成

  • 更新并观测已发布 integration source head,同时保留经过 review 的本地计划。
  • OpenCode Goal bridge 更新到 opencode-goal-plugin 0.7.0。
  • 本版本不声明 benchmark 分数、排行榜或长程 outcome uplift。

文档与兼容性

  • 文档重组为 product、capability、integration、development、concept 与 reference 多级路径,并加入公开安全的 Agent IM / LoopX / OpenViking 协作 RFC。
  • 更新开发者群二维码和贡献任务看板;保留既有本地安装、升级与 named-version 合同。

社区贡献者

  • @Ray0907 修复 global summary 的 blocked Todo 计数,并实现快速 --version 路径(#2748#2751)。
  • @elegracer 将 OpenCode Goal bridge 更新到 0.7.0 plugin 合同(#2753)。

可选能力启用与使用

Agent Turn Recall

**启用:**为目标显式启用 Reward Memory 并配置 agent_workflow.turn_admission surface,在 quota/Todo 选择后通过 --execute 调用 recall。

**验证:**去掉 --execute 运行同一命令,可在不访问 provider 的情况下预览有界 situation 与 query。

**停用 / 回退:**移除目标的 turn-admission recall 配置,或停止调用 agent-turn-recall。Provider 失败会回退为空 context。

**权限边界:**Recall guidance 只是私有只读上下文,不授予动作权限;当前 Todo、interaction、capability、write scope 与 user gate 仍是权威来源。

**文档:**https://github.com/huangruiteng/loopx/blob/main/docs/capabilities/agent-turn-recall/README.md

loopx agent-turn-recall \
  --goal-id <goal-id> \
  --agent-id <agent-id> \
  --turn-instance-id <iso-turn-id> \
  --quota-decision-json .local/turn-quota.json \
  --format json

Content Ops Item Lifecycle

**启用:**无需持久开关;显式调用 loopx content-ops item-create 创建 item,持久化仍由调用方负责。

**验证:**检查返回的 content_ops_item_v0 与 transition receipt,再使用调用方持有的 event JSON 调用 item-transition

**停用 / 回退:**停止调用 lifecycle,或在本地将 item 标记为 superseded/skipped;helper 不修改 provider 状态。

**权限边界:**Approval ref 与 provider effect 仍来自外部权威;LoopX 只验证 revision/digest lineage,不发布内容、不保存正文、不持有凭据。

**文档:**https://github.com/huangruiteng/loopx/blob/main/docs/reference/protocols/content-ops-item-lifecycle-v0.md

loopx content-ops item-create \
  --item-id launch-post-v1 \
  --item-kind post \
  --channel x \
  --content-digest sha256:0000000000000000000000000000000000000000000000000000000000000000 \
  --content-ref draft:launch-post-v1 \
  --created-at 2026-08-04T00:00:00Z \
  --format json

发布验证

  • Tag target: eadaccae911e7de27970f5ca79a563984dedaad1.
  • GitHub Full Public Smokes passed on the exact release target.
  • Final release-notes, named-version, and public-boundary smokes passed locally.