Source Code:
src/gaia/Introduction
GAIA is an open-source framework that runs generative AI applications on AMD hardware. GAIA uses ONNX Runtime GenAI via Lemonade Server for running Large Language Models (LLMs). GAIA utilizes both NPU and iGPU on Ryzen AI systems for optimal performance on 300 series processors or above.Before You Start
System Requirements
| Requirement | Minimum | Recommended |
|---|---|---|
| OS | Windows 11 Pro 24H2 / Ubuntu 22.04+ | - |
| RAM | 16GB | 64GB |
| CPU | Ryzen AI 300-series | Ryzen AI MAX+ 395 |
| Storage | 20GB free | - |
| Component | Minimum Version |
|---|---|
| Radeon iGPU | 32.0.22029.1019 |
| NPU | 32.0.203.314 |
Software Requirements
- Git - For version control
- Lemonade Server - Download from lemonade-server.ai
Setup and Installation
GAIA uses uv, a fast Python package manager that handles virtual environments, Python installation, and dependencies automatically.Step 1: Install uv
Windows (PowerShell):Step 2: Clone GAIA
Step 3: Create Virtual Environment
Note: uv will automatically download Python 3.12 if not already installed.
Step 4: Activate the Environment
Windows (PowerShell):(.venv) in your terminal prompt when activated.
Step 5: Install Dependencies
Deactivating
When done working:See also: Chat SDK Documentation
Running GAIA
Verify Installation
Start Chatting
Note: GAIA automatically starts Lemonade Server when needed. For manual start: lemonade-server serve
Running Electron Applications
GAIA includes Electron-based GUI applications. To run the JAX (Jira Agent Experience) app: Windows:Troubleshooting
”uv” command not found (Windows)
After installing uv, the command may not be recognized because PATH hasn’t updated. Solution 1: Restart PowerShell (simplest) Solution 2: Update PATH in current session:Virtual Environment Activation Fails (Windows)
If you see a script execution error:Model Loading Issues
- Check available system memory
- Verify model compatibility with your hardware
- Ensure all dependencies are correctly installed
Environment Variable Issues
- Verify the virtual environment is activated (look for
(.venv)prefix) - Try restarting your terminal
- Re-run the activation command for your platform
Support
Report issues to[email protected] or create an issue on GitHub.