CHANGELOG

Changelog

Notable changes to slashsynthex.com — the public marketing and documentation site. For Synthex plugin releases, see the upstream repository at

bluminal/lumenai

.

Versions follow SemVer with site-content-level granularity: major = visual/IA overhauls, minor = new pages or sections, patch = copy/style fixes.

Next — Grok install

The public install guides now include Grok beside the other supported harnesses. Grok uses the same LumenAI marketplace and the same generated Agent Skills as Codex. The canonical command and agent Markdown is unchanged.

Added

Next — Synthex 1.0

Synthex is becoming Claude-first, now for any agent. Claude Code remains the original and primary plugin experience; version 1.0 also distributes the same workflows through Agent Skills for Codex CLI, Gemini CLI, OpenCode, and future compatible harnesses.

Added

Amended

0.2.1 — 2026-06-08

Native-looping reliability fix, tracked from upstream. Synthex 0.9.10 + synthex-plus 0.5.10 hardens how a loop binds to its Claude Code session so iteration keeps being driven to completion instead of silently stalling at the first turn-end. This release clarifies that session binding on the concept page. See the upstream plugin release at

bluminal/lumenai

.

Amended

Acknowledgements

The plugin-side fix was authored and shipped by the upstream Synthex maintainers; this release covers only the documentation work to surface it on the public site.

0.2.0 — 2026-05-14

Native-looping coverage. The Synthex plugin shipped a native iteration primitive (synthex 0.8.0 + synthex-plus 0.4.0); this release documents and showcases it across the site. See the upstream plugin release at

bluminal/lumenai

.

Added

Amended

Acknowledgements

The plugin-side feature was authored and shipped by the upstream Synthex maintainers; this release covers only the documentation work to surface it on the public site.

0.1.0 — 2026-05-11

Initial public release. The site goes live at slashsynthex.com with the full code-side deliverable across the five planned phases.

Pages

Per-route OG cards

Every route ships with a tailored OG image generated at the edge via @vercel/og. Landing, docs-section, and reference-detail templates cover the full surface. All four dynamic OG handlers wrap their primary render in try/catch with a system-font fallback.

Programmatic affordances

Quality gates (CI-enforced)

Infrastructure

Acknowledgements

Sponsored and developed by Bluminal. The Ralph Loop driving the authoring iterations is itself a Claude Code plugin pattern.

Upcoming

The implementation plan tracks per-task status at the source level; this changelog records material site changes as they ship.