How copilot-kit detects the domain of your request and routes it to the right specialist agent.
Agent routing is silent and automatic. The Risk Engine analyzes domain signals in your request (not just keywords — context-aware) and maps them to the best specialist agent. No extra commands or syntax required.
In FLUID and STANDARD mode, routing happens with no announcement. In STANDARD+ mode, a compact banner appears: [frontend applied]. In LOCKDOWN, the full agent header is shown.
| Domain signal | Primary agent | Skills loaded |
|---|---|---|
| Mobile (iOS, Android, RN, Flutter) | mobile-developer | mobile-design |
| Web / Next.js / React | frontend-specialist | frontend-design |
| API / Backend / DB | backend-specialist | api-patterns, database-design |
| Security / Auth / Secrets | security-auditor | vulnerability-scanner |
| Multi-domain / Orchestration | orchestrator | Per sub-agent |
| Planning / Architecture | project-planner | plan-writing |
| Debug / Investigation | debugger | clean-code, domain skill |
| AI / ML / DL | ml-engineer | ai-engineering |
mobile-developer, not frontend-specialist. The domain detection disambiguates these automatically.Mention an agent explicitly with the @agent-name syntax to bypass auto-routing:
@security-auditor Review this Express middleware for vulnerabilities
@ml-engineer Help me choose between fine-tuning vs RAG for my use case
@debugger Investigate why this React component re-renders 40 times on mountWhen a request spans multiple domains, all matching agents are scored by keyword density. The top two collaborate, with orchestrator coordinating if 3 or more agents are needed.
Example: Full-stack feature request
"Add authentication to this Next.js app using Prisma and JWT"