Skip to content

LoopX v2.4.0

Latest

Choose a tag to compare

@loopx-agent loopx-agent released this 21 Nov 20:54
· 2 commits to main since this release
a6ffb3b

LoopX v2.4.0

Keep original work, evidence, and conversations connected after interruption across Core 2.4.0, Desktop App 2.4.0, and dsh-loopx-plugin 0.1.1-beta.7. Core 2.4.0 adds one-confirmation Goal creation, searchable loaded conversations, isolated Steward memory, probe-gated Steward monitors and protected PR merge confirmations, bidirectional Codex/Antigravity Steward failover, and runtime-composed quota_settlement_plan_v2 Turn envelopes while retaining quota_packet as the ordinary public default. Installation, data compatibility, and optional host integrations retain their own checks.

At a Glance

Create a Goal from Chat with one confirmation. Search loaded conversations back to the original message. Recover interrupted Tasks through their original Turn, lease, and receipt. Coordinate Steward monitors, protected PR merge confirmations, peer result reads, bidirectional Codex/Antigravity routing, Lark group/private channels, Desktop App 2.4.0, and dsh-loopx-plugin 0.1.1-beta.7 against LoopX 2.4.0.

Upgrade

After v2.4.0 appears on your current distribution channel, check and apply the upgrade through that installation's owner. Review the migration below first if your registry still uses the legacy paused or stopped status.

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

Illustrated Feishu upgrade guide

