aa2448208027-code/localaihotswap — explained in plain English
Analysis updated 2026-05-18
Compare outputs from multiple local AI models in the same conversation without restarting or losing context.
Run experiments across different local models on GPU-limited hardware by unloading one before loading the next.
Point existing OpenAI-API-compatible tools at this proxy without changing their request format.
| aa2448208027-code/localaihotswap | amapvoice/pilottts | bennjordan/kirlianorbits_win64 | |
|---|---|---|---|
| Stars | 39 | 39 | 39 |
| Language | Python | Python | Python |
| Setup difficulty | moderate | hard | moderate |
| Complexity | 3/5 | 4/5 | 3/5 |
| Audience | developer | developer | general |
Figures from each repo's GitHub metadata at analysis time.
Requires a working llama.cpp setup and local model files in addition to this proxy.
LocalAIHotSwap is a small control layer that sits in front of a locally running AI model server called llama.cpp. Its job is to let you swap out one AI model for another while keeping your conversation history intact, without needing to restart everything from scratch. When you run AI models locally, each model is a large file that must be loaded into your GPU's memory before it can respond to questions. Switching between models normally means losing whatever context the conversation had built up. This project solves that by acting as a middleman: it stores your conversation messages and any preset instructions separately from the model server itself, then coordinates the unloading and reloading of model files in a way that keeps memory usage low. The default approach, called zero_overlap, unloads the current model completely before loading the next one. This avoids having two large model files in GPU memory at the same time, which matters a lot on machines with limited VRAM. Once the new model is loaded, the saved conversation history is fed back in so the chat can continue. The project is honest that this replay step does take time, and that there is no shortcut around it. From the user's perspective, the proxy accepts chat requests in the same format that OpenAI's API uses, so existing tools that speak that format work without changes. You can also send a switch command to change which model is active, and the proxy makes sure any in-progress responses finish before the old model is unloaded. Configuration is handled through a TOML file where you point to your local model files and set limits like how many messages to keep in history, how large the context window can be, and how long to wait for active requests to drain before switching. The project is aimed at developers running experiments across multiple local models who want to compare outputs without constantly losing their session state.
A proxy that sits in front of llama.cpp and lets you swap local AI models mid-conversation without losing chat history.
Mainly Python. The stack also includes Python, llama.cpp, TOML.
The excerpt does not state a license, so terms for reuse and redistribution are unclear from the available text.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.