PUBLISHED RELEASE ·

Stable release

Multi Codex v1.7.1

The Multi Codex desktop launcher owns Orbit. It shows selected Codex Desktop conversations, live managed CLI sessions and one session per open VS Code window. VS Code stays visible on an empty New Chat composer, and clicking its session focuses that specific window. Retained history and background engine caches no longer appear as extra open chats. Existing Desktop and VS Code instances keep running during the update; the current observer or bridge becomes available when those clients next close normally and are launched through Multi Codex. Desktop monitoring availability is shown explicitly.

Hyprland uses a real layer-shell overlay with fixed bounds, stable hover, dragging and fullscreen hide/restore. Multiple chats use diagonal or corner mini avatars, with overflow for more than four. Inactive accounts stay dim and still; open accounts move gently when animation is enabled. Linux tray icons use the colored app icon for visibility.

Settings is wider and uses two columns on larger windows, with a single column for narrow windows. What’s New groups every skipped release since your previous version and keeps the same range when reopened. Older installs without a saved starting version show the bundled release history.

Settings → Release channel offers Stable updates or All updates, including previews. The website and signed update feed use the same explicit classification. This release is Stable; v1.7.0 remains Preview. The channel cannot change during an installation.

Update

Use Multi Codex’s Update button. The signed update preserves accounts and profile data and restarts the launcher. Your existing Codex and VS Code sessions keep running. Turn Orbit off directly in Settings.

Linux x64, Apple Silicon macOS 26+ and Windows x64 have launcher packages. Orbit supports macOS and Linux Hyprland, GNOME and Plasma 6. Windows retains launcher, shared-chat and editor integration support. The bundled VS Code bridge is v0.3.1.

Validation

Native package, installer, signed updater and editor results are recorded in the candidate validation evidence. Runner checks use disposable accounts and synthetic conversations. Exact platform versions and untested cases are recorded separately; a successful build does not establish every manual acceptance case.

The final local Hyprland and installed Update-button retests were omitted at the owner’s request to publish immediately; earlier candidate results do not establish those final-package checks.

Mac bundles are ad-hoc signed. Developer ID and notarization are not configured. The reported macOS 27 issue needs that environment; macOS 26 runner results do not establish macOS 27 behavior. Mixed-monitor scaling, tray contrast on every panel and long-duration use remain outside the automated matrix.