{"version":"2.1.283","anchor":"post-turn-memory-config-gains-role-line-scan-and-a-hosted-sc","canonical_anchor":"post-turn-memory-config-gains-role-line-scan-and-a-hosted-sc","heading":"Post-turn memory config gains role_line_scan","tier":"use","area":"Memory","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/post-turn-memory-config-gains-role-line-scan-and-a-hosted-sc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Post-turn memory config gains role_line_scan\n\nThe post-turn memory config now takes a role_line_scan option choosing which attachments, instruction files and first window are scanned\n\n**Unclear.** What the role line scan does is not known.\n\n**What**\n\nThe JSON config read from `CLAUDE_CODE_POST_TURN_MEMORY_CONFIG` now accepts a `role_line_scan` object with three settings:\n\n- `attachments`: on by default.\n\n- `instruction_files`: on by default.\n\n- `first_window`: either \"full\", the default, or \"ignore_session_start_blocks\".\n\nThe values are passed on to memory extraction. A separate \"hosted\" caller checks the config against a different schema.\n\n**Why**\n\nThis controls which parts of a conversation the post-turn memory step looks through, such as attached files, instruction files, and the blocks added at the start of a session. The defaults scan everything.\n\n- Area: Memory\n- Names: `CLAUDE_CODE_POST_TURN_MEMORY_CONFIG`, `role_line_scan`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}