update-codex-sdk

Updates VS Code's bundled @openai/codex dependency and verifies the Codex Agent Host end to end.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/jimeh/hucode --skill update-codex-sdk-jimeh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-codex-sdk
Source: https://github.com/jimeh/hucode/tree/main/.agents/skills/update-codex-sdk
Command: npx skills add https://github.com/jimeh/hucode --skill update-codex-sdk-jimeh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Bumping VS Code's bundled Codex SDK is error-prone: the public npm latest version is often unavailable in the private Azure DevOps feed used by CI, version pins live in multiple package manifests and lockfiles, and the generated protocol client must stay in sync. This Skill automates version selection, pinning, regeneration, testing, and live verification. ## Core Features & Use Cases - Private-feed version selection: A helper script authenticates via Azure CLI and queries the private VS Code npm feed to find the newest stable Codex release with all platform binaries present. - Consistent version pinning: Updates package.json, package-lock.json, the agent-sdk lockfile, and codex-version.txt with exact versions while keeping lockfile URLs on the public registry. - Protocol regeneration and validation: Regenerates the vendored app-server client, runs compile, unit, hygiene, and Agent Host E2E checks, then verifies a real Codex session in a launched Code OSS window. - Use Case: When a new @openai/codex release ships, run this Skill to safely bump the bundled SDK, regenerate the protocol client, and prove the Agent Host works before opening a pull request. ## Quick Start Use the update-codex-sdk skill to update VS Code to the newest private-feed-available Codex SDK and verify it end to end.

Frequently Asked Questions about update-codex-sdk

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update the bundled @openai/codex version in VS Code?▼

Run the latest-private-version.ts helper to pick a CI-available version, then npm install that exact version in the root and build/agent-sdk/agents/codex packages, update build/codex/codex-version.txt, and regenerate the protocol client with npm run codex:gen-protocol.

Why can't I use the latest public npm version of @openai/codex?▼

VS Code CI installs from a private Azure DevOps feed where new third-party package versions are typically quarantined for seven days. The public npm latest version may not exist there, so the helper script queries the private feed for the newest fully available stable release.

How do I check if a specific Codex version is available in the private feed?▼

Run node --experimental-strip-types scripts/latest-private-version.ts --version x.y.z from the repository root. The script authenticates through the Azure CLI and reports whether the root package and all platform binary aliases for that version are present.

What authentication is required to query the private VS Code npm feed?▼

The helper script obtains an Azure DevOps access token from the signed-in Azure CLI for the monacotools organization. If Azure CLI authentication is missing or expired, you must sign in again; the script never falls back to the public registry.

Which files must change when bumping the Codex SDK version?▼

The version must be pinned in package.json and package-lock.json, build/agent-sdk/agents/codex package.json and package-lock.json, and build/codex/codex-version.txt. The generated protocol files under src/vs/platform/agentHost/node/codex/protocol/generated are regenerated, never hand-edited.

How is the Codex Agent Host verified after an SDK update?▼

After compile, unit, hygiene, and Agent Host E2E tests pass, launch an isolated Agents window, start a Codex-backed session, and run a deterministic command that prints the SDK version. Success requires the exact sentinel response and a clean Agent Host log.