A menu for what a chat may use, and three keys

Six smaller things, all of them about the interface not saying what is true.

The @ button only ever inserted the character, which the @ key already does
without a button. It becomes the scope menu: what this chat may use, switched
off per chat. Chat.scope_json is filtered inside resolve_tools AFTER the
capability, permission and instance gates -- exactly as chat.knowledge_bases
narrows knowledge_search -- so a crafted POST turning something on reaches a
tool the gates already removed, and there is a test that writes the column
directly to prove it. Absent means on, for every key, so "why is this off?" has
one answer. It is keyed on the gate rather than the tool name, so notes is one
switch rather than five. The switches carry no role="menuitem", deliberately:
ui.js closes a picker when a menuitem is clicked, which is right for an action
menu and wrong for a list you want to set several of -- which is why the menu
needs no JavaScript at all. Typing @ is untouched.

With no skills, nothing should mention them. tool.skills was gated on the family
alone, so somebody with an empty library was told "the list below gives each
one's name" above no list, handed skill_get, and watched the model spend a round
finding out. It requires skills now; the writing half moved to
tool.skills_write, which is deliberately not gated, because saving the first one
is what somebody with none most needs. And core.tool_list finally reads
tool_names, which had been resolved and documented with no fragment using it.

The composer's toolbar is one row again. .composer__actions is last in the DOM
with margin-left:auto, so the moment an agent chat added a connection, a
directory and a mode, Send and the microphone dropped to a second line.
chat.css has no media queries by design and the fix is not to add one:
.composer__context is the single child allowed to shrink and scroll sideways.
There is a test asserting the file still contains no @media.

The effort picker shows the level in force. "Effort: default" named no level and
was true of nothing in particular; chat.resolved_effort is the chat's own value
and build_request reads the same field, so what is shown is what is sent. The
model's default is a seed, copied onto the row at creation and on a model
change, and never consulted at request time -- a fallback would resurrect it
underneath a cleared effort and make "off" silently do nothing. "off" is a
sentinel and not an empty value, because start_chat declares Form("") and cannot
tell absent from empty: with value="" the reader picks off and gets high.

Alt+M dictates, Alt+R reads the last reply aloud, Ctrl+Enter sends from
anywhere. All three click the button that already does the job, so audio.js
keeps its one delegated listener. Alt+M and not Alt+D, which is the address bar
in Chrome and Firefox. Ctrl+Enter never means Stop -- Send and Stop are the same
element, and Esc already stops. Driven under a DOM stub before committing, per
the rule in CLAUDE.md, and tests/test_commands_js.py pins that every key has a
row in SHORTCUTS, since /help reads that list.

And the memory tooling, which had seven defects. The worst: memory_forget was a
case-insensitive substring first-match delete with nothing warning about it, so
forgetting "coffee" against "Drinks coffee black" and "Allergic to coffee"
silently removed whichever was older -- a wrong deletion nobody would ever find
out about, from a tool whose description invited exactly the short fragment that
misfires. It matches exactly first, then by substring, and refuses an ambiguous
one while naming what it matched. add() refuses an exact duplicate. The
at-the-limit refusal no longer tells the model to delete one to make room: past
the block's budget it is not shown all of them and would be guessing, which
feeds straight back into the first defect. And context.memories no longer claims
the memories "still apply", which nothing checks and which taught a model to
trust a stale one over what the person had just said.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

src/lembas/services/library/memories.py

@@ -57,23 +57,45 @@ def get(db: DBSession, memory_id: str, user: User | None) -> Memory | None:
 
 
 def add(db: DBSession, *, owner: User, content: str, author: str = AUTHOR_MODEL) -> Memory:
-    """Record a fact. Raises ValueError when there is no room or nothing to say."""
+    """Record a fact. Raises ValueError when there is no room or nothing to say.
+
+    An exact repeat returns the record that already exists rather than making a
+    second one. The prompt asks the model to check before adding -- it is shown
+    every memory, so it can -- but the same preference saved four times in
+    slightly different words is the commonest failure here, and it is worse than
+    wasted tokens: it makes `memory_forget` ambiguous for every one of them.
+    Wording handles the near-duplicates; this handles the exact ones, which is
+    the half a prompt cannot be relied on for.
+    """
     content = " ".join((content or "").split())
     if not content:
         raise ValueError("A memory cannot be empty.")
