Skip to content

Releases: huangruiteng/loopx

LoopX v0.1.8

Choose a tag to compare

@huangruiteng huangruiteng released this 04 Jul 08:57
c0c3fd0

Summary

LoopX v0.1.8 promotes deterministic agent onboarding and host-loop activation to the stable channel.

The main change is small but important: a new agent host should no longer guess whether codex means Codex App or Codex CLI. Hosts can now ask LoopX for the canonical agent type catalog, pass an exact runtime such as codex-app, codex-cli, or claude-code, and receive the matching host-loop activation contract.

Highlights since v0.1.7

  • Added loopx agent-onboard --list-agent-types and loopx agent-onboard --agent-type ... as the deterministic onboarding interface for host runtimes.
  • Ambiguous values such as codex now fail closed with concrete suggestions instead of silently falling into the wrong activation path.
  • /loopx <task> command packs now explicitly require host-loop activation after todo writeback: Codex App heartbeat automation, Codex CLI visible /goal <task_body>, Claude Code native /loop, or a declared custom host loop.
  • Bootstrap command packs now include a host_loop_activation packet and a low-cost recheck policy so normal ticks do not redo onboarding every turn.
  • README and protocol docs now distinguish command entry from the underlying loop driver, especially for Codex CLI TUI users.
  • Added focused smoke coverage for agent type routing, ambiguous-input rejection, and Codex CLI host-loop activation output.

Update

Existing users can update from the stable channel:

loopx update --check
loopx update --execute
loopx doctor

After updating, refresh host command entries if needed:

loopx slash-commands --install

New hosts can inspect the exact runtime catalog:

loopx agent-onboard --list-agent-types
loopx agent-onboard --agent-type codex-cli --project .

Compatibility notes

  • Existing LoopX CLI commands remain compatible.
  • Codex App and Codex CLI are intentionally separate agent types because their loop activation mechanisms differ.
  • codex is intentionally rejected as an agent type; use codex-app or codex-cli.
  • Codex CLI cannot be considered connected by registry/quota identity alone; after todo writeback it must have /goal <task_body> active or show the exact pasteable gate.

Validation

  • python3 examples/control_plane/agent-onboard-host-loop-activation-smoke.py
  • python3 examples/release/release-version-contract-smoke.py
  • python3 examples/release/release-readiness-doc-smoke.py
  • python3 -m py_compile loopx/__init__.py loopx/host_loop_activation.py loopx/agent_onboarding.py loopx/bootstrap_command_pack.py loopx/slash_commands.py loopx/slash_command_install.py loopx/cli_commands/starter_bootstrap.py loopx/cli.py examples/control_plane/agent-onboard-host-loop-activation-smoke.py
  • python3 -m loopx.cli --format json agent-onboard --agent-type codex --project . returns code 2 with codex-app / codex-cli suggestions.
  • python3 -m loopx.cli --format json agent-onboard --agent-type codex-cli --project . --goal-id loopx-meta --task-text 'demo task'
  • python3 -m loopx.cli --format json bootstrap-command-pack --project . --host-surface codex-cli-tui --goal-id loopx-meta --goal-text 'demo task'
  • python3 -m loopx.cli --format json version reports 0.1.8.
  • git diff --check
  • python3 -m loopx.cli check --scan-path ... public boundary scans were clean.

loopx check reported the pre-existing loopx-meta duplicate-index warning; it is unrelated to this release. No GitHub Actions checks were reported for the release PRs.

LoopX v0.1.7

Choose a tag to compare

@huangruiteng huangruiteng released this 04 Jul 04:58
d4f0bf7

Summary

LoopX v0.1.7 promotes the command-entry integration layer to the public stable channel at commit d4f0bf7.

This release is mostly about making the supported "how do I invoke LoopX from my agent host?" path explicit and less magical. Codex does not currently support native custom slash commands, so LoopX now installs explicit Codex command-facade skills such as $loopx instead of pretending /loopx is a native Codex command. Claude Code receives matching skill entries, and the richer LoopX workflow skills stay available for implicit project, PR, doc, social, and self-repair behavior.

Highlights since v0.1.6

  • Command-entry install is now a first-class layer: loopx slash-commands --install installs LoopX-managed command facades for Codex and Claude Code.
  • Codex command facades are explicit-only (allow_implicit_invocation: false), while workflow skills such as loopx-project, loopx-pr-review, loopx-doc-registry, and loopx-self-repair remain implicitly invokable when the task matches them.
  • Legacy LoopX-managed Codex prompt shims are retired during install, while user-owned or unrelated files are left alone.
  • README and setup docs now describe the real Codex path: install/connect, then use $loopx <complex task> or /skills; native /loopx remains a future host capability, not a current Codex feature.
  • Auto-research and visible-pane startup continued to improve: bootstrap contracts, visible wake readiness, todo index projection, and live pane startup were tightened.
  • Control-plane read models were extracted for status, active state metadata, global registry health, usage, event ledger, decision freshness, handoff, attention items, todo summaries, and replan obligations.
  • SkillsBench and benchmark operations got safer fail-fast behavior for setup stalls, verifier watchdog coverage, missing-score attribution, and release packaging coverage for the runtime package.

