Environment reads go through one shared accessor; same variables, same behaviour.
What's wrong with this entry?
Many direct process environment reads now go through the shared environment object instead. Same variables, same behaviour, read through a single coercing accessor.
- Covers alt-screen full repaint, bench live counts, TMUX/STY/WT_SESSION detection, ConEmu and TERM_PROGRAM progress reporting, VISUAL/EDITOR, and the custom API key settings row.
CLAUDE_CODE_ALT_SCREEN_FULL_REPAINT
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.237
Poll-events switch cannot be set from settings
Both mention environment variable
-
v2.1.224
Create a cloud session without a terminal
Both mention environment
-
v2.1.224
Clearer error when
--bgand--environmentare combinedBoth mention environment