The stop-compressing-requests switch is now saved through the storage layer.
What's wrong with this entry?
The switch that stops compressing request bodies after a server rejects one now writes through the storage handle. The stored record and its timestamp and status are unchanged, and setting CLAUDE_CODE_GZIP_REQUEST_BODIES still bypasses persistence entirely.
gzipRequestBodiesLatchedOff
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.247
Gzipped request bodies for Remote Control traffic, off by default
Both mention gzip request body