feat(api): update gpt-4o usage to gpt-4.1#2536
Merged
nickscamara merged 1 commit intomainfrom Dec 10, 2025
Merged
Conversation
nickscamara
approved these changes
Dec 10, 2025
Contributor
There was a problem hiding this comment.
1 issue found across 7 files
Prompt for AI agents (all 1 issues)
Check if these issues are valid — if so, understand the root cause of each and fix them.
<file name="apps/api/src/lib/extract/url-processor.ts">
<violation number="1" location="apps/api/src/lib/extract/url-processor.ts:21">
P2: Model changed to `gpt-4.1` but cost tracking still references `openai/gpt-4o`. The `costTracking.addCall` call (lines 44-58) should use `openai/gpt-4.1` for both the `model` field and `calculateCost` to ensure accurate cost tracking and analytics.</violation>
</file>
Reply to cubic to teach it or ask questions. Re-run a review with @cubic-dev-ai review this PR
| try { | ||
| const result = await generateText({ | ||
| model: getModel("gpt-4o", "openai"), | ||
| model: getModel("gpt-4.1", "openai"), |
Contributor
There was a problem hiding this comment.
P2: Model changed to gpt-4.1 but cost tracking still references openai/gpt-4o. The costTracking.addCall call (lines 44-58) should use openai/gpt-4.1 for both the model field and calculateCost to ensure accurate cost tracking and analytics.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At apps/api/src/lib/extract/url-processor.ts, line 21:
<comment>Model changed to `gpt-4.1` but cost tracking still references `openai/gpt-4o`. The `costTracking.addCall` call (lines 44-58) should use `openai/gpt-4.1` for both the `model` field and `calculateCost` to ensure accurate cost tracking and analytics.</comment>
<file context>
@@ -18,7 +18,7 @@ export async function generateBasicCompletion(
try {
const result = await generateText({
- model: getModel("gpt-4o", "openai"),
+ model: getModel("gpt-4.1", "openai"),
prompt: prompt,
providerOptions: {
</file context>
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
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 by cubic
Switch model usage from gpt-4o to gpt-4.1 across extraction and URL processing. Primary calls still use gpt-4o-mini; gpt-4.1 is now the retry/fallback.
Written for commit 1214cab. Summary will update automatically on new commits.