provider-codex

Detect upstream Codex CLI changes and update the gateway contract.

10|Updated Mar 31, 2026

Search Tags:#Codex #contract management #version tracking #upstream changes #CLI integration

Ready to run

npx skills add https://github.com/verivus-oss/llm-cli-gateway --skill provider-codex

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: provider-codex
Source: https://github.com/verivus-oss/llm-cli-gateway/tree/main/.agents/skills/provider-codex
Command: npx skills add https://github.com/verivus-oss/llm-cli-gateway --skill provider-codex

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Ensures consistency between the gateway's Codex integration and the upstream CLI, identifying and handling contract changes.

Core Features & Use Cases

Contract Tracking: Keeps the Codex (codex) integration updated with any changes to the upstream CLI.
Error Handling: Identifies and reports when Codex contract changes could affect codex request processing.
Update Procedure: Guideline on updating the Codex contract when changes are detected.

Quick Start

Update the Codex integration using npm run upstream:scan -- --provider codex.

Frequently Asked Questions about provider-codex

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

FAQPage Schema

How do I detect upstream changes to the OpenAI Codex CLI contract?▼

You can detect upstream Codex CLI changes by running `npm run upstream:scan -- --provider codex`, which validates the contract and reports changes that could affect request processing.

Why does my Codex CLI integration break after upstream contract updates?▼

Codex CLI integration breaks when upstream contract changes alter request processing rules. The provider-codex tool identifies these changes and provides update guidelines to realign the gateway with the upstream CLI.

What is Codex contract management and when do I need it?▼

Codex contract management tracks and validates the agreement between your gateway's Codex integration and the upstream OpenAI CLI. You need it whenever upstream CLI changes could impact request handling or processing consistency.

How to update the Codex contract when upstream CLI changes are detected?▼

Run `npm run upstream:scan -- --provider codex` to scan for changes, then follow the update procedure guidelines to modify the contract and restore alignment between the gateway and upstream CLI.

Does the Codex contract validator work without additional dependencies?▼

Yes, the Codex contract validator operates with no external dependencies. It uses built-in scripts to scan upstream changes and validate contract alignment directly through the npm CLI.