Foundry Local models from cache

I have Foundry Local running, and trough the command line, you can see I have the model GPT-OSS in my cache and it is running.

When I use github copilot, and I get to select models from Foundry Local (while using the AI Toolkit Extentions) I have also selected the GPT-OSS model, and it wants to start downloading it again, while it is already on my machine as you can see in the lists with cached models.

Also the Azure AI Foundry extention when selecting a model from my Foundry Local installation, it keeps asking to download the model again. It seems that those plugins do look to a different cache directory, or perhaps do not make the API call to Foundry Local to find what models are already available in the cache.

Something else I noticed as well, in VS Code I get to select the specific version of the model it needs to download, instead of harnessing the power of Foundry Local, to rely on the hardware detection of my machine.

As you can see in the postman call to foundry local the models are available in the cache.

Is this a bug in Foundry Local or in the extention that is not using the same cache folder?

Reproduce the GPT-OSS selection flow in VS Code through the AI Toolkit and Azure AI Foundry extensions, then compare it with the Postman request showing Foundry Local's cached models. Investigate whether the extensions use a different cache directory or omit the model-availability API call; done means an already cached model is recognized without another download.