Revert "Support OpenAI o3 and o4-mini"

[twfz7]

💻 变更类型 | Change Type

• feat
• fix
• refactor
• perf
• style
• test
• docs
• ci
• chore
• build

🔀 变更说明 | Description of Change

📝 补充信息 | Additional Information

Summary by CodeRabbit

• Bug Fixes
  • Improved handling of vision models by updating which models are recognized as vision-capable.
• Chores
  • Removed outdated model identifiers from internal model lists.

[vercel]

@twfz7 is attempting to deploy a commit to the NextChat Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

This change updates the handling of vision-capable models within the application. It removes the "o3" and "o4-mini" models from both the list of supported OpenAI models and the regular expressions used to identify vision models. Corresponding logic in the OpenAI platform integration is updated so that the max_tokens property is now always added for vision models, regardless of whether they are "o1" or "o3" prefixed, and the check for "o4-mini" is eliminated from the relevant condition.

Changes

Files/Paths	Change Summary
app/client/platforms/openai.ts	Modified logic to remove "o4-mini" from the isO1OrO3 check and to always add max_tokens for vision models.
app/constant.ts	Removed "o3" and "o4-mini" from both the VISION_MODEL_REGEXES array and the openaiModels array.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant OpenAI Platform
    participant Constants

    Client->>Constants: Get vision model regexes and model list
    Client->>OpenAI Platform: Prepare request payload
    OpenAI Platform->>Constants: Check if model is vision-capable
    OpenAI Platform-->>Client: Add max_tokens if vision model (no longer excludes o1/o3)

Loading

Possibly related PRs

• Use regular expressions to make the code more concise. #5998: Both PRs modify the VISION_MODEL_REGEXES array in app/constant.ts by removing specific model regex patterns, directly relating their changes to the handling of vision model identification.
• fix no max_tokens in payload when the vision model name does not cont… #5304: Both PRs modify the logic in app/client/platforms/openai.ts related to when the max_tokens property is added to the request payload for vision models, specifically broadening the conditions under which max_tokens is set.
• chore: o1模型使用max_completion_tokens #5788: Both PRs modify the handling of token limits for the "o1" model in app/client/platforms/openai.ts, with the main PR adjusting conditions for adding max_tokens and the retrieved PR introducing max_completion_tokens specifically for the "o1" model.

Suggested labels

planned

Suggested reviewers

• Dogtiti
• lloydzhou

Poem

The models "o3" and "o4-mini" hop away,
No longer in our vision field,
Now all sighted models get their say,
With max tokens always revealed.
Constants trimmed, logic neat—
This code garden’s looking sweet!
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3809375 and 0c91604.

📒 Files selected for processing (2)

• app/client/platforms/openai.ts (2 hunks)
• app/constant.ts (0 hunks)

💤 Files with no reviewable changes (1)

• app/constant.ts

🔇 Additional comments (2)

app/client/platforms/openai.ts (2)

199-201: Variable name now accurately reflects checked model prefixes

The condition for the isO1OrO3 boolean variable has been updated to remove the check for models starting with "o4-mini", aligning with the PR objective of reverting support for these models. The variable name now accurately represents what it's checking.

---

246-247: Simplified handling for vision models

The condition for adding max_tokens has been simplified to apply to all vision models, rather than having special handling for certain model types. This change ensures consistent behavior across all vision-capable models and makes the code more maintainable.

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.