HomerandClaude Opus 5.5 f20e8c4307 Context hygiene at insert time: result ids, read stubs, the cap, recall
Harness spec 3.0.0 (context.md, loop.json `context`), in session/results.ts,
applied by the engine when a result goes into the conversation and never
afterwards:

- every result is headed by its id ([#0001]); a read also by the path as
  given, its lines, the file's length and the first 8 hex digits of the
  content's SHA-256; an empty file says so;
- a read of an unchanged file whose lines lie inside an earlier full read is
  a stub naming it; a list/glob/grep repeated with the same arguments and the
  same result is "Same result as #…";
- output over 400 lines or 40,000 characters keeps head and tail with the
  elided line; the full result is kept with the session (a new `results`
  table in sessions.db, gone with the session);
- edit, multiedit, write and apply_patch answer with their hunks under a
  bracket with the new content's hash; a new file is "Created, N lines.";
- recall (new built-in tool) shows any stored result, or a range of it, also
  after a resume; ids are never reused;
- compaction appends the table of the reads still in the conversation to the
  summary.

A stub only ever points at a result still in the conversation, so after a
compaction, an /undo or a rewind the file is read in full. compaction.prune
is gone: cutting old outputs in place threw the prompt cache away (an old
config's key is dropped with a warning). blocks/context.md is in the prompt
wherever recall is offered. Conformance runner for the `context` area (11
cases pass).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-27 20:27:17 +00:00
2026-10-09 21:59:03 +00:00
2026-10-09 21:59:03 +00:00
2026-10-09 21:59:03 +00:00
2026-10-09 21:59:03 +00:00
2026-10-09 21:59:03 +00:00
2026-10-09 21:59:03 +00:00
2026-10-09 21:59:03 +00:00
2026-10-09 21:59:03 +00:00
2026-10-09 21:59:03 +00:00
2026-10-09 21:59:03 +00:00
2026-10-09 21:59:03 +00:00
2026-10-09 21:59:03 +00:00
2026-10-09 21:59:03 +00:00
2026-10-09 21:59:03 +00:00

LLeMbas CLI — terminal coding agent

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.

Licence

MIT — see LICENSE and THIRD_PARTY.md.

2026-10-25 19:50:11 +00:00
Languages
TypeScript 98.6%
Shell 1.4%