diff --git a/CHANGELOG.md b/CHANGELOG.md
index 18e81d3..5f219a4 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -9,6 +9,39 @@ one of them changed. An entry says which artefact and which version, so `web 0.1
 Every version published to a channel appears here. Nothing is written from memory afterwards: a build
 cannot be published without its entry.
 
+## 2026-09-12 — Long conversations open quickly, and you can search inside them `web 0.136.0`
+
+A conversation of several hundred turns had become slow in a way that spread past itself. Opening one
+took the better part of half a minute. Once it was open the rest of the console went with it — the
+notification bell, which has nothing to do with the transcript, took fifteen seconds to drop its
+list. The cause was one number: the browser was laying out sixty thousand elements, and every part of
+the app that asked it a question about the page had to wait for all of them.
+
+**The transcript now only measures the turns you can actually see.** Everything above and below stays
+in the page, exactly where it is — nothing is unloaded, nothing is fetched again when you scroll back
+— but the browser stops doing the arithmetic for turns that are off screen. On a seven-hundred-turn
+conversation, opening it went from 24 seconds to under 3, and the notification bell from 29 seconds
+to 2.6. The last few turns are deliberately left out of this, so a streaming reply still lands
+exactly where it should.
+
+**Coming back to a conversation now puts you back where you were, on the turn you were reading**, not
+at a remembered pixel. The distinction matters now that most of the page is unmeasured: a pixel
+offset means something different every time, and restoring one dropped you tens of turns from where
+you had been. It now remembers the message, which does not move.
+
+**There is a find bar for the conversation you are in.** ⌘F, Ctrl+F, or the magnifier in the header —
+at every width, including a phone, where scrolling back through four hundred turns is worst. Type and
+every matching message is marked down the side of the transcript, with the words lit inside the one
+you are on; Enter and Shift+Enter walk forward and back through them and wrap around; Escape closes
+it. The counter counts **messages**, not occurrences, and it is exact: it is computed from the
+conversation itself rather than from what happens to be on screen, so "12 / 35" means thirty-five
+turns mention what you typed, including the ones six hundred rows back. Accents and case are ignored
+in both directions — _deploiement_ finds _déploiement_, and so does _DÉPLOIEMENT_.
+
+Your browser's own Ctrl+F still works on this screen if you press it again while our bar has focus.
+
+**Self-hosters:** console only. No schema change, no configuration, no new key, nothing to do.
+
 ## 2026-09-12 — Half the tooltips in the app were the browser's, not Jarvis's `web 0.135.0`
 
 Hovering the mark beside a conversation drew a dark rounded bubble with a little arrow, in the