{"version":"2.1.275","anchor":"repl-bindings-retained-across-compaction-currently-dark","canonical_anchor":"repl-bindings-retained-across-compaction-currently-dark","heading":"Compaction summaries now report kept REPL bindings","tier":"soon","area":"REPL","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/repl-bindings-retained-across-compaction-currently-dark","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Compaction summaries now report kept REPL bindings\n\nCompaction summaries now say when your REPL\/notebook variable state was kept, replacing the old cleared-state flag\n\n**Unclear.** The finding describes this as currently dark; whether or how it is enabled for any accounts is not stated.\n\n**What**\n\nCompaction summaries (the notes shown when Claude Code condenses conversation history) can now include a note that your REPL (read-eval-print loop, i.e. notebook\/code execution) variable bindings were preserved across compaction, saying \"Your REPL VM state was kept across this compaction.\" This is powered by a new `replBindingsKept` field, computed from tool state, which replaces the previous `replStateCleared` boolean. This behavior is currently gated and not yet generally visible.\n\n**Why**\n\nThis gives a clearer, positive signal about what was retained after compaction rather than only reporting that state was cleared, though it isn't yet enabled for all users.\n\n- Area: REPL\n- Names: `replBindingsKept`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}