HomerandClaude Fable 5.1
837f38c744
The spec: plan_write and plan_update (new, shared, offered in every mode) and plan_submit (now shared) keep one structured plan — findings, objectives, phases of tasks — in place of the todo list, which lives on as a former name of plan_write. The shared system text is one text for both projects, with variables for what differs; the mode texts, a prototypes block and a library block are shared. acp.md: the client hands the device what only it knows (context, library, prototypes), the plan travels as a structure (plan_state), library calls carry the chat's scope, and a client may rewind a session. loop.json says its numbers as numbers. Four conformance areas: plan, prototype, library_scope, toolcall_index. The CLI: the plan is kept per session in the store and drawn above the prompt and on the approval card; the prompt is assembled from the spec's texts with their variables filled; the link reads the instance's instructions, personalization, knowledge scope and prototype offer, sends the plan as a structure and answers rewind; library calls to the instance carry the session as scope; a prototype written in the terminal is saved as a file and named in the transcript; a tool-call fragment without an index continues the last call; the default theme is Moria; dead exports and Hermes leftovers removed. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
LLeMbas CLI
A terminal coding agent and project manager: the lembas command. It talks to any LLM API
(OpenAI-compatible servers such as llama.cpp, vLLM or LM Studio, the OpenAI Responses API,
Anthropic, Gemini, Ollama), works in your project with four permission modes and a git snapshot of
every turn, remembers what it learns across sessions, and can sign in to a
LLeMbas server to use its models, library and search — and
let its 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
cd your-project && lembas # the TUI
lembas login https://your-server # sign in to a LLeMbas server and use its models
Without a server, add a connection to ~/.config/lembas/connections.yaml and set model: in
~/.config/lembas/config.yaml.
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.