Highlights

  • Create a Goal from Chat and search loaded history. Review a draft and confirm once to create the Goal and open its conversation when runtime and permissions are ready; search loaded conversations back to original messages, keep saved Research answers intact across Desktop reopenings, recover interrupted answers or pre-dispatch requests, diagnose lost workers, and preserve readable quoted Markdown. #8676, #8780, #8863, #8868, #8880, #8892, #8983, #9120, #9125
  • Steward monitors, exact-head PR review signals, and protected merge confirmations. Generic probe-gated continuous_monitor Todos support context_handoff and bounded steward_user_actions, scoped GitHub PR signal monitors aggregate per-monitor findings and deliver one readable report directly into bound App or Feishu chat_root sessions (#9182), exact-head PR review screening and queue model-coverage tracking power /confirm pr.merge previews with head/review drift checks, bounded advancement evidence, inline autonomous replan settlement with isolated native_result sinks, and pre-host deferral retries (#9187, #9188, #9191) alongside report/queue/pre-dispatch recovery (including stopped/saved candidate recovery and minor JSON delimiter glitch tolerance) harden cross-endpoint Steward reliability, and opt-in steward_memory adds isolated OpenViking memory scoped strictly to verified owner private Steward chats. #9014, #9074, #9077, #9081, #9083, #9093, #9143, #9155, #9157, #9159, #9164, #9182, #9187, #9188, #9191
  • Recover original work with Complete Turn and quota_settlement_plan_v2. Installed workspaces discover the Manager via the installed CLI and resume authorized Tasks on their original Turn, debit identity, and lazily rebound hard-lease fence (#9183); Complete Turn / native host callers compose loopx_turn_envelope_v1 with runtime-owned quota_settlement_plan_v2 (--settle-turn --settlement-receipt), while ordinary unhosted JSON quota should-run retains quota_packet as the qualified public default. #8489, #8615, #8802, #8830, #8956, #9030, #9047, #9084, #9097, #9111, #9154, #9157, #9158, #9160, #9161, #9183
  • Antigravity Carbon, per-endpoint preferences, and bidirectional Steward failover. Registers Antigravity Carbon (gemini-4-carbon-{high,medium,low}) while keeping Argon as the product default, adds endpoint_models preferences in steward_executor_machine_defaults_v1 (with JSON-mode editor guidance), enables bidirectional Codex/Antigravity flexible failover (loopx-codex-provider-routing 0.15.9) with Antigravity reasoning-effort capacity aliases and flexible_primary_available transitions, recovers Codex loopback relay 401 failures and Steward active-cascade resume_failed states, prevents truncated Codex API relay traffic, and preserves Codex session history across model switches. #8713, #8977, #8984, #9134, #9141, #9145, #9147, #9167, #9170
  • Multi-agent collaboration and hardened Lark group/private channels. Peers read pending results via read_peer_returns and consume_peer_result without reopening the Manager Inbox, Goal lifetime guard locks batch per Goal, and Lark gains reconnect queue recovery, read-only Steward shortcuts, Turn-scoped native images, shared card callbacks, single-pass card escaping, international setup URL recognition, and input-aware noop backoff reset. #8668, #8695, #8741, #8871, #8921, #8990, #9027, #9085, #9114, #9117, #9119
  • Desktop App 2.4.0, dsh-loopx-plugin 0.1.1-beta.7, LooChat workbench, and remote task gateway. Desktop App prepares updates before workspace teardown, bounds readiness probes, skips immutable-release frontend re-hashing, adds release/chat-bundle download retries, and verifies default_contract before caching macOS preview updates; dsh-loopx-plugin 0.1.1-beta.7 requires LoopX 2.4.0+, qualifies DSH 0.2.2-rc.1..rc.3 (including quota_settlement_plan_v2 closeout tests), surfaces GoalBar admission failures, and isolates hot uninstall; apps/workbench/ introduces the experimental LooChat conversation layer; and the remote task gateway adds scoped read ACLs and a PostgreSQL/TLS Compose self-hosting bundle. #8508, #8675, #8723, #8739, #8765, #8843, #8861, #8879, #8887, #8899, #9029, #9089, #9147

Replan Fixes

  • Intentional watches remain in replan history so the next Turn sees what it was waiting for. #8672
  • When the only work in scope is blocked, the scheduler waits for its dependency; superseded heartbeat receipts are fenced before Python follow-up, and historical ACK admissions stay on their original receipt fenced by GoalRef. #8511, #8647, #8708, #8907, #8975
  • Same-second review-bound successors and whole-second historical ACKs resolve as post-admission, Monitor-streak and pure replan Turns preserve their receipt source and exact closeout commands, and invalid vision outcomes remain recoverable. #8731, #8804, #8854, #8855, #8958
  • Explicit Goal resume and replan successor identity stay recoverable (including rearmed_after_obligation_id across successor reconstruction and post-admission same-Agent ACKs, #9118), warm deltas and saved C1 replans bind to the original capture digest, native captured_decision replan openings keep bound Yardstick reversal cues inline (nativeReplanPresentation), scoped_user_gate_fallback excludes ready deferred_successor_replan lifecycle replans from execution-lease preparation, replan recovery stays within projection boundaries (projected_ack writeback and monitor_poll lease_proof), and zero-effect monitors plus cleared-replan Steward reports recover cleanly. #8923, #9016, #9022, #9046, #9118, #9143, #9160, #9165, #9168

Contributors

22 community contributors are credited below, including 9 first merged contributions. Community Contributors

Release Decision

Who should upgrade: Personal Workspace, Desktop App, Steward, and Lark users wanting one-confirmation Goal creation, searchable conversations, probe-gated Steward monitors, protected PR merge previews, bidirectional Codex/Antigravity failover, or hardened Lark delivery, plus dsh-loopx-plugin 0.1.1-beta.7 operators who require LoopX 2.4.0+. Teams with scripts mutating legacy registry status pause fields must update them first.

What this release solves: It reduces Goal creation to one confirmation, connects loaded chat search and saved Research answers to original Turns, enables probe-gated Steward monitoring and exact-head PR merge confirmation, adds isolated owner-private Steward memory and bidirectional Codex/Antigravity failover, and hardens Task/lease recovery, Desktop preview qualification, Lark delivery, and DSH 0.2.2 compatibility.

Breaking changes: Yes. Legacy registry status values paused and stopped are retired in favor of activation.state and Goal lifecycle commands with a backed-up migration (#8431); the unqualified compaction working memory experiment is retired with saved settings kept inert (#8928); and dsh-loopx-plugin 0.1.1-beta.7 requires LoopX 2.4.0 or newer for the quota receipt reader (#8899). Ordinary unhosted JSON quota should-run keeps quota_packet as the qualified public default (#9084).

How to verify: Verify 2.4.0 and the owning Python environment in loopx doctor, confirm an existing Goal and original Task or new Chat draft, and confirm the read-only archive check passes after any registry migration.

Contributors: Release maintainer @huangruiteng and the 22 community contributors credited below (9 first merged contributions). Community Contributors

loopx --version
loopx doctor
loopx status --goal-id "$LOOPX_GOAL_ID"
loopx authority-archive upgrade --all-known --require-current

State Kernel & Control Plane

  • Recovery retains the original Turn, debit identity, and prepared or lazily rebound hard-lease fence (--task-lease-idempotency-key / --task-lease-expected-version, plus .validation-recovery. / .admission-retry and monitor_poll lease_proof recovery) only while recovery still needs an active lease — preserving committed-Turn replay and retired-lease closeout recovery (#9183) — while rechecking a fresh selection's gates; first generic-cli Turns declared with the complete v1 adapter and an independent validator auto-prepare missing task leases (#9047), settled C1 Turns stay prevented from reacquiring a native Codex lease, quota_result_delivery retains host_poll_receipt on transport errors without recording premature capture_sha256 digests, checkpoint-relocated accounting artifact reads (readQuotaSpendEventFromRun) resolve safely inside the active runs directory, and a validated Todo-less original Turn recovers its own receipt without a second spend. #8860, #8894, #8900, #9047, #9097, #9111, #9157, #9158, #9160, #9161, #9183
  • Complete Turn (loopx_turn_envelope_v1) and native host callers compose runtime-owned quota_settlement_plan_v2 (--settle-turn --settlement-receipt), keeping quota_spend as a runtime step in ordered_steps, routing stateless capture read selection through the TypeScript context_select owner (#9142), and aligning explicit --capture-dir settlement plan reads with progressive context-read references (#9154, #9158, #9160), while ordinary unhosted JSON quota should-run retains the qualified quota_packet public default until RFC §9 qualification; quota polling preserves explicit Monitor Todo selection (#9099), verifies gate scope through signed lane references (#9101), loads large write-scope lists on demand during Todo preparation and keeps claim overlap scopes accessible (#9078, #9086, #9106), preserves rearmed_after_obligation_id across Vision successor reconstruction and post-admission same-Agent ACKs (#9118), defers backup preimage directory-sync imports inside registry_codec for test/adapter isolation (#9161), and retires legacy heartbeat work prompt generation in favor of the unified contract. #8489, #8956, #9000, #9030, #9054, #9057, #9078, #9084, #9086, #9099, #9101, #9106, #9118, #9142, #9154, #9158, #9160, #9161
  • Ordinary Todo edits preserve compatible stored declarations; when new fields require a newer reader, archive rollback checks the target runtime's Todo read before switching, rolls back both CLI and archive-managed loopx-apply-rrule launchers atomically on POSIX (#9007), honors custom bin and release directory overrides (#9066), and leaves current runtime and state untouched if the check fails. #8902, #8906, #9007, #9066
  • Goal storage import follows the registered source and serializes its final source check with registry writers without substituting global discovery for that source; an already canonical Goal needs no cold import. #8864
  • Installed task recovery uses the original execution lease and receipt through the shared task lifecycle, refresh-state accepts inline JSON, spend-slot accepts --delivery-workspace-path, cross-repository binding errors explain missing bindings clearly, and standalone heartbeat settlement uses the installed route. #8615, #8707, #8827, #8926, #8933
  • Peer collaboration reads pending results via read_peer_returns and consume_peer_result (with read_token and --disposition) without reopening the Manager Inbox, Goal lifetime guard locks batch per Goal in handoff queries, terminal return scans are cached and blocked follow-ups gated, cross-Goal peer mismatches refuse safely, and single-agent Goal owners can close exact linked user gates. #8644, #8779, #8803, #8844, #8846, #8853, #9027, #9085, #9088, #9117
  • PostgreSQL authority archives preserve checkpoint history beyond 20,000 commits for backup and restore; remote authority task service adds complete remote task lifecycle (complete, block, defer, todo_add, snapshot), active-Goal-scoped read ACLs, and a self-hosted PostgreSQL/TLS Compose bundle. #8508, #8759, #8765, #8861, #8887

Capabilities & Workflows

  • Personal Workspace & Research continuity: Conversational Goal creation uses a single draft confirmation with runtime readiness and workspace checks (#8780), loaded conversation search jumps back to original messages (#8676), long conversation headers wrap cleanly on narrow phone viewports (#9121), review materials restore keyboard focus (#8913), manager read views disclose omitted records and recover oversized Todo details through bounded pages (#8954, #8959, #8962), saved Research results, case links, interrupted answers, lost-worker diagnostics, pre-dispatch requests, and quoted Markdown stay recoverable across Desktop and Lark channels (#8863, #8868, #8880, #8892, #8983, #9120, #9125).
  • Steward monitors, exact-head PR review signals, and protected pr.merge:
    • User outcome: Owners can declare natural-language continuous_monitor Todos over arbitrary portfolio/repository signals, aggregate scoped GitHub PR signal monitors without cross-monitor wakeups and receive one readable report directly in bound App or Feishu chat_root sessions (#9182), triage exact-head GitHub PR reviews (including author-owned COMMENTED fallback verdicts and conflict detection), and confirm protected pr.merge previews with /confirm bound to PR head, approval URL, and bypassed gates.
    • Shipped layer: TypeScript admission & probe gates (steward_managed_mode.ts), github_pr_evidence.py, steward_pr_merge.py, steward_monitor.py, and steward_turn.py (#9074, #9081, #9093, #9143, #9182), plus bounded advancement evidence items, inline autonomous replan settlement with isolated native_result sinks, and pre-host deferral retries (#9187, #9188, #9191), report validator drift/Python-upgrade tolerance, frozen/stopped report contract recovery (#9157, #9164), minor JSON delimiter glitch tolerance in host_candidate.py (#9164), observation monitor queue preservation, pre-dispatch endpoint failure recovery with bounded receipt discovery (#9159), and mid-turn failed report cancellation (#9155).
    • Last-mile boundary: Merge confirmations still require explicit owner /confirm and authorized repository scope; unavailable external probes fail closed without overwriting the last verified hash. #9074, #9077, #9081, #9093, #9143, #9155, #9157, #9159, #9164, #9182, #9187, #9188, #9191
  • Isolated OpenViking Steward memory (steward_memory):
    • User outcome: Private owner Steward conversations can recall standing preferences and past exchanges without leaking memory into group chats, project conversations, or worker Agents.
    • Shipped layer: Default-off steward_memory machine configuration namespace (steward_memory_machine_defaults_v0), TypeScript policy/normalization owner (steward_memory.ts), host adapter (loopx/capabilities/steward_memory/), Dashboard Settings UI, and OPENVIKING_* worker env scrubbing.
    • Last-mile boundary: Explicitly opt-in (enabled: false by default); requires operator-configured OpenViking CLI/credentials on the Chat host and excludes project chats, group channels, monitor/report/review turns, and unverified senders. #9083
  • LooChat workbench (experimental): Imports the Calli TypeScript/web workbench (apps/workbench/, @loopx/loochat) next to the existing dashboard as an optional conversation layer with Goal creation, task/acceptance views, recoverable cross-directory local session discovery (LOOCHAT_HIDDEN_SESSION_DIRS and explicit import workdirs), and /api/loopx/* proxying to Core; automatic LoopX continuation remains owned by Core rather than the workbench UI. #8843, #9063, #9113
  • Material lifecycle & Explore / Context cleanup: Material lifecycle adds stateless wave-based rerank previews (plan-wave-rerank) while keeping ranking application owner-authorized (#8579); Yardstick evaluation defers until explicitly selected and empty Todo queues stay out of ordinary worker context (#9034, #9059, #9060); and the unqualified compaction working memory experiment is retired (#8928).

Quality & Testing

  • SQLite reliability & ENOSPC matrix: Expanded regression coverage across lagging persisted-cursor consumers, backup/restore lineage, concurrent CAS and lost-response retries, and disk-full injection (SQLITE_FULL and real macOS ENOSPC sparse volume fail-closed recovery). #8367, #8482, #8498, #9126
  • Type safety, CLI modularization & test isolation: Eliminated Any annotations with ratchet baselines across control-plane, quota, Lark, reward-memory, benchmark, and domain-pack modules (#8971–#8993, #8013), modularized large CLI, issue-fix, and Lark/Chat modules (including internal typed loopx/chat/ action grouping #9056), pruned ceremonial/obsolete smoke stacks (#8883, #8884, #9073), reclaimed completed and read-only pytest temporary trees cleanly (#9070, #9189), pinned C1/Complete Turn output budgets, CLI help catalogs, architecture import guards, onboarding gates, UTF-8 host transports, and settlement tests (#8940, #8994, #9010, #9019, #9025, #9042, #9044, #9048, #9052, #9102, #9104, #9152, #9154, #9156, #9158, #9160, #9161), and bound doctor package update readback to its owning Python environment (#9009). #8013, #8897, #8933, #8940, #8971, #8994, #9009, #9044, #9056, #9070, #9102, #9104, #9152, #9154, #9156, #9158, #9160, #9161, #9189
  • Canary & release qualification gates: Strengthened base/head CLI probe and budget-baseline isolation (#8948, #9103), complete C1 input routing for external-wait host prompt probes (#8981), peer-runtime controller-ownership classification in canary checks (#9092), runtime snapshot qualification (#8919, #8922, #8952, #9018), canary timeout/incomplete diagnostics (#9001), Git pathname preservation (#8426, #8429, #8558, #8585, #8645, #8678), unified local-path URL vs path: verdicts across presentation and public-output guards (#9080, preserving bare-root inline code examples in #9190), and local-first verification and public smoke workflows (#9040, #9152), alongside --max-workers concurrent live portfolio qualification, an 8 KiB host-tool error output cap preserving deep-path replan context recovery, digest consumer manifest & multi-goal bootstrap smoke alignment, standalone test_effect_turn_live_quota_decision import qualification (#9168), --settle-turn vision-closeout receipt / creation-allowance wakeup race hardening (#9178), lazy resumed task-lease rebinding plus goal-frontier maintainability extraction (#9183), and unmanaged Lark poll retirement / generic-cli validator lease gating fixes (#9190), plus pruned pytest directory discovery, parallel-default live model qualification, and single-wave clean-checkout pytest sharding (#9193). #8426, #8645, #8919, #8922, #8948, #8952, #8981, #9001, #9018, #9040, #9080, #9092, #9103, #9152, #9168, #9178, #9183, #9190, #9193

Benchmarks & Integrations

  • Antigravity, Codex & Steward executor routing: External hosts can opt into --complete-turn (loopx_turn_envelope_v1) with digest-bound context-read pagination and verified original capture recovery (#8489, #8940, #9022, #9048). Steward executor routing adds Antigravity Carbon (gemini-4-carbon-{high,medium,low}) while retaining Argon as default, optional endpoint_models preferences in steward_executor_machine_defaults_v1 (with JSON-mode authoring notes in configuration_ui.py), bidirectional codex / antigravity flexible failover (loopx-codex-provider-routing 0.15.9) with reasoning_effort alias capacity resolution (#9147), flexible_primary_available conversation transitions (#9145), and native Steward monitor/report fallback parity; legacy session model preservation (#8977, #8984), Antigravity schedule patrol and Stop hooks (#8874), Codex API relay untruncated streaming/payload handling and loopback relay 401 recovery (#8713, #9167), Steward active-cascade resume_failed recovery and bounded thinking-only error loops (#9170), UTF-8 Codex App stdout decoding (#8485), quiet completion receipts (#8454), failed-start Session adapter retention (#9134), and managed chat observer lock handoff (#9130) complete the host layer. #8454, #8485, #8489, #8713, #8874, #8977, #8984, #9130, #9134, #9141, #9145, #9147, #9167, #9170
  • Lark group & private channel hardening: Private Lark replies stay off the main blocking path, preserve queued messages on reconnect, offer read-only Steward shortcut cards, deliver Turn-scoped native images and recover legacy captured images, steer mentions into frozen original Turns, share callback dispatch across query and operation cards, escape Goal Channel operation card text in a single pass, recognize international Lark setup URLs, coalesce listener snapshots, cache recovery lookups, and reset noop recovery backoff when Turn/session inputs change. #8270, #8668, #8695, #8741, #8858, #8870, #8871, #8893, #8903, #8921, #8990, #8999, #9041, #9096, #9098, #9100, #9114, #9119
  • Desktop App 2.4.0 & dsh-loopx-plugin 0.1.1-beta.7: Desktop App prepares updates before workspace teardown, bounds readiness probes, opens the usable workspace before optional updates, skips immutable-release frontend re-hashing (#9089), adds download retries to chat-bundle packaging and Desktop release/updater workflows (#9147), and checks signature-verified archives for supported runtime default_contract before preparing macOS preview updates (#9029). dsh-loopx-plugin 0.1.1-beta.7 adds DSH 0.2.2-rc.1..rc.3 compatibility, aligns integration closeout tests with quota_settlement_plan_v2 (#9147), surfaces GoalBar continuationAdmission failures, isolates hot uninstalls from the shared Web server, fences Start/Pause with Core source fingerprints, preserves replacement cancellation/error pauses, and fixes Windows continuation paths. #8504, #8675, #8723, #8739, #8879, #8899, #9029, #9087, #9089, #9147
  • Windows & Benchmark tooling (no net long-horizon outcome claim): Windows receives PowerShell settlement quoting, bounded error payloads, UTF-8 decoding, source lease clock-skew tolerance, file identity checks, and local NTFS loopx-jev capture (#8599, #8620, #8641, #8643, #8761). Benchmark adapters add benchmark.runtime.planning_batch initial task planning (#9090), idle-boundary staged CLI activation (#8501), governed single-worker Turn extraction (#8499), Codex resume restoration (#9031), Frontier shared task clocks (#8875), and restored frozen v1 archive and standalone benchmark import boundaries (#9151); no net long-horizon benchmark outcome or total-cost improvement is claimed in this release. #8499, #8501, #8599, #8620, #8641, #8643, #8761, #8875, #9031, #9090, #9151

Documentation & Compatibility

  • A Japanese README joins the existing public reading entrypoints, alongside updated bilingual RFCs and Bootstrap/Control-Plane guides. #8839, #9035, #9113
  • dsh-loopx-plugin 0.1.1-beta.7 requires LoopX 2.4.0 or newer (loopx>=2.4.0) for the original-Turn quota receipt reader and qualifies DSH 0.2.2-rc.1..rc.3 (retaining 0.1.5..0.2.1-rc.2). Core 2.4.0, Desktop App 2.4.0, and the DSH plugin have separate releases and support matrices; updating Core does not automatically publish or upgrade an installed DSH plugin. #8879, #8899
  • Ordinary unhosted JSON quota should-run retains quota_packet as the qualified public default (public_default_contract.json), and macOS Desktop preview updates verify that signature-verified archives declare the matching default_contract before caching or replacing the App. #8952, #9018, #9029, #9084
  • A backed-up upgrade converts legacy Goal pause metadata to activation.state. A raw pip or source install can run loopx authority-archive upgrade --all-known --require-current as a read-only check. For a registry you own that requires migration, run loopx authority-archive upgrade --all-known --execute and retain its returned backup path. Conflicting pause metadata stays stopped pending owner review. #8431
  • A standalone loopx-core wheel preparation candidate (packages/loopx-core/) enables workspace-free CLI and TypeScript runtime installations while keeping the ordinary loopx package default unchanged. #8615, #8830, #8840

Community Contributors

Optional Capability Activation & Use

Remote task gateway

Activation: From a source checkout with a qualified Node runtime and npm ci --ignore-scripts, provision an isolated PostgreSQL authority schema, a restricted runtime role, a service policy, and TLS credentials (or start the self-hosted PostgreSQL/TLS Compose bundle in examples/coordination/remote-authority-compose). Start the service as shown below. Optional scheduler observation requires an explicit remote_authority.enabled: true for one registered Goal plus its HTTPS origin, verified tenant and store identity, scoped actor, stable existing probe Todo, and private CA path when applicable. #8508, #8765, #8887

Validation: Recover a known operation receipt with the example client and a prepared command.json. For the configured Goal, use quota should-run to read the bounded remote observation through the normal scheduler.

Disable / rollback: Set remote_authority.enabled: false on the affected Goal. Stop the listener and remove its access grants to retire the service. PostgreSQL retains its receipts.

Authority boundary: The scoped principal and restricted PostgreSQL role define task mutation rights. Host observation is read-only. For a resource-scoped read-only listener, select loopx_remote_authority_scoped_read_policy_v1 and authorize each exact Goal lifetime, Todo, and audience. Supply its original creation or first-adoption receipt; absent proof stays unavailable. That listener rejects writes and withholds free-form notes, lease keys, and global provider revisions. Remove the matching grant or ACL entry to revoke subsequent admissions. Local admission, owner Stop, and quota remain authoritative. #8861

Docs: Remote authority task service

node --experimental-strip-types examples/coordination/remote-authority-service.ts \
  --policy "$SERVICE_POLICY" --cert "$TLS_CERT" --key "$TLS_KEY" --host 127.0.0.1 --port 8443
# In the scoped client environment, with the service credential loaded privately:
node --experimental-strip-types examples/coordination/remote-authority-client.ts \
  --endpoint "$SERVICE_HTTPS_ORIGIN" --ca "$TLS_CA" --recover < command.json
loopx --format json quota should-run --goal-id "$LOOPX_GOAL_ID" --agent-id "$LOOPX_AGENT_ID"

Complete Turn context for external hosts

Activation: Add --complete-turn to JSON quota should-run in an external host that can consume the complete v1 contract (loopx_turn_envelope_v1, composing runtime-owned quota_settlement_plan_v2). Give it an explicit fresh Turn ID and a writable capture directory. Ordinary unhosted JSON quota should-run without Complete Turn or host flags continues returning quota_packet. #8489, #8956, #9084

Validation: Confirm loopx_turn_envelope_v1 and quota_settlement_plan_v2 on the returned or saved decision. Finish its required Goal/context reads and follow the same Turn's execution and single-command settlement contract (--settle-turn --settlement-receipt). Follow the pinned reader supplied with a progressive response and verify the original digest and Turn identity.

Disable / rollback: Omit --complete-turn from subsequent requests to return to the prior quota_packet context path. Keep the original digest-bound commands for existing captures.

Authority boundary: The current Goal, Agent, admission, permissions, required reads, hard-lease fence, and Stop conditions govern the Turn.

Docs: Turn envelope reference

loopx --format json quota should-run --goal-id "$LOOPX_GOAL_ID" \
  --agent-id "$LOOPX_AGENT_ID" --turn-instance-id "$LOOPX_TURN_ID" \
  --complete-turn --decision-output-dir ./complete-001

The reader's JSON Pointer selects a field inside the captured JSON; it is not a filesystem path. Copy the returned current reader reference into CAPTURE_READER. Listing and selecting the current capture does not require reading an older delta baseline or creating another admission.

loopx --format json quota context-read --reference-file "$CAPTURE_READER" --list --list-depth 2
loopx --format json quota context-read --reference-file "$CAPTURE_READER" --select /selected_todo

A selected Todo is only part of the contract. Read its applicable Goal requirements, constraints, and required sources before work. Keep the original Turn, capture, and settlement identity after compaction or recovery. A diagnostic-only recovery response grants no execution.

Material wave rerank preview

Activation: Supply a request with ordered material references and exact-read annotations to plan-wave-rerank (per-command opt-in; no persistent switch). #8579

Validation: Review proposed ordering, protected items, and coverage of the exact input. The preview uses the material lifecycle contract.

Disable / rollback: Stop invoking the preview or discard its output. If an operator separately applies a plan, recover through the original material lifecycle rollback receipt.

Authority boundary: The command is stateless. Applying or rolling back a ranking uses the material owner's authorized operation and current revision.

Docs: Material lifecycle capability

loopx material-lifecycle architecture --format json
loopx material-lifecycle plan-wave-rerank --input request.json --format json

Private Lark conversations

Activation: In an authorized local installation, install the bundled loopx-lark provider if needed, then enable that provider and connect the private conversation in the workspace's Lark settings using its existing authorized account (supporting both domestic Feishu and international Lark setup URLs). #8871

Validation: Read the provider doctor result. From your own configured private conversation, send an authorized test request and verify that the reply, Steward shortcut card, or Turn-scoped native image appears in that same conversation. After a reconnect, check that a queued request appears once and reaches its original destination.

Disable / rollback: Disconnect the configured conversation. To retire this local provider, disable it and stop its host-managed collector if one is running.

Authority boundary: The connector uses the established conversation binding, provider identity, and granted permissions. Steward triage shortcuts are read-only, group channels remain restricted, and image delivery follows the original private reply scope.

Docs: The Lark extension lifecycle

loopx extension install --bundled loopx-lark --execute --format json
loopx extension enable loopx-lark --execute --format json
loopx extension doctor loopx-lark --execute --format json
# To retire the local provider:
loopx extension disable loopx-lark --execute --format json

Staged benchmark CLI activation

Activation: An existing authorized Docker benchmark controller stages a qualified source revision into its versioned release directory and previews its existing owned launcher with activate_cli_source(..., execute=False). Provide the exact run identity, archive digest, and required source, native receipt, and current Stop callbacks. Revalidate those inputs before any explicitly authorized execution. #8501

Validation: Run the source-checkout receipt-readback test below. For an authorized actual change, follow the source identity and launcher readback and observe the next real Host input separately.

Disable / rollback: Omit activation to keep the current launcher. For an interrupted switch, reconcile the original owned receipt with reconcile=True. An explicitly authorized repair="old" uses current control and reverified source identity.

Authority boundary: The existing benchmark controller holds the idle-boundary lock, Stop policy, and finite allowance. The activation changes its future CLI subprocesses and requires separate execution authorization.

Docs: Host CLI source activation

uv run --extra test python -m pytest -q tests/control_plane/test_cli_source_activation_readback.py

Private backup inspection

Activation: In Settings → Capability Center → device defaults → Configuration backup and recovery, choose Full archive inspection for the original archive and matching external manifest. Unsupported services/platforms leave the operation unavailable. The CLI operations below are per-command. Preview a private full-state backup for the project and the selected configuration cohort before creating it. Retain the matching archive, external manifest, and compatible package. #8864

Validation: Verify the pair before extraction. Only --execute creates the new inert inspection directory; it does not activate an authority or start a Host. Review included and missing sources.

Disable / rollback: Stop invoking the commands or omit --execute. Preserve retained backups privately. Reinstalling an older runtime does not reverse newer data writes; keep the current runtime when a target reader cannot verify them, and use the owning recovery process for further changes.

Authority boundary: An archive or restored historical lease is evidence, not a new execution grant. Full modern reactivation requires its own identity, pending-effect, and admission checks. Never unpack an old archive over live state.

Docs: Configuration backup and recovery, Agent-assisted in-place upgrade

loopx backup-state --project "$PROJECT_ROOT" --current-project-only \
  --configuration-goal-id "$LOOPX_GOAL_ID" --no-automations --no-skills \
  --output-dir "$PRIVATE_BACKUP_DIR"
# After reviewing the plan and within the existing authorization, repeat with --execute.
loopx backup-state verify --archive "$BACKUP_ARCHIVE" --manifest "$BACKUP_MANIFEST" \
  --destination "$NEW_INSPECTION_DIR"

Isolated OpenViking Steward memory

Activation: Default-off (enabled: false). In Dashboard Settings → Steward → Isolated OpenViking memory, or via loopx machine-config preview / apply on the steward_memory namespace (steward_memory_machine_defaults_v0), set enabled: true, user_space, auto_recall, and recall_timeout_seconds (1–15). Supply the OpenViking runtime credentials/config privately in the Chat host environment (OPENVIKING_*). #9083

Validation: Inspect loopx machine-config inspect --format json for steward_memory (enabled: true and revision), then send a substantive message in a verified owner private Steward conversation. Verify recall/commit works while group chats, project conversations, answer/metadata reviews, and Codex worker environments remain isolated and exclude OPENVIKING_* variables.

Disable / rollback: Preview and apply enabled: false, or remove/roll back the steward_memory namespace with loopx machine-config remove / rollback.

Authority boundary: Applies strictly to verified owner private Steward conversations (external_audience, bound_steward, private_conversation); rejects project conversations, monitor/report/review turns, group channels, and unverified senders; rejects model-authored routing or target overrides (speaker, owner, uri, user_space, etc.); scrubs OPENVIKING_* from worker subprocesses; and grants no Goal, Todo, or host tool authority.

Docs: Steward memory machine configuration, Steward memory policy owner

loopx machine-config describe --format json
loopx machine-config preview --namespace steward_memory --config-json steward-memory.json --format json
loopx machine-config apply --namespace steward_memory --config-json steward-memory.json \
  --expected-plan-revision "$PLAN_REV" --execute --format json
loopx machine-config inspect --format json
loopx machine-config remove --namespace steward_memory --expected-plan-revision "$REMOVE_REV" --execute

Steward executor routing and failover

Activation: Open Settings → Steward → Models and executor (or preview/apply steward_executor under steward_executor_machine_defaults_v1 via loopx machine-config). Select selection_policy (preferred, pinned, or flexible), primary executor_endpoint (codex, antigravity, or managed), optional eligible_endpoints (["codex", "antigravity"]), and optional per-endpoint endpoint_models in JSON mode (for example Antigravity gemini-4-carbon-high alongside default gemini-4-argon-high, preserved across guided saves). Bidirectional codex / antigravity failover and API fallback require loopx-codex-provider-routing (0.15.9+) installed and enabled separately. #9141, #9145, #9147

Validation: Inspect loopx machine-config inspect --format json and loopx-codex-accounts status (if installed), then test an ordinary private Steward message and an Apply to this conversation idle switch. Verify that Carbon tiers match account offerings and exhausted primary routes fail over cleanly within eligible_endpoints while preserving native monitor/report support.

Disable / rollback: Switch selection_policy back to preferred or pinned on a single executor_endpoint, clear endpoint_models, or roll back the machine-configuration transaction with loopx machine-config rollback.

Authority boundary: Selecting an endpoint, model tier, or flexible pool does not store credentials, grant host tools beyond manager_runtime, bypass native Antigravity/Codex approvals, or authorize unconfigured paid API use without explicit opt-in and measured exhaustion.

Docs: Manager runtime profile v0, Native Codex accounts

loopx machine-config preview --namespace steward_executor --config-json steward-executor.json --format json
loopx machine-config apply --namespace steward_executor --config-json steward-executor.json \
  --expected-plan-revision "$PLAN_REV" --execute --format json
loopx machine-config inspect --format json

DSH native plugin (0.1.1-beta.7)

Activation: Install dsh-loopx-plugin 0.1.1-beta.7 (requiring LoopX 2.4.0 or newer and supporting DSH 0.2.2-rc.1..rc.3 alongside 0.1.5..0.2.1-rc.2) into your DSH web or desktop profile from the release tarball or source installer, then start DSH (dsh --profile web --port 0 or loopx dsh-launch web). #8879, #8899, #9147

Validation: Confirm the four plugin rows with dsh --profile web --dump-config, invoke /loopx <task> in a Session, and read back the exact Session binding and GoalBar status (continuationAdmission, Start/Pause, and Personal Workspace panel when loopx dashboard is running on loopback).

Disable / rollback: Remove the plugin from the same DSH profile (dsh plugin --profile web remove dsh-loopx-plugin; 0.1.1-beta.7 preserves the shared Web server during hot uninstall), or reinstall a retained 0.1.1-beta.6 tarball with --ignore-scripts; optionally delete the plugin's isolated runtime directory when DSH is stopped.

Authority boundary: Passive until the exact live Session contains typed loopx skill invocation evidence and one unique LoopX binding; Core remains the sole authority for Goals, Todos, quotas, and Source fingerprint CAS; replacement retains cancellation ownership and error pauses; grants no extra model tools or Goal write authority.

Docs: DSH plugin README

dsh plugin --profile web add \
  "https://github.com/loopx-project/loopx/releases/download/dsh-loopx-plugin-v0.1.1-beta.7/dsh-loopx-plugin-0.1.1-beta.7.tgz"
dsh --profile web --dump-config
loopx --registry .loopx/registry.json --format json resolve-agent-thread \
  --host-surface deepseek-harness-native --thread-id "$DSH_SESSION_ID"
dsh plugin --profile web remove dsh-loopx-plugin

LooChat workbench (experimental)

Activation: Preview and install the optional TypeScript/web workbench from apps/workbench/install.sh (pass --dry-run first, or build from apps/workbench/ with npm install && npm run setup && npm run build), configure LOOCHAT_WORKDIRS and LOOCHAT_LOOPX_CORE_URL in .env, and start the workbench alongside a running LoopX Core. #8843, #9113

Validation: Verify /api/health and bearer-authenticated /api/loopx/healthz, sign in with the generated token on loopback (or trusted VPN), and confirm Goal preview/confirm creation and conversation binding appear in the UI.

Disable / rollback: Stop the daemon (scripts/install-service.sh --remove or install.sh --uninstall); ~/.config/loochat, ~/.local/state/loochat, LoopX Core, and loopx dashboard remain untouched.

Authority boundary: Only directories allowlisted in LOOCHAT_WORKDIRS / LOOPX_GOAL_WORKSPACES are accessible; Goal permissions stay owned by LoopX Core (read-only or Codex workspace-auto per Turn); the workbench does not start/upgrade Core or drive automatic continuation on its own; bind HTTP+token only on loopback or trusted VPN interfaces.

Docs: LooChat workbench README, Workbench agent install guide

curl -fsSL https://raw.githubusercontent.com/loopx-project/loopx/v2.4.0/apps/workbench/install.sh \
  | LOOCHAT_REF=v2.4.0 bash -s -- --dry-run
# From a full checkout:
npm --prefix apps/workbench install && npm --prefix apps/workbench run build

Standalone Core wheel candidate

Activation: Opt-in source build (packages/loopx-core/prepare.py) that packages the CLI and TypeScript task runtime into a separate virtual environment without the Chat package, web assets, or canary suite. Do not co-install or overlay it into the same Python environment as the full loopx package. #8615, #8830, #8840

Validation: Run loopx --help, loopx doctor --installation-only --deep --format json, and a read-only loopx start-goal --guided --project . --goal-text "..." preview inside the new environment.

Disable / rollback: Deactivate or remove the isolated loopx-core virtual environment and switch back to the ordinary loopx installation while preserving Goal/task state.

Authority boundary: Requires Python 3.11+ and Node 22.22.3+ for governed Tasks; shares the exact same state, lease, and validation owners as ordinary LoopX without supplying a model provider, credentials, or automatic execution.

Docs: Standalone Core README

uv run --extra test python packages/loopx-core/prepare.py --output /tmp/loopx-core-source
uv build /tmp/loopx-core-source --out-dir /tmp/loopx-core-dist
uv venv /tmp/loopx-core-env
uv pip install --python /tmp/loopx-core-env/bin/python /tmp/loopx-core-dist/loopx_core-*.whl
/tmp/loopx-core-env/bin/loopx doctor --installation-only --deep --format json

Benchmark initial planning batch

Activation: Per-invocation opt-in inside an already authorized loopx-planned benchmark planning wake when the planning frontier is empty: save the requirement declaration and ordered advancement Todos in PROPOSAL.json with the checkpoint's input_digest and acceptance provider_revision, then invoke python -m benchmark.runtime.planning_batch PROPOSAL.json. #9090

Validation: Confirm exit code 0 with "status": "ready", distinct created todo_ids, and bound goal-acceptance links matching the unchanged input_digest. If interrupted, replay the exact unchanged proposal file.

Disable / rollback: Omit planning_batch and use the ordinary goal-acceptance and todo add planning steps for existing work, requirement changes, or blockers.

Authority boundary: Reuses existing public LoopX CLI operations (goal-acceptance refine, todo add) with per-write operation IDs, spends zero execution quota, and grants no admission, scoring, or budget authority beyond the active benchmark wake.

Docs: Benchmark runtime guide

python -m benchmark.runtime.planning_batch PROPOSAL.json

Scoped GitHub PR signal monitors

Activation: Opt in per Steward continuous_monitor Todo inside a bound private App or Feishu chat_root Steward session by supplying target_key plus signal_scope (schema_version: "steward_signal_monitor_scope_v0", include_portfolio, include_inbox, and optional pr_filter fields such as exclude_drafts, exclude_conflicting, effective_verdicts, required_approver_declarations, author_mode/authors, and min_stalled_hours) when creating or updating the monitor action. #9074, #9182

Validation: Confirm the normalized scope file is persisted at steward-monitors/<goal_id>/scopes/<target_key>.json and that StewardMonitor evaluates each monitor independently without cross-monitor wakeups, delivering one aggregated steward_monitor_report_delivery_v0 report to the exact bound session_id / chat_root. Note that updating signal_scope on an existing Monitor Todo requires an accompanying non-empty Todo field patch (such as summary, cadence, or stop_condition), otherwise todo update rejects an empty Todo patch (Todo update requires a non-empty patch).

Disable / rollback: Pause or stop the Monitor Todo in Steward chat (pause / stop), or move it out of open in CLI (loopx todo update --goal-id "$LOOPX_GOAL_ID" --todo-id "$MONITOR_TODO_ID" --status blocked or deferred / done) and confirm via loopx todo list --goal-id "$LOOPX_GOAL_ID" that no further polling occurs. Do not delete steward-monitors/<goal_id>/scopes/<target_key>.json as a disable shortcut on an open Todo, because missing scope files fall back to unfiltered repository observation; existing scope and snapshot files stay preserved under blocked/done state so resuming later retains configuration and history.

Authority boundary: steward_managed_mode.ts rejects unknown signal_scope / pr_filter fields fail-closed; external GitHub probes stay read-only and never overwrite the last verified hash on outage; and report deliveries are pinned strictly to the bound session_id / chat_root without granting PR merge or repository write authority.

Docs: Steward monitor controller, Steward managed mode

loopx todo list --goal-id "$LOOPX_GOAL_ID"
cat "$LOOPX_RUNTIME_ROOT/steward-monitors/$LOOPX_GOAL_ID/scopes/$MONITOR_TARGET_KEY.json"
loopx todo update --goal-id "$LOOPX_GOAL_ID" --todo-id "$MONITOR_TODO_ID" --status blocked
loopx todo list --goal-id "$LOOPX_GOAL_ID"

Install / Update

For a new PyPI install, run the following once 2.4.0 is available, then restart the agent host.

python3 -m pip install --upgrade 'loopx==2.4.0'
loopx workflow-skills --install
loopx slash-commands --install
loopx doctor

For an existing pip, pipx, or archive install, use the explicit update commands above. To revalidate enabled extensions, use the existing operator path.

loopx extension doctor --all-enabled --execute

Verification boundaries

  • The package version and tag are 2.4.0 / v2.4.0. Confirm availability through the current installation owner, then verify the same Goal and original task after upgrading.
  • Check ordinary File/SQLite write compatibility, original receipts and lease records, quota_packet public default compatibility, and rejection of a newer incompatible field set separately. Historical reads from an inert backup do not reactivate a modern Goal.
  • Final clean commit/tree/version/tag, complete packaged pages, native Host, Desktop App 2.4.0 platform artifacts, dsh-loopx-plugin 0.1.1-beta.7 tarball publication, real-model checks, the personal illustrated guide, and public distribution remain separately evidenced under the release contract. This usage guide is not a qualification receipt.
  • This release describes reliability and workflow changes. No net long-horizon outcome gain is asserted.

中文摘要

本页说明 LoopX Core 2.4.0、Desktop App 2.4.0 与 dsh-loopx-plugin 0.1.1-beta.7 的升级与可选能力用法:在对话中一次确认创建 Goal、检索已载入消息、使用独立管家长期记忆与受保护 PR 合并确认、按原任务与回执恢复工作,并支持 Codex/Antigravity 双向切换。安装、数据兼容与可选 Host 集成分别核验。

升级

现有安装渠道提供 2.4.0 后,依次执行 loopx update check、loopx update plan、loopx update apply,再运行 loopx --version 和 loopx doctor。仍使用旧暂停字段的 registry 先核对下方迁移路径。

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

飞书图文升级与验收指南

主要变化

  • 一次确认创建 Goal 与对话历史检索。 在 Chat 审核并确认一次草稿即可创建 Goal 并打开原会话;支持在已载入会话中搜索并跳回原消息,桌面重开后保留已保存研究回答、恢复中断回答及派发前请求、诊断失联 worker 与清晰引用 Markdown。 #8676, #8780, #8863, #8868, #8880, #8892, #8983, #9120, #9125
  • 管家通用监控、精确 Head PR 审查信号与受保护合并确认。 原生管家支持基于探针门控的自然语言 continuous_monitor(含 context_handoff 与受控 steward_user_actions),支持作用域隔离的 GitHub PR 信号监控内部聚合并在触发后向绑定 App 或飞书 chat_root 会话投递单篇可读汇报(#9182),支持精确 Head PR 审查筛选与队列模型覆盖追踪(#9014)及 /confirm pr.merge 合并预览、推进证据有界化、一次提交前重试、主结果分离的自治重规划内联结算及宿主演前 deferral 重试(#9187, #9188, #9191)、跨端点派发前失败与报告/队列恢复(含已停止或已保存报告候选恢复及轻微 JSON 分隔符容错)、以及默认关闭的独立 OpenViking 管家长期记忆(仅限本人私聊)。 #9014, #9074, #9077, #9081, #9083, #9093, #9143, #9155, #9157, #9159, #9164, #9182, #9187, #9188, #9191
  • Complete Turn 与 quota_settlement_plan_v2 原任务恢复。 已安装工作台经 CLI 发现 Manager 并沿原 Turn、扣额身份与惰性重绑定硬租约护栏恢复已授权任务;Complete Turn 与原生宿主组合 loopx_turn_envelope_v1 与 quota_settlement_plan_v2(--settle-turn --settlement-receipt),普通未托管 JSON quota should-run 继续保留 quota_packet 公开默认。 #8489, #8615, #8802, #8830, #8956, #9030, #9047, #9084, #9097, #9111, #9154, #9157, #9158, #9160, #9161, #9183
  • Antigravity Carbon、每端点模型偏好与双向容灾切换。 注册 Antigravity Carbon(gemini-4-carbon-{high,medium,low})并保留 Argon 默认,在 steward_executor_machine_defaults_v1 增加 endpoint_models JSON 模式配置说明,支持 Codex 与 Antigravity 双向 flexible 切换(配合 loopx-codex-provider-routing 0.15.9、reasoning_effort 容量别名与 flexible_primary_available 状态转换)及原生监控/周报回退对齐,修复 Codex API relay 请求/响应截断、回环中继 401 故障与管家主动级联 resume_failed 恢复(#9170),并在切换模型时保留 Codex 原会话历史。 #8713, #8977, #8984, #9134, #9141, #9145, #9147, #9167, #9170
  • 多 Agent 协作与飞书群聊/私聊加固。 对等体可通过 read_peer_returns 与 consume_peer_result 直接读回协作结果而无需重开 Manager Inbox,并按 Goal 批量加锁和缓存扫描;飞书连接器支持重连排队保留、只读管家快捷卡片、Turn 作用域原生图片、共享卡片回调、单趟卡片转义、国际版 Lark 配置识别及按输入重置退避。 #8668, #8695, #8741, #8871, #8921, #8990, #9027, #9085, #9114, #9117, #9119
  • Desktop App 2.4.0、dsh-loopx-plugin 0.1.1-beta.7、LooChat 工作台与远程任务网关。 Desktop App 在关闭工作区前准备更新、限制就绪探测耗时、跳过不可变发布包前端重哈希、为发布/ChatBundle 下载补齐重试,并在缓存 macOS preview 更新前核验 default_contract;dsh-loopx-plugin 0.1.1-beta.7 要求 Core 2.4.0+、兼容 DSH 0.2.2-rc.1..rc.3 与 quota_settlement_plan_v2 结案回归、在 GoalBar 暴露准入失败并隔离热卸载;新增实验性 LooChat 工作台(apps/workbench/)及远程任务网关的逐资源读 ACL 与 PostgreSQL/TLS Compose 自托管示例。 #8508, #8675, #8723, #8739, #8765, #8843, #8861, #8879, #8887, #8899, #9029, #9089, #9147

重规划修复

  • 保留重规划历史中的主动监控事项;范围内唯一任务被阻塞时等待依赖,已被替换的 heartbeat 回执在 Python 后续路径前拦截,历史 ACK 准入与写回继续绑定原回执并按 GoalRef 护栏。 #8511, #8647, #8672, #8708, #8907, #8975
  • 同秒评审后继与整秒历史 ACK 按准入后处理;Monitor 连续重规划及纯重规划 Turn 保留回执来源与精确结案命令,异常 Vision 结论保持可恢复。 #8731, #8804, #8854, #8855, #8958
  • 显式 Goal 恢复与重规划后继身份保持可恢复(含在后继重建与准入后同 Agent ACK 中保留 rearmed_after_obligation_id,#9118),温增量与已保存 C1 重规划绑定原捕获摘要,原生 captured_decision 重规划首屏继续内联保留绑定的 Yardstick 反转线索(nativeReplanPresentation),scoped_user_gate_fallback 将就绪 deferred_successor_replan 生命周期重规划排除出执行租约准备检查(#9168),重规划恢复限制在投影边界内(含 projected_ack 写回与 monitor_poll lease_proof),零效应监控与已清理重规划的管家报告可恢复。 #8923, #9016, #9022, #9046, #9118, #9143, #9160, #9165, #9168

升级决策

谁需要升级: 在 Chat 创建 Goal 或检索原消息、使用桌面端或已安装工作台恢复任务、依赖管家监控/PR 合并确认/双向切换/飞书收发的用户可优先升级;dsh-loopx-plugin 0.1.1-beta.7 用户必须同时使用 LoopX 2.4.0 及以上版本。仍有脚本编辑旧 registry 暂停状态的团队需先迁移调用。

解决了什么: 把 Goal 创建和打开会话收敛到一次确认,改善已载入会话检索、原任务/回执恢复与多 Agent 结果读取,并补齐管家探针监控、精确 Head PR 合并确认、私聊独立长期记忆、Codex/Antigravity 双向容灾、Desktop 预览校验、飞书队列与 DSH 0.2.2 兼容性。

是否有破坏性变更: 有。Registry 停用旧 status: paused/stopped,暂停与恢复统一使用 activation.state 和 Goal lifecycle 命令并支持备份迁移(#8431);未通过验收的压缩工作记忆实验已退役(#8928);dsh-loopx-plugin 0.1.1-beta.7 要求 LoopX 2.4.0 或更新版本(#8899)。普通未托管 JSON quota should-run 继续维持 quota_packet 公开默认(#9084)。

如何验证: 确认版本为 2.4.0 与 loopx doctor 所属环境正常,打开既有 Goal 与原任务或在 Chat 确认新草稿,并确保迁移后的只读检查命令通过。

贡献者: 发布维护者 @huangruiteng 与下文列出的 22 位社区贡献者(其中 9 位首次获合并)。 社区贡献者

状态内核与控制面

  • 恢复原 Turn、扣额身份和已准备或惰性重绑定的硬租约护栏(--task-lease-idempotency-key / --task-lease-expected-version,含 .validation-recovery. / .admission-retry 与 monitor_poll lease_proof)时仅在仍需有效租约时按需重绑定、保持已提交 Turn 重放与已退役租约结案恢复不被破坏(#9183),并继续核对新选择的门禁;已声明完整 v1 适配层与独立验证器的首次 generic-cli Turn 自动准备缺失租约(#9047),已结算的 C1 Turn 禁止再次获取原生 Codex 租约,quota_result_delivery 在传输失败时保留 host_poll_receipt 诊断而不提前写入 capture_sha256,检查点重定位的账务制品读取(readQuotaSpendEventFromRun)安全约束在当前 runs 目录内,已验证的无 Todo 原 Turn 可读取自身回执避免重复扣额。 #8860, #8894, #8900, #9047, #9097, #9111, #9157, #9158, #9160, #9161, #9183
  • Complete Turn(loopx_turn_envelope_v1)与原生宿主调用方组合运行时拥有的 quota_settlement_plan_v2(--settle-turn --settlement-receipt),将 quota_spend 保留为 ordered_steps 中的 runtime 步骤、将无状态捕获读取选择交回 TypeScript context_select owner(#9142)并对齐显式 --capture-dir 与分段 context-read 读回(#9154、#9158、#9160);配额轮询保留显式 Monitor Todo 选择(#9099)、通过签名车道引用校验门禁作用域(#9101)、在 registry_codec 中延后备份预映像的目录同步导入以保持适配层测试隔离(#9161)、按需延迟加载大体积写入作用域并在重叠长认领下保留就绪控件(#9078、#9086、#9106)、在 Vision 后继重建与准入后同 Agent ACK 中保留 rearmed_after_obligation_id(#9118);普通未托管 JSON quota should-run 在 RFC §9 验收前保留 quota_packet 公开默认,并退役旧版心跳工作提示生成。 #8489, #8956, #9000, #9030, #9054, #9057, #9078, #9084, #9086, #9099, #9101, #9106, #9118, #9142, #9154, #9158, #9160, #9161
  • 普通 Todo 修改保留兼容声明;新字段需要新版读取器时,归档回退先校验目标版本能否读取 Todo、在 POSIX 上原子回退 CLI 与归档托管 loopx-apply-rrule 两个启动器(#9007)、沿用自定义安装与发行目录(#9066),失败则保留当前运行时与数据。 #8902, #8906, #9007, #9066
  • 存储导入沿已注册源执行并与 registry 写方串行核对,已采用 canonical authority 的 Goal 无需冷导入;安装环境恢复沿用原租约和回执,refresh-state 支持内联 JSON,spend-slot 新增 --delivery-workspace-path,跨仓库绑定错误说明更清晰。 #8615, #8707, #8827, #8864, #8926, #8933
  • 多 Agent 协作支持通过 read_peer_returns 与 consume_peer_result 直接读回对等体结果而无需重开 Manager Inbox,交接查询按 Goal 批量加锁并缓存历史与终态扫描,阻断跨 Goal 误投递并允许单 Agent Goal 由 owner 关闭精确关联门禁。 #8644, #8779, #8803, #8844, #8846, #8853, #9027, #9085, #9088, #9117
  • PostgreSQL 支持超过 20,000 条提交历史的 checkpoint 备份和恢复;远程任务网关支持完整生命周期、按活跃 Goal 授权的只读 ACL 及 PostgreSQL/TLS Compose 自托管部署包。 #8508, #8759, #8765, #8861, #8887

能力与工作流

  • 个人工作台与研究连续性: 打包工作台交付一次确认创建 Goal、已载入消息搜索、手机端窄屏会话标题自然换行(#9121)、审阅材料键盘焦点恢复、截断记录披露及 Todo 分页读回;桌面与飞书通道下可保留并恢复原研究答案、中断回答、失联 worker 诊断、派发前请求、案例链接与清晰引用 Markdown。 #8676, #8780, #8863, #8868, #8880, #8892, #8913, #8954, #8959, #8962, #8983, #9120, #9121, #9125
  • 管家通用监控、精确 Head PR 审查与受保护合并: 用户成果为在私聊管家统一承接自然语言 continuous_monitor、作用域隔离 GitHub PR 信号监控聚合与 App/飞书 chat_root 单篇直达汇报(#9182)、精确 Head PR 审查判定与 /confirm 受保护合并;已交付 steward_managed_mode.ts、github_pr_evidence.py、steward_pr_merge.py 与 steward_monitor.py,并补齐推进证据有界化、一次提交前重试、主结果分离的自治重规划内联结算及宿主演前 deferral 重试(#9187, #9188, #9191)、跨 Python 升级的周报选择与冻结/已停止报告候选恢复(含 host_candidate.py 轻微 JSON 分隔符容错 #9164)、观察监控队列防误杀、失败取消及跨端点派发前恢复(含回执检索降噪 #9159);最终合并仍需明确授权与精确 Head 一致性。 #9074, #9077, #9081, #9093, #9143, #9155, #9157, #9159, #9164, #9182, #9187, #9188, #9191
  • 独立 OpenViking 管家长期记忆(steward_memory): 用户成果为在本人私聊管家按说话人隔离召回与记忆偏好而不外泄到群聊、项目对话或 worker 进程;已交付默认关闭的 steward_memory 机器配置命名空间、TS 策略/规范化 owner、宿主适配与环境剥离;默认关闭且需由操作者在宿主环境配置 OpenViking 凭据。 #9083
  • LooChat 工作台(试验): 将 Calli 工作台迁入 apps/workbench/(@loopx/loochat)提供可选会话层、跨目录本地会话发现与可恢复显式导入目录(LOOCHAT_HIDDEN_SESSION_DIRS)、Goal 页面与 /api/loopx/* 代理;自动推进仍由 LoopX Core 负责。 #8843, #9063, #9113
  • 材料分波排序与实验退役: 材料生命周期提供无状态分波排序预览(plan-wave-rerank),应用排序仍需材料 owner 授权;Yardstick 延迟至显式启用,空队列不再进入普通 Worker 上下文,未通过验收的压缩工作记忆实验已退役(旧配置保留兼容读取且不生效)。 #8579, #8928, #9034, #9059, #9060

质量与测试

  • SQLite 回归矩阵覆盖落后消费者、备份 lineage、并发 CAS/响应丢失重试以及 SQLITE_FULL / 真实 macOS ENOSPC 磁盘满 fail-closed 与恢复。 #8367, #8482, #8498, #9126
  • 控制面、配额、Lark、奖励记忆、基准与领域包消除 Any 并建立基线护栏,大体积 CLI、issue-fix 与 Lark/Chat 模块完成拆分(含内部 loopx/chat/ typed action 分组 #9056),及时回收已通过与只读的 pytest 临时目录树(#9070, #9189),补齐 C1 规划/交付/结算与 UTF-8 传输/扩展/工作台回归,加固 CLI help 目录、架构导入守卫与新手引导选标门禁,精简冗余示例,并使 doctor 升级读回绑定所属 Python 环境。 #8013, #8897, #8933, #8940, #8971, #8994, #9009, #9044, #9056, #9070, #9102, #9104, #9152, #9154, #9156, #9158, #9160, #9161, #9189
  • 加固 base/head CLI 差分与预算基线隔离(#8948、#9103)、外部等待宿主提示词探针走完整 C1 输入(#8981)、canary 对等运行时检查正确识别 controller 归属(#9092)、统一展示与公开输出边界对本地路径 URL 与 path: 的判定(#9080,并在 #9190 保留行内代码根路径示例与同步 DSH 插件观察器规则)、runtime snapshot 默认契约校验、canary 超时诊断与 Git 原始路径保留,并沉淀本地优先验证规范与公开 smoke 门禁修复(#9152),同时支持 --max-workers 并发真实模型行为评估、深路径重规划上下文恢复的 8 KiB 宿主工具错误输出上限、对齐摘要消费者清单、多 Goal 引导 smoke 契约与 test_effect_turn_live_quota_decision 独立导入(#9168)、修复 --settle-turn 视觉结案回执读取及 creation_allowance 测试唤醒竞态(#9178),并实现按需惰性重绑定恢复租约以保全已提交 Turn 重放与已退役租约结案恢复、收敛 goal-frontier 投影可维护性圈复杂度(#9183)以及修复非托管飞书轮询清理与 generic-cli 独立校验器租约门控(#9190)并收敛 pytest 目录发现、并发默认真实模型评估与单波干净检出分片验收(#9193)。 #8426, #8645, #8919, #8922, #8948, #8952, #8981, #9001, #9018, #9040, #9080, #9092, #9103, #9152, #9168, #9178, #9183, #9190, #9193

基准与集成

  • Antigravity、Codex 与管家执行器路由: 外部 Host 可显式使用 --complete-turn 与摘要绑定 context-read;管家配置新增 Antigravity Carbon(gemini-4-carbon-{high,medium,low},默认仍为 Argon)、每端点 endpoint_models JSON 模式偏好说明、Codex 与 Antigravity 双向 flexible 容灾切换(配合 loopx-codex-provider-routing 0.15.9、reasoning_effort 容量别名与 flexible_primary_available 状态转换)及回退路径的原生监控/周报支持,同时修复 Codex API relay 请求/响应截断与回环中继 401 恢复、管家主动级联 resume_failed 恢复与纯思考错误循环有界处理(#9170)、Codex 模型切换历史保留、UTF-8 输出解码、静默完成回执、失败重试 Session 适配器保留及受管观察锁交接(#9167)。 #8454, #8485, #8489, #8713, #8874, #8977, #8984, #9130, #9134, #9141, #9145, #9147, #9167, #9170
  • 飞书群聊与私聊加固: 私聊反馈不阻塞主回复,重连保留排队消息,提供只读管家快捷卡片,支持 Turn 作用域原生图片与历史图片恢复、mention 定向回原冻结 Turn、查询与操作卡片共享回调分发、单趟卡片文本转义、国际版 Lark URL 识别、监听快照合并与恢复缓存,并在输入变化时重置空转退避。 #8270, #8668, #8695, #8741, #8858, #8870, #8871, #8893, #8903, #8921, #8990, #8999, #9041, #9096, #9098, #9100, #9114, #9119
  • Desktop App 2.4.0 与 dsh-loopx-plugin 0.1.1-beta.7: Desktop App 在关闭工作区前准备更新、限制就绪探测耗时、先打开可用工作区、跳过不可变版本前端重哈希、为 chat_bundle.py 与桌面发布/更新工作流增加下载重试(#9147),并在缓存 macOS preview 更新前核验签名包里的 default_contract;dsh-loopx-plugin 0.1.1-beta.7 兼容 DSH 0.2.2-rc.1..rc.3、对齐 quota_settlement_plan_v2 集成结案测试(#9147)、在 GoalBar 展示准入失败、隔离热卸载、保持替代后取消/错误暂停归属、用来源指纹保护 Start/Pause 并支持 Windows 原生路径。 #8504, #8675, #8723, #8739, #8879, #8899, #9029, #9087, #9089, #9147
  • Windows 与基准工具(不宣称长程净收益): Windows 修复 PowerShell 引号、错误载荷上限、文件身份核对及本地 NTFS loopx-jev 捕获;基准工具新增初始规划批写入(benchmark.runtime.planning_batch)、空闲边界 staged CLI 切换预览、单 worker 回合提取、Codex 恢复、Frontier 共享时钟,并恢复冻结 v1 归档与独立 benchmark/ 导入边界(#9151)。本版本不宣称可比长程任务结果或完整成本净收益。 #8499, #8501, #8599, #8620, #8641, #8643, #8761, #8875, #9031, #9090, #9151

文档与兼容性

  • 新增日文 README 并接入现有公开阅读入口,同步更新多份双语 RFC 与 bootstrap/审计文档。 #8839, #9035, #9113
  • dsh-loopx-plugin 0.1.1-beta.7 需要 Core 2.4.0 及以上版本的原 Turn quota receipt 读取能力,支持 DSH 0.2.2-rc.1..rc.3。Core、Desktop App 与插件各自发布并核对支持矩阵,升级 Core 不会自动发布或升级插件包。 #8879, #8899
  • 普通未托管 JSON quota should-run 继续保持 quota_packet 公开默认;macOS 桌面 preview 更新前会核对签名归档中的 default_contract。 #8952, #9018, #9029, #9084
  • 用 loopx authority-archive upgrade --all-known --require-current 检查旧暂停字段;需要迁移时,获授权的 registry owner 可执行 loopx authority-archive upgrade --all-known --execute 并保留返回的备份路径。字段冲突时保持停止,交由 owner 核对。 #8431
  • 新增独立 loopx-core wheel 构建候选(packages/loopx-core/),支持无工作台环境的 CLI 与 TS 运行时安装,不改变普通 loopx 默认包。 #8615, #8830, #8840

社区贡献者

  • @2430468136(首次获合并) — 统一报告 schema、可见范围与测试字段的 owner。 #8629, #8832, #8833
  • @BigDataDZ — 处理 Windows 来源租约时钟偏差,固定租约清单排序。 #8761, #8762
  • @cf3901646(首次获合并) — 在 authority store 状态诊断中呈现底层 SQLite 错误。 #8459
  • @cocolord — 迁移旧 Goal 暂停元数据、交付一次确认创建 Goal、支持声明完整 v1 的首次 generic-cli Turn 自动准备缺失租约并将无状态捕获选择委托给 TypeScript owner、完成独立 Core 打包与安装环境 Manager 发现、分组内部 Chat action 模块并及时回收已通过 pytest 临时目录、退役压缩工作记忆实验、延迟 Yardstick 与基准发现,并完善重规划/研究/验收路径。 #8372, #8374, #8431, #8433, #8443, #8456, #8466, #8474, #8478, #8481, #8531, #8544, #8545, #8565, #8578, #8582, #8590, #8615, #8624, #8652, #8658, #8661, #8665, #8669, #8671, #8673, #8686, #8687, #8691, #8699, #8736, #8738, #8740, #8743, #8744, #8746, #8747, #8749, #8764, #8769, #8774, #8777, #8780, #8788, #8790, #8792, #8793, #8795, #8798, #8802, #8805, #8807, #8813, #8818, #8820, #8821, #8822, #8824, #8830, #8840, #8846, #8872, #8915, #8928, #9034, #9047, #9056, #9059, #9060, #9070, #9072, #9073, #9142
  • @Duang777 — 拒绝异常额度时钟与非法日历时间,保留同秒恢复,处理截断的多字节历史行,按 GoalRef 护栏历史 ACK 准入与写回,加固入站/迁移/glob/botmux 校验,并在输入变化时重置飞书空转恢复退避。 #8371, #8632, #8679, #8680, #8681, #8682, #8683, #8684, #8731, #8804, #8907, #8975, #9119
  • @eltociear(首次获合并) — 新增日文 README,并接入已有公开入口。 #8839
  • @gcl-coder — 让 Issue Fix、canary、Integration Branch 和 Change Quality 保留准确的 Git 路径,统一展示与公开输出边界的本地路径判定,并在 Python 后续路径拦截被替换的 heartbeat 回执。 #8426, #8429, #8558, #8585, #8603, #8645, #8647, #8678, #9080
  • @GZY-SUPER-HACKER — 按 UTF-8 读取 Codex App CLI 输出。 #8485
  • @hhyykk — 避免重复扫描 Explore 时间线,修复 CLI/宿主/飞书/打包契约与过期 canary 检查,加固运行时清理,并修正 bootstrap 指引与代码审计发现。 #8733, #8737, #8985, #9113
  • @Jim-jimu — 保留 Mermaid 节点身份,新增带认证的远程任务命令。 #8370, #8508
  • @LIHUA919 — 覆盖 SQLite 消费、lineage、并发 CAS 与磁盘满 ENOSPC 恢复边界,清理无用工作台 UI 键,拒绝被替换的 heartbeat 回执,并实现 Goal Channel 卡片单趟文本转义。 #8367, #8414, #8482, #8498, #8708, #9114, #9126
  • @Luoluoluo0110(首次获合并) — 统一 issue 关闭事件、project ID 规则和 backlog 条目语法。 #8636, #8637, #8638
  • @lurenxiao1998(首次获合并) — 在重规划历史中保留主动监控。 #8672
  • @maxliux5 — 将 Calli 工作台迁入 apps/workbench/,作为连接 LoopX Goal 对话的实验性 LooChat 会话层并支持跨目录本地会话发现。 #8843, #9063
  • @mojunzi(首次获合并) — 让 owner 可以收口单 Agent Goal 中精确关联的用户门禁,并识别国际版 Lark 配置 URL。 #8844, #8871
  • @psychologister(首次获合并) — 将召回摘要与 Issue-Fix 维护者/评审词汇交回对应的 canonical owner。 #8611, #8613, #8826
  • @Seyamalam(首次获合并) — 修复 Issue-Fix 的评审协议链接,并将宿主选择、门禁 item_patch 与心跳提示 smoke 固定到现行契约。 #8834, #8867, #8951, #8996
  • @songoow — 提出基于 billion-context 研究的上下文策略。 #8453
  • @steven-kid — 尊重 Turn 计划 Markdown 详情请求、呈现 Host 失败证据,并支持检索已载入对话中的原消息。 #8449, #8642, #8676
  • @xiaobaifly7 — 保留依赖等待与硬暂停、算力门禁和监控与门禁边界;修复 Codex/Todo/change-window/content-ops/JEV 的 Windows 兼容与空闲运行时退出;并在 dsh-loopx-plugin 补齐 Windows 原生续跑与调度周期支持。 #8504, #8510, #8511, #8517, #8520, #8521, #8533, #8576, #8577, #8580, #8581, #8583, #8584, #8598, #8599, #8600, #8609, #8618, #8620, #8697, #8770, #8854, #8855, #8876
  • @xyx2002OvO — 恢复质量门禁 Any 上限与工作区契约,修复 Windows 固定入口结算命令引号,并控制错误载荷大小。 #8013, #8641, #8643
  • @ZaynQuinn(首次获合并) — 保留 Codex App 静默完成回执。 #8454

可选能力启用与使用

Remote task gateway

启用: 从源码检出准备合格的 Node、npm ci --ignore-scripts、隔离 PostgreSQL authority schema、受限角色、服务策略与 TLS 证书,运行服务示例(或使用 examples/coordination/remote-authority-compose 自托管 Compose 部署包)。调度器观测另需在某个已注册 Goal 显式设置 remote_authority.enabled: true,绑定 HTTPS origin、已核验的 tenant 和 store identity、授权 Agent、既有 probe Todo 和所需私有 CA。 #8508, #8765, #8887

验证: 用示例客户端和已准备的 command.json 读取既有操作回执。通过 quota should-run 查看当前 Goal 的远程只读观测。

停用 / 回退: 在该 Goal 设置 remote_authority.enabled: false。停止监听器并撤销访问授权可停用服务。PostgreSQL 保留已写回执。

权限边界: 远程写入由受限 principal、数据库角色和策略控制。Host 观测提供只读输入。逐资源只读 listener 选择 loopx_remote_authority_scoped_read_policy_v1,精确授权 Goal lifetime、Todo 与接收者,并提供原创建或首次采用回执;缺少来源证明时保持不可用。该 listener 拒绝写命令,不返回自由文本、租约密钥或全局 provider revision。移除对应 grant 或 ACL 项可撤销后续准入,继续遵循本地准入、Stop 和额度约束。 #8861

文档: 远程任务网关

node --experimental-strip-types examples/coordination/remote-authority-service.ts \
  --policy "$SERVICE_POLICY" --cert "$TLS_CERT" --key "$TLS_KEY" --host 127.0.0.1 --port 8443
# 另在受授权的客户端环境私下加载服务凭据后执行:
node --experimental-strip-types examples/coordination/remote-authority-client.ts \
  --endpoint "$SERVICE_HTTPS_ORIGIN" --ca "$TLS_CA" --recover < command.json
loopx --format json quota should-run --goal-id "$LOOPX_GOAL_ID" --agent-id "$LOOPX_AGENT_ID"

Complete Turn context for external hosts

启用: 可消费完整 v1 契约(loopx_turn_envelope_v1 与运行时拥有的 quota_settlement_plan_v2)的外部 Host 在 JSON quota should-run 上显式传入 --complete-turn,提供新的 Turn ID 和可写捕获目录。不传 Complete Turn 或宿主标志的普通 JSON quota should-run 继续返回 quota_packet。 #8489, #8956, #9084

验证: 在本次决策或保存的捕获中确认 loopx_turn_envelope_v1 与 quota_settlement_plan_v2,完成其必读 Goal/上下文,并沿同一 Turn 的执行和单命令结算契约(--settle-turn --settlement-receipt)推进。如返回分段导航,使用随决策返回的固定 reader,核对原摘要和 Turn 身份。

停用 / 回退: 后续请求省略 --complete-turn,恢复原 quota_packet 上下文路径。原捕获保留原摘要绑定的读取命令。

权限边界: 继续遵循本次 Goal、Agent、准入、权限、硬租约护栏、必读内容和 Stop 条件。

文档: Turn envelope

loopx --format json quota should-run --goal-id "$LOOPX_GOAL_ID" \
  --agent-id "$LOOPX_AGENT_ID" --turn-instance-id "$LOOPX_TURN_ID" \
  --complete-turn --decision-output-dir ./complete-001

reader 的 JSON Pointer 指向捕获 JSON 内的字段,不是文件路径。将返回的当前 reader 引用赋给 CAPTURE_READER 后可目录查看或选读;读取当前捕获不要求先读旧差分基线,也不需要重新准入。

loopx --format json quota context-read --reference-file "$CAPTURE_READER" --list --list-depth 2
loopx --format json quota context-read --reference-file "$CAPTURE_READER" --select /selected_todo

选中的 Todo 只占契约的一部分。工作前仍需读取适用的 Goal 要求、限制与必读来源;压缩或恢复后保留原 Turn、capture 和结算身份。仅用于诊断的恢复结果不授予执行权。

Material wave rerank preview

启用: 向 plan-wave-rerank 提供有序材料引用与准确读取后形成的标注(按命令单次启用,无持久开关)。 #8579

验证: 检查预览中的排序建议、受保护项和输入覆盖范围。

停用 / 回退: 停止调用或丢弃预览。若另经授权应用过,以原变更回执走材料生命周期回退。

权限边界: 预览是无状态的。应用或回退需要材料 owner 授权并核对当前 revision。

文档: 材料生命周期

loopx material-lifecycle architecture --format json
loopx material-lifecycle plan-wave-rerank --input request.json --format json

Private Lark conversations

启用: 已获授权的本地安装可按需安装并启用内置 loopx-lark,然后在工作台的 Lark 设置中用已获授权的账号绑定私聊来源(支持国内飞书与国际版 Lark 配置链接)。 #8871

验证: 读取 provider doctor。用自己已配置的私聊发出获授权的测试请求,确认回复、管家快捷卡片或 Turn 作用域原生图片回到同一会话。重连后核对排队消息只出现一次并回到原会话。

停用 / 回退: 断开已配置的会话。退役本地 provider 时执行 disable,并停止还在运行的采集进程。

权限边界: 沿用既有会话绑定、provider 身份和授权范围。Steward 快捷卡片只读,群聊保持受限,图片交付沿原私聊回复范围。

文档: Lark 扩展生命周期

loopx extension install --bundled loopx-lark --execute --format json
loopx extension enable loopx-lark --execute --format json
loopx extension doctor loopx-lark --execute --format json
# 退役本地 provider 时执行:
loopx extension disable loopx-lark --execute --format json

Staged benchmark CLI activation

启用: 由已有授权的 Docker benchmark controller 将通过资格检查的源码放入版本目录,用 activate_cli_source(..., execute=False) 预览所持有的 launcher。传入精确运行身份、归档摘要、源码/原生回执和当前 Stop 回调。实际切换需明确授权并重新核对输入。 #8501

验证: 运行下方源码检出的回执读回用例。获授权的实际切换另需验证源码与 launcher,观察下一次真实 Host 输入。

停用 / 回退: 省略调用可延用当前 launcher。切换中断后用 reconcile=True 收敛原回执。在当前控制规则与源码一致性均通过时,由授权 owner 用 repair="old" 恢复旧目标。

权限边界: 空闲边界锁、Stop 与有限预算沿用原 benchmark controller。此接口作用于后续 CLI 子进程,执行需要单独授权。

文档: Host CLI 源切换

uv run --extra test python -m pytest -q tests/control_plane/test_cli_source_activation_readback.py

Private backup inspection

启用: 在 Settings → Capability Center → device defaults → Configuration backup and recovery 选择 Full archive inspection,提供原归档及匹配的外部 manifest。不支持的服务或平台保持不可用。下方 CLI 按次调用。先预览项目及所选配置范围的私有完整备份,再在现有授权内创建;保留匹配的 archive、外部 manifest 和兼容版本。 #8864

验证: 先验证文件对,再提取。只有 --execute 创建新的隔离检查目录,不激活 authority 或启动 Host;核对 included 和 missing 范围。

停用 / 回退: 停止调用或省略 --execute,已有备份继续私有保留。重装旧运行时不会撤销新版数据写入;目标读取器无法核验时保持当前运行时,后续数据操作沿原恢复 owner。

权限边界: 归档和历史租约是证据,不是新的执行授权。现代再激活另需身份、未决 effect 与准入检查;不能把旧归档直接覆盖到现用状态。

文档: 配置备份与恢复、Agent 原地升级

loopx backup-state --project "$PROJECT_ROOT" --current-project-only \
  --configuration-goal-id "$LOOPX_GOAL_ID" --no-automations --no-skills \
  --output-dir "$PRIVATE_BACKUP_DIR"
# 核对预览后,在现有授权内重复命令并加 --execute。
loopx backup-state verify --archive "$BACKUP_ARCHIVE" --manifest "$BACKUP_MANIFEST" \
  --destination "$NEW_INSPECTION_DIR"

Isolated OpenViking Steward memory

启用: 默认关闭(enabled: false)。在 Dashboard 的「设置 → 管家 → 独立 OpenViking 长期记忆」,或通过 loopx machine-config preview / apply 对 steward_memory 命名空间(steward_memory_machine_defaults_v0)设置 enabled: true、user_space、auto_recall 与 recall_timeout_seconds(1–15),并在 Chat 宿主环境私下提供 OpenViking 凭据(OPENVIKING_*)。 #9083

验证: 执行 loopx machine-config inspect --format json 核对 steward_memory 已启用与版本,再在本人已校验私聊管家中测试实质问题;确认群聊、项目对话、回答/元数据审阅和 Codex worker 子进程均被隔离且剥离了 OPENVIKING_* 环境变量。

停用 / 回退: 预览并应用 enabled: false,或通过 loopx machine-config remove / rollback 移除或回退 steward_memory 命名空间。

权限边界: 严格限定于已校验本人私聊管家(external_audience、bound_steward、private_conversation);拒绝项目对话、监控/周报/审阅回合、群聊和未验明发送者;拒绝模型侧覆写 speaker、owner、uri、user_space 等目标字段;自动从 worker 子进程剥离 OPENVIKING_*;不授予 Goal、Todo 或宿主工具权限。

文档: 管家记忆机器配置、管家记忆 TS 策略

loopx machine-config describe --format json
loopx machine-config preview --namespace steward_memory --config-json steward-memory.json --format json
loopx machine-config apply --namespace steward_memory --config-json steward-memory.json \
  --expected-plan-revision "$PLAN_REV" --execute --format json
loopx machine-config inspect --format json
loopx machine-config remove --namespace steward_memory --expected-plan-revision "$REMOVE_REV" --execute

Steward executor routing and failover

启用: 在「设置 → 管家 → 模型与执行器」(或通过 loopx machine-config 管理 steward_executor 命名空间 steward_executor_machine_defaults_v1)选择 selection_policy(preferred、pinned 或 flexible)、主 executor_endpoint(codex、antigravity 或 managed)、可选 eligible_endpoints(如 ["codex", "antigravity"])及 JSON 模式下填写并经引导保存保留的 endpoint_models(如为 Antigravity 指定 gemini-4-carbon-high)。Codex 与 Antigravity 双向容灾与 API fallback 需另行安装并启用 loopx-codex-provider-routing(0.15.9+)。 #9141, #9145, #9147

验证: 执行 loopx machine-config inspect --format json 与 loopx-codex-accounts status(若已安装),随后在本人私聊管家测试普通消息及「应用到当前对话」;核对 Carbon 档位匹配账号供给,以及主执行器耗尽后在 eligible_endpoints 内切换且回退会话正常承接监控与周报。

停用 / 回退: 将 selection_policy 切回单个 executor_endpoint 的 preferred 或 pinned,清空 endpoint_models,或用 loopx machine-config rollback 回退配置事务。

权限边界: 配置端点、模型档位或 flexible 池不保存凭据,不突破 manager_runtime 宿主工具边界,不绕过 Antigravity/Codex 原生审批,也不在未显式启用并观测到耗尽时开启付费 API。

文档: Manager runtime profile v0、原生 Codex 账号

loopx machine-config preview --namespace steward_executor --config-json steward-executor.json --format json
loopx machine-config apply --namespace steward_executor --config-json steward-executor.json \
  --expected-plan-revision "$PLAN_REV" --execute --format json
loopx machine-config inspect --format json

DSH native plugin (0.1.1-beta.7)

启用: 将 dsh-loopx-plugin 0.1.1-beta.7(要求 LoopX 2.4.0 及以上版本,支持 DSH 0.2.2-rc.1..rc.3 并保留 0.1.5..0.2.1-rc.2 兼容)通过发布 tarball 或源码安装脚本加入 DSH web 或 desktop profile,再启动 DSH(dsh --profile web --port 0 或 loopx dsh-launch web)。 #8879, #8899, #9147

验证: 执行 dsh --profile web --dump-config 核对四个插件行,在 Session 中运行 /loopx <task> 后读回唯一绑定、GoalBar 状态(continuationAdmission、Start/Pause)及 Personal Workspace 面板(需已启动本地 loopx dashboard)。

停用 / 回退: 从同一 profile 移除插件(dsh plugin --profile web remove dsh-loopx-plugin;0.1.1-beta.7 热卸载保持共享 Web 运行时在线),或用 --ignore-scripts 重装先前保留的 0.1.1-beta.6 归档包;停用 DSH 后可按需清理插件隔离运行时目录。

权限边界: 在当前实时 Session 出现明确类型的 loopx skill 调用证据及唯一 LoopX 绑定前保持静默;Core 继续拥有 Goal、Todo、配额与来源指纹 CAS 权威;插件替换保留取消责任与错误暂停状态;不授予额外模型工具或 Goal 写权限。

文档: DSH 插件说明

dsh plugin --profile web add \
  "https://github.com/loopx-project/loopx/releases/download/dsh-loopx-plugin-v0.1.1-beta.7/dsh-loopx-plugin-0.1.1-beta.7.tgz"
dsh --profile web --dump-config
loopx --registry .loopx/registry.json --format json resolve-agent-thread \
  --host-surface deepseek-harness-native --thread-id "$DSH_SESSION_ID"
dsh plugin --profile web remove dsh-loopx-plugin

LooChat workbench (experimental)

启用: 先用 --dry-run 预览 apps/workbench/install.sh(或在 apps/workbench/ 执行 npm install && npm run setup && npm run build),在 .env 配置 LOOCHAT_WORKDIRS 与 LOOCHAT_LOOPX_CORE_URL,再与独立运行的 LoopX Core 配合启动。 #8843, #9113

验证: 在本地回环或受信任 VPN 上核对 /api/health 与带 token 的 /api/loopx/healthz,登录页面确认 Goal 预览确认创建及会话绑定展示。

停用 / 回退: 停止工作台服务或执行 scripts/install-service.sh --remove / install.sh --uninstall;~/.config/loochat、~/.local/state/loochat、LoopX Core 与 loopx dashboard 保持不变。

权限边界: 仅暴露 LOOCHAT_WORKDIRS / LOOPX_GOAL_WORKSPACES 白名单目录;Goal 权限继续由 LoopX Core 判定(只读或 Codex workspace-auto);工作台本身不启停 Core 也不提供自动推进;HTTP+token 监听仅限回环或可信 VPN 网卡。

文档: LooChat 工作台说明、Agent 安装指南

curl -fsSL https://raw.githubusercontent.com/loopx-project/loopx/v2.4.0/apps/workbench/install.sh \
  | LOOCHAT_REF=v2.4.0 bash -s -- --dry-run
# 从完整源码检出构建:
npm --prefix apps/workbench install && npm --prefix apps/workbench run build

Standalone Core wheel candidate

启用: 按需从源码执行 packages/loopx-core/prepare.py,将仅含 CLI 与 TypeScript 任务运行时的独立包安装到全新虚拟环境(不含 Chat 包、前端资产或 canary)。勿与完整 loopx 包混装在同一环境中。 #8615, #8830, #8840

验证: 在新环境中运行 loopx --help、loopx doctor --installation-only --deep --format json 与只读 loopx start-goal --guided --project . --goal-text "..." 预览。

停用 / 回退: 退出或移除该隔离 loopx-core 虚拟环境,切回普通 loopx 安装环境并保留原有 Goal 与任务状态。

权限边界: 受管任务仍需 Python 3.11+ 与 Node 22.22.3+;与普通发行版共用同一套状态、租约与校验 owner,不附带模型提供方、凭据或自动执行权限。

文档: 独立 Core 包说明

uv run --extra test python packages/loopx-core/prepare.py --output /tmp/loopx-core-source
uv build /tmp/loopx-core-source --out-dir /tmp/loopx-core-dist
uv venv /tmp/loopx-core-env
uv pip install --python /tmp/loopx-core-env/bin/python /tmp/loopx-core-dist/loopx_core-*.whl
/tmp/loopx-core-env/bin/loopx doctor --installation-only --deep --format json

Benchmark initial planning batch

启用: 仅在已获授权的 loopx-planned 基准规划唤醒且规划前沿为空时按次启用:使用当前检查点的 input_digest 与验收 provider_revision 保存 PROPOSAL.json,运行 python -m benchmark.runtime.planning_batch PROPOSAL.json。 #9090

验证: 确认返回退出码 0、"status": "ready"、不重复的真实 todo_ids 及与原 input_digest 绑定的验收链接;若调用中断,用未改动的原提案文件重放恢复。

停用 / 回退: 省略 planning_batch,对已有工作、需求变更或阻塞场景继续使用普通 goal-acceptance 与 todo add 规划步骤。

权限边界: 仅复用现有公开 LoopX CLI 操作(goal-acceptance refine、todo add)并保留逐条幂等 ID,不消耗执行额度,也不授予规划唤醒之外的准入、评分或预算权限。

文档: 基准运行时指南

python -m benchmark.runtime.planning_batch PROPOSAL.json

Scoped GitHub PR signal monitors

启用: 在已绑定的私聊 App 或飞书 chat_root 管家会话中创建或更新 continuous_monitor 待办时,显式传入稳定 target_key 与 signal_scope(schema_version: "steward_signal_monitor_scope_v0"、include_portfolio、include_inbox 及可选 pr_filter 条件,如 exclude_drafts、exclude_conflicting、effective_verdicts、required_approver_declarations、author_mode/authors、min_stalled_hours)。 #9074, #9182

验证: 确认作用域已写入 steward-monitors/<goal_id>/scopes/<target_key>.json,StewardMonitor 对每个监控独立聚合并按精确 session_id / chat_root 投递单篇可读汇总(steward_monitor_report_delivery_v0),互不串扰唤醒。需注意在更新既有监控待办的 signal_scope 时必须附带非空的待办字段修改(如摘要、周期或 stop_condition),仅改作用域而不改待办本体会按现行基线返回 Todo update requires a non-empty patch。

停用 / 回退: 在管家对话中暂停或停止对应监控待办(pause / stop),或在 CLI 将该待办状态切离 open(loopx todo update --goal-id "$LOOPX_GOAL_ID" --todo-id "$MONITOR_TODO_ID" --status blocked 或 deferred / done),随后通过 loopx todo list --goal-id "$LOOPX_GOAL_ID" 读回确认状态不再为 open 且停止到期轮询。切勿通过删除 steward-monitors/<goal_id>/scopes/<target_key>.json 替代停用——对仍处于 open 的监控删除作用域文件会使其回退为无过滤默认观察范围;按上述方式暂停/完成后,作用域与快照文件会保留以供后续恢复。

权限边界: steward_managed_mode.ts 对未知 signal_scope / pr_filter 字段 fail-closed 拒绝;GitHub 外部探针仅只读采样且异常时不覆盖最近已核验哈希;报告严格投递到精确绑定的 session_id / chat_root,不授予仓库写或 PR 合并权限。

文档: 管家监控控制器、管家受控模式

loopx todo list --goal-id "$LOOPX_GOAL_ID"
cat "$LOOPX_RUNTIME_ROOT/steward-monitors/$LOOPX_GOAL_ID/scopes/$MONITOR_TARGET_KEY.json"
loopx todo update --goal-id "$LOOPX_GOAL_ID" --todo-id "$MONITOR_TODO_ID" --status blocked
loopx todo list --goal-id "$LOOPX_GOAL_ID"

发布验证

  • 软件包版本与标签为 2.4.0 / v2.4.0。先确认当前安装渠道已提供该版本,再升级并读回相同 Goal 与原任务。
  • File/SQLite 的普通写入兼容、原回执与租约记录、quota_packet 公开默认兼容以及实际新字段的旧版拒读分别核对。隔离备份的历史读回不等于现代 Goal 恢复执行。
  • 最终干净 commit/tree/version/tag、完整打包页面、原生 Host、Desktop App 2.4.0 平台制品、dsh-loopx-plugin 0.1.1-beta.7 包发布、真实模型、个人飞书图文及公开渠道验收沿发布契约分别记录。此用法文档不替代这些结果。
  • 本版列出可靠性和工作流改动,不宣称已获得可比长程任务的净效果提升。

版本源码范围