{"version":"2.1.227","anchor":"fleet-view-can-read-session-transcripts-through-a-stream-bac","canonical_anchor":"fleet-view-can-read-session-transcripts-through-a-stream-bac","heading":"Fleet view can read session transcripts through a stream backend","tier":"internal","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/fleet-view-can-read-session-transcripts-through-a-stream-bac","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Fleet view can read session transcripts through a stream backend\n\nThe fleet list can read each job's last transcript line through a stream backend when supplied.\n\n**What**\n\nThe agents\/fleet list reads each job's last transcript line through a transcript stream backend when one is supplied, statting the transcript and reading its final 16384 bytes. With no backend it falls back to the previous local filesystem stat and tail read, so behaviour is unchanged for anyone not running one.\n\n**Details**\n\n- The stream key only resolves for a `.jsonl` file sitting directly under the projects directory; anything else takes the filesystem path.\n- Stat results are reported as present with a modification time, absent, refused (for `ELOOP` and `ENXIO`) or unreadable.\n- Failures raise \"fleet view transcript tail read failed\" or \"fleet view transcript tail: stream not found\".\n- Neither the errors nor the key descriptor shape exist in v2.1.226.\n\n**Evidence**\n\n`fleet view transcript tail read failed`\n\n- Area: Background Tasks\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}