# LoopX Release History and Changelog: Complete Version Guide

> Explore the LoopX release history and changelog. Discover milestone updates and detailed per-release notes to understand every LoopX version.

- Repository: [huangruiteng/loopx](https://github.com/huangruiteng/loopx)
- Tags: release-history
- Published: 2026-08-14

---

**LoopX maintains its release history in [`docs/project/history.md`](https://github.com/huangruiteng/loopx/blob/main/docs/project/history.md) as milestone‑level milestones rather than a traditional linear changelog, with granular per‑release details stored in dated files under `docs/update-notes/`.**

The `huangruiteng/loopx` repository documents its evolution through a hybrid approach: a curated timeline of major milestones in the *Project History* document and detailed update notes for specific date ranges. This structure emphasizes governance and product identity changes while preserving granular technical details for developers upgrading between versions.

## Where LoopX Stores Release History

Unlike conventional open‑source projects that rely on a single [`CHANGELOG.md`](https://github.com/huangruiteng/loopx/blob/main/CHANGELOG.md) file, LoopX distributes its release information across two complementary locations:

- **[`docs/project/history.md`](https://github.com/huangruiteng/loopx/blob/main/docs/project/history.md)** — The canonical timeline of major milestones, governance changes, and versioned releases
- **`docs/update-notes/`** — Per‑date‑range Markdown files containing detailed commit‑level changes

This design separates *narrative* project history from *technical* upgrade notes, making each resource serve distinct audiences.

## Major Milestones in LoopX Development

The *Project History* document records eight critical events from the repository's inception through the v0.2 launch:

| Date | Milestone | Significance |
|------|-----------|------------|
| **2026‑05‑31** | Repository opens | First public commit (`7dcdc9d`) introduced the goal‑harness scaffold for long‑running agent work |
| **2026‑06‑17** | Contributor surface appears | Public task board created for claimable external work (`7bb3152`) |
| **2026‑06‑21** | Product renamed to LoopX | Core control‑plane renamed, establishing permanent product identity (`320fbed`) |
| **2026‑06‑22** | Visual assets released | Branding materials added to match new product name (`ac13d32`) |
| **2026‑06‑23 – 06‑24** | First external contributions | Hardware‑agent showcase and Claude Code CLI LoopX mode merged (#597, #604) |
| **2026‑07‑02** | Public release archive starts | **LoopX v0.1.3** becomes first official GitHub release |
| **2026‑07‑10** | Peer‑runtime for agent coordination | Hierarchical agent model replaced by peer‑runtime authority model (#1787) |
| **2026‑07‑11** | v0.2 control‑plane shipped | **LoopX v0.2.0** delivers peer‑agent runtime, extended lifecycles, and validation surfaces |

Each entry links to the exact commit, pull request, or release tag, enforcing traceability without speculative context.

## Per‑Release Changelog Files in `docs/update-notes/`

For concrete upgrade guidance, LoopX aggregates changes into dated Markdown files. These files follow the naming convention [`YYYY-MM-DD-to-YYYY-MM-DD.md`](https://github.com/huangruiteng/loopx/blob/main/YYYY-MM-DD-to-YYYY-MM-DD.md) and reference specific pull requests and commits.

### Available Update‑Note Files

| File | Coverage Period | Contents |
|------|---------------|----------|
| [`2026-06-28-to-2026-07-11.md`](https://github.com/huangruiteng/loopx/blob/main/2026-06-28-to-2026-07-11.md) | v0.2 development | New capabilities, bug fixes, and documentation updates leading to v0.2.0 |
| [`2026-06-14-to-2026-06-27.md`](https://github.com/huangruiteng/loopx/blob/main/2026-06-14-to-2026-06-27.md) | Pre‑v0.2 improvements | Changes leading to the public release archive |
| [`2026-05-31-to-2026-06-13.md`](https://github.com/huangruiteng/loopx/blob/main/2026-05-31-to-2026-06-13.md) | Repository inception | Initial scaffold and early development |
| [`automation.md`](https://github.com/huangruiteng/loopx/blob/main/automation.md) | — | Guidelines for generating and maintaining update‑note files |

These files are referenced from [`docs/project/history.md`](https://github.com/huangruiteng/loopx/blob/main/docs/project/history.md) and provide the granular detail developers need when migrating between LoopX versions.

## How to Access LoopX Version Information Programmatically

### Retrieve Installed Version from Package Metadata

```python
from importlib.metadata import version, PackageNotFoundError

try:
    latest = version("loopx")
    print(f"Current LoopX version: {latest}")
except PackageNotFoundError:
    print("LoopX is not installed in this environment.")

```

This pattern is useful in CI pipelines, health checks, and diagnostic scripts that need to verify the deployed LoopX version.

### Load Update Notes for a Specific Date Range

```python
from pathlib import Path

def load_update_notes(start: str, end: str) -> str:
    """Read the update-notes file for the specified period."""
    notes_path = (
        Path(__file__).parent 
        / "docs" 
        / "update-notes" 
        / f"{start}-to-{end}.md"
    )
    return notes_path.read_text(encoding="utf-8")

print(load_update_notes("2026-06-28", "2026-07-11"))

```

Use this approach to surface relevant changes in deployment automation or to generate custom release notifications.

## Governance Rules for LoopX Release Documentation

The *Project History* document establishes strict criteria for milestone inclusion:

- **Identity changes** — Renames, rebranding, or product repositioning
- **Governance changes** — Contribution models, licensing, or maintainer structures
- **Release‑line changes** — New stable branches or version series
- **Durable contract changes** — Breaking API modifications or deprecation notices

Private context, speculative roadmap items, and commit‑level noise are explicitly excluded from the public timeline. This ensures the history remains authoritative and maintainable.

## Summary

- **Primary location**: [`docs/project/history.md`](https://github.com/huangruiteng/loopx/blob/main/docs/project/history.md) contains the curated milestone timeline for LoopX release history
- **Granular details**: `docs/update-notes/` holds per‑date‑range changelogs with specific commits and pull requests
- **Versioned releases**: v0.1.3 (2026‑07‑02) and v0.2.0 (2026‑07‑11) are the first entries in the official GitHub release archive
- **Programmatic access**: Use `importlib.metadata.version()` for runtime version checks and `Path` operations for loading update notes
- **Governance model**: Milestones are filtered for identity, governance, release‑line, or contract significance only

## Frequently Asked Questions

### Where is the LoopX changelog file?

LoopX does not use a single [`CHANGELOG.md`](https://github.com/huangruiteng/loopx/blob/main/CHANGELOG.md) file. Instead, milestone‑level changes live in [`docs/project/history.md`](https://github.com/huangruiteng/loopx/blob/main/docs/project/history.md) while detailed per‑release notes are stored in [`docs/update-notes/YYYY-MM-DD-to-YYYY-MM-DD.md`](https://github.com/huangruiteng/loopx/blob/main/docs/update-notes/YYYY-MM-DD-to-YYYY-MM-DD.md) files. This hybrid structure separates narrative project history from technical upgrade details.

### How do I find what changed between LoopX versions?

Check `docs/update-notes/` for the date range covering your upgrade. For example, upgrading to v0.2.0 would involve reading [`2026-06-28-to-2026-07-11.md`](https://github.com/huangruiteng/loopx/blob/main/2026-06-28-to-2026-07-11.md). Each file aggregates relevant pull requests, commits, and behavioral changes with direct links to source modifications.

### When did LoopX start making official releases?

**LoopX v0.1.3** on 2026‑07‑02 marks the first entry in the official GitHub release archive. Prior milestones were tracked as commits and pull requests without versioned release tags. The v0.2.0 release followed on 2026‑07‑11, introducing the peer‑runtime authority model.

### What qualifies as a milestone in LoopX project history?

According to the source documentation, milestones must represent identity changes, governance changes, release‑line changes, or durable contract changes. Routine bug fixes, documentation updates, and speculative features are excluded from [`docs/project/history.md`](https://github.com/huangruiteng/loopx/blob/main/docs/project/history.md) and relegated to update‑note files instead.