feat: per-task model override for kanban workers#23234
Closed
hongchen1993 wants to merge 1 commit into
Closed
Conversation
- Add model_override field to Task class and tasks schema - Add migration for existing databases - Spawn worker with -m model when model_override is set
Contributor
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
4 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.
Summary
Allow Producer to set per-Consumer model via
model_overridefield on kanban tasks.Changes
Task.model_overridefield (Optional[str])_default_spawnpasses-m modelwhen model_override is setMotivation
Without per-task model override, ALL workers run on the profile's default model. This means:
This enables Hands allocation matrix to route per-Consumer model selection.
Usage