Files
LLeMbas-CLI/README.md
T
HomerandClaude Opus 5.5 a029ee6f07
ci / check (push) Canceled after 0s
login --token-stdin: a token a program already holds, checked, then stored as a device login
`lembas login --token-stdin --server <url> [--ca file] [--json]` reads one lmb_ token from
stdin (never an argument or the environment), checks discovery's protocol and then
GET /api/v1/instance with the token, whose `scope` must include `link` (a 404 or no `scope`
is an older server), and stores the login through the same path as the device code:
the key file, the webui entry, lembas.json, an earlier login replaced with its token signed
out naming the new one. --json prints the device login's `done` / `error` line. For LLeMbas
Desktop, which gets the agent's token from the one approval.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-03 14:48:02 +00:00

49 lines
1.9 KiB
Markdown

<p align="center">
<img src="assets/banner.svg" alt="LLeMbas CLI — terminal coding agent" width="100%">
</p>
# LLeMbas CLI
A terminal coding agent and project manager: the `lembas` command. It signs in to a
[LLeMbas](https://github.com/LLeMbas/LLeMbas) server and uses its models, memory and search, works
in your project with four permission modes and a git snapshot of every turn, keeps its own notes,
knowledge bases and skills on your machine, and lets the server's web UI work the same sessions.
Linux, x64 and arm64.
## Install
```sh
curl -fsSL https://github.com/LLeMbas/LLeMbas-CLI/releases/latest/download/get.sh | bash
```
Or download a binary from [Releases](https://github.com/LLeMbas/LLeMbas-CLI/releases). Every
release's `SHA256SUMS` is signed with the release key, and `get.sh` checks the signature and the
checksum before installing anything ([SECURITY.md](SECURITY.md) shows how to check by hand).
## First steps
```sh
lembas login https://your-server # sign in to your LLeMbas server
cd your-project && lembas # the TUI, on the server's models
```
A program that already holds an agent's token for this machine (LLeMbas Desktop does, from the
same approval as its own) hands it over on stdin, never as an argument:
`… | lembas login --token-stdin --server https://your-server [--json]`.
From 2.0 the CLI talks only to the LLeMbas server it is logged in to; the custom connections of 1.x
(`dialect:` entries in `connections.yaml`) are gone.
`lembas` updates itself (`lembas update` does it now); `lembas uninstall` removes it, and
`--purge` takes settings and sessions too.
## Links
- Documentation: <https://llembas.eu/cli.html> and <https://llembas.eu/docs/>
- Changelog: <https://llembas.eu/changelog.html>
- The server: <https://github.com/LLeMbas/LLeMbas>
## Licence
MIT — see [LICENSE](LICENSE) and [THIRD_PARTY.md](THIRD_PARTY.md).