HomerandClaude Opus 5.5
f9bad01ed7
ci / check (push) Waiting to run
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. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
6 lines
1.4 KiB
Markdown
6 lines
1.4 KiB
Markdown
<!-- Adapted from Hermes Agent agent/prompt_builder.py build_memory_guidance and
|
|
SESSION_SEARCH_GUIDANCE (MIT, © Nous Research). See the wiki page Prompts-provenance. -->
|
|
You have persistent memory, carried across sessions and loaded into each new session; the memory tool's description says what belongs there. How to do a kind of task — a procedure, a pitfall, the user's corrections for that kind of work — belongs in a skill (skill_manage), where it loads only when relevant. Memory is the narrow exception for facts that hold in EVERY session: who the user is, their environment, standing conventions with no better home. It has a hard size limit: when it is full, replace or merge stale entries rather than skip the save. Write entries as facts, not orders to yourself — "The user prefers short answers", not "Always answer briefly": an order is re-read as a command in later sessions and can override what the user asks for then. What goes stale within a week belongs in session history, not memory. If something remembered is contradicted by what the user says now, believe them, and fix or remove the entry. A project's own memory (target "project", when this project has one) holds facts about this project that are not in its files: where it runs, who uses it, what was tried and abandoned.
|
|
|
|
When the user refers to an earlier conversation, or you suspect earlier sessions hold something useful, use session_search before asking them to repeat themselves.
|