Skip to content

fix: strip empty messages on OpenAI->Claude translation#295

Closed
KooshaPari wants to merge 1 commit intorouter-for-me:mainfrom
KooshaPari:feat/clean-base-1698-strip-empty-messages-rebase
Closed

fix: strip empty messages on OpenAI->Claude translation#295
KooshaPari wants to merge 1 commit intorouter-for-me:mainfrom
KooshaPari:feat/clean-base-1698-strip-empty-messages-rebase

Conversation

@KooshaPari
Copy link
Copy Markdown

Cherry-picks the same behavioral fix from router-for-me#1698 onto a clean base of router-for-me/CLIProxyAPIPlus main.\n\nThis avoids the large historic divergence from the previous branch and keeps only the intended one-file change.

Cherry-picked from merge/1698-strip-empty-messages-openai-to-claude into aligned base
@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @KooshaPari, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refines the translation logic from OpenAI to Claude API requests by explicitly filtering out and skipping any text content parts that are empty strings. This ensures that only meaningful text content is passed to the Claude API, enhancing the robustness and reliability of the translation layer by preventing issues caused by empty message components.

Highlights

  • OpenAI to Claude Translation Fix: Implemented a behavioral fix to prevent empty text messages from OpenAI requests from being translated and included in Claude requests, which could previously lead to errors or unexpected behavior.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • internal/translator/claude/openai/chat-completions/claude_openai_request.go
    • Added a check to skip text content parts if their value is an empty string during the conversion of OpenAI requests to Claude format.
Activity
  • No activity has been recorded for this pull request yet.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@KooshaPari KooshaPari closed this Feb 26, 2026
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request addresses an issue where empty messages were not being stripped during the translation from OpenAI to Claude format. The changes correctly add checks to skip empty text content parts for system, user, and assistant messages. I've added one comment regarding code duplication which could be addressed in a follow-up to improve maintainability.

Comment on lines +159 to 165
textContent := part.Get("text").String()
if textContent == "" {
return true
}
textPart := `{"type":"text","text":""}`
textPart, _ = sjson.Set(textPart, "text", part.Get("text").String())
textPart, _ = sjson.Set(textPart, "text", textContent)
out, _ = sjson.SetRaw(out, fmt.Sprintf("messages.%d.content.-1", systemMessageIndex), textPart)
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This logic to handle empty text parts is duplicated for system messages here, and for user/assistant messages later in this file (lines 185-191). To improve maintainability, consider refactoring this into a helper function in a future change.

@KooshaPari KooshaPari deleted the feat/clean-base-1698-strip-empty-messages-rebase branch February 27, 2026 09:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant