Skip to content

Conversation

@lifeizhou-ap
Copy link
Collaborator

@lifeizhou-ap lifeizhou-ap commented Jul 30, 2025

Why

  1. Simplify agent/agent.rs
  2. Fix the issue Goose Recipe/Sub recipe does not work when GOOSE_ROUTER_TOOL_SELECTION_STRATEGY is set #3730 in Goose cli

What

* main:
  Ok, well, that got out of hand (#3718)
  feat: openrouter out of the box experience for goose installations (#3507)
  Iand/make goosehints blog post visible (#3729)
  skip app-related CI jobs for doc/blog PRs (#3704)
  Blog:How OpenRouter Unlocked Our Workshop Strategy (#3726)
let (frontend_requests, remaining_requests, filtered_response) =
self.categorize_tool_requests(response).await;

// Record tool calls in the router selector
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

moved this logic outside of this function

} else if tool_call.name == ROUTER_VECTOR_SEARCH_TOOL_NAME
|| tool_call.name == ROUTER_LLM_SEARCH_TOOL_NAME
{
let selector = self.router_tool_selector.lock().await.clone();
Copy link
Collaborator Author

@lifeizhou-ap lifeizhou-ap Jul 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Moved the logic to tool_route_manager dispatch_route_search_tool function

}
};

// Append final_output tool if present (for structured output recipes, [Issue #3700](https://github.com/block/goose/issues/3700)
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is no longer needed as we used disabled the vector or llm strategy for recipe

})
.map_err(|e| ToolError::ExecutionError(e.to_string()));

drop(extension_manager);
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

need to release the lock as later on it uses read lock

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice

* main:
  Must have missed this one (#3733)
Copy link
Contributor

@wendytang wendytang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for cleaning this up - we actually don't use vector search strategy anymore as well

@lifeizhou-ap lifeizhou-ap merged commit e20a885 into main Jul 30, 2025
9 checks passed
@lifeizhou-ap lifeizhou-ap deleted the lifei/refactor-tool-route branch July 30, 2025 22:39
michaelneale added a commit that referenced this pull request Jul 31, 2025
* main:
  chord: refactor tool route (#3732)
katzdave added a commit that referenced this pull request Jul 31, 2025
* 'main' of github.com:block/goose:
  feat: Allow configuring hints filename(s) (#3269)
  Add support for mouse back nav button to Settings screen (#3195)
  chore: Remove the wrong tailwind package (#3754)
  chore: fix typo in desktop readme for goosed (#3752)
  feat: upgrade rmcp (#3738)
  feat: allow users view and edit their non-secret config's (#3005)
  fix: View extensions link (#3751)
  chord: refactor tool route (#3732)
@lifeizhou-ap
Copy link
Collaborator Author

Thank you @wendytang for review!

we actually don't use vector search strategy anymore as well
Just to confirm that

  1. Do we still support llm search strategy?

  2. we can remove the code related to "vector search strategy" including UI?

@wendytang
Copy link
Contributor

Do we still support llm search strategy?
We still support llm search strategy.

we can remove the code related to "vector search strategy" including UI?
Yes, we can remove any code related to vector search strategy including the UI - also let dev rel know to update the docs too

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.

3 participants