{"version":"2.1.232","anchor":"clear-error-when-every-tool-an-agent-could-use-is-denied","canonical_anchor":"clear-error-when-every-tool-an-agent-could-use-is-denied","heading":"Clear error when every tool an agent could use is denied","tier":"notice","area":"Subagents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/clear-error-when-every-tool-an-agent-could-use-is-denied","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Clear error when every tool an agent could use is denied\n\nIf your permissions deny every tool an agent could use, you now get a clear explanation.\n\n**What**\n\nIf your permission settings deny all the tools a subagent type is allowed to use, launching or resuming that agent now fails with a message saying so, instead of a misleading \"not found\".\n\n**Details**\n\n- Applies to launching a subagent by type, resuming one, and the workflow `agent({agentType})` path.\n- Two new telemetry outcomes record it: `subagent_type_tools_denied` and `subagent_resume_tools_denied`.\n\n**Evidence**\n\n`is unavailable because every tool it may use is denied by the current permission settings.`\n\n- Area: Subagents\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}