{"version":"2.1.304","anchor":"offline-peer-entries-report-busy-and-lastheardat","canonical_anchor":"offline-peer-entries-report-busy-and-lastheardat","heading":"Unresponsive peers and machines now report when they were last heard from and whether they said they were busy","tier":"notice","area":"Peers","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/offline-peer-entries-report-busy-and-lastheardat","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Unresponsive peers and machines now report when they were last heard from and whether they said they were busy\n\nOffline peer entries and unreachable-session results now include lastHeardAt and a busy hint, so busy and gone can be told apart\n\n**What**\n\nWhen another session or machine (a peer) is not answering, Claude Code now gives more detail about its last known state:\n\n- Offline entries in the peer roster, the list of known peers, now include a `lastHeardAt` time. For peers marked 'asleep', this is when they went to sleep.\n\n- Those roster entries also include `busy: true` when the peer's last 'still here' signal (`lastStillHereAt`) is newer than `lastHeardAt`.\n\n- The result returned for an unreachable machine now includes `lastHeardAt` too. Before, it held only `machineNotAnswering` and `saidAsleep`, with no times.\n\n- That result adds `saidBusy` when a still-here signal is newer than the last heartbeat, the regular check-in a machine sends.\n\n**Why**\n\nA peer that is silent because it is busy can now be told apart from one that is gone, and you can see how long ago it was last heard from.\n\n- Area: Peers\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}