Support center

Collect useful evidence without exposing more data than necessary.

The fastest support path starts with health checks, exact versions, reproducible steps, and a reviewed diagnostic export.

CMT Codex Toolbox

Run health checks

Check database access, folder permissions, backup state, and available disk space.

  • Record failed check names and timestamps
  • Avoid repeated destructive retries
  • Confirm whether Codex was open during the issue

Prepare the support package

Export only the logs and configuration needed for the issue.

  • Preview every included item
  • Mask account names, private paths, serials, and order data
  • Include application version and reproduction steps

License and purchase support

Use the appropriate evidence for activation, deactivation, payment, or fulfillment questions.

  • Never send a full serial in ordinary email
  • Include the external order reference for payment issues
  • Describe the old and new device state for license moves

Choose the issue category

Separate application behavior, backup or restore, licensing, and external payment issues before collecting evidence.

  • Use operation history for application failures
  • Use integrity results for backup or restore issues
  • Use the external order number only for payment enquiries

Restore and data recovery

Stop repeated cleanup attempts when expected data is missing.

  • Record the original path and approximate deletion time
  • Keep the backup folder unchanged during investigation
  • Include the integrity result and selected conflict option

Privacy review

Support evidence should contain only information required to reproduce or diagnose the problem.

  • Remove complete serials and order documents unless specifically required
  • Mask Windows account names and private project paths
  • Review exported logs and screenshots before sending

A complete request

A useful support request identifies the product build, environment, action, expected result, actual result, and timing.

  • List concise reproduction steps
  • Attach the redacted support package when relevant
  • State whether Codex was open and whether the action was retried

Organize Codex conversations, handoffs, and backups