update-codex-sdk

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @openai/codex, and 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, multiple version pins must stay in sync, and generated protocol clients must be regenerated and validated. This Skill automates that entire workflow safely. ## Core Features & Use Cases - Private feed version selection: Queries the private VS Code npm feed via Azure CLI authentication to find the newest stable Codex release with all platform binaries present. - Synchronized version pinning: Updates package.json, lockfiles, and codex-version.txt to the exact same version 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 tests. - Real session verification: Launches an isolated Agents window and confirms a live Codex session reports the expected version sentinel. - Use Case: A maintainer needs to bump @openai/codex from 0.148.0 to the newest CI-available release; the Skill selects the version, updates every pin, regenerates the protocol client, runs all tests, and verifies a real Codex Agent Host session before delivery. ## 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 script to pick a CI-available version, then use npm install with --save-exact to update package.json and lockfiles, set 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?▼

The Azure pipeline installs from the private vscode feed, where new third-party package versions are typically quarantined for seven days. The public npm latest version may not be installable in CI, so you must select a version from the private feed.

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. It authenticates via Azure CLI, queries the private feed, and reports whether the version and all its platform binary aliases are present.

What tests should I run after updating the Codex SDK?▼

Run npm run codex:check-protocol, npm run compile, ./scripts/test.sh --grep codex, the build directory tests, npm run test-agent-host-e2e, and npm run hygiene. Then verify a real Codex Agent Host session in a launched Agents window.

What if the Agent Host E2E tests fail after a Codex SDK update?▼

Read the agent-host-e2e-tests skill documentation before deciding whether to re-record replay fixtures. Never weaken or silently skip a failing test; investigate whether the SDK change caused replay misses or stale fixtures first.