Update

Existing users can update from the stable channel:

loopx update --check
loopx update --execute
loopx doctor

If you want to refresh host command entries after updating, run:

loopx slash-commands --install

New users can install from the stable channel:

curl -fsSL https://raw.githubusercontent.com/huangruiteng/loopx/main/scripts/install-from-github.sh | bash
export PATH="$HOME/.local/bin:$PATH"
loopx doctor

Compatibility notes

  • Existing LoopX CLI commands remain compatible.
  • Codex users should use $loopx <task> or select the LoopX skill through /skills; Codex native custom slash commands are not available today.
  • Claude Code skill entries are installed by the same command-entry installer; deeper Claude hook/adapter installation remains opt-in where applicable.
  • The stable ref is expected to point at the v0.1.7 release commit after promotion.

Validation

  • python3 -m compileall -q loopx
  • python3 examples/release/release-version-contract-smoke.py
  • python3 examples/release/release-readiness-doc-smoke.py
  • python3 examples/slash-command-install-smoke.py
  • python3 examples/slash-command-catalog-smoke.py
  • python3 examples/claude-install-optin-smoke.py
  • python3 examples/release/codex-cli-no-clone-release-verification-smoke.py
  • python3 examples/fresh-clone-quickstart-smoke.py
  • python3 examples/loopx-update-smoke.py
  • python3 examples/install-local-smoke.py
  • python3 examples/cli-help-manpage-smoke.py
  • python3 examples/canary/canary-promotion-readiness-smoke.py --no-write-evidence
  • git diff --check
  • PYTHONPATH=. python3 -m loopx.cli --format json check --scan-path README.md --scan-path docs/ --scan-path examples/ --scan-path loopx/slash_command_install.py --scan-path skills/

loopx check and the promotion canary reported the pre-existing loopx-meta duplicate-index warning; public/private boundary scans were clean. The promotion canary skipped dashboard browser checks because local dashboard npm dependencies were unavailable, matching the existing optional dashboard skip behavior.

LoopX v0.1.6

Choose a tag to compare

@huangruiteng huangruiteng released this 03 Jul 09:07
1e3df9d

Summary

LoopX v0.1.6 promotes the latest stable control-plane fixes from main to the public stable channel at commit 1e3df9df.

This release is a fast follow after v0.1.5. It focuses on making visible long-running work easier to start, easier to route across agents, and safer to validate through the release path.

Highlights since v0.1.5

  • Auto-research startup is more visible and easier to trigger: one-click start entry, question contract entrypoint, visible wake acceptance, and public readiness notes.
  • Decentralized/multi-agent operation is clearer: A2A driver contract, multi-agent wake prompt, pane-local tick rounds, and runtime-driver hints in help/manpage.
  • Monitor and scheduler behavior is steadier: monitor cadence is respected in scheduler backoff, and explicit next action now takes precedence over monitor repair noise.
  • Codex CLI first-run release path is tighter: loopx commands now exposes the full first-run verification command set while top-level loopx --help stays compact.
  • SkillsBench app-server flow is safer for goal prompts and bridge-only baselines.
  • Canary and release readiness coverage improved through organized control-plane/canary smokes, product capability smokes, and the public release timeline.

Update

Existing users can update from the stable channel:

loopx update --check
loopx update --execute
loopx doctor

New users can install from the stable channel:

curl -fsSL https://raw.githubusercontent.com/huangruiteng/loopx/main/scripts/install-from-github.sh | bash
export PATH="$HOME/.local/bin:$PATH"
loopx doctor

Compatibility notes

  • Existing commands remain compatible.
  • loopx --help remains a compact start surface and points users to loopx commands for the grouped command reference.
  • loopx commands now includes codex-cli-bootstrap-message, codex-cli-tui-bootstrap-smoke-bundle, and codex-cli-visible-attach-acceptance for the no-clone Codex CLI first-run route.
  • Known update-check limitation: loopx update --check is still freshness-based. If a very recent v0.1.5 snapshot reports no update needed, run loopx update --execute to force a refresh to v0.1.6.

