Skip to content

v1.4.0

Compatible Runtime hot updates and generation diagnostics.

Updated View as Markdown

Published 2026-10-10 · Original GitHub release notes and downloads

Changes

  1. Compatible Runtime hot updates: Supported running macOS windows and the installed Windows window can apply UI and shared action updates without restarting Codex or refreshing the page. Pending requests finish with their original handlers; failed activation attempts trigger rollback, with failures reported explicitly.
  2. Keep running generations usable: Publishing a newer Runtime no longer prevents an existing process from reading its verified modules. Windows opens new private windows with the CLI matching its retained Runtime.
  3. Separate publication from activation: Diagnostics report verified publication, startup controller, active actions and acknowledged window generations separately, preserving missing acknowledgements and rollback failures.
  4. Upgrade once, then update compatible changes live: For Homebrew, script or managed Windows installations, run inc update. For a source installation, update your checkout with git pull, then run cargo install --locked --path crates/incodex-cli and incodex runtime. If you already use app integration, finish active work and exit Codex normally, then run incodex install once to refresh the macOS loader catalog or Windows helper. On macOS, repeat your original --app <path> or --clone option if you used one. If you only use incodex open, update and reopen your private window; no installation is needed. Other Runtime changes still require reopening; native helper or loader changes require installation. Already-open incognito windows retain their privacy Runtime until normal close. Automatic recovery after a real Windows Store upgrade remains experimental.
Navigation

Type to search…

↑↓ navigate↵ selectEsc close