Unreadable agent metadata is now logged with the underlying error instead of ignored.
What's wrong with this entry?
When the small file holding an agent's saved metadata cannot be read, the failure is now logged with the underlying error and the name of the code that hit it, before falling back to treating the file as absent.
- Replaces a bare catch that returned nothing.
- Callers identify themselves, for example
persistAgentMetadataandclearWorktreeFromAgentMetadata.
agent metadata sidecar unreadable, treating as absent
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.235
Question options with identical text are no longer confused with each other
Both mention agent
-
v2.1.236
Teammate messages whose summary swallowed the body are split back apart
Both mention agent
-
v2.1.238
Claude is told to stay in a worktree even when it did not create one
Both mention agent