feat: add api_mode selection to custom endpoint setup#6210
Closed
chinaboard wants to merge 1 commit into
Closed
Conversation
When configuring a custom endpoint, prompt the user to choose the API protocol (chat_completions, anthropic_messages, codex_responses, or auto-detect). Default is Enter-to-accept auto-detection; type '?' to see all options. Changes: - Add _prompt_api_mode_selection() helper with Enter-to-accept UX - _model_flow_custom(): prompt for api_mode after context length - _model_flow_named_custom(): read/apply saved api_mode from provider - _save_custom_provider(): persist api_mode in custom_providers entries - _custom_provider_map: include api_mode field Closes NousResearch#6209
bd7237a to
8719cc4
Compare
Contributor
|
Closing as already fixed on Triage notes (high confidence): If you still see this on the latest version, please reopen with reproduction steps. (Bulk-closed during a CLI triage sweep.) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds an API protocol (
api_mode) selection step to the custom endpoint setup flow. Closes #6209.Problem
Custom endpoint setup collects URL, API key, model, and context length — but never asks which API protocol to use. Auto-detection works for most URLs, but breaks with proxies/gateways that serve multiple protocols on the same URL, or endpoints where the URL gives no hints about the protocol.
Solution
Add a lightweight prompt after the context-length step:
Changes
_prompt_api_mode_selection()?to expand choices_model_flow_custom()_model_flow_named_custom()_save_custom_provider()api_modeparameter_custom_provider_mapapi_modefield from custom_providers entriesTesting
ast.parse)_detect_api_mode_for_urlin runtime_provider.py,_curses_prompt_choicein setup.py)