Quickstart — Bring your own CLI

Start Libi any way you like — the desktop app, or npx @nagellabs/libi — and leave it running. It serves all of its own tools on one local endpoint: http://127.0.0.1:3457/mcp. (If something else already has that port, Libi picks another one; connect always writes whichever it is using.)

Then, in the folder you work from, run connect. It registers Libi's tools for your whole account and installs Libi's skills in that folder. Start Claude Code or Codex in that same folder and both are there. (Codex finds a folder's skills from a subfolder only inside a git repo — open Codex in the folder itself otherwise.)

connect touches three things and nothing else.

Add --global to install Libi's skills for every folder instead of one: ~/.claude/skills (or $CLAUDE_CONFIG_DIR/skills) and ~/.agents/skills. The tools are registered for your whole account either way. One level per agent: installing for every folder removes any folder installs Libi recorded for that agent, since every folder has them then.

Libi doesn't generate images, video or voice itself — the agent does that through a provider's own MCP server, such as fal.ai, Higgsfield or ElevenLabs, added to your Claude Code or Codex. Libi never holds a provider key, not on your machine and not on any server of ours. The key lives where your agent keeps its MCP servers, the request goes from your machine straight to the provider, and the bill is between you and them.

Agents → Providers helps you add one. Pick the agent at the top, then Add on a provider: Libi types the agent's own mcp add command into a terminal under the row, and nothing runs until you press Enter. For a provider that uses a key, the command asks for it at a hidden prompt and passes it straight to your agent — Libi never sees it. Higgsfield has no key: you sign in with your Higgsfield account in your browser. The row shows Connected once your agent has it, and has Remove for taking it out again.

You don't need Libi for any of this. The same commands work in your own terminal — put your key where it says <your key>. Codex reads fal.ai's key from a FAL_KEY variable instead, so export that in your shell profile first.

Nothing to do. Libi records every skills install connect (or the app) makes, and rewrites it after every skill change and every time Libi starts — new Libi versions with new skills reach your folders on their own.

Everything connect does is also on the Global setup tab (Agents → Global setup), with a Claude Code | Codex switch at the top (Set up libi for) and, below it, two sections for the agent you picked: Tools has the Libi MCP row (Connect / Reconnect / Disconnect — Reconnect shows up once the registration points at an old port), and Skills has Every folder (Install / Remove) and Specific folders (Add folder / Remove). The command each button builds opens in a terminal under the row you clicked, with a line saying what it will do before you press Enter. Folders added with connect show up there labelled "added with libi connect".

Every folder shows Not installed, Installed · N skills, or Couldn't update with the reason. Specific folders shows each folder as Up to date, Folder not found, or Couldn't update with the reason. Either row can also note skills skipped because you already use the name. Libi's own chats and terminal always have Libi's tools and skills; the tab is only about your own Claude Code and Codex.

Skills come out from the app; the tool registrations come out with each agent's own command.