Tater is a local-first AI platform with built-in LLM, vision, voice, memory, automation, and integration systems. Hydra handles reasoning, orchestration, and tool use, while Tater can run local models through llama.cpp, Hugging Face Transformers, and MLX, or connect to remote providers through OpenAI-compatible APIs. It includes a built-in voice system that talks directly to ESPHome devices like VoicePE, Sat1, S3Box, and ReSpeaker XVF3800, a WebUI for setup, configuration, chats, model management, and system monitoring, plus integrations across Discord, Home Assistant, HomeKit, IRC, macOS, Matrix, Meshtastic, Telegram, and even the OG Xbox via XBMC4Xbox.
Tater is built around a modular system:
- Cores β core systems that extend Tater's capabilities
- Portals β integrations with platforms like Discord, Home Assistant, and more
- Verbas β AI-driven tools and actions Tater can perform
- Integrations β modular provider packages for devices, services, search providers, and external APIs
These catalogs, versions, metadata, and update paths are managed through Tater Shop:
π https://github.com/TaterTotterson/Tater_Shop
Integration packages are maintained here:
π TaterTotterson/Tater_Integrations
Some Portals are paired with companion repos/apps that complete the end-user integration:
| App / Repo | Purpose |
|---|---|
| HA Add-ons | Home Assistant add-on repository for running Tater directly inside HAOS/Supervised setups. |
| HomeKit Shortcuts | Shortcut guide for Siri -> HomeKit bridge -> Tater workflows. |
| Meshtastic Bridge | Host-side BLE bridge service for connecting Tater to Meshtastic radios over a simple local API. |
| microWakeWords | Tater VoicePE, Satellite1, ReSpeaker, and related ESPHome firmware plus microWakeWord model assets. |
| microWakeWord Trainer - Apple Silicon | Apple Silicon trainer for creating custom microWakeWord models. |
| microWakeWord Trainer - NVIDIA Docker | NVIDIA Docker trainer for creating custom microWakeWord models with GPU acceleration. |
| NanoWakeWord Trainer | Trainer for custom NanoWakeWord models used by Tater's local or standalone NanoWakeWord server. |
| openWakeWord Trainer | Trainer for custom openWakeWord models used by Tater's local or standalone openWakeWord server. |
| Tater MacOS | Menu bar companion app and bridge client for desktop chat, quick actions, and uploads. |
| Reachy Mini Voice Satellite | Reachy Mini robot app that turns Reachy Mini into a voice satellite for Tater or Home Assistant. |
| Reachy Mini Tater Standalone | Reachy Mini robot app that can run the full Tater app/stack directly on Reachy. |
| Tater NWW Server | Standalone NanoWakeWord WebSocket server for Tater satellites using remote NanoWakeWord wake detection. |
| Tater OWW Server | Standalone openWakeWord WebSocket server for Tater satellites that need remote wake detection outside the main Tater app. |
| Tater S3Box Display | ESP32-S3-BOX display firmware for Tater voice and dashboard-style device experiences. |
| XBMC4Xbox Skin | OG Xbox/XBMC4Xbox skin and script integration for on-console Tater access. |
Note:
- Tater can run any compatible local or OpenAI-compatible model. If you use a thinking model, disable thinking for best Hydra/tool behavior. Tater's built-in local providers try to suppress thinking automatically where supported.
- Python 3.11
- A local OpenAI-compatible LLM runtime (such as Ollama, LocalAI, LM Studio, or Lemonade) or Tater's built-in Hugging Face Transformers, llama.cpp GGUF, or MLX LM providers
- Docker is optional.
- Clone the Repository
git clone https://github.com/TaterTotterson/Tater.git- Navigate to the Project Directory
cd Tater- Run Tater Setup
Use the interactive setup menu to choose the right local runtime profile:
sh setup_tater.shThe setup menu creates .venv, installs Tater's Python dependencies, and writes the selected runtime profile to .runtime/tater_profile.env.
Available local profiles:
- CPU: safe default for most local Linux installs and generic ARM hosts.
- macOS Apple Silicon: native Mac setup with Apple Metal/MPS for PyTorch-backed SpeechBrain and Kokoro when available, plus MLX Whisper for local STT.
- NVIDIA desktop/server: native amd64 CUDA setup for RTX/GTX machines.
- AMD ROCm / Strix Halo: native Linux setup for ROCm-capable Radeon and Ryzen AI Max / Strix Halo systems.
- Jetson: native ARM64 setup that uses JetPack/system AI packages and CUDA when compatible Python runtimes are installed.
- Jetson Thor: native ARM64 setup for Thor / JetPack 7 systems and CUDA 13-compatible JetPack runtimes.
Non-interactive setup is also available:
sh setup_tater.sh cpu
sh setup_tater.sh macos
sh setup_tater.sh nvidia
sh setup_tater.sh rocm
sh setup_tater.sh jetson
sh setup_tater.sh thorThe setup profile only prepares the runtime. Actual voice model choices are managed in TaterOS under Settings -> Models and Settings -> ESPHome -> Voice Pipeline.
macOS Apple Silicon:
- The macOS profile writes
PYTORCH_ENABLE_MPS_FALLBACK=1so PyTorch can fall back to CPU for unsupported MPS operations. - It attempts to install
mlx-whisperand the official PyTorchkokoropackage. - It installs the Metal
llama-cpp-pythonwheel on Apple Silicon when available; MLX LM remains the preferred Apple-native local LLM provider. - Select Settings -> Models -> STT Backend -> MLX Whisper for Apple-native Whisper STT.
- MLX Whisper defaults to
mlx-community/whisper-base.en-mlx; setTATER_MLX_WHISPER_MODELto use another MLX Whisper model. - Kokoro automatically uses the PyTorch engine on Apple Metal/MPS when available. Set
TATER_KOKORO_ENGINE=onnxto force the existing ONNX path orTATER_KOKORO_ENGINE=torchto force PyTorch.
If native macOS dependency builds fail, install these Homebrew packages and rerun setup:
brew install ffmpeg libolm pkg-configNVIDIA desktop/server:
- The
nvidiaprofile installs CUDA PyTorch wheels, CUDA/cuDNN runtime packages, a CUDA-enabledllama-cpp-python, and the GPU ONNX Runtime build. llama-cpp-pythondefaults to the upstream CUDA 12.4 wheel index (TATER_LLAMA_CPP_CUDA_WHEEL=cu124) because that index carries current published CUDA wheels; setTATER_LLAMA_CPP_CUDA_WHEEL=sourceto compile locally withCMAKE_ARGS="-DGGML_CUDA=on"instead.- In TaterOS, use Settings -> Models -> Voice Acceleration to select Auto, CPU, NVIDIA CUDA, AMD ROCm, or Apple Metal/MPS where supported.
- Faster Whisper compute type defaults to Auto. Auto uses
float16on newer CUDA GPUs and switches toint8on older CUDA cards such as Pascal / GTX 10-series, wherefloat16can fail. - To override Faster Whisper compute type, use Settings -> ESPHome -> Voice Pipeline -> Speech Recognition -> Faster Whisper Compute Type or set
TATER_FASTER_WHISPER_COMPUTE_TYPEtoauto,int8,float32,float16,int8_float32, orint8_float16. - To restrict which GPUs native Tater can see, start it with
CUDA_VISIBLE_DEVICES=0 sh run_ui.shor use a GPU UUID.
AMD ROCm / Strix Halo:
- The
rocmprofile installs PyTorch from the ROCm wheel index, then installs Tater dependencies and the official PyTorch Kokoro package. - Tater keeps the ROCm PyTorch wheel in place when installing dependencies so Hugging Face Transformers can use ROCm through PyTorch when the device is supported.
- AMD ROCm support is Linux-only and depends on the ROCm runtime installed for the GPU/APU.
- Tater uses ROCm for PyTorch-backed models such as Kokoro Torch and SpeechBrain Speaker ID / Emotion ID. PyTorch ROCm exposes devices through the
cudaAPI internally, but Tater labels it separately as AMD ROCm in settings and logs. - llama.cpp ROCm/hipBLAS is not installed automatically; build it locally with
TATER_LLAMA_CPP_CMAKE_ARGS="-DGGML_HIPBLAS=on"if you want GGUF GPU offload on AMD. - Faster Whisper still falls back to CPU unless its CTranslate2 backend reports CUDA support; ROCm acceleration is not assumed for Faster Whisper.
- Strix Halo may require newer AMD ROCm wheels than the default PyTorch index. Override the PyTorch ROCm wheel source with
TATER_ROCM_PYTORCH_INDEX_URLbefore running setup if needed.
Jetson and Thor:
- The
jetsonandthorprofiles create a venv with--system-site-packagesso NVIDIA JetPack-provided Python AI packages can be reused. - Setup intentionally avoids replacing JetPack PyTorch with generic pip wheels.
- Hugging Face Transformers can use JetPack CUDA when the system PyTorch install exposes CUDA. llama.cpp CUDA on Jetson/Thor usually requires a local source build and is not forced by setup.
General voice notes:
- Tater warms selected local STT/TTS models at startup and after saving voice model settings. Set
TATER_SPEECH_WARMUP_ON_STARTUP=falseto disable startup warmup. - Kokoro and Pocket TTS output are boosted slightly by default for clearer satellite playback. Tune them in Settings -> Models -> Speech -> TTS, or override local runs with
TATER_KOKORO_OUTPUT_GAIN/TATER_POCKET_TTS_OUTPUT_GAIN; both default to1.5. - Voice activity detection defaults to Silero VAD. Low-power hosts can switch the Voice Pipeline VAD backend to WebRTC, which uses
webrtcvad-wheels. - If Speaker ID or Emotion ID is enabled, SpeechBrain can use CUDA or MPS when supported, with CPU fallback.
Start the TaterOS backend/frontend:
sh run_ui.shIf .venv exists, run_ui.sh uses it automatically. It also loads .runtime/tater_profile.env when present.
The launcher listens on 0.0.0.0:8501 by default. To change it, set HTMLUI_PORT:
HTMLUI_PORT=8601 sh run_ui.shThen open:
http://127.0.0.1:8501
Once the WebUI is up, continue to Post-Install Setup below.
Pull the prebuilt image with the following command:
docker pull ghcr.io/tatertotterson/tater:latestRecommended Docker networking:
- Use
--network hostso Tater shares the host network directly. - This avoids managing a growing list of
-pmappings for WebUI, voice, and other runtime surfaces. - With host networking, Tater listens on the host directly, so you do not need to publish Tater ports manually.
- To change the WebUI port, set
HTMLUI_PORT, for example-e HTMLUI_PORT=8601. - If you are not using host networking, publish the same container port, for example
-p 8601:8601.
Important for Docker persistence:
- Add a path mapping for
/app/agent_lab(container) ->/mnt/user/appdata/tater/agent_lab(host example). - Without this mapping, data in
/agent_lab(logs/downloads/documents/workspace) can be lost on container rebuilds/updates. - Add a path mapping for
/app/.runtime(container) ->/mnt/user/appdata/tater/runtime(host example). - Without this mapping, local runtime settings can be lost on container rebuilds/updates.
Example: Docker setup
docker run -d --name tater_webui \
--network host \
-e TZ=America/Chicago \
-e HTMLUI_PORT=8501 \
-v /etc/localtime:/etc/localtime:ro \
-v /etc/timezone:/etc/timezone:ro \
-v /agent_lab:/app/agent_lab \
-v /tater_runtime:/app/.runtime \
ghcr.io/tatertotterson/tater:latest
The NVIDIA image is amd64-only. Use the default latest image for CPU-first installs and ARM hosts.
The NVIDIA image uses CUDA 12.8 PyTorch wheels, CUDA/cuDNN runtime packages, GPU ONNX Runtime, and the upstream CUDA llama-cpp-python wheel for RTX 30, 40, and 50 series cards. Voice model tuning, Faster Whisper compute type, warmup, VAD, SpeechBrain acceleration, and llama.cpp GGUF offload use the same TaterOS settings described in Local Voice Acceleration Notes.
Host requirements:
- Install the NVIDIA driver.
- Install NVIDIA Container Toolkit before starting the compose override.
- The CUDA llama.cpp wheel needs
libcuda.so.1, which is supplied by the host driver at container runtime. If diagnostics mentionlibcuda.so.1, the image built correctly but the container was not started with NVIDIA GPU access.
Optional NVIDIA GPU build for Faster Whisper STT plus Kokoro TTS:
docker compose -f docker-compose.yml -f docker-compose.nvidia.yml up --build
Prebuilt NVIDIA image:
docker pull ghcr.io/tatertotterson/tater:nvidiaTo restrict which GPUs Tater can see in the NVIDIA compose setup, set NVIDIA_VISIBLE_DEVICES before launching, for example NVIDIA_VISIBLE_DEVICES=0 or a GPU UUID. Inside the container, CUDA device 0 maps to the first visible GPU.
Build and push the NVIDIA image:
docker buildx build \
--platform linux/amd64 \
-f Dockerfile.nvidia \
-t ghcr.io/tatertotterson/tater:nvidia \
--push .Once the container is running with host networking, open your browser and navigate to:
- http://localhost:8501 from the same machine
http://<host-ip>:8501from another device on your network
If you changed HTMLUI_PORT, use that port in the URL.
Once the WebUI is up, continue to Post-Install Setup below.
Tater is available in the Unraid Community Apps store.
You can install Tater directly from the Unraid App Store with a one-click template.
Unraid note:
- Add container path mappings for
/app/agent_laband/app/.runtimeto persistent shares, for example/mnt/user/appdata/tater/agent_laband/mnt/user/appdata/tater/runtime. - Also set
TZand map/etc/localtimeplus/etc/timezoneif you want local time inside the container.
Once the Unraid containers are installed and running, continue to Post-Install Setup below.
A dedicated Home Assistant add-on repository is available here:
https://github.com/TaterTotterson/hassio-addons-tater
Click the button below to add the repository to Home Assistant:
Once added, the Tater AI Assistant add-on will appear in the Home Assistant Add-on Store.
Install order:
- Install Tater AI Assistant.
- Configure your LLM settings in the Tater add-on.
- Start Tater.
Once the add-ons are running, continue to Post-Install Setup below.
After Tater is running, open TaterOS and finish the first-run setup:
- Configure your base model in Settings -> Models -> LLM / Vision:
- choose
OpenAI-Compatible APIfor Ollama, LM Studio, LocalAI, Lemonade, vLLM, or a hosted compatible API - choose
Hugging Face Transformersto load a local model directly inside Tater - choose
llama.cpp GGUFto load a GGUF model through llama-cpp-python - choose
MLX LM (Apple Silicon)to load an MLX model directly on an Apple Silicon Mac - for built-in local providers, download models from the Hugging Face mini-tab first, then select the downloaded model from the Settings mini-tab
- for OpenAI-compatible providers, set the endpoint host/port and model name
- choose
- Optional:
- add more Base servers for round-robin regular AI calls
- enable
Beast Modeand set per-head model settings for Chat/Astraeus/Thanatos/Minos/Hermes
Hydra model settings are saved by TaterOS and used at runtime. Base, Spudex, Beast Mode routing, and Vision can each use the selected built-in local providers or OpenAI-compatible providers.
- Download local Hugging Face Transformers, llama.cpp GGUF, or MLX models from the Hugging Face mini-tab first, then select them from Settings.
- Model caches live under
agent_lab/models/llm/by default:huggingfacefor Transformersllama-cppfor GGUF models and matchingmmproj*.ggufvision projectorsmlxfor MLX text and vision models
- The Hugging Face browser uses the token saved in Integration Manager -> Hugging Face for private/gated models and better Hub rate limits.
- llama.cpp uses GPU offload by default when the installed build supports it. Set
TATER_LLAMA_CPP_N_GPU_LAYERS=0for CPU-only. - MLX is intended for Apple Silicon Macs. Use llama.cpp GGUF on Linux, Raspberry Pi, NVIDIA, AMD/ROCm, Jetson, or other non-Apple-Silicon devices.
- Vision can use an OpenAI-compatible API, the loaded Base model, or a dedicated local vision model.
- If Base is already loaded and vision-capable, Tater reuses it instead of loading the same model twice.
- Dedicated vision models are managed separately from Base.
- Local context length is configured in Settings -> Models -> LLM / Vision.
- Thinking suppression is enabled by default for local providers when supported.
run_ui.shstarts Uvicorn with--no-access-logto suppress per-request log spam.