CLI reference

langonrock --help
langonrock --version

Running with no arguments prints the usage and exits 1. --help prints the same thing and exits 0.

Commands

compile

langonrock compile sources/acme/sales --bundle sales --summary-width 80

Writes the manifest to stdout and nothing to the store, so it is the fastest way to see what the compiler makes of a folder. Diagnostics and statistics go to stderr. Without --bundle, the directory name is used.

put and sync

put treats the directory as a single bundle. sync treats every immediate subdirectory as its own bundle and compiles them together into one snapshot.

langonrock put sources/acme/sales --data ./data --tenant acme --bundle sales
langonrock sync sources/acme --data ./data --tenant acme

Both report the resulting snapshot on stderr, and both say whether it was new or reused:

snapshot eaf251169a59 (new), 2 bundles [ops sales], 3 concepts, 850 bytes on disk

(reused) means the tree hashed to a snapshot that already existed, so nothing was written.

watch

langonrock watch sources/acme --data ./data --tenant acme --debounce 500

Runs until interrupted. Writes inside dot directories are ignored, because .git and .obsidian change constantly and rebuilding on them would never stop.

manifest and get

langonrock manifest --data ./data --tenant acme
langonrock get orders customers --section schema --data ./data --tenant acme

get prints each concept prefixed by @@ <id>. It warns on stderr for any id it could not find, and exits 1 when at least one is missing.

Both read the store directly. Use query instead to go through a daemon or a server.

serve

langonrock serve --data ~/okf/data --socket /tmp/okf.sock
langonrock serve --data ~/okf/data --host 127.0.0.1 --port 7777

Without --socket, --host or --port, the daemon listens on <data>/langonrock.sock. See Running a server.

token

langonrock token --data ~/okf/data --tenant acme            # read-only
langonrock token --data ~/okf/data --tenant acme --write    # may edit source

The token goes to stdout so you can capture it into a variable. Everything else goes to stderr. See Tokens and TLS.

gc

langonrock gc --data ~/okf/data --dry-run
langonrock gc --data ~/okf/data --tenant acme --keep 5

Without --tenant it collects every tenant. It exits 1 when a tenant's current points at a snapshot that is missing or truncated. See Backup and collection.

mcp

langonrock mcp "okf:///abs/path/to/data?tenant=acme"

Speaks MCP over stdio against any connection string. The transport owns stdout, so diagnostics go to stderr only.

query

langonrock query <dsn> <verb> [args]

One command against any connection mode, so a local store and a remote server are driven the same way.

Read verbs

langonrock query "okf+unix:///tmp/okf.sock?tenant=acme" search order grain --k 5
langonrock query "okf+http://127.0.0.1:7777?token=$TOKEN" manifest --bundle sales

Write verbs

langonrock query "$DSN" source
langonrock query "$DSN" read sales tables/orders.md
langonrock query "$DSN" write sales metrics/new.md --create < new.md
langonrock query "$DSN" write sales tables/orders.md --replaces "$HASH" < edited.md
langonrock query "$DSN" delete sales tables/old.md --force
langonrock query "$DSN" sync

Flags

Store and tenant

Reading

Compiling

Serving

--tls-cert and --tls-key must be given together, and neither works with a unix socket.

Writing source

Tokens

Collection

Exit codes