-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
🎅 I WISH LITELLM HAD... #361
Comments
[LiteLLM Client] Add new models via UI Thinking aloud it seems intuitive that you'd be able to add new models / remap completion calls to different models via UI. Unsure on real problem though. |
User / API Access Management Different users have access to different models. It'd be helpful if there was a way to maybe leverage the BudgetManager to gate access. E.g. GPT-4 is expensive, i don't want to expose that to my free users but i do want my paid users to be able to use it. |
cc: @yujonglee @WilliamEspegren @zakhar-kogan @ishaan-jaff @PhucTranThanh feel free to add any requests / ideas here. |
[Spend Dashboard] View analytics for spend per llm and per user
|
Auto select the best LLM for a given task If it's a simple task like responding to "hello" litlellm should auto-select a cheaper but faster llm like j2-light |
Integration with NLP Cloud |
That's awesome @Pipboyguy - dm'ing on linkedin to learn more! |
@ishaan-jaff check out this truncate param in the cohere api This looks super interesting. Similar to your token trimmer. If the prompt exceeds context window, trim in a particular manner. I would maybe only run trimming on user/assistant messages. Not touch the system prompt (works for RAG scenarios as well). |
Option to use Inference API so we can use any model from Hugging Face 🤗 |
@haseeb-heaven you can already do this -
from litellm import completion
response = completion(model="huggingface/gpt2", messages=[{"role": "user", "content": "Hey, how's it going?"}])
print(response) |
Wow great thanks its working. Nice feature |
Support for inferencing using models hosted on Petals swarms (https://github.com/bigscience-workshop/petals), both public and private. |
@smig23 what are you trying to use petals for ? We found it to be quite unstable and it would not consistently pass our tests |
finetuning wrapper for openai, huggingface etc. |
@shauryr i created an issue to track this - feel free to add any missing details here |
Specifically for my aims, I'm running a private swarm as a experiment with a view to implementing with in private organization, who have idle GPU resources, but it's distributed. The initial target would be inferencing and if litellm was able to be the abstraction layer, it would allow flexibility to go another direction with hosting in the future. |
I wish the litellm to have a direct support for finetuning the model. Based on the below blog post, I understand that in order to fine tune, one needs to have a specific understanding on the LLM provider and then follow their instructions or library for fine tuning the model. Why not the LiteLLM do all the abstraction and handle the fine-tuning aspects as well? https://docs.litellm.ai/docs/tutorials/finetuned_chat_gpt |
I wish LiteLLM has a support for open-source embeddings like sentence-transformers, hkunlp/instructor-large etc. Sorry, based on the below documentation, it seems there's only support for the Open AI embedding. |
I wish LiteLLM has the integration to cerebrium platform. Please check the below link for the prebuilt-models. |
@ranjancse26 what models on cerebrium do you want to use with LiteLLM ? |
@ishaan-jaff The cerebrium has got a lot of pre-built model. The focus should be on consuming the open-source models first ex: Lama 2, GPT4All, Falcon, FlanT5 etc. I am mentioning this as a first step. However, it's a good idea to have the Litellm take care of the internal communication with the custom-built models too. In-turn based on the API which the cerebrium is exposing. |
@smig23 We've added support for petals to LiteLLM https://docs.litellm.ai/docs/providers/petals |
I wish Litellm has a built-in support for the majority of the provider operations than targeting the text generation alone. Consider an example of Cohere, the below one allows users to have conversations with a Large Language Model (LLM) from Cohere. |
I wish Litellm has a ton of support and examples for users to develop apps with RAG pattern. It's kind of mandatory to go with the standard best practices and we all wish to have the same support. |
I wish Litellm has use-case driven examples for beginners. Keeping in mind of the day-to-day use-cases, it's a good idea to come up with a great sample which covers the following aspects.
|
I wish Litellm to support for various known or popular vector db's. Here are couple of them to begin with.
|
I wish Litellm has a built-in support for performing the web-scrapping or to get the real-time data using known provider like serpapi. It will be helpful for users to build the custom AI models or integrate with the LLMs for performing the retrieval augmented based generation. https://serpapi.com/blog/llms-vs-serpapi/#serpapi-google-local-results-parser |
I wish litellm had an API to check available models from providers in real time. |
I wish LiteLLM had support for Sambaverse. Thanks |
Discord alerting would be nice |
Wilcard for model_name property in model_list:
|
@ggallotti would that be similar to how we do it for openai today - https://docs.litellm.ai/docs/providers/openai#2-start-the-proxy |
Thanks for the response. |
Streamlined way to call vision and non-vision models would be great. Being LLM-agnostic is a big reason why I use the package but currently still have to handle different request format depending on which model it goes to. For example: Calling GPT4 Vision, messages.content is an array. Using the same code to call Azure's Command R+ would result in
I'm aware this is on the model provider's side, but GPT's non-vision models for example support both format. |
@ducnvu seems like something we need to fix - can you share the command r call? |
@krrishdholakia Thanks for the prompt response, the call is something like this. I don't have access to all models supported by litellm to test but so far OpenAI models work with both string messages.content and the format below, Command R is where I first encounter this error. All my calls are through Azure.
|
Hi guys, I am trying to use open interpreter with gemini 1.5 flash and getting this error: raise APIConnectionError( by default, open interpreter use functions and it seems to fail. Does google gemini 1.5 via litellm supports functions? Which version? If does not support, I wish litellm had this implemented... |
Ok, functions or tools is defintely not working. I am following this tutorial and works greatly calling the gemini api directly: However, passing the same set of commands to litellm, gives this error:
I think part of the problem is in the utils.py:6570 check where the
gemini supports way more than that. I am making a call like this:
|
@guiramos got it - found the issue, we have it implemented for vertex ai, not google ai studio (which i think is what you're calling). Can you try running this with return litellm.completion(
messages=messages,
temperature=0.0,
model="vertex_ai/gemini-1.5-pro",
tools=tools,
safety_settings=[
{
"category": "HARM_CATEGORY_HARASSMENT",
"threshold": "BLOCK_NONE",
},
{
"category": "HARM_CATEGORY_HATE_SPEECH",
"threshold": "BLOCK_NONE",
},
{
"category": "HARM_CATEGORY_SEXUALLY_EXPLICIT",
"threshold": "BLOCK_NONE",
},
{
"category": "HARM_CATEGORY_DANGEROUS_CONTENT",
"threshold": "BLOCK_NONE",
},
]
) and let me know if that works? - https://docs.litellm.ai/docs/providers/vertex Also tracking the issue for gemini google ai studio - #3086 |
@krrishdholakia I could not test with vertex as I don't have a api key for that. Also, I tried for google studio and did work! Using the new version 1.40.2. Do you have an estimate day for this? Please help. |
+1. Would be great to gave an estimate for when 1.5 pro w/ tools is supported using AI studio. |
hey @danielflaherty @guiramos this should be fixed by end of week |
@krrishdholakia really appreciate this! Thank you! |
@horahoradev This is live now https://docs.litellm.ai/docs/proxy/alerting#advanced---using-discord-webhooks @horahoradev any chance we can hop on a call sometime this week? I'd love to learn how we can improve litellm for you My linkedin if you prefer DMs: https://www.linkedin.com/in/reffajnaahsi/ |
Hi @nbaav1 We support this using the @nbaav1 any chance we can hop on a call ? I'd love to learn how how we can improve litellm for you.
![]()
|
Support for Redis Clusters. LiteLLM currently only supports Redis Standalone nodes. |
support vision on local images litellm/litellm/llms/prompt_templates/factory.py Lines 624 to 635 in 3a35a58
|
Support for custom models imported in Bedrock. Use case: we have a fine-tuned model deployed in Bedrock. The tuned model is based on OpenOrca, so the start and end tokens are different than instruct version. If the provider is
Tokens Tried using a custom provider as a workaround. However, the body is empty and the request fails:
The only thing we need is that prompt template configuration is respected, as it is done with
litellm/litellm/llms/bedrock.py Lines 743 to 746 in 3a35a58
|
Hey @motin this is possible already Proxy: https://docs.litellm.ai/docs/proxy/reliability#test---client-side-fallbacks |
First: We ❤️ LiteLLM I admit I haven't thought the API through well, since this is a feature that only one providers offers at this point (but it likely won't be the last). |
Hey @andresd95 bedrock custom prompts is fixed in latest release - can you confirm this works for you? Hey @Taytay tracking #4284. DM'ed on LinkedIn to setup a support channel on this as well |
Awesome @krrishdholakia! I tested and it works wonderfully. Here is the configuration I used for OpenOrca, in case anyone else has the same use case:
Thank you! |
This is a ticket to track a wishlist of items you wish LiteLLM had.
COMMENT BELOW 👇
With your request 🔥 - if we have any questions, we'll follow up in comments / via DMs
Respond with ❤️ to any request you would also like to see
P.S.: Come say hi 👋 on the Discord
The text was updated successfully, but these errors were encountered: