Last updated
Keep Codex thread history in one provider bucket.
$ winget install --id Wangnov.codex-threadripper --exact --version 0.3.0Run in Command Prompt, PowerShell, or Windows Terminal. Prompts for any agreements.
codex-threadripper uses MSI (WiX). The silent install switches are /quiet /norestart.
msiexec.exe /i codex-threadripper-x86_64-pc-windows-msvc.msi /quiet /norestart
See the full silent install reference for codex-threadripper →
For Intune admins
Automated application patching for Microsoft Intune. Pckgr keeps a curated library of 1,000+ apps continuously up-to-date in your tenant via Microsoft Graph - no manual repackaging, no chasing vendor sites.
Start free 30-day trialNo credit card required.
你有没有遇到过这种情况:在 Codex 里切到另一个 model_provider,然后发现之前的会话全不见了?打开 Codex.app,列表空空如也;执行 codex resume,什么都恢复不了。
会话其实还在,只是 Codex 的 SQLite 状态库里每条线程记录了创建它的 provider,切换 provider 之后 Codex 只会显示当前 provider 的线程,其他的就像蒸发了一样。
codex-threadripper 就是为了解决这件事而生的。它会把 Codex 的 SQLite 状态库和 rollout JSONL 首行里的 provider 字段统一收敛到你当前用的那个,这样不管你来回怎么切,codex resume、Codex.app 和 app-server 客户端都能看到完整的历史记录。
Copy a command tailored to that specific architecture, type, and scope - useful when winget would otherwise pick a different default.
No known CVEs for codex-threadripper.
Coverage is best-effort and depends on a winget package mapping to an NVD CPE entry. Absence here is not a guarantee of safety.