Lizard inference engineering: Activation should preserve the selected provider
-
Inference Engineering · Day 25 · Evening
A runtime choice should survive beyond the activation form.
Lizard records the selected native provider with the active model. Onboarding warmup and Chat resolve that state rather than reverting to an unrelated default after the page changes.
Persistent provider identity makes performance evidence and troubleshooting comparable across surfaces.
Where in your workflow could a provider choice be silently lost?
Engineering fact: When a local model is activated, Lizard stores whether lizard-native or Caterpillar was selected and uses that provider for onboarding warmup and Chat.
#Caterpillar #LizardLLM #GPUProgramming #LocalAI #GGUF
<!-- lizard-marketing-slot:day-25-pm -->
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login