LIA — Your next conversation, already prepared
I built LIA because I wanted to pick up a conversation without piecing its context together again.
This free, open-source, self-hosted AI assistant brings your emails, meeting notes and open commitments into view, then helps you prepare the next step. The software is free; hosting and connected services may incur costs.
Start the guided installer:
git clone --depth 1 https://github.com/jgouviergmail/LIA-Assistant.git && cd LIA-Assistant && ./install.sh
For a Linux host with Git, Python and Docker Compose. Prerequisites and setup choices.
Explore LIA · Try the interactive walkthrough · Installation guide · Documentation
Why LIA?
The moment I wanted to improve is simple: “I'm speaking with Claire. What did we agree, what changed, and what do I still owe her?”
- Pick up the relationship. Open Relations for the recent exchanges, debrief and open commitments associated with a person.
- Prepare from your own material. Ask LIA to bring together the project brief, recent emails and previous meeting notes. Inspect the sources and anything that conflicts.
- Choose what happens next. Review the email draft before sending. Edit it, approve it or say no.
- Use your services yourself. Open Tools for mail, calendar, tasks, contacts, files and Hue controls: by hand with no model call, and yellow stars where one click asks LIA for a summary, a reply or a form to check. The connected provider determines the available controls.
Try: “Prepare my catch-up with Claire using the project brief, our recent emails and the last meeting notes. Highlight anything that conflicts.”
That continuity is LIA's focus: the relationship, its sources and the next action in one place. Start there; voice, personal Radio, routines and the rest are available when you need them. The functional map shows how those pieces connect.
Quick Start
The command above starts the installer in install.sh. It asks how to expose the instance, creates the administrator account and walks you through provider keys. The first source build takes longer than starting an already installed instance.
Have these ready: a supported Linux host, Git, Python and Docker Compose; see the installer prerequisites for versions and disk space. The current installer asks for OpenAI and DeepSeek keys. Add the optional Gemini key for memory recall, document search and image analysis.
- Run the command above; choose LAN for a first installation on your local network.
- Follow the printed address, sign in and connect the services you want LIA to use.
- Open Relations, or ask for a conversation brief using sources available to your account.
Already have the checkout? Run ./install.sh from its root. An interrupted installation can continue with ./install.sh --resume.
The self-hosting guide covers every installer choice and troubleshooting. The getting-started guide covers the wider setup.
Self-Hosting in Production
A guided installer lives at the repository root (ADR-215). It asks a short questionnaire (LAN exposure, your own reverse proxy, or managed HTTPS with Caddy), generates a private .env and Compose overlay, applies the reference seeds atomically, creates the admin and provider keys over stdin, verifies the installation beyond /ready and prints a non-secret report.
The experimental speaking avatar is an optional choice, disabled by default; each person then connects their own Simli account.
A complete source checkout builds the images locally; an official release directory uses prebuilt digests only when its adjacent manifest is qualified.
The Google Gemini key is an optional question — memory recall, searches by meaning and image analysis wait for it — and the final report names every capability left waiting for a key.
Two optional key pairs follow, each given whole or left empty: a Google Maps browser key with its Cloud map ID for interactive place maps, and, on an instance reached on a public domain, a Cloudflare Turnstile widget's keys for the anti-robot check on the password doors (ADR-364).
Every line of the shipped env templates states the code's default or says why it differs, and .env.prod.example carries the values production runs.
Resume an interrupted run with ./install.sh --resume; change a running installation with ./install.sh --reconfigure, which shows the answers in force (Enter keeps them) and every setting they would rewrite before anything changes, replaces each file atomically after a private backup, recreates the containers without rebuilding and puts the previous files and stack back if the new one does not come back ready.
The shipped .env profiles size the connection pools against the database's memory floor as well as its ceiling, and a guard reads both profiles with the Compose file so the sizing cannot drift (ADR-283).
This is the beginning of the README. Read the rest at the original. Read the full README ↗
