[Feature]: OpenHands-managed provider fallback for Codex ACP conversations
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
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
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
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di OpenHands/software-agent-sdk
-
[Bug]: `list_directory` reports a complete listing as truncated when a directory has exactly 500 entriesForse già presa @balabommablock-cpu l’ha presa 29 giorni fa. Apertabug priority:low ready-for-dev
Difficoltà 2/5 1-3 ore Idoneità per principianti 87/100
OpenHands/software-agent-sdk#6133 ·
I maintainer di solito rispondono entro 1 giorno
-
[Bug]: Command hook that exits 1 is treated as blocking when its stdout is a JSON `deny` or `continue: false`Forse già presa Una pull request collegata a questa issue è aperta o già unita. Apertabug priority:low ready-for-dev
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
OpenHands/software-agent-sdk#6116 · 3 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
[Bug]: TypeScript GET-with-body requests remain pending after a truncated responseForse già presa @BlueRaddish l’ha presa 34 giorni fa. Apertabug priority:low ready-for-dev
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
OpenHands/software-agent-sdk#6059 ·
I maintainer di solito rispondono entro 1 giorno
-
[Bug]: Document whether `prompt_tokens` includes `cache_read_tokens` in accumulated token usageForse già presa @Jaxon1216 l’ha presa 36 giorni fa. Apertapriority:low ready-for-dev
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
OpenHands/software-agent-sdk#5975 ·
I maintainer di solito rispondono entro 1 giorno
-
priority:low
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
OpenHands/software-agent-sdk#5708 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di OpenHands/software-agent-sdk
Issue simili
-
[Bug]: reme CLI crashes when the running server used a relative config pathForse già presa @nurlanmnn l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
agentscope-ai/ReMe#770 ·
I maintainer di solito rispondono entro 1 giorno
-
Pi: paused model calls are reported as "not signed in" when the model's provider comes from an extensionForse già presa @balcsida l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 73/100
microsoft/TokenEconomizer#288 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 67/100
sickn33/agentic-awesome-skills#2437 ·
I maintainer di solito rispondono entro 1 giorno
-
site-bug triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
ethereum/consensus-specs#5846 ·
I maintainer di solito rispondono entro 1 giorno