CodexRemote-fix 2.5.6

CodexRemote-fix 2.5.6

• Replaced the unsigned self-extracting installer release with a manifest-bound portable ZIP. Release validation now binds the ZIP, checksum, TrayHost provenance, external payload manifest, and every archived payload file.
• Added a verified portable entrypoint that scans the payload with Microsoft Defender before installation, without disabling protection or adding exclusions.
• Added a staged portable uninstall finalizer that removes only the marker-bound current-user payload after the existing fail-closed cleanup proves the runtime/session boundary. The DPAPI device-key store remains untouched.

CodexRemote-fix 2.5.5

CodexRemote-fix 2.5.5

• Added a tightly scoped compatibility inspection for an older manifest-sealed controller that omitted its ProcessControl import. It accepts only the exact correlated legacy failure and requires a manifest-verified read-only ordinary-session recheck immediately before each protected uninstall deletion boundary.
• New SessionController runtimes now load ProcessControl globally, and regression coverage rejects every other controller failure or changed compatibility proof.

CodexRemote-fix 2.5.4

CodexRemote-fix 2.5.4

• Made fail-closed uninstall recovery preclaim a durable nonempty controller result placeholder so it works with a still-manifest-sealed older controller runtime.
• Added regression coverage for the legacy strict byte-array writer and the prelaunch placeholder ordering.

CodexRemote-fix 2.5.3

CodexRemote-fix 2.5.3

• Fixed fail-closed uninstall recovery when its authenticated controller result placeholder is initially empty.
• Added regression coverage for atomically replacing the empty preclaimed controller result file.

CodexRemote-fix 2.5.2

CodexRemote-fix 2.5.2

• Fixed the fail-closed uninstaller payload to include TrustedLogonIdentity.psm1, required by the staged StateStore dependency.
• Added a regression that imports staged InstallLifecycle before cleanup, proving its payload-local dependency closure is complete.

CodexRemote-fix 2.5.1

CodexRemote-fix 2.5.1

• Fixed a Supervisor startup contract mismatch that rejected the complete schema-two active runtime pointer immediately after installation.
• Added regression coverage that reads the canonical active pointer before Supervisor readiness, including upgrade pointers with a previous runtime.

CodexRemote-fix 2.5.0

CodexRemote-fix 2.5.0

• Rebuilt restart and repair as a durable Supervisor-owned lifecycle that resumes safely after delayed or manual Codex launches.
• Simplified the tray to truthful connection/protection status, one repair action, language, logs, About, and safe Exit.
• Made upgrades wait for the new runtime and tray, preserved authorized devices, and unified Windows Settings and direct uninstall behind a fail-closed cleanup flow.

CodexRemote-fix 2.4.24

CodexRemote-fix 2.4.24

• Fixed upgrades leaving no tray icon even though the controlled Codex session was active.
• The installer now waits for the previous IgnoreNew scheduled-task instance to leave Running before starting the new Supervisor.
• Added lifecycle regression coverage and a stable CCOD_INSTALL_SUPERVISOR_TASK_BUSY failure when the old task cannot exit within the bounded wait.

CodexRemote-fix 2.4.23

CodexRemote-fix 2.4.23

• Replaced the embedded COM application activator with the standard Windows explorer.exe shell:AppsFolder\<AUMID> route.
• Preserved reliable ordinary Codex relaunch while removing the new embedded interop signature that triggered Defender's Program:Win32/Contebrew.A!ml download heuristic.
• Added regression coverage that forbids the embedded COM activator and verifies the exact AppsFolder launch request.

CodexRemote-fix 2.4.22

CodexRemote-fix 2.4.22

• Fixed Restart now closing Codex without reopening it by activating the ordinary packaged app through Windows' native Application Activation Manager.
• Ordinary launches now use the exact Codex AUMID OpenAI.Codex_2p2nqsd0c76g0!App; controlled launches with debugging arguments keep their existing verified executable path.
• Added a regression test that rejects direct WindowsApps executable launches for ordinary Codex recovery.