{"version":"2.1.234","anchor":"the-idle-remote-control-upsell-moved-into-the-nudge-registry","canonical_anchor":"the-idle-remote-control-upsell-moved-into-the-nudge-registry","heading":"The idle remote-control upsell moved into the nudge registry","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/the-idle-remote-control-upsell-moved-into-the-nudge-registry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### The idle remote-control upsell moved into the nudge registry\n\nThe idle remote-control suggestion now comes from the shared nudge system; you see the same thing.\n\n**What**\n\nThe suggestion to try \/remote-control or enable push notifications after an idle stretch now comes from the shared registry of in-session nudges rather than its own bespoke UI effect. Each upsell keeps its existing eligibility rules, so what you see is unchanged.\n\n**Details**\n\n- The registry entry keys off last query completion time, loading state and the clock.\n- The data passed to nudges gained the transcript, loading state, last query completion time and submit count.\n\n**Evidence**\n\n`\"remote-control-upsell\"`\n\n- Area: Elsewhere\n- Names: `\/remote-control`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}