{"version":"2.1.247","anchor":"a-hardcoded-fallback-string-in-the-prompt-footer","canonical_anchor":"a-hardcoded-fallback-string-in-the-prompt-footer","heading":"A hardcoded fallback string in the prompt footer","tier":"soon","area":"Terminal UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/a-hardcoded-fallback-string-in-the-prompt-footer","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### A hardcoded fallback string in the prompt footer\n\nThe prompt footer has a hardcoded placeholder string that may or may not ever appear.\n\n**What**\n\nThe footer used to show an indicator only when configuration supplied one, capped at 32 characters and 6 lines. This build adds a fallback that prints the literal text `rulz12` when no indicator is configured and a new per-render condition holds. That condition is computed from the current permission mode and the resolved main-loop model, and the function it calls is not identifiable in the shipped bundle, so whether it is ever true is not determinable from the build.\n\n**Details**\n\n- The result is memoized over the main-loop model, the session's model and the permission mode.\n- The string does not exist in 2.1.246.\n\n**Evidence**\n\n`rulz12`\n\n- Area: Terminal UI\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}