{"version":"2.1.268","anchor":"sessionagent-auto-naming-gains-a-cache-mode","canonical_anchor":"sessionagent-auto-naming-gains-a-cache-mode","heading":"Session\/agent auto-naming gains a 'cache' mode","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/sessionagent-auto-naming-gains-a-cache-mode","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Session\/agent auto-naming gains a 'cache' mode\n\nSession\/agent auto-naming adds a 'cache' mode with its own path for new names and name collisions\n\n**Unclear.** What triggers 'cache' mode naming and what the dedicated collision path does differently is not stated.\n\n**What**\n\nThe 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.\n\n**Why**\n\nThis gives conversation naming a separate track for cache-driven naming, keeping it distinct from the normal transcript-based naming and collision handling.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}