HomerandClaude Opus 5.5
880289970b
team.md: a lead adds members (team_add) that work in the background on
the parts they own; members may lead areas of their own. The chat
setting agents {min, max} (defaults 1/4, an instance cap of 32) bounds
the whole tree, task helpers included; a team is offered only where
subagents are enabled and the model serves two requests at once
(capacity.parallel). A manager's work calls — risk write or execute,
bar job_stop and reading bash — answer a fixed refusal while the tool
list stays unchanged. The room: team_send to names or all, delivered
under "[Team message from X to Y:]" at the next step or waking a
finished member; a member's final reply is its report to its manager;
team_read shows the tree and the visible part of the room; team_stop
stops a subtree. Past the model's capacity a member waits for a slot,
the lead first. Size notes in context.note; texts in loop.json team;
prompts blocks/team_lead.md and team_member.md; tools allowed by
default. Conformance area team, written from a reference model.
The CLI embeds the new tool and prompt files; its tools are pending.
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.