PUBLISHED RELEASE ·
Stable release
Multi Codex v1.6.1
Storage now reports the disk space occupied by unique files. Shared extension payloads are counted once even when several account catalogs refer to the same hardlinked bytes. Sparse files use their allocated space, and linked directories outside the app are not followed. Linux and Mac use filesystem block allocation; Windows uses native file allocation and file identities. Sizes use KiB, MiB and GiB consistently. Backups remain outside the app total.
The storage screen shows two figures—space on disk and cache currently safe to clear—above compact account rows. Account details, shared files, backup tools and conversation deletion are tucked into expandable sections. Active accounts contribute no clearable cache. Cleanup keeps login credentials, conversations, editor settings and installed tools.
Opening an account with a verified shared layout now uses its pinned extension catalog instead of silently repeating migration after a launcher update. The startup queue also retains valid completed layouts across version changes. Initial setup and explicit repair still create verified recovery backups; this release does not automatically delete recovery data. Failed extension publication checks clients before copying packages and removes unpublished staging files if a later check fails.
Shared extension packages and shared conversations from the 1.6 development series are included. Shared conversations in managed VS Code windows can be listed and resumed across saved accounts while logins remain private. Automatic account memory folders remain separate.
Updating
Use the launcher’s Update button when v1.6.1 becomes available. The existing signed updater downloads the matching package and restarts Multi Codex. Saved accounts and data keep their existing locations. The launcher can update separately from VS Code and Codex sessions.
Linux x64, Apple Silicon Mac on macOS 26 or newer, and Windows x64 packages use the existing release pipeline. Mac packages remain ad-hoc signed unless Apple signing credentials are configured; updater signatures are separate from Apple notarization.
Validation
Local checks cover unique allocation across hardlinks, sparse files, external links, shared cache references, unchanged login/settings/history after cache cleanup, and removal of failed publication staging. React interaction tests and the production frontend build passed. The storage dialog was visually checked at desktop and 480-pixel window widths.
Exact native build, installer, isolation and signed-updater evidence is recorded in the release validation report. Broader Linux desktop/distribution coverage and Apple notarization are outside the completed release checks.
The initial native runs exposed disposable test-fixture cleanup issues. The exact signed Windows installer and Mac DMG were retested with corrected fixture cleanup; the native production source and package hashes were unchanged. The production Update button has not been exercised on the owner's laptop; the completed updater checks use the real updater SDK with disposable fixtures.