F
licenseNot graded
qualityA
maintenanceEnables a primary AI assistant to delegate tasks to multiple specialized coding sub-agents, run them in parallel with shared project context, and synthesize their responses from within the IDE.
-
SubagentBridge
by rzqllh
Related Servers
Alternatives to SubagentBridge
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables a primary AI assistant to delegate tasks to specialized local AI sub-agents in parallel, share project context, and synthesize their responses from within an IDE.-
- AlicenseAqualityAmaintenanceEnables Claude Code and Claude Desktop to delegate token-heavy tasks to Antigravity headless subagents, offloading file edits, test runs, and exploration while preserving Claude's context window.1210 npm1MIT
- FlicenseNot gradedqualityAmaintenanceEnables a primary AI coding assistant to delegate tasks in parallel to specialized CLI-based AI sub-agents, sharing project context and synthesizing their responses from within an IDE.-
- FlicenseNot gradedqualityAmaintenanceEnables a primary coding assistant to delegate tasks in parallel to specialized local sub-agents, sharing project context and synthesizing their responses into a single result.-
- FlicenseNot gradedqualityAmaintenanceEnables a primary AI coding assistant to delegate tasks to multiple specialized CLI-based sub-agents in parallel, share project context, and synthesize their responses into a single result. It supports using existing subscriptions and local tools without extra markup.-
TDQS
C2.7/5.0
Scored across 20 tools
Disambiguation3/5
The core lifecycle tools (submit_goal, execute_run, execute_task, list_tasks, get_task_evidence, get_run) are reasonably distinct, but the surface contains explicit duplicates: get_pending_approvals vs list_pending_actions and reject_approval vs reject_action are the same operation, and the six 'legacy helper' agent/session tools overlap conceptually with the new run/task tools. The 'Legacy' labels in descriptions help an agent pick the modern path, but they do not remove the redundancy.
Naming Consistency4/5
Nearly everything follows a snake_case verb_noun pattern (submit_goal, list_tasks, cancel_run, get_model_usage), which is predictable and readable. Minor deviations like wait_for_idle and get_agent_status, plus vocabulary drift between 'agent', 'session', 'run', and 'task' for related concepts, keep it from a perfect score.
Tool Count3/5
20 tools is heavy for the apparent scope, and roughly a third of them (spawn_agent, send_message, wait_for_idle, get_agent_status, list_agents, kill_agent, reject_action, list_pending_actions) are deprecated legacy duplicates or aliases rather than new capability. The set would be better scoped near a dozen tools without the legacy tail.
Completeness3/5
The goal-to-run-to-task-to-evidence lifecycle, cancellation, approvals listing, model discovery, skills, and usage accounting are covered. However, the approval workflow is one-sided: there is get_pending_approvals and reject_approval but no tool to approve an action, which is a hard dead end under CHAT_APPROVAL mode, and there is no retry/resume for a failed task.
Maintenance
ActivityMaintained
ResponsivenessResponsive