Proposal: Allow a model with no model ("langfuse"), and per-provider keys for langfuse/other prompt management backends. #11614
radiosilence
started this conversation in
Ideas
Replies: 1 comment
-
Ok after some experimentation, it seems that if you don't pass the API key to the config, it picks up the correct one from your environment anyway! So you can just do: - model_name: dynamic
litellm_params:
model: langfuse/
- model_name: dynamic-claude-fallback
litellm_params:
model: langfuse/anthropic/claude-sonnet-4-20250514 and as long as you have |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Currently if I want to use langfuse I have to define it like this somehow:
However, I might be defining model in my langfuse config, so the model param becomes moot:
However, if I now want to try out claude in using langfuse config, it breaks because the API key is the wrong one.
One way to solve this is to store the
api_key
in the langfuse prompt config, which is a terrible idea and bad.Proposal
You can sooorta do this with custom handlers I think, however, it isn't great or formalized and a bit of a hack. I will have a go at doing this after standup and breakfast.
Beta Was this translation helpful? Give feedback.
All reactions