Release center

Know what changed before you update.

CMT publishes release metadata, package integrity information, and update notes through the official website.

CMT Codex Toolbox

Check the current release

The application can compare its installed build with the official version manifest.

  • Review version and build numbers
  • Verify the package SHA-256 value
  • Read behavior changes before installation

Update safely

Back up important local data and close running Codex windows before maintenance-sensitive updates.

  • Keep the previous package until validation is complete
  • Run the health check after updating
  • Confirm your backup and retention settings remain correct

When an update fails

Do not repeatedly overwrite a working installation without collecting evidence.

  • Record the installed and attempted versions
  • Export a redacted support package
  • Use the previous verified package while support investigates

Release information

Version, build, date, package size, checksum, and notable behavior changes identify each published release.

  • Compare the website manifest with the application
  • Treat a changed checksum as a different package
  • Review known limitations before deployment

Rollback evidence

If validation fails, keep enough information to return to the previous verified build safely.

  • Retain the previous installer and its checksum
  • Record settings or data migrations performed by the update
  • Confirm the restored build with health and backup checks

Organize Codex conversations, handoffs, and backups