+    content = content[:MAX_MEMORY_CHARS]
+
+    existing = db.scalars(
+        select(Memory).where(Memory.owner_id == owner.id, Memory.content == content)
+    ).first()
+    if existing is not None:
+        return existing
 
     count = db.scalar(
         select(func.count()).select_from(Memory).where(Memory.owner_id == owner.id)
     )
     if (count or 0) >= MAX_RECORDS:
+        # Deliberately does NOT say "remove one first". Past MAX_TOTAL_CHARS the
+        # injected block is truncated, so the model is not shown every memory
+        # and would be choosing blind -- and deleting the wrong one is not
+        # something anybody finds out about.
         raise ValueError(
-            f"There are already {MAX_RECORDS} memories. Remove one first, or put "
-            f"this in a note instead."
+            f"There are already {MAX_RECORDS} memories, which is the limit, so "
+            f"nothing was saved. Do not remove one to make room — you are not "
+            f"shown all of them and would be guessing. Say that the limit has "
+            f"been reached, and put this in a note instead."
         )
 
     memory = Memory(
         owner_id=owner.id,
-        content=content[:MAX_MEMORY_CHARS],
+        content=content,
         author=author if author in (AUTHOR_USER, AUTHOR_MODEL) else AUTHOR_MODEL,
     )
     db.add(memory)

src/lembas/services/library/skills.py

@@ -23,6 +23,7 @@ from __future__ import annotations
 
 import logging
 import re
+from collections.abc import Iterable
 
 from sqlalchemy import select
 from sqlalchemy.orm import Session as DBSession
@@ -72,18 +73,34 @@ def by_name(db: DBSession, name: str, user: User | None) -> Skill | None:
     return db.scalar(visible(db, user).where(Skill.name == slugify(name)))
 
 
-def enabled_for(db: DBSession, user: User | None) -> list[Skill]:
-    """Skills that should appear in the index, oldest first for a stable order."""
+def enabled_for(
+    db: DBSession, user: User | None, *, exclude: Iterable[str] = ()
+) -> list[Skill]:
+    """Skills that should appear in the index, oldest first for a stable order.
+
+    `exclude` is what one chat has switched off by name -- a narrowing of what
+    the library already allows, never a widening of it.
+    """
     if user is None:
         return []
-    return list(
-        db.scalars(
-            visible(db, user)
-            .where(Skill.enabled.is_(True))
-            .order_by(Skill.name)
-            .limit(MAX_INDEX_SKILLS)
-        )
+    hidden = {slugify(name) for name in exclude}
+    rows = db.scalars(
+        visible(db, user)
+        .where(Skill.enabled.is_(True))
+        .order_by(Skill.name)
+        .limit(MAX_INDEX_SKILLS + len(hidden))
     )
+    return [skill for skill in rows if skill.name not in hidden][:MAX_INDEX_SKILLS]
+
+
+def count_enabled(db: DBSession, user: User | None, *, exclude: Iterable[str] = ()) -> int:
+    """How many skills are available here at all.
+
+    Zero is what withdraws `skill_get` and `skill_edit`: reading and improving
+    are meaningless with nothing to read, and a model told to "read one with
+    skill_get" above a list that is not there spends a round finding out.
+    """
+    return len(enabled_for(db, user, exclude=exclude))
 
 
 def search(db: DBSession, user: User | None, needle: str, *, limit: int = 10) -> list[Skill]:
@@ -199,9 +216,9 @@ def delete(db: DBSession, skill: Skill) -> None:
     db.commit()
 
 
-def index_block(db: DBSession, user: User | None) -> str:
+def index_block(db: DBSession, user: User | None, *, exclude: Iterable[str] = ()) -> str:
     """The one-line-per-skill listing that goes into the prompt."""
-    skills = enabled_for(db, user)
+    skills = enabled_for(db, user, exclude=exclude)
     if not skills:
         return ""
     return "\n".join(f"- {skill.name}: {skill.description}" for skill in skills)