PUBLISHED RELEASE ·
Stable release
Multi Codex v1.8.0
This release adds T3 Code desktop as another way to open a saved account on Linux x86_64 and Windows x64. macOS stays on v1.7.5 while its T3 account-routing support is unfinished.
What changed
- Installed T3 Code appears beside existing account launch buttons and in the native account menu. CLI source builds support
multi-codex launch --account <account> --target t3. - Every account gets its own T3 backend, settings, cache and Electron profile. The launcher configures T3's existing-Codex provider with that account's Codex home and executable. It does not copy your global T3 login or modify global T3 settings.
- Discovery accepts installed desktop versions without a version allowlist. Install T3 separately; the
t3server command alone is not a desktop installation. For custom locations, setMULTI_CODEX_T3_PATHto the absolute desktop executable path before starting Multi Codex. - T3 opens its own project interface. Choose your project inside T3. Existing Codex, VS Code and CLI launches keep their previous behavior.
Upgrade
Use the Linux or Windows installer for v1.8.0 from the installation page. Existing accounts and conversations remain in place. T3 requires an available Codex CLI through the existing executable discovery.
Older apps use a platform-blind update feed. That feed stays on v1.7.5 so Macs cannot receive this Linux/Windows-only release. Existing Linux and Windows users must use the installer once to reach v1.8.0. This version uses platform-specific update feeds for future releases.
macOS download commands stay pinned to v1.7.5. No new macOS desktop package ships with v1.8.0. Published older packages remain unchanged.
Limits and validation
T3 remains a separate application with its own projects, interface and onboarding. T3 sessions are not native Orbit navigation shortcuts. Extra providers can be configured within each account's T3 instance.
Release validation uses disposable fixtures, including two simultaneous official T3 Code v0.1.7 desktop instances on native Linux and Windows runners. This does not mean every upstream release or an authenticated agent turn has been tested. Completed checks and exact package hashes are recorded in the validation evidence before publication.