{"version":"2.1.314","anchor":"upload-write-failures-now-carry-extra-diagnostics-uploads-c","canonical_anchor":"upload-write-failures-now-carry-extra-diagnostics-uploads-c","heading":"Headless sessions now keep a count of uploads after each turn","tier":"internal","area":"Headless Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/upload-write-failures-now-carry-extra-diagnostics-uploads-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Headless sessions now keep a count of uploads after each turn\n\nSessions run by a program now do an uploads count at the end of every turn, and file writes return extra details\n\n**Unclear.** What the uploads count records, and whether it is sent anywhere, is not known.\n\n**What**\n\nA headless session is one run by a program rather than typed into on screen. These sessions now do an uploads count at the end of every turn, next to an existing memory count. A turn is one round of the model replying.\n\nFile writes also return extra details now, whether they succeed or fail.\n\n**Why**\n\nThis looks like per-turn record keeping about uploads.\n\n- Area: Headless Mode\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}