{"version":"2.1.275","anchor":"memory-extraction-gains-an-optional-laptop-extract-runner","canonical_anchor":"memory-extraction-gains-an-optional-laptop-extract-runner","heading":"Memory extraction gains an optional 'laptop extract runner' hook","tier":"soon","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/memory-extraction-gains-an-optional-laptop-extract-runner","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Memory extraction gains an optional 'laptop extract runner' hook\n\nMemory extraction can now run an optional extra 'laptop extract runner' hook at the end of each turn\n\n**Unclear.** What the 'laptop extract runner' does and when it is available is not stated.\n\n**What**\n\nThe memory-extraction process that runs at the end of a turn now also instantiates and runs an optional \"laptop extract runner\" component, if one is available, alongside its existing extraction logic.\n\n**Why**\n\nThe finding doesn't say what this runner does, so its practical effect on memory extraction isn't clear.\n\n- Area: Memory\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}