HomerandClaude Opus 5.5
6d5a25cdad
acp.md said a logged-in device reads "the resource holding the entries for the prompt" without naming it, so neither side could implement it. It is `lembas://memory`: the entries as the memory block of a system prompt shows them, read as a session starts and kept for it. Only `memory` is taken from /mcp — notes, knowledge bases and skills stay the device's; the scope rides on the resource read as on the tool call; a token's older `library` scope counts as `memory`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
LLeMbas CLI
A terminal coding agent and project manager: the lembas command. It signs in to a
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
curl -fsSL https://github.com/LLeMbas/LLeMbas-CLI/releases/latest/download/get.sh | bash
Or download a binary from 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 shows how to check by hand).
First steps
lembas login https://your-server # sign in to your LLeMbas server
cd your-project && lembas # the TUI, on the server's models
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 and THIRD_PARTY.md.