HomerandClaude Opus 5.5
6ec95fbd66
The four team tools (tool/team_tools.ts) on the rules of team/team.ts, driven from real turns by team/runtime.ts: - Members run on the subagent job machinery (app.ts spawn with `member`): background, unattended, their own prompt from blocks/team_member.md (the whole of team_lead.md for one with lead: true), team_send and team_read (team_add and team_stop for one that leads). Not jobs to the model: job_list and the job_* tools skip them; a client over the link still sees them as subagent jobs named "<name>: <role>". - The room: messages and reports with their marks, delivered at the next step boundary or waking a finished member or the idle lead; report posts to the manager. - A manager's work calls answer the refusal before the permission check, by risk class (an MCP tool by its readOnlyHint); the tool list is unchanged. job_stop and reading bash stay. - Slots: the lead waits for one before its turn (Esc stops the wait); members wait in order; task helpers in a team count toward the size and hold a slot; job_send restarting a helper is refused when full. - The offer is decided with the prompt and kept with it: a resumed session takes it from its kept tool list. - The size: agents.min/max settings, refused outside 1 <= min <= max <= cap, kept across /new and resume; said in a note on the first message, after a change, after a compaction and a rewind. - TUI: /team (tree and room, size, stop a member, dialogs for both), an "agents" row beside the effort in /effort, "team n/max" in the status bar. /team works over ACP too. tests/team.test.ts runs a lead, a member and its report through the app. 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.