{"version":"2.1.312","anchor":"padding-whitespace-now-seeded-rather-than-mathrandom","canonical_anchor":"padding-whitespace-now-seeded-rather-than-mathrandom","heading":"Trailing whitespace padding no longer comes straight from random numbers","tier":"internal","area":"API Requests","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/padding-whitespace-now-seeded-rather-than-mathrandom","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Trailing whitespace padding no longer comes straight from random numbers\n\nA routine that adds a random-looking run of trailing spaces and tabs now builds it from a different source instead of plain random numbers\n\n**Unclear.** It is not clear whether the new source produces the same padding each time, so whether behaviour actually changes is unknown.\n\n**What**\n\nClaude Code has a small routine that adds a run of spaces and tabs to the end of some text. It appears to be padding that keeps cached copies from being reused. Before, each character and the length of the run were picked with plain random numbers. Now the mix of spaces and tabs is built from the result of another internal calculation.\n\n**Why**\n\nIf that calculation gives the same result each time, the padding would be the same each time instead of random.\n\n- Area: API Requests\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}