-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Sort providers in alphabetical vs random #5090
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
DOsinga
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need to sort them in the backend and the frontend? I would just go frontend.
I've been working on this: #5084 that does introduce the notion of a prefered provider
cli on goose configure drives me absolutely insane with random order. |
* 'main' of github.com:block/goose: Sort providers in alphabetical vs random (#5090)
…utonomous * origin/main: feat: add Daily Standup Report Generator recipe (#5123) (#5131) Sort providers in alphabetical vs random (#5090) Declarative providers (#5084) adding youtube link to firecrawl mcp tutorial, merge after 9am Eastern Oct 15 (#5173) Ollama integration: modified default model + added models (#5153) Fix codex subagent configuration in documentation (#5180) fix: include apple silicon build of the desktop app in build artifacts (#5174) fixing video embed (#5171) chore: clean up random unused files (#5166) fix: adjust download_cli.sh to tolerate no OS variable (#5169) mcp tutorial page for firecrawl (#5152) Remove orphaned tool calls before compaction (#5059) feat: add copy as markdown button to documentation pages (#5158) chore: include vendored node executable (#5160) remove extra whitespace from message (#5159)
* main: (55 commits) [docs] Add Blog Post: "Designing AI for Users, Not Just LLMs" (block#5190) docs: update cognee, jetbrains, mbot extensions config (block#5172) Minimally disable subagents when not in autonomous model (block#5149) Fix provider sort (block#5188) blog: Getting Started with Goose on Windows (block#5156) feat: add CI/CD Pipeline recipe (block#5183) feat: add Daily Standup Report Generator recipe (block#5123) (block#5131) Sort providers in alphabetical vs random (block#5090) Declarative providers (block#5084) adding youtube link to firecrawl mcp tutorial, merge after 9am Eastern Oct 15 (block#5173) Ollama integration: modified default model + added models (block#5153) Fix codex subagent configuration in documentation (block#5180) fix: include apple silicon build of the desktop app in build artifacts (block#5174) fixing video embed (block#5171) chore: clean up random unused files (block#5166) fix: adjust download_cli.sh to tolerate no OS variable (block#5169) mcp tutorial page for firecrawl (block#5152) Remove orphaned tool calls before compaction (block#5059) feat: add copy as markdown button to documentation pages (block#5158) chore: include vendored node executable (block#5160) ...
* main: Skip hidden & real format (#5194) docs: Hacktoberfest blog submission - Best Practices for Using Goose in Enterprise Environments by Anudhyan Datta. (#5184) docs: prompt injection detection (#5193) Fix mcp large response race condition (#5065) Compaction overhaul (#5186) fix: #3960 better approach to input schema for dynamic task params (#5189) used recipe id or deeplink to start agent (#5154) [docs] Add Blog Post: "Designing AI for Users, Not Just LLMs" (#5190) docs: update cognee, jetbrains, mbot extensions config (#5172) Minimally disable subagents when not in autonomous model (#5149) Fix provider sort (#5188) blog: Getting Started with Goose on Windows (#5156) feat: add CI/CD Pipeline recipe (#5183) feat: add Daily Standup Report Generator recipe (#5123) (#5131) Sort providers in alphabetical vs random (#5090) Declarative providers (#5084) adding youtube link to firecrawl mcp tutorial, merge after 9am Eastern Oct 15 (#5173) Ollama integration: modified default model + added models (#5153) Fix codex subagent configuration in documentation (#5180)
I know we'd also discussed potentially having different tiers of provider support within our testing; is this something we want to potentially expose here?