{"version":"2.1.280","anchor":"artifact-deploy-capability-refused-errors-now-aggregate-and","canonical_anchor":"artifact-deploy-capability-refused-errors-now-aggregate-and","heading":"Artifact deploy capability_refused errors now aggregate and truncate multiple entries","tier":"notice","area":"Artifacts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/artifact-deploy-capability-refused-errors-now-aggregate-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Artifact deploy capability_refused errors now aggregate and truncate multiple entries\n\nCapability-refused errors during artifact deploy now get summarized and truncated instead of shown raw\n\n**What**\n\nWhen an artifact deploy fails with a 422 `capability_refused` error, Claude Code now parses the server's message, which can list multiple `capabilities.*` entries, and keeps only as many as fit within a size limit. If entries are cut off, it appends a note saying how many more aren't shown, and adds a closing instruction to fix each named entry and republish. Previously the raw error message was passed through as-is.\n\n**Why**\n\nThis keeps capability-refused error messages readable and actionable even when many entries are refused at once, instead of dumping a potentially huge raw error.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}