Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Internal ChangesKind: in v2.1.268,
Internal ChangesSection of the release
Unclear What triggers 'cache' mode naming and what the dedicated collision path does differently is not stated.
What
The internal function that assigns or renames a conversation's auto-generated name now takes an explicit source setting, defaulting to "transcript" as before. It also adds a new "cache" mode: when naming happens in cache mode and no session has been established yet, it goes through a different, dedicated path rather than registering the name the normal way, and if the chosen name collides with an existing one, that collision is also resolved through the cache path instead of the usual collision resolver.
Why
This gives conversation naming a separate track for cache-driven naming, keeping it distinct from the normal transcript-based naming and collision handling.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat triggers 'cache' mode naming and what the dedicated collision path does differently is not stated.
