{"version":"2.1.229","anchor":"usage-limit-messages-can-be-told-your-progress-was-saved","canonical_anchor":"usage-limit-messages-can-be-told-your-progress-was-saved","heading":"Usage-limit messages can be told your progress was saved","tier":"soon","area":"Rate Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/usage-limit-messages-can-be-told-your-progress-was-saved","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Usage-limit messages can be told your progress was saved\n\nUsage-limit messages can append \"progress saved\", but callers only pass it when a server flag is on.\n\n**What**\n\nThe code that writes \"You've hit your \u2026\" and \"You're out of usage credits\u2026\" can now append \" \u00b7 progress saved\" to those messages. It is off in this build: callers only pass the flag when the `tengu_vellum_anchor` remote setting is on, which falls back to off, so the messages read exactly as before.\n\n**Details**\n\n- The suffix is a new option on the message builder rather than a separate string, so both limit messages pick it up together.\n\n**Evidence**\n\n`progressSavedSuffix`\n\n- Flag `tengu_vellum_anchor`: Off in both readings (read for one account on one subscription tier against v2.1.229; this account: off, anonymous baseline: off, 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: Rate Limits\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}