[Feature]: OpenHands-managed provider fallback for Codex ACP conversations

Aperta
#6,964 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
22/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
ai, backend

Direzione di ricerca

This is a design-level request: no file, class or test is named, and the reporter explicitly leaves the scope as "Unknown". Start by reading how Codex ACP conversations are configured and launched in the Agent Server, and where the existing native OpenHands LLM fallback is wired, to judge whether provider switching can be layered on without touching Codex itself. Done means the four acceptance criteria hold: opt-in bounded failover, an explicit report of the provider/model change, workspace preservation with a clear stop when continuity fails, and no credential leakage or tool-action replay. A maintainer should decide feasibility and shape before anyone starts coding.

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

Descrizione

priority:low
Is there an existing feature request for this?
  • I have searched existing issues and feature requests, and this is not a duplicate.
Problem or Use Case

Hi team! Would you consider adding opt-in provider fallback managed by OpenHands for Codex-backed ACP conversations?

My use case is a ChatGPT-backed Codex primary, with a separately authenticated Kimi Coding backup when the primary hits its quota or has a temporary outage. I'd like to keep Codex as the execution engine rather than switch to a different agent.

Kimi documents custom-provider support through Codex, so this is a request for a general orchestration capability, not a new provider-specific integration.

Desired Behavior

Let users configure a primary and backup provider/model, their credential references, and bounded failover conditions at the OpenHands layer, without requiring Codex itself to implement automatic failover.

The important part is a safe, visible handover. I'm not assuming native Codex session state can simply transfer between providers. If a fresh session or reconstructed context is needed, please make that clear and stop if safe continuation isn't possible.

Acceptance Criteria
  • Failover is opt-in, bounded, and triggered by configured conditions such as quota exhaustion or temporary provider failures.
  • Codex remains the execution engine, and the actual provider/model change is reported explicitly.
  • The workspace is preserved, with safe context recovery or a clear stop when continuity cannot be established.
  • Credentials remain protected, completed tool actions are not replayed, and permission or policy denials are not bypassed.
Alternatives Considered

Native OpenHands LLM fallback applies to a different inference path. openai/codex#32341 requests failover inside Codex; this request is for OpenHands-owned orchestration that can be considered independently.

Automatically routing work to competing providers may not align with OpenAI's commercial incentives, so they may be less interested in prioritising that request. An OpenHands-managed implementation would avoid that dependency and keep fallback decisions provider-neutral.

Priority / Severity

Medium - Would improve experience

Estimated Scope

Unknown - Not sure about the technical complexity

Feature Area
  • Agent API / Core functionality
  • Agent Server
  • Configuration / Settings
Additional Context

If there's already a supported way to do this for Codex ACP conversations, a pointer to its configuration and continuity guarantees would be very welcome. Thanks for taking a look!

Lingua principale
Python
Stelle
1.4k
Fork
797
Merge medio
1g 17h
PR unite (30g)
354

Preparare l'ambiente

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 OpenHands/software-agent-sdk

Tutte le issue di OpenHands/software-agent-sdk

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.