{"version":"2.1.248","anchor":"richer-requires-action-payloads-for-remote-clients-stay-off","canonical_anchor":"richer-requires-action-payloads-for-remote-clients-stay-off","heading":"Richer \"requires action\" payloads for remote clients stay off","tier":"soon","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/richer-requires-action-payloads-for-remote-clients-stay-off","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Richer \"requires action\" payloads for remote clients stay off\n\nDetailed requires-action payloads for remote clients remain off.\n\n**What**\n\nThe detailed requires-action payload sent to remote clients, carrying the question header, a plan-ready label and a sanitised command, is still behind `tengu_bridge_requires_action_details`, whose fallback is false. This release only reworked its body.\n\n**Evidence**\n\n`tengu_bridge_requires_action_details`\n\n- Flag `tengu_bridge_requires_action_details`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.248; this account: on, anonymous baseline: on, compiled default: off)\n- Area: Sessions\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}