Skip to content

Conversation

@jsibbison-square
Copy link
Contributor

Closes #3700

Ensure the final output tool is always available during vector and llm tool selections to avoid endless looping.

@jsibbison-square jsibbison-square merged commit 5de9f84 into main Jul 29, 2025
11 of 12 checks passed
@jsibbison-square jsibbison-square deleted the jsibbison-20250729-structured-output-vector branch July 29, 2025 02:18
michaelneale added a commit that referenced this pull request Jul 29, 2025
* main:
  fix: Ensures final output tool is available when using vector tool search (#3701)
  chore: adding in some new models token limits (#3685)
  blog: streamlining detection development w/ recipes (#3689)
  fix: have option for cli providers to use their configured or default model  (#3683)
  docs: new blog post and corrections to an old one on goosehints (#3657)
  Resolve sub recipe path relative to the parent recipe path (#3642)
  Speed up recipe loading from deeplinks and various fixes (#3662)
  fix cmd + , not opening settings (#3694)
  Add warning when JSON env parsing fails. (#3696)
  chore: refactor session naming into provider (#3678)
  feat (ui): File picker for scheduling recipes default to recipe dir (#3611)
  fix: address issue with streamable http interactions via mcp (#3693)
  Provider scenario tests (#3688)
michaelneale added a commit that referenced this pull request Jul 29, 2025
* main:
  fix: Ensures final output tool is available when using vector tool search (#3701)
  chore: adding in some new models token limits (#3685)
atarantino pushed a commit to atarantino/goose that referenced this pull request Aug 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Structured output does not work when vector tool selection strategy is used

3 participants