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.

Read the relevant Lizard page

#Caterpillar #LizardLLM #GPUProgramming #LocalAI #GGUF

<!-- lizard-marketing-slot:day-25-pm -->