{"version":"2.1.283","anchor":"new-storage-backend-error-wrapping-for-host-file-operations","canonical_anchor":"new-storage-backend-error-wrapping-for-host-file-operations","heading":"Clearer errors when the storage backend fails a host file operation","tier":"internal","area":"Remote Tools","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/new-storage-backend-error-wrapping-for-host-file-operations","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Clearer errors when the storage backend fails a host file operation\n\nFailed host file operations now report whether the storage backend refused them, with an error code, or simply could not perform them\n\n**Unclear.** Which file operations reach these new errors is not traced.\n\n**What**\n\nClaude Code now sorts errors from the storage backend, the service that stores files, into two kinds when a file operation on the host machine fails:\n\n- a refusal that carries an error code, reported as \"host file operation refused by the storage backend\" with the code attached\n\n- anything else, reported as \"host file operation could not be performed by the storage backend\"\n\n**Why**\n\nFile-operation failures in cloud or remote sessions should come with more specific errors and codes, which makes it easier to tell a refusal from a general failure.\n\n- Area: Remote Tools\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}