Quickstart — Bring your own CLI
Use Libi from your existing Claude Code or Codex terminal session — no GUI required.
Install in headless mode
Bring-your-own-CLI mode runs the Libi server without opening a browser window. From any project directory, run the headless command and Libi will write a `.claude/settings.local.json` (or equivalent) into the current working directory.
Your CLI agent reads that settings file on its next launch and discovers the libi.* tool surface automatically.
cd ~/projects/my-video-piece
npx @nagellabs/libi --connect-agent
# leave it running. start a new terminal:
claude # or: codexWhat gets written
The settings file points your CLI agent at Libi's MCP server over stdio. It is small, readable, and committed-friendly if you want it in source control. Libi keeps it up to date on every launch.
{
"mcpServers": {
"libi": {
"type": "stdio",
"command": "npx",
"args": ["@nagellabs/libi", "serve-mcp"]
}
}
}Bring your own keys
External AI services need keys. Add them through the Libi Settings UI (`libi.show_mcp_settings`) or set them as environment variables before launching `npx @nagellabs/libi --connect-agent`.
Libi never proxies your keys — they go directly from the local server to the upstream service.
- ELEVEN_API_KEY for ElevenLabs
- FAL_KEY for fal.ai
- GOOGLE_API_KEY for Veo
- ANTHROPIC_API_KEY / OPENAI_API_KEY are managed by your CLI, not Libi.