Skip to content

Releases

Changelog

The public release history for Origin, plus how to read unreleased work on main.

Qi-Xuan LuUpdated 5 min read

At a glance

01

The current stable release in the repository changelog is v0.7.0, dated 2026-05-24.

02

Recent main-branch work after v0.7.0 is visible through merged PRs, but it should be treated as unreleased until the next release lands.

01

Current stable release

Origin v0.7.0 is the current stable release recorded in CHANGELOG.md and the release-please manifest. It shipped cross-platform Linux and Windows support, spaces, eval reproducibility work, page and KG faithfulness benchmarks, and release pipeline hardening.

The website keeps public install and product claims aligned to the stable release unless a page explicitly labels a feature as unreleased or on main.

02

v0.7.0 highlights

The v0.7.0 release broadened Origin from a macOS-first local runtime into a cross-platform local memory layer with explicit spaces and stronger evaluation discipline.

  • Cross-platform runtime support for macOS, Linux, and Windows.
  • origin space subcommands and doctor resolver state.
  • Plugin and server space resolver plumbing.
  • KG-faithfulness and page-distillation faithfulness benchmarks.
  • Structured binary judge and reproducibility foundations for evals.
  • Release pipeline fixes for crates, npm, Homebrew, and version sync.

03

Earlier milestones

The v0.6.x line introduced the domain-to-space transition, curation workflows, pending revisions, and stronger daemon/client boundaries.

The v0.5.x line merged the MCP server and Claude Code plugin into the monorepo, established the locked skill set, and made the public packages line up with the repo runtime.

04

Unreleased main work

After v0.7.0, main has received a wave of opt-in retrieval, refinery, and read-time experiments. Examples include query decomposition, graph activation gates, FTS hardening, temporal filters, session diversification, salience priors, fact channels, k-hop graph traversal, global preludes, background reflection debounce, CoT retrieval, and LLM read-time routing.

Those PRs are useful signals for roadmap direction, but public users should treat them as main-branch work until a release entry publishes them.

05

Where to follow releases

GitHub releases are the canonical place to inspect release artifacts. CHANGELOG.md is generated by release-please and records the release history in the source repo.

View full changelog

Next

Releases and Versioning

Understand how Origin turns merged work into tagged releases, package versions, binaries, npm packages, and crates.

Read next