[Feature]: Support direct OpenAI Decisions API routing

Aperta
  • Qualcosa non va?
#8,190 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
55/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
backend-api-design

Direzione di ricerca

Start with src/combos/jev-decision-contract.ts and the Vercel Decisions support in PR #7574; trace how decision provider connection testing and routing select request and response formats. Compare that path with OpenAI’s Decisions API requirements in the linked docs. Done means an OpenAI key limited to Decisions → Write can be tested and used for routing while existing model and effort restrictions, timeouts, fallbacks, and other backends continue to work.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement proxy
Area

Proxy and routing

What are you trying to accomplish?

I'd like to use my OpenAI API credits to choose the model and reasoning effort for a JEV Combo. The selected models would still run through my existing provider connections, ncluding my existing Codex-login provider.

What prevents this today?

The v2.97.0 code only recognises ai-gateway.vercel.sh as a Decisions endpoint. Pointing a decision provider at OpenAI still uses the System One request format.

This comes from checking the source. I haven't tested it with a live OpenAI request.

What should OpenCodex do?

Let users connect directly to OpenAI's Decisions API with their own API key, using OpenAI's request and response format.

Connection testing and routing should work with a key limited to Decisions → Write. The existing model and effort restrictions, timeouts, fallbacks, and other decision backends should keep working as they do today.

Example usage or interface

Add a decision provider with these settings from OpenAI's API docs:

Endpoint: https://api.openai.com/v1/decisions
Model: gpt-6-luna
Authentication: OpenAI API key

Then select it as the decision provider for a JEV Combo containing my existing Codex models.

Alternatives or workarounds

I've considered TypeSafe JEV, Vercel AI Gateway, and using a Responses model as the router. I'd prefer to use the Decisions API directly through OpenAI.

Additional context

PR #7574 added Vercel Decisions support. OpenAI also lists Decisions as covered by eligible ChatGPT API credits.

Checks
  • I searched existing issues and documentation.
  • This request describes a concrete OpenCodex workflow rather than merely naming a desired technology.
  • I removed secrets and personal data.
Lingua principale
TypeScript
Stelle
16.9k
Fork
1.3k
Merge medio
19h 31m
PR unite (30g)
676

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di lidge-jun/opencodex

Tutte le issue di lidge-jun/opencodex

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.