{"version":"2.1.234","anchor":"background-queries-pass-a-proactivity-level-that-is-always-u","canonical_anchor":"background-queries-pass-a-proactivity-level-that-is-always-u","heading":"Background queries pass a proactivity level that is always undefined","tier":"internal","area":"Proactivity","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/background-queries-pass-a-proactivity-level-that-is-always-u","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Background queries pass a proactivity level that is always undefined\n\nBackground queries carry a \"proactivity level\" whose supplier is empty, so it is always undefined.\n\n**What**\n\nInternal one-shot queries such as summarisation, title generation and permission helpers now include a proactivity level in their options. The helper that supplies it has an empty body, so the value is undefined at every call site.\n\n**Details**\n\n- A matching proactivity-level change notifier was added to the session config class.\n\n**Evidence**\n\n`notifyProactivityLevelChanged`\n\n- Area: Proactivity\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}