Skip to content

[Partner Nodes] add Gpt 5.5 and 5.5-pro LLM models#13673

Merged
bigcat88 merged 4 commits intomasterfrom
feat/api-nodes/openai-gpt5.5
May 5, 2026
Merged

[Partner Nodes] add Gpt 5.5 and 5.5-pro LLM models#13673
bigcat88 merged 4 commits intomasterfrom
feat/api-nodes/openai-gpt5.5

Conversation

@bigcat88
Copy link
Copy Markdown
Contributor

@bigcat88 bigcat88 commented May 2, 2026

API Node PR Checklist

Scope

  • Is API Node Change

Pricing & Billing

  • Need pricing update
  • No pricing update

If Need pricing update:

  • Metronome rate cards updated
  • Auto‑billing tests updated and passing

QA

  • QA done
  • QA not required

Comms

  • Informed Kosinkadink

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 2, 2026

📝 Walkthrough

Walkthrough

The PR adds two new members to the SupportedOpenAIModel enum: gpt-5.5 and gpt-5.5-pro. It also updates OpenAIChatNode's price_badge expression by inserting conditional branches for gpt-5.5-pro (usd: [0.03, 0.18] per 1K tokens) and gpt-5.5 (usd: [0.005, 0.03] per 1K tokens) before the existing gpt-5-* pricing branches.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and specifically describes the main change: adding gpt-5.5 and gpt-5.5-pro models to the Partner Nodes OpenAI integration.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description check ✅ Passed The pull request description provides a structured checklist confirming it adds GPT-5.5 and GPT-5.5-pro models with necessary pricing updates and QA.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


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

Comment @coderabbitai help to get the list of available commands and usage tips.

Signed-off-by: bigcat88 <bigcat88@icloud.com>
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

🧹 Nitpick comments (1)
comfy_api_nodes/nodes_openai.py (1)

744-753: 💤 Low value

Pricing values are correct; $contains ordering is correct.

Confirmed against OpenAI's official pricing page: gpt-5.5 is priced at $5 per 1M input tokens and $30 per 1M output tokens ($0.005/$0.030 per 1K — matches lines 751), and gpt-5.5-pro is priced at $30 per 1M input tokens and $180 per 1M output tokens ($0.030/$0.180 per 1K — matches line 746).

The branch order (gpt-5.5-pro before gpt-5.5) is correct: since "gpt-5.5" is a substring of "gpt-5.5-pro", reversing the order would misroute the pro model to the base pricing.

One minor forward-looking note: if gpt-5.5-mini or gpt-5.5-nano variants are introduced later, the current $contains($m, "gpt-5.5") branch would silently absorb them with pro pricing before any dedicated branches could be added. This is the same pattern used elsewhere in the expression (gpt-5, gpt-4.1, etc.), so it's consistent — just worth keeping in mind when adding sub-variants.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@comfy_api_nodes/nodes_openai.py` around lines 744 - 753, Pricing values and
ordering are correct, but to prevent future sub-variants (e.g., gpt-5.5-mini)
from being misclassified, tighten the gpt-5.5 branch condition: replace the
loose $contains($m, "gpt-5.5") check with a stricter matcher such as a regex
$match($m, "^gpt-5\\.5($|[^-])") or add a negative check like $contains($m,
"gpt-5.5") && !$contains($m, "gpt-5.5-"); keep the gpt-5.5-pro branch first and
leave its condition unchanged.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@comfy_api_nodes/nodes_openai.py`:
- Around line 744-753: Pricing values and ordering are correct, but to prevent
future sub-variants (e.g., gpt-5.5-mini) from being misclassified, tighten the
gpt-5.5 branch condition: replace the loose $contains($m, "gpt-5.5") check with
a stricter matcher such as a regex $match($m, "^gpt-5\\.5($|[^-])") or add a
negative check like $contains($m, "gpt-5.5") && !$contains($m, "gpt-5.5-"); keep
the gpt-5.5-pro branch first and leave its condition unchanged.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: c22161d1-ed3f-4929-bcb1-1138b3d26e21

📥 Commits

Reviewing files that changed from the base of the PR and between 013a544 and 213156a.

📒 Files selected for processing (1)
  • comfy_api_nodes/nodes_openai.py

gpt_4_1_nano = "gpt-4.1-nano"
o4_mini = "o4-mini"
o3 = "o3"
o1_pro = "o1-pro"
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Looks like these models will be deprecated soon?

o1
o1-pro
o4-mini
gpt-4.1-nano

@bigcat88 bigcat88 merged commit 6917bce into master May 5, 2026
17 checks passed
@bigcat88 bigcat88 deleted the feat/api-nodes/openai-gpt5.5 branch May 5, 2026 13:53
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.

3 participants