{"version":"2.1.281","anchor":"memory-file-load-telemetry-gains-size-fields-and-skips-autom","canonical_anchor":"memory-file-load-telemetry-gains-size-fields-and-skips-autom","heading":"Memory-file load telemetry gains size fields and skips automem in one mode","tier":"internal","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/memory-file-load-telemetry-gains-size-fields-and-skips-autom","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Memory-file load telemetry gains size fields and skips automem in one mode\n\nThe CLAUDE.md load event now records instruction sizes and is skipped in one mode that also limits auto-memory\n\n**Unclear.** The finding does not say which mode this is or how a user enters it.\n\n**What**\n\nThe `tengu_claudemd__initial_load` event, recorded when your CLAUDE.md instruction files are first loaded, now also records:\n\n- `instructions_content_length`: the total size of the loaded instructions.\n\n- `max_file_content_length`: the size of the largest single file.\n\nIn one mode the event is no longer recorded at all, and in that same mode the auto-memory list is reduced to its single non-index entry.\n\n**Why**\n\nThe event now shows how large the loaded instructions are. In the one mode affected, less auto-memory is loaded.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}