Install Libi
What you need before you start, and the three ways to run Libi — desktop app, npx, or your own coding-agent CLI.
Pick how you run it
All three give you the same Libi — the same agent, the same tools. They differ only in where you sit while you work.
- Desktop app — the full studio in its own window, with nothing to install first.
- npx — one command, same studio in a browser tab, nothing left on your machine but the workspace.
- Your own CLI — run
libi connectonce: Libi's tools for your whole Claude Code and Codex account, and Libi's skills in that folder, kept up to date by Libi.
Before you start
Libi runs on macOS and Windows today; Linux is coming. Everything below applies to all three ways of running it, except where it says otherwise.
- A coding agent you are already signed in to — Claude Code or Codex. Libi installs the adapter it needs; you bring the account.
- Node.js 20.9 or newer — only for the npx route. The desktop app bundles its own runtime.
- About 1 GB of free disk, and a connection for the first launch. Libi downloads ffmpeg and ffprobe when it first starts, and the adapter for your agent when you pick one. Everything else — the Chromium used for rendering, tracking and background-removal models — comes down the first time you use it.
- No API keys to get started. Image, video and voice generation go through providers you add to your own agent — see Generation providers.
Working on Libi itself
Running from a checkout, the test commands, the database workflow and the project layout all live in the repo's README, next to the code they describe. We deliberately don't copy them here — a second copy is a copy that goes stale.
Looking for the full documentation?
The full documentation lives inside the Libi editor itself. Open the Instructions page in the app sidebar to read exactly how the agent behaves — every tool, workflow, and convention — and the Memories tab to shape it.