HomerandClaude Opus 5.5
4b8786b7f6
progress.md: thirteen fixed phases (queued … failed), each { phase, since, data },
their texts as shared i18n keys (loop.json progress), one line every client draws,
sent beside the old status text in /api/v2 and over the link (capability progress).
subagents.md §5–§13 (supersedes team.md where they differ): only the main agent
adds, assigns, replaces, stops and decides; sub-managers direct those placed under
them; ids, positions, parents; Min above 1 opens slots; permissions inherited and
never widened, request options decided by the main agent, what nobody in the tree
can allow goes to the person; team_finish, findings, running out of context;
transcripts read-only; the tree over the link (capability tree). New tools
team_whoami, team_finish, team_findings, team_request, team_decide, team_assign,
team_replace. Conformance: progress, delegation; team updated.
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
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 and THIRD_PARTY.md.