logishell

The LogiShell CLI. One static binary, two names:

npx logishell scan .        # try it without installing anything
npm i -g logishell          # then it is `lsh` every day
lsh scan ~/some/other/repo

What it is for

lsh scan <path> reads a repository — yours or somebody else's — and prints a map of it: packages, the files under each, what depends on what, and what goes outward through a door (network, filesystem, a process). The map is the document an agent reads instead of the code.

On a 1878-file TypeScript monorepo: 0.1 seconds, ~21k tokens of map against ~8.9M tokens of source — 435× smaller.

lsh scan .                        # markdown, the default
lsh scan . --format json          # the same document, for a program
lsh scan . --depth sym            # descend to symbols (needs a language server)
lsh scan . --group                # name the subsystems, using your own API key
lsh help                          # the engine verbs: validate, plan, run, test…

--group is BYOK: the key comes from --key, LOGISHELL_LLM_KEY or ANTHROPIC_API_KEY, and nothing but the structure of your repository is sent — no file contents. Without a key the structural map still prints, and says the grouping is off.

Install

npm i -g logishell puts both logishell and lsh on your PATH. The package downloads the binary for your platform from dl.logishell.com and checks its sha256 against the published checksums before writing it.

Or build it yourself with go build -o lsh ./apps/runner/cmd/lsh and point LOGISHELL_BINARY at it. (A Homebrew tap is not published yet — the line that promised one sent people to a 404.)