[FEATURE] enable/disable agents by project
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
● ★ Insight ─────────────────────────────────────
The Reality of Agent Management in Claude Code
- No built-in way to disable specific agents - They're all loaded by default
- Custom agents can be added, but built-ins can't be removed
- Token overhead is fixed at startup - it's the cost of flexibility
- Workaround: Environment variables for broader optimization
─────────────────────────────────────────────────
🎯 The Truth: No Direct Agent Filtering
I apologize - I gave you incorrect information. After checking the official Claude Code documentation, there is no configuration option to selectively disable built-in Task tool agents. The
agent-config.json file I suggested doesn't exist in Claude Code.
Proposed Solution
<project>/agent-config.json:
{
"disabled_agents": [
"frontend-mobile-development:*",
"multi-platform-apps:*",
"nextjs-vercel-pro:*",
"kubernetes-operations:*",
"cloud-infrastructure:kubernetes-architect",
"deployment-strategies:*",
"cicd-automation:*",
"database-cloud-optimization:*",
"database-design:*",
"database-migrations:*",
"api-scaffolding:*",
"payment-processing:*",
"blockchain-web3:*",
"business-analytics:*",
"customer-sales-automation:*",
"content-marketing:*",
"seo-*",
"hr-legal-compliance:*",
"llm-application-dev:*",
"machine-learning-ops:*"
],
"enabled_agents": [
"code-reviewer",
"debugging-toolkit:debugger",
"error-debugging:error-detective",
"Explore",
"general-purpose",
"code-documentation:docs-architect",
"documentation-generation:*",
"backend-development:backend-architect",
"shell-scripting:*",
"git-workflow:git-flow-manager",
"pr-review-toolkit:*",
"performance-optimizer:performance-engineer",
"security-pro:security-auditor"
]
}
Alternative Solutions
_No response_
Priority
Critical - Blocking my work
Feature Category
CLI commands and flags
Use Case Example
_No response_
Additional Context
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