PUBLISHED RELEASE ·

Stable release

Multi Codex v1.8.3

This maintenance release applies the release-workflow hardening prepared during the security audit. Existing account and conversation storage is unchanged.

Release signing

Linux builds and tests run without an injected updater signing key. A separate step signs the final repacked AppImage. Mac signing credentials are limited to the app build-and-sign step; Windows already uses a scoped build-and-sign step. Other steps no longer receive workflow-wide signing credentials.

Release jobs default to read-only repository access. Draft publication alone receives write access, and the Windows workflow receives only its declared signing secrets. Third-party actions in the four release-chain workflows are pinned to full commit IDs rather than mutable tags.

These changes reduce exposure; they do not provide a completely isolated signing service. Mac/Windows build-and-sign processes still trust build code, and installed tooling remains a supply-chain dependency. No signing-key compromise was established by the audit.

The account launch button now reads T3, with the duplicate T3 glyph removed.

Install and update

Use the same install link across supported computers, or the existing launcher's Update button. Linux x64 and Windows x64 retain T3 desktop launching. Apple Silicon Macs on macOS26+ receive the same version without T3. This release does not upgrade your installed Codex, VS Code or T3 applications.

Verification and remaining scope

Fresh native package, installer, signed-updater and extension checks must pass before publication. Exact source and asset hashes are recorded in the validation evidence.

The earlier audit's other findings, including desktop CSP, first-install publisher verification, glib/maintenance warnings, issue quotas and environment/URL hardening, are not claimed fixed in this release. Standalone npm CLI and Marketplace versions are unchanged; GitHub release VSIXs and bundled helpers are rebuilt.