feat(agent): add OpenAI service tier configuration and UI support#2718
feat(agent): add OpenAI service tier configuration and UI support#2718maddygoround wants to merge 1 commit into
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 495af02aeb
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Some(value) => match value.to_ascii_lowercase().as_str() { | ||
| "auto" => Ok(Some(OpenAiServiceTier::Auto)), | ||
| "default" => Ok(Some(OpenAiServiceTier::Default)), | ||
| "flex" => Ok(Some(OpenAiServiceTier::Flex)), | ||
| "priority" => Ok(Some(OpenAiServiceTier::Priority)), |
There was a problem hiding this comment.
OpenAI's current API reference for Chat/Responses lists scale as a valid service_tier value, but this parser rejects anything except auto|default|flex|priority. For users with Scale Tier who set BUZZ_AGENT_SERVICE_TIER=scale, the agent now fails during startup configuration before it can make a request; include scale in the enum/parser/UI values or explicitly document why this supported tier is intentionally unavailable. See https://developers.openai.com/api/reference/resources/chat/subresources/completions/methods/create/.
Useful? React with 👍 / 👎.
| </p> | ||
| </div> | ||
|
|
||
| {isOpenAi && ( |
There was a problem hiding this comment.
This new service-tier env key is rendered solely from component/provider state, so AcpRuntimeCatalogEntry/deriveAgentConfigFieldModel never learn that buzz-agent supports the knob. Any shared config surface driven by the catalog (for example global defaults/onboarding) can diverge or omit it, and future harness metadata changes won't update this control; add the env key/capability to KnownAcpRuntime and project it through the config core before rendering it here.
Useful? React with 👍 / 👎.
1 participant
No description provided.