gerbil
gerbil copied to clipboard
A desktop app for running Large Language Models locally.
Gerbil 
A desktop app to easily run Large Language Models locally.
Core Features
- Run LLMs locally - Powered by KoboldCpp, a feature-rich fork of llama.cpp
- Cross-platform - Native support for Windows, macOS, and Linux (including Wayland)
- Offline capable - Import pre-downloaded KoboldCpp binaries and run entirely without an internet connection
- Automatic backend updates - Download and keep your KoboldCpp binary up-to-date effortlessly
- Flexible hardware support - Works on CPU-only systems while also supporting GPU acceleration (CUDA, ROCm, Vulkan, CLBlast, Metal)
- Image generation - Built-in presets for Flux, Chroma, Qwen Image, and Z-Image workflows
- Integrated HuggingFace search - Browse models, view model cards, and download GGUF files directly from the app
- SillyTavern integration - Launch SillyTavern for advanced character interactions (requires Node.js)
- OpenWebUI integration - Launch OpenWebUI for a modern web-based chat interface (requires uv)
- Privacy-focused - Everything runs locally with no external data transmission or telemetry
Installation
Pre-built Binaries
Download the latest release for your platform from the GitHub Releases page:
- Windows:
Gerbil-Portable-X.X.X.exe(portable executable) - Windows:
Gerbil-Setup-X.X.X.exe(installer executable) - macOS:
Gerbil-X.X.X.dmg(disk image) - Linux:
Gerbil-X.X.X.AppImage(portable application)
Linux - AUR (Arch Linux)
For Arch Linux users, install from the AUR using your preferred AUR helper:
# Using yay
yay -S gerbil
# Using paru
paru -S gerbil
# Manual installation
git clone https://aur.archlinux.org/gerbil.git
cd gerbil
makepkg -si
The AUR package automatically handles installation, desktop integration, and system updates. This is the ideal way to run Gerbil on Linux.
Open a Mac app from an unknown developer
After installing on macOS, you will notice that the app will not run as it was not verified by Apple. You will need to follow these instructions to remove it from your system's quarantine to be able to run it. Alternatively you can run xattr -r -d com.apple.quarantine /Applications/Gerbil.app in the terminal.
Demo & Screenshots
https://github.com/user-attachments/assets/9e7ecfb3-3576-443c-8cef-a14e06ab5b60
Download & Setup
|
Model Launch Configuration
|
Text Generation
|
Image Generation
|
SillyTavern integration
|
OpenWebUI integration
|
Future features
Not all koboldcpp features have currently been ported over to the UI. As a workaround one may use the "Additional arguments" on the "Advanced" tab of the launcher to provide additional command line arguments if you know them.
CLI Mode
The --cli argument allows you to use the Gerbil binary as a proxy to the downloaded KoboldCpp binary. This enables you to run KoboldCpp from the command line using the same binary that the GUI has downloaded.
CLI Arguments
Gerbil supports the following command-line arguments:
--version- Display the Gerbil version and exit--cli- Run in CLI mode (proxy to KoboldCpp binary). All arguments after--cliare passed to KoboldCpp--minimized- Start Gerbil GUI minimized to system tray (requires system tray to be enabled in settings)
Considerations
You might want to run CLI Mode if you're looking to use a different frontend, such as OpenWebUI, than the ones bundled (eg. KoboldAI Lite, llama.cpp, Stable UI) with KoboldCpp AND you're looking to minimize any resource utilization of this app. Note that at the time of this writing, Gerbil only takes about ~200MB of RAM and ~100MB of VRAM for its Chromium-based UI. When running in CLI Mode, Gerbil will still take about 1/3 of those RAM and VRAM numbers.
Usage
Linux/macOS:
# Basic usage - launch KoboldCpp launcher with no arguments
gerbil --cli
# Pass arguments to KoboldCpp
gerbil --cli --help
gerbil --cli --port 5001 --model /path/to/model.gguf
# Any KoboldCpp arguments are supported
gerbil --cli --model /path/to/model.gguf --port 5001 --host 0.0.0.0 --multiuser 2
# CLI inception (Gerbil CLI calling KoboldCpp CLI mode)
# This is the ideal way to run a custom frontend
gerbil --cli --cli --model /path/to/model.gguf --gpulayers 57 --contextsize 8192 --port 5001 --multiuser 1 --flashattention --usemmap --usevulkan
Windows:
CLI mode will only work correctly on Windows if you install Gerbil using the Setup.exe from the github releases. Otherwise there is currently a technical limitation with the Windows portable .exe which will cause it to not display the terminal output correctly nor will it be killable through the standard terminal (Ctrl+C) commands.
You can use the CLI mode on Windows in exactly the same way as in the Linux/macOS examples above, except you'll be calling the "Gerbil.exe". Note that it will not be on your system PATH by default, so you'll need to manually specify the full path to it when callig it from the Windows terminal.
Local Dev
Prerequisites
- fnm - Fast Node.js version manager (installs correct Node.js versions automatically)
Setup
-
Install fnm (if not already installed):
# Using package manager (recommended for Arch Linux) yay -S fnm-bin # Or using curl (other distros) curl -fsSL https://fnm.vercel.app/install | bash -
Clone the repository
-
Install Node.js and dependencies:
# fnm will auto-install Node.js based on .nvmrc or engines field fnm use --install-if-missing npm install -g yarn yarn -
Start the development server:
yarn dev
My Setup
- OS: Archlinux + KDE + Wayland
- Gerbil: installed from AUR via yay
- KoboldCpp: nocuda build, vulkan backend
- Hardware: RX 7900 GRE (16GB VRAM, undervolted, overclocked), Ryzen 7 7800X3D, ASUS B650-E, 32GB RAM (EXPO 1: 6000Mhz)
- LLM: Q4 Gemma 3 27b abliterated+ Open WebUI + Dolphin system message
Known Issues
- Windows ROCm support is... problematic and currently requires for the user to manually add the installed ROCm bin directory to the system PATH. In particular "hipInfo.exe" must be present, which is not always the case for older versions of ROCm.
License
AGPL v3 License - see LICENSE file for details