{"version":"2.1.285","anchor":"allusersprofile-added-to-an-env-allowlist-opus-4-max-token","canonical_anchor":"allusersprofile-added-to-an-env-allowlist-opus-4-max-token","heading":"ALLUSERSPROFILE is allowed through, and the Opus 4 output limit table is gone","tier":"internal","area":"Windows","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/allusersprofile-added-to-an-env-allowlist-opus-4-max-token","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### ALLUSERSPROFILE is allowed through, and the Opus 4 output limit table is gone\n\nALLUSERSPROFILE joins a list of allowed Windows variables, and a table fixing Opus 4 and 4.1 output at 8192 tokens was replaced\n\n**Unclear.** What the variable list governs, and where the Opus 4 limits now come from, is not stated.\n\n**What**\n\nTwo small changes:\n\n- `ALLUSERSPROFILE`: this Windows environment variable (a named value the system provides to programs) joins a list of allowed variables that already had `HOMEDRIVE` and `PROGRAMDATA`.\n\n- Opus 4 limits: a built-in table setting 8192 as the token limit for Claude Opus 4 and Opus 4.1 was replaced.\n\n**Why**\n\nThe first affects which Windows variables Claude Code passes along. The second affects limits applied to older Opus models.\n\n- Area: Windows\n- Names: `ALLUSERSPROFILE`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}