Gustav Hertz

@FabianHertwig Thanks for the link. The suggested workaround seems to work for `codestral-latest` and `codestral-2407` but not for `codestral-2501` which is the model I'm interested in. I tried the linked...

I also want it to work for Continue, so let's try to make it work together! Ill try your script too.

Continue calls `" url = f"{api_base.rstrip('/')}/fim/completions"` not `url = f"{api_base.rstrip('/')}/v1/completions"` for autocomplete. (a bit depending on what provider you report in continue, but if you set it to Mistral it...

I set up a local proxy between continue and LiteLLM to log all the requests and responses. This is what the request looks like: ``` { "timestamp": "2025-03-14T11:50:33.031801", "method": "POST",...

The other option is to use a pass-through endpoint, but I struggled to get the keys to work correctly there.

Hi again. I share your view that the endpoint is not implemented. The codestral implementation in litellm/llms/codestral/completion is not reachable if I understand the code correctly, but I feel like...

Hey @FabianHertwig I think I figured out how to call my Azure deployment of codestral through litellm. You are not gonna like it. LiteLLM does not support the `/fim/completions` endpoint...

@krrishdholakia @ishaan-jaff If you guys see this -> please implement the `fim/completions` endpoint :)

You can make Conitnue call the /completions endpoint with a suffix parameter if you set your continue config.yaml like this: ``` - name: Autocompletion provider: siliconflow model: codestral-latest apiBase: https://...

@FabianHertwig Did you get the cost tracking in LiteLLM to work properly? I cannot seem to overwrite the 0$ default cost using this here: ``` - model_name: codestral-latest litellm_params: model:...