{"version":"2.1.257","anchor":"maple-rung-nudge-eligibility-check-reworked","canonical_anchor":"maple-rung-nudge-eligibility-check-reworked","heading":"Maple-rung nudge eligibility check reworked","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/maple-rung-nudge-eligibility-check-reworked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Maple-rung nudge eligibility check reworked\n\nA nudge's eligibility check was rewritten around a different allowed-state helper, still gated by the same flag.\n\nThe Maple-rung nudge's `isRelevant` eligibility check has been reworked from `!ch() || !NV() || !Mt(\"allow_remote_control\")` to `!$ve() || !Oq()`, where `$ve()` now checks `_S() && oFe() === \"allowed\"`. The nudge still ultimately gates on `tengu_maple_rung`.\n\n- Flag `tengu_maple_rung`: Not enough to say (read for one account on one subscription tier against v2.1.257; this account: no value returned, anonymous baseline: no value returned, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}