{"version":"2.1.302","anchor":"remote-session-file-reads-and-lists-now-go-through-a-path-re","canonical_anchor":"remote-session-file-reads-and-lists-now-go-through-a-path-re","heading":"Remote session file reads now check each path first and skip ones that fail","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/remote-session-file-reads-and-lists-now-go-through-a-path-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Remote session file reads now check each path first and skip ones that fail\n\nSeveral readers of remote and session files now check a path before reading it and return nothing when the check gives no result\n\n**Unclear.** What makes a path fail the new check, and so get skipped, is not known.\n\n**What**\n\nSeveral places that read stored session files now pass each path through a check first. When the check gives no result, the read is skipped and returns an empty or missing value instead. This covers:\n\n- listing information about remote agents\n\n- session aliases, the alternative names a session can have\n\n- reading the end of a session's transcript\n\n- looking up tools whose details are loaded later\n\nA new step also looks through each session's `ccr-tip.json` file while a remote session is being set up.\n\n**Why**\n\nIn practice, some of these reads can now come back empty where they used to read the file directly. The change looks aimed at making reads of transcripts and remote storage safer.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}