Provide a way to pull latest changes made to a registered tool on demand.

[sangee2004]

Steps to reproduce the problem:

1. Register a new tool from a github repo.
2. Add this tool to an agent.
3. Chat with the agent that involves this tool call.
4. Make some changes to the tool in the github repo.

There is no way for me to use the new version of the tool.

Even when I delete the tool and add the same tool again, I only get the version of the tool from step1 (changes from step4 are not available).

Expected Behavior:
Provide a way to pull latest changes made to a registered tool on demand.

[thedadams]

The backend changes for this PR have merged and this is ready for UI work.

The API for "force refresh" of a tool reference is POST /api/tool-references/{id}/force-refresh.

[ryanhopperlowe]

@cjellick - should this be available on all tools or just custom ones?

[cjellick]

Custom. @thedadams did you put distinguish between the two?

[ryanhopperlowe]

@cjellick @thedadams - The api that the backend exposes here seems to return an asynchronous response. My steps:

• Update tool
• Force Refresh Tool
• refetch GET /api/tool-references?type=tool

I do not see the list update as I'd expect. Refreshing gets the new data.

options here are to either make the response synchronous or implement Polling in the UI. If we were to go with Polling, I'd probably want some indicator as to when the tool was last updated so I know when to stop polling for the updates

Edit: I tried using revision as an indicator, but that did not help because there will be times where Force Refresh is triggered and there will be no changes to the repo. In this scenario, polling would start but never stop (unless with an arbitrary timeout)

With this in mind polling is not a good solution and I'd push to make the api synchronous. Very open to discussion on the matter though.

WDYT?

[thedadams]

Custom. @thedadams did you put distinguish between the two?

There is no difference from the backend perspective; it makes sense to refresh either.

@ryanhopperlowe Regarding synchronous/asynchronous: the refreshing is done asynchronously. I believe polling is already implemented for tool references in the UI because I added a resolved field to the tool reference object that is false or undefined until the tool reference has been updated. That field should still be useful in this case.

[sangee2004]

Able to pull the latest version for custom tools using "Refresh Tool" option provided the tool in the Tools page.