libi · documentation · v0.4
Start

Quickstart — npx

Run the same studio from one command, in a browser tab, with nothing installed.

Run it

One command, no install step. Libi serves the studio locally and opens it in your browser once it's up. With no desktop to open one — over SSH, in a container — it prints the URL instead.

The first run sets up ~/.libi/ and downloads ffmpeg and ffprobe, which takes a minute or two and prints its progress. After that, startup is quick. Everything else downloads the first time you use it.

Start the studio
npx @nagellabs/libi

# opens http://localhost:3456

Flags and environment

Everything the command accepts.

  • --port 4000 — serve somewhere other than the default 3456.
  • --no-open — don't open a browser, just print the URL (or set LIBI_OPEN=0).
  • LIBI_HOME=/path/to/dir — put the workspace somewhere other than ~/.libi.
  • LIBI_MCP_PORT=3500 — serve Libi's MCP endpoint somewhere other than 3457. Set it before you run connect, since the address is saved in your agent's config.
  • LIBI_DEBUG=1 — verbose MCP transport logging, for when something isn't talking to something else.
  • npx @nagellabs/libi connect [dir] [--global] — see Bring your own CLI.
Examples
npx @nagellabs/libi --port 4000
LIBI_HOME=~/work/libi npx @nagellabs/libi

Closing it down

Stop the process and the studio is gone. Your projects and media are not — they live in ~/.libi/, and the next npx @nagellabs/libi picks up exactly where you left off. (The desktop app keeps its own workspace, so the two don't share projects.)

was this helpful? open an issue or PRedit on github →