{"version":"2.1.267","anchor":"artifact-tool-result-files-error-no-longer-marked-is-error","canonical_anchor":"artifact-tool-result-files-error-no-longer-marked-is-error","heading":"Artifact tool_result files_error no longer marked is_error","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/artifact-tool-result-files-error-no-longer-marked-is-error","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Artifact tool_result files_error no longer marked is_error\n\nArtifact files_error results no longer flagged as errors\n\n**Unclear.** It is not stated what, if anything, now signals this failure to the model instead of `is_error`.\n\n**What**\n\nWhen an artifact operation fails with a files_error, the tool result returned to the model no longer carries the `is_error` flag that previously marked it as an error result.\n\n**Why**\n\nThis changes how the model perceives a files_error case; without the flag, it may no longer be treated as a hard failure in the same way, though the finding does not say what replaces that signal.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}