OpenAI Completions Responses Migration Pack
https://github.com/openai/completions-responses-migration-pack- Category
- Developer Tools
- Rank
- No. 1189Tools index
Previous survey · No. 1164 ·
- Pricing
- Open Source
- Type
- TOOL
- Builder
- openai
- GitHub
- 106 stars
- Date
About
Developer toolkit to migrate applications from the legacy OpenAI Completions/Chat Completions APIs to the unified Responses API, guided by Codex CLI.
What it does
It scans a target Git repository for old OpenAI request patterns, then asks Codex CLI to plan or apply the conversion. It updates endpoints, client setup, request fields, response handling, tools, streaming, and conversation state. The workflow can create a migration branch, run available checks, summarize results, and optionally open a pull request.
Why it's ranked here
This is a focused migration runner backed by unusually practical reference material. It covers simple field renames and harder cases such as structured output, tool calls, content item types, reasoning settings, and multi-turn state. Dry runs, approval policies, branch isolation, and optional pull requests make the generated edits easier to inspect. Its value still depends on Codex interpreting each application correctly.
What's good
The pack treats migration as repository work, not a blind text replacement. It preserves streaming only when already used, converts function calling to JSON Schema tools, and makes client-managed conversation state explicit. It also supplies examples for Node.js, Python, Go, Java, Ruby, and C#. Version pinning and checksum verification give CI users a more controlled installation path.
Tradeoffs
Codex CLI and OpenAI access are required, so this is not a standalone converter. Automated edits can write broadly across a repository, while the dangerous mode removes sandbox and approval protections. The documented retention policy always disables response storage and avoids previous response identifiers, which may conflict with applications that want server-managed state. Language coverage is also uneven: Node.js and Python receive richer recipes than the HTTP-oriented examples.
How to use it well
Use it when an existing Git repository contains legacy Completions or Chat Completions calls and you want a reviewable migration branch. Start with a dry run, inspect the proposed state, tool, streaming, and structured-output changes, then run the project’s own tests and linting. Pin the downloaded artifact and verify its checksum in CI. It does not replace application-specific testing, API credentials, or product decisions about retained versus client-managed conversation state.
Technical notes+
README.md defines an interactive and headless Bash CLI workflow with dry-run, write, approval, model, pull-request, and unsafe execution options. It says the runner creates a migration branch, installs repository guidance, invokes Codex automation, runs available checks, and can open a PR. docs/migration-notes.md and docs/responses-cheatsheet.md specify endpoint and payload mappings, JSON Schema formatting, SSE streaming, tool-result flow, content item conversion, reasoning policy, and store:false behavior. The six files under docs/language-recipes/ provide Node.js, Python, Go, Java, Ruby, and C# examples. scripts/_helpers.sh is an optional Bash logging helper and explicitly is not a runtime dependency of the published standalone launcher. assets/SHA256SUMS supplies integrity data, while LICENSE and SECURITY.md document licensing and vulnerability reporting.
Observed
- License
- MIT License
- Primary language
- Bash shell scripting
- Interface
- Command-line workflow supporting interactive, headless, dry-run, and write modes
- Installation surface
- Standalone shell download, with tag or commit pinning and SHA-256 verification documented
- Platform support
- macOS and Linux, with Windows supported through WSL2
- Required services
- Codex CLI authentication and OpenAI API access
- Language recipes
- Node.js, Python, Go, Java, Ruby, and C#
Read from README.md, docs/migration-notes.md, docs/responses-cheatsheet.md, docs/language-recipes/go.md, docs/language-recipes/java.md, docs/language-recipes/node.md, docs/language-recipes/ruby.md, docs/language-recipes/csharp.md, docs/language-recipes/python.md, LICENSE, SECURITY.md, CONTRIBUTING.md, assets/VERSION, assets/SHA256SUMS, scripts/_helpers.sh.
What it can do
Migrate legacy Completions API calls to unified Responses API
Existing application code using OpenAI Completions API → Updated code compatible with Responses API
Migrate legacy Chat Completions API calls to unified Responses API
Existing application code using OpenAI Chat Completions API → Updated code compatible with Responses API
Analyze application code for API compatibility issues
Application source code files → Report of deprecated API usage and migration requirements
Generate migration guidance through Codex CLI
Legacy API implementation patterns → Step-by-step migration instructions and code suggestions
Transform API request structures
Legacy API request formats and parameters → Converted request structures for unified API
Update API response handling logic
Code that processes legacy API responses → Modified response handling for new API format
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.