{"version":"2.1.309","anchor":"transcript-api-request-replay-records-held-until-the-first","canonical_anchor":"transcript-api-request-replay-records-held-until-the-first","heading":"Request details wait for your first message before going into the transcript","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/transcript-api-request-replay-records-held-until-the-first","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Request details wait for your first message before going into the transcript\n\nClaude Code now holds saved request details until your first message is written to the session file\n\n**What**\n\nThe session file, called the transcript, can store the details of each request Claude Code sends: the system prompt, the tool list and the settings. When a new session file is being created, Claude Code now holds these details back until your first real message has been written, and then writes them. If no transcript ends up existing, the held details are dropped.\n\nBefore, they were written straight away.\n\n**Why**\n\nA session file no longer starts with request details before there is any message of yours in it, which keeps transcripts and resumed sessions tidy.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}