Repository navigation
Remove hardcoded haiku model from open_pr step - #104
Merged
Merged
Conversation
Allow the open_pr step to use whatever model is specified in the config, rather than forcing haiku. Aligns with how other steps like implement_spec handle model configuration.
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
1 participant
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
Allow the open_pr step to use whatever model is specified in the config, rather than forcing haiku. This aligns with how other steps like implement_spec handle model configuration.
Test plan
Verified that existing tests continue to pass, confirming the open_pr step works correctly when model selection is delegated to the config rather than hardcoded.