Validation

  • python3 -m py_compile loopx/*.py loopx/cli_commands/*.py
  • python3 examples/release/release-version-contract-smoke.py
  • python3 examples/release/release-readiness-doc-smoke.py
  • python3 examples/loopx-update-smoke.py
  • python3 examples/fresh-clone-quickstart-smoke.py
  • python3 examples/release/codex-cli-no-clone-release-verification-smoke.py
  • python3 examples/canary/canary-promotion-readiness-smoke.py --no-write-evidence
  • python3 examples/codex-cli-first-run-rehearsal-smoke.py
  • python3 examples/codex-cli-tui-bootstrap-smoke-bundle-smoke.py
  • python3 examples/codex-cli-proof-capture-demo-fixtures-smoke.py
  • git diff --check
  • PYTHONPATH=. python3 -m loopx.cli --version
  • PYTHONPATH=. python3 -m loopx.cli --format json check --scan-path README.md --scan-path docs/ --scan-path examples/ --scan-path loopx/help_surface.py
  • isolated temporary-HOME install from stable, followed by loopx --version and loopx doctor

Note: loopx check reported the pre-existing loopx-meta duplicate-index warning; public/private boundary scans were clean. The promotion canary skipped dashboard browser readiness because local dashboard npm dependencies were unavailable, and still completed the non-browser promotion checks successfully.

LoopX v0.1.5

Choose a tag to compare

@huangruiteng huangruiteng released this 03 Jul 05:28
c036d60

Summary

LoopX v0.1.5 promotes the latest stable control-plane fixes from main to the public stable channel.

Highlights since v0.1.4:

  • tighter quota/status/runtime routing for long-running agent work;
  • improved monitor and scheduler projection behavior;
  • stronger canary smoke discovery and release packaging coverage;
  • updated outcome-floor recovery semantics so agents produce evidence or concrete blockers instead of surface-only progress.

Update

Existing users can update with:

loopx update --check
loopx update --execute
loopx doctor

New users can install from the stable channel with:

curl -fsSL https://raw.githubusercontent.com/huangruiteng/loopx/main/scripts/install-from-github.sh | bash
export PATH="$HOME/.local/bin:$PATH"
loopx doctor

Validation

  • python3 examples/release/release-version-contract-smoke.py
  • python3 examples/canary-promotion-readiness-smoke.py --no-write-evidence
  • PYTHONPATH=. python3 -m loopx.cli check --scan-path README.md --scan-path docs/ --scan-path examples/
  • release/install/update smokes from PR #1193

Note: local loopx check reported an existing runtime index duplicate warning under loopx-meta; public boundary scans were clean and returned ok=True.

LoopX v0.1.4

Choose a tag to compare

@huangruiteng huangruiteng released this 02 Jul 16:24
07d0a75

Highlights

  • Promotes current main to the public stable channel.
  • Includes the product-capability monitor projection fixes merged after v0.1.3.
  • Keeps the named release contract aligned across loopx.version, pyproject.toml, tag v0.1.4, and stable.

Upgrade

Existing users can check and update with:

loopx update --check
loopx update --execute

Fresh install remains:

curl -fsSL https://raw.githubusercontent.com/huangruiteng/loopx/main/scripts/install-from-github.sh | bash

Validation

  • Release compatibility smokes passed.
  • Quota/work-lane regression smokes passed.
  • Canary promotion readiness smoke passed after installing dashboard npm dependencies.
  • Public boundary scan reported no errors; one existing loopx-meta duplicate-index warning remains.

LoopX v0.1.3

Choose a tag to compare

@huangruiteng huangruiteng released this 02 Jul 06:45
10509b0

LoopX v0.1.3 - Initial public release

LoopX v0.1.3 is the first public stable-channel release. It promotes the stable channel to commit 10509b06b092deefbe6f2884fbaeaffa25dc1a9a and makes LoopX installable as a local-first control plane for long-running AI agents.

What LoopX is in this release

LoopX is loop engineering for long-running agents. Instead of asking every agent session to remember the whole project, LoopX keeps goal state, todos, gates, quota, evidence, scheduler hints, and handoff contracts in a shared local control plane. That lets an agent resume safely, ask the user for concrete gates, stop when only non-due monitor work remains, and leave enough evidence for the next turn or side agent to continue.

Why the public timeline starts here

Pre-v0.1.3 work focused on proving the local control plane, archive installer, update path, and canary route. The public GitHub release timeline starts at v0.1.3 because this is the first version with a named stable promotion contract and a validated no-clone install/update path suitable for new users.

Highlights

  • First public stable-channel release for the no-clone install path.
  • Named package version contract: loopx.__version__, pyproject.toml, public tag, release note, and stable-channel promotion now share one release identity.
  • New-user lifecycle: install from GitHub archive, run loopx doctor, update through loopx update, and verify the named version without cloning the repository.
  • Initial public control-plane surfaces for long-running work: status, quota, todo, gate, evidence, heartbeat prompt, and handoff-oriented state projection.
  • Visible auto-research demo startup fixes.
  • SkillsBench app-server context-only turn recovery.
  • Package version bump to 0.1.3.

Install

curl -fsSL https://raw.githubusercontent.com/huangruiteng/loopx/main/scripts/install-from-github.sh | bash
export PATH="$HOME/.local/bin:$PATH"
loopx doctor

Update

Existing users can update from the stable channel:

loopx update --check
loopx update --execute
loopx doctor

Validation recorded for this release

  • python3 examples/codex-cli-no-clone-release-verification-smoke.py
  • python3 examples/release-version-contract-smoke.py
  • python3 examples/loopx-update-smoke.py
  • local loopx update --execute returned install=0 and doctor=0
  • default local loopx --version reports 0.1.3

Follow-up release timeline

  • v0.1.4: fast-follow hardening for product-capability monitor projection, release-readiness checks, and canary evidence.
  • v0.1.5: stronger quota/status/runtime routing, monitor and scheduler projection, release packaging coverage, and outcome-floor recovery for stuck or low-progress loops.