Upgrade prompt compares to upstream Codex (0.50.0) instead of code's latest (0.4.4)

[darlingm]

What version of Code is running?

code 0.4.4

Which model were you using?

GPT-5-Codex (high), but don't think that's relevant to this

What platform is your computer?

Linux 6.17.5-arch1-1 x86_64 unknown

What steps can reproduce the bug?

1. Install: npm install -g @just-every/code
2. Run: code
3. Observe the startup banner

The CLI reports an available update to 0.50.0, which appears to be the OpenAI Codex CLI version, not the latest release of just-every/code. This leads to a misleading prompt implying that upgrading the fork to 0.50.0 is possible/expected, even though the fork’s latest published version is 0.4.4.

What is the expected behavior?

I expect the upgrade checker should compare the installed code version to the latest release/tag of code.

The banner should clearly identify which product/version stream it’s comparing against.

If it intentionally references upstream versions, if it's internally comparing the Codex CLI version that code includes code through, it should:

Label them as “upstream Codex CLI” and offer appropriate guidance (maybe: “Code v0.4.4 is based on Codex CLI v0.xx.x. Upstream Codex is v0.50.0. Code will integrate those changes in a future release.”)

What do you see instead?

┌────────────────────────────────────────────────────────────────────┐
│ ★ Upgrade Available ★ │
│ Latest release: 0.4.4 → 0.50.0 │
│ │
│ Use /upgrade to upgrade now or enable auto-update. │
└────────────────────────────────────────────────────────────────────┘

Additional information

No response

[darlingm]

/settings under Updates also shows Latest available: 0.50.0. (I have auto update disabled.)

[darlingm]

I see ~/.code/log/codex-tui.log includes ERROR Failed to update version: error sending request for url (https://api.github.com/repos/just-every/code/releases/latest), and ~/code/logs/critical.log.2025-10-29 includes ERROR tokio-runtime-worker ThreadId(33) Failed to update version: error sending request for url (https://api.github.com/repos/just-every/code/releases/latest).

I know combined with #377 this suggests a networking issue. Like I mentioned in that thread, I have a straightforward networking setup and nothing else ever has problems accessing the internet.

Happy to run any diagnostics given.

[darlingm]

See #377. This does appear to be a networking issue, somehow occurring in code installations through npm but not when built from source. I don't see this version comparison bug when built from source. The npm installed version seems to not be able to access the OpenAI API endpoints or check code's most recent version, but somehow can check codex's most recent version and then uses that instead of code's version.

[darlingm]

See #377. It appears the npm code must be able to check the most recent Codex CLI version since it's seeing v0.50.0, even though it can't check the most recent Code version or access the OpenAI API endpoint.

[darlingm]

#377 turned out to be a DNS resolving issue that was caused on my system a few days ago.

At first, I thought fixing that resolved this, but removing ~/.code to start fresh showed me code's version compared to Codex's 0.50.0 despite properly connecting to the internet. Perhaps that version comparison is only done on upgrades, as subsequent runs don't show it. So, there's probably still a tweak that could be done here.