{"version":"2.1.265","anchor":"large-project-memory-files-are-now-offloaded-to-a-local-file","canonical_anchor":"large-project-memory-files-are-now-offloaded-to-a-local-file","heading":"Large project memory files are now offloaded to a local_file pointer instead of inlined","tier":"notice","area":"Project Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/large-project-memory-files-are-now-offloaded-to-a-local-file","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Large project memory files are now offloaded to a local_file pointer instead of inlined\n\nLarge project memory files are now offloaded to a downloadable file instead of being pasted in full\n\n**What**\n\nWhen reading project memory files, content that stays under a certain size is still returned inline as before. Content that exceeds that size threshold is now written to a local file, and a pointer to that file (a `local_file` reference) is returned instead of embedding the full text directly.\n\n**Why**\n\nThis keeps large remembered files from bloating the conversation context, since only a reference is included by default rather than the entire file's contents, following the same offload-to-file approach already used for other project uploads.\n\n- Area: Project Memory\n- Names: `local_file`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}