Use codex update for standalone installs#4185
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
ApprovabilityVerdict: Needs human review Enables native update functionality for Codex standalone installs by populating You can customize Macroscope's approvability policy. Learn more. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit d91cc75. Configure here.

What Changed
~/.codexstandalone installer.codex updatecommand instead of treating those installs as npm-managed.codex updateas the displayed command.Why
Standalone Codex installations are not managed by npm. Codex already owns its platform-specific self-update flow, so T3 Code only needs to delegate to
codex updateusing the same executable it detected for the provider instance.This supersedes #3626 with the minimal default-install behavior. Custom
CODEX_HOMEtargeting and version-pinned release paths are intentionally outside this PR.Validation
./node_modules/.bin/vp test run apps/server/src/provider/providerMaintenance.test.ts apps/server/src/provider/Layers/ProviderInstanceRegistryLive.test.ts./node_modules/.bin/vp check apps/server/src/provider/Drivers/CodexDriver.ts apps/server/src/provider/Layers/ProviderInstanceRegistryLive.test.ts apps/server/src/provider/providerMaintenance.test.ts apps/server/src/provider/providerMaintenance.ts./node_modules/.bin/vp run --filter t3 typecheckChecklist
Note
Enable
codex updatefor standalone Codex installsisCodexStandaloneCommandPathhelper in CodexDriver.ts that detects if the active binary path is a standalone Codex install (under/.codex/packages/standalone/).nativeUpdatein the maintenance resolver to runcodex update(with lockKeycodex-native) when the helper returns true.maintenanceCapabilitiesupdate block.Macroscope summarized d91cc75.
Note
Low Risk
Scoped to provider maintenance capability detection and update command wiring; no auth or session runtime changes.
Overview
Standalone Codex binaries under
~/.codex/packages/standalone/are now recognized as native installs, so in-app provider updates runcodex updateinstead of falling back to npm/Homebrew-style maintenance.Codex driver adds
isCodexStandaloneCommandPathand wiresnativeUpdatewith lock keycodex-native, matching how other providers delegate to their own updater.Provider maintenance gains optional
useResolvedExecutable: when set, the update action runs the resolved binary path from capability detection while keeping a human-readablecommandstring (e.g.codex update). Registry tests assert the work Codex instance exposes the expectedmaintenanceCapabilitiesfor a standalone path.Reviewed by Cursor Bugbot for commit 14bbd62. Bugbot is set up for automated code reviews on this repo. Configure here.