{"version":"2.1.286","anchor":"footer-indicator-can-come-from-a-model-capability","canonical_anchor":"footer-indicator-can-come-from-a-model-capability","heading":"Footer label can now also be set by the model's configuration","tier":"notice","area":"Footer","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/footer-indicator-can-come-from-a-model-capability","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Footer label can now also be set by the model's configuration\n\nThe footer indicator is read from `CLAUDE_CODE_FOOTER_INDICATOR`, then from the main model's configuration, then from startup data\n\n**What**\n\nClaude Code can show a short label, the footer indicator, at the bottom of its screen. It now looks for that label in this order:\n\n- the `CLAUDE_CODE_FOOTER_INDICATOR` environment variable\n\n- a footer label attached to the main model's configuration\n\n- the label sent in the data Claude Code receives when it starts\n\nThe middle step is the change. Before, Claude Code checked only the environment variable and then the startup data.\n\n**Why**\n\nWhoever runs the model setup can now label groups of users through the model's configuration. Setting `CLAUDE_CODE_FOOTER_INDICATOR` yourself still takes priority over everything else.\n\n- Area: Footer\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}