{"version":"2.1.271","anchor":"session-log-picker-now-receives-the-current-session-id","canonical_anchor":"session-log-picker-now-receives-the-current-session-id","heading":"Session-log picker now receives the current session id","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/session-log-picker-now-receives-the-current-session-id","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Session-log picker now receives the current session id\n\nThe session-resume list now always includes and can highlight the currently active session\n\n**Unclear.** The finding shows the id is now always included and available for use but does not confirm it is used for visual highlighting.\n\n**What**\n\nThe component that lists past conversations for resuming (renamed from `amt` to `A_t`) now takes a `currentSessionId` value instead of only a maximum-height setting. Its filtering logic has also changed so that a session matching that id is always kept in the list, even if it would otherwise have been filtered out.\n\n**Why**\n\nThis likely makes it possible to highlight or otherwise distinguish the session you're currently in when browsing the resume list, and ensures it doesn't disappear from that list due to filtering.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}