fix(agent): fix triage model provider path for gpt-5-nano - #11206
Merged
Conversation
Corrects the model identifier to `kilo/openai/gpt-5-nano`. Previously, running the triage agent failed because the prefix was missing, throwing an Model Not Found error. Resolved by explicitly using the `kilo/openai/gpt-5-nano` target path.
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (1 file)
Reviewed by claude-4.6-sonnet-20260217 · 265,205 tokens Review guidance: REVIEW.md from base branch |
chrarnoldus
approved these changes
Jun 15, 2026
t7tran
pushed a commit
to t7tran/kilocode
that referenced
this pull request
Aug 14, 2026
fix(agent): fix triage model provider path for gpt-5-nano
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
2 participants
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.
Context
This PR fixes an issue where running the triage agent crashes with an
UnknownError. The router was attempting to load the target model usingopenai/gpt-5-nano, which couldn't be resolved by the backend server logs. Updating the identifier to its explicit path resolves the mapping failure.Implementation
Updated the triage agent configuration to explicitly target
kilo/openai/gpt-5-nano. No major structural changes or refactors were required.Screenshots / Video
Note: The command, when run locally, still fails, but not due to a missing model. My account currently does not have any credits.
How to Test
Manual/local verification
bun dev run --agent triagelocally and confirmed that the model initializes properly and successfully processes the triage payload instead of erroring out.Reviewer test steps
kilo run --agent triage "The following issue was just opened, triage it:"