@rasmusgodske/lore

lore, the command-line client for the knowledge-base orchestrator. Used by people and by agents alike; what a caller may do is decided by the token, not by the tool. No runtime dependencies: plain fetch and types generated from ../../openapi.json.

lore login <url> --token T    save server and token to ~/.config/lore/config.json
lore me                       who the current token belongs to
lore session <cmd>            create | list | show | close | log
lore exec [ID] -- <cmd...>    run a command in a session; stdin is streamed when piped
lore token <cmd>              create | list | revoke
lore user <cmd>               create | list | token          (admin only)
lore mirror <cmd>           status | sync            (whether main is mirrored to a git host)
lore mcp                    MCP server over stdio: the server's tools plus lore_put
lore update [--check]       install the latest published version with npm
lore --version

lore mcp lets any MCP client use the saved login: claude mcp add lore -- lore mcp. It is the CLI's own MCP server, not a relay: it offers the five tools the server's /mcp endpoint offers, implemented against the HTTP API like every other command, plus lore_put, which copies a local file or directory into a session by streaming it, the same path as tar -c . | lore exec -- 'tar -x'. An agent with the CLI on its machine should register this one; the HTTP endpoint is for callers without a shell.

lore update runs npm install -g @rasmusgodske/lore@<latest> for you, after asking the npm registry what the latest is; if the global install belongs to root it prints the sudo line to run instead. Once a day an interactive command may add one line on stderr when a newer version exists (LORE_NO_UPDATE_CHECK=1 turns that off; it never prints in lore mcp or when piped).

LORE_URL and LORE_TOKEN override the config file. LORE_SESSION is the default session id. Output is JSON when stdout is not a terminal, readable otherwise; --json forces JSON.

Exit codes: the command's own pass through; 100 connection, 101 auth, 102 no such session, 103 timeout, 104 usage. Transport failures always carry a lore: prefix on stderr; a command's own stderr never does.

npm run generate   # regenerate src/generated/api.d.ts from ../../openapi.json
npm run build
npm test