agent-duet
Related Servers
Alternatives to agent-duet
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables Codex to delegate implementation, independent review, rework, and acceptance tasks to Claude Code via local terminal or optional Orca sessions, tracking progress and verifying changes before merge.185 npm6MIT
- AlicenseNot gradedqualityBmaintenanceOrchestrates Claude Code and OpenAI Codex to plan, implement, review, and verify code changes via pull requests with security controls.1MIT
- AlicenseNot gradedqualityBmaintenanceTurns Claude Code into an engineering project manager by orchestrating feature development with isolated Git worktrees, structured task validation, and approval-gated integration.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables delegating bounded tasks from Codex to Claude Code, including read-only reviews, isolated branch edits, long-running background work, and approval handling.185 npmMIT
- AlicenseAqualityAmaintenanceEnables a two-model AI coding workflow inside Claude Code, where one model plans and reviews while a second model writes code, with test verification, automatic rollback, and learned improvements.101MIT
- AlicenseBqualityBmaintenanceRuns headless claude, codex and grok processes as one team from whichever of the three CLIs you work in, letting your session delegate work to other engines in their own sandboxes with modes that assign planner, reviewer, implementer and resolver roles and enforce git merge guards.13MIT
TDQS
Scored across 5 tools
Each tool maps to a distinct lifecycle stage (start, status, wait, cancel, finalize). The only mild overlap is duet_wait vs duet_status, since both return status, but the descriptions clearly distinguish waiting-for-phase-change from a plain status read.
All five tools use the same duet_ prefix followed by a concise verb (start, status, wait, cancel, finalize) in consistent snake_case. The pattern is predictable and readable.
Five tools cleanly cover an orchestration lifecycle without redundancy. Each tool earns its place and nothing feels padded or missing for the stated scope.
The surface covers the full run lifecycle: start, poll status, wait for phase change, cancel, and finalize/publish. Nothing essential (create, monitor, abort, commit) is missing for a single-run orchestration model.