fix: update developer tool prompts to use plan task status to match allowable statuses update_plan tool call#107
Merged
ahau-square merged 1 commit intomainfrom Oct 3, 2024
Merged
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
The developer toolkit's
update_plantool only accepts "planned", "complete", "failed" and "in-progress" as statuses, but the developer prompt currently has few-shot examples using the "pending" status. I noticed that this sometimes causes the first tool call from Goose toupdate_planto fail by trying to set statuses to "pending". This PR updates the prompt to use the "planned" status everywhere instead of "pending".