{"version":"2.1.227","anchor":"unreadable-agent-metadata-is-logged-instead-of-silently-igno","canonical_anchor":"unreadable-agent-metadata-is-logged-instead-of-silently-igno","heading":"Unreadable agent metadata is logged instead of silently ignored","tier":"internal","area":"Agents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/unreadable-agent-metadata-is-logged-instead-of-silently-igno","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Unreadable agent metadata is logged instead of silently ignored\n\nUnreadable agent metadata is now logged with the underlying error instead of ignored.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- Replaces a bare catch that returned nothing.\n- Callers identify themselves, for example `persistAgentMetadata` and `clearWorktreeFromAgentMetadata`.\n\n**Evidence**\n\n`agent metadata sidecar unreadable, treating as absent`\n\n- Area: Agents\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}