HomerandClaude Opus 5.5
b75923e724
Config, data and state are rooted at <project>/.agent/local/lembas (or .lembas/), kept out of git; a local directory the repository carries is refused. The user's logins and connections.yaml are read, never written; the user's config.yaml is not read. The TUI is started with TMPDIR inside it (the compiled binary unpacks its native library there) and OpenTUI's cache goes there too; the agent's commands keep the user's TMPDIR. An instance serves models, chat, speech and the balance only: the link, /remote, the service and the hub are off, deletes are not sent, and the server library, search, fetch, embeddings and personalization are not used. Self-update and uninstall are refused. hardline_disable is ignored, and tools treat the local directory as outside the project. The smoke test runs a whole local session in the compiled binary and checks that HOME, the XDG directories and TMPDIR gained nothing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
3.2 KiB
3.2 KiB
Changelog
All notable changes to LLeMbas CLI. The format follows Keep a Changelog, and the project uses Semantic Versioning.
[Unreleased]
Added
lembas remote list | add <dir>… | remove <dir>… | enable | disable | mode <m> | terminal <on|off>manages theremote:block without editing YAML, keeping the file's comments.addstores each directory as an absolute real path, skips one already covered by a root, refuses a missing one (nothing is written), and turns remote work on.--jsonprints one object,{"enabled", "roots", "max_mode", "terminal"}, with the defaults applied — for a program such as LLeMbas Desktop.lembas -l/lembas --local: local mode. Config, sessions, memory, skills, the library, snapshots, worktrees, caches, trust and history live in the project's git-ignored.agent/local/lembas/(.lembas/where.agentis another tool's), and nothing is written anywhere else — not even temporary files: the TUI starts with TMPDIR there, and the TUI library's cache goes there too (the commands the agent runs keep your TMPDIR). Your logins and connections.yaml are read, never written; your config.yaml is not read. A LLeMbas instance is used for its models, chat, speech in and out and the balance only: no link,/remote, service or hub, no deletes sent, no server library, no search, fetch or embeddings through it, no account personalization, and no self-update. The instance still records each request's usage, as any API does.-ldoes not trust the project by itself; the first start asks, and the answer is kept in the local directory. A local directory the repository carries is refused,hardline_disableis ignored, and tools treat the local directory as outside the project: no tool writes there (but in its worktrees), and reading it asks as anything outside the project does. The status bar sayslocal, andlembas -l --helpexplains it.
Changed
- A running
lembas servicefollows theremote:block without a restart: roots, mode, trust, terminals andenabledare read again whenever they are used (a stat of config.yaml; parsed only when it changed). When what the instance was told changes, the link is dialled again once nothing is working, so the web UI hears the new limits. lembas servicelinks even before any folder is allowed; it then accepts no session until one is added. With remote work off or no roots it tells the instanceroots: []and refuses every session, directory and terminal; before,service runexited at once and the instance could not tell "remote off" from "not running".- Harness spec 1.0.1:
acp.mdsays so.
[1.1.0] — 2026-10-14
Added
lembas login --jsonprints the code to approve and the outcome as one JSON object per line, for a program that drives the login (LLeMbas Desktop).
[1.0.0] — 2026-10-09
The first public release of LLeMbas CLI: a terminal coding agent and project manager for any LLM API, with permission modes, git snapshots, memory and skills, knowledge bases, MCP, voice, and a link to a LLeMbas instance whose web UI can work its sessions too. Signed Linux binaries for x64 and arm64.