You'll notice
Useful3 Signal2
Files Claude Code writes now follow your umask instead of a fixed permission mode.
What's wrong with this entry?
Anonymous. No account, no email.
What
Files written by several subsystems now use a permission mode of 0666 masked by the current umask instead of a fixed default, so newly created files match whatever your environment already sets for the rest of your work. Alongside this, the writers involved were tidied up to create parent directories and write in place rather than assuming a directory exists.
Details
- Covers the teammate inbox writer, which stores messages between agents working together, and which logs
[TeammateMailbox] inbox update failedwhen a write does not land. - Covers the write that carries a task across to a fork, and a new helper that saves fetched binary content to disk.
- The binary save helper reports each write as
tengu_binary_content_persisted, carrying the size and the file extension. - Snapshot and metadata writers on the workflow, MCP task and changelog paths create their parent directory first and write in place, but only when the newer storage layer is on; otherwise they take the previous path.
Evidence
tengu_binary_content_persisted, [TeammateMailbox] inbox update failed
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.