Skip to content

roadmap.md

Latest commit

 

History

History
49 lines (35 loc) · 1.66 KB

roadmap.md

File metadata and controls

49 lines (35 loc) · 1.66 KB
Raw

Roadmap

Current Status

This project is paused. No stable public release or main-branch merge is planned while the product scope is unclear.

The current implementation is useful as a reference for:

  • Keeping Codex App signed in with ChatGPT while model requests use a third-party provider.
  • Splitting provider auth into a proxy-managed local file.
  • Handling service_tier conservatively for Responses API traffic.
  • Redacted diagnostics, request metadata, benchmark records, update, restore, and uninstall flows.

Not In Scope Today

This project does not currently translate Codex Responses API traffic into Chat Completions traffic. That means providers that only expose Chat Completions-style APIs, such as common DeepSeek, Kimi, GLM, MiniMax, and similar configurations, are not the primary target unless an upstream proxy already offers a Responses-compatible route.

Resume Criteria

The project becomes worth resuming if it adds a reliable, provider-agnostic adapter:

Codex Responses API
        |
        v
local adapter
        |
        v
provider Chat Completions API

The adapter should be data-driven rather than a pile of provider-specific branches. It would need to preserve streaming behavior, tool calls, errors, usage metadata, model selection, reasoning-related fields where possible, and Codex's expectations for incremental Responses events.

Maintenance Policy

Until then, keep changes small:

  • Security fixes.
  • Broken uninstall or restore fixes.
  • Documentation updates that prevent user confusion.
  • Compatibility notes for existing users.

Avoid broad feature work unless it directly supports the Responses-to-Chat-Completions adapter.