Use it now
Useful2 Signal2
SDK debug logging tags a session id and can write through the storage layer when given one.
What's wrong with this entry?
Anonymous. No account, no email.
DEBUG_CLAUDE_AGENT_SDK
What
The SDK debug logger now mints a session id of the form sdk-<uuid> at startup and, when the caller hands it a storage handle, appends through that instead of writing the file directly. With no handle it writes to the same debug file as before. Only runs when DEBUG_CLAUDE_AGENT_SDK is set.
Evidence
{ namespace: "log", sessionId: Fyi, channel: "debug" }
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.232
Session logs get a place in the managed storage layer
Both mention debug
-
v2.1.247
Renaming a session warns when other sessions may keep the old name
Both mention debug
-
v2.1.235
Question options with identical text are no longer confused with each other
Both mention agent