{"version":"2.1.265","anchor":"session-signal-absorption-now-also-updates-a-per-host-aggreg","canonical_anchor":"session-signal-absorption-now-also-updates-a-per-host-aggreg","heading":"Session-signal absorption now also updates a per-host aggregate","tier":"internal","area":"Session Management","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/session-signal-absorption-now-also-updates-a-per-host-aggreg","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Session-signal absorption now also updates a per-host aggregate\n\nSession-signal tracking now also updates a per-host aggregate, alongside existing per-session tracking\n\n**Unclear.** The finding doesn't say what this per-host aggregate is used for or what visible effect it has.\n\n**What**\n\nInternal tracking of \"session signals\" (state like which bash tools or tools have been used) now also updates a shared aggregate tied to the session's host, in addition to the existing tracking that was scoped to just the bash tool, host, and used-tools set. This happens both when signals are absorbed and when they are reset.\n\n**Why**\n\nThis is internal bookkeeping that lets related state be tracked at the host level rather than only per individual session, which the finding doesn't further explain the purpose of.\n\n- Area: Session Management\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}