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
…atch allowable task status in 'update_plan' for developer tool
Collaborator
|
Hi @ahau-square , Good catch! Just wondering whether it will be also useful to give a bit more explanation of each status here, especially what |
lifeizhou-ap
approved these changes
Oct 3, 2024
Contributor
Author
I don't necessarily want to add more explanation into the status there as that would use up tokens in the tool description, but Goose seems pretty good at understanding what each status is for. Planned is for tasks that it plans to do, complete for tasks it's finished that were in its plan, failed is tasks that errored for example in a failed tool call, and in-progress seems to be for tasks that it is about to do without tool calling (e.g., summarize something it just retrieved with ripgrep) |
lifeizhou-ap
added a commit
that referenced
this pull request
Oct 4, 2024
* main: fix: exit the goose and show the error message when provider environment variable is not set (#103) fix: Update OpenAI pricing per https://openai.com/api/pricing/ (#110) fix: update developer tool prompts to use plan task status to match allowable statuses update_plan tool call (#107) fix: removed the panel in the output so that the user won't have unnecessary pane borders in the copied content (#109) docs: update links to exchange to the new location (#108) chore: setup workspace for exchange (#105)
lily-de
pushed a commit
that referenced
this pull request
Oct 7, 2024
…llowable statuses update_plan tool call (#107)
lukealvoeiro
added a commit
that referenced
this pull request
Oct 9, 2024
* main: (41 commits) chore: Add goose providers list command (#116) docs: working ollama for desktop (#125) docs: format and clean up warnings/errors (#120) docs: update deploy workflow (#124) feat: Implement a goose run command (#121) feat: saved api_key to keychain for user (#104) docs: add callout plugin (#119) chore: add a page to docs for Goose application examples (#117) fix: exit the goose and show the error message when provider environment variable is not set (#103) fix: Update OpenAI pricing per https://openai.com/api/pricing/ (#110) fix: update developer tool prompts to use plan task status to match allowable statuses update_plan tool call (#107) fix: removed the panel in the output so that the user won't have unnecessary pane borders in the copied content (#109) docs: update links to exchange to the new location (#108) chore: setup workspace for exchange (#105) fix: resolve uvx when using a git client or IDE (#98) ci: add include-markdown for mkdocs (#100) chore: fix broken badge on readme (#102) feat: add global optional user goosehints file (#73) docs: update docs (#99) chore(release): release 0.9.3 (#97) ...
ahau-square
added a commit
that referenced
this pull request
May 2, 2025
…llowable statuses update_plan tool call (#107)
cbruyndoncx
pushed a commit
to cbruyndoncx/goose
that referenced
this pull request
Jul 20, 2025
…llowable statuses update_plan tool call (block#107)
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
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".