Caterpillar is an inference runtime, not another model or agent orchestrator.

It loads the same GGUF foundation but organizes execution around a precompiled compute-graph plan. The design target is less repeated host coordination around token generation, with its own shader cache and optimized paths.

Keeping it separate from lizard-native lets both engines evolve and remain measurable.

Which part of your token loop is still being rebuilt or resubmitted every step?

Engineering fact: Caterpillar is a separate GGUF runtime whose execution core uses a precompiled compute-graph plan to reduce repeated CPU-to-GPU coordination around token generation.

Read the relevant Lizard page

#Caterpillar #LizardLLM #GPUProgramming #LocalAI #GGUF

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