perch-agent
Related Servers
Alternatives to perch-agent
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceLets orchestrators like Claude Code and opencode hand off coding tasks to an autonomous Perch AI worker that does the work and returns verifiable evidence. Supports async job handoff with status polling and cancellation, thread continuation, model pinning, and built-in discipline guidelines for minimal, verified changes.4MIT
- AlicenseNot gradedqualityBmaintenanceEnables delegating bounded tasks from Codex to Claude Code, including read-only reviews, isolated branch edits, long-running background work, and approval handling.353 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables an assistant to run pi coding-agent tasks in the background: dispatching a task, polling its status and tool trace, reading the final result, and cancelling it when no longer needed, all without pulling the delegate's context into its own conversation.MIT
- AlicenseNot gradedqualityCmaintenanceLets an agent delegate coding tasks and reviews to Claude Code, Codex or Grok Build CLIs running locally in isolated git worktrees, then poll an inbox for the status, question or final answer. Each caller sees only its own threads.21 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code, Codex, and Cursor to delegate self-contained coding tasks to one another on the user's own subscriptions, with each task isolated in a git worktree and sandbox, usage tracked, budgets enforced, and results returned for review.438 npm2Apache 2.0
- AlicenseAqualityBmaintenanceEnables Claude Code to delegate tasks to OpenCode subagents asynchronously, with tools for starting tasks, polling status, and fetching results.7111 npm5MIT
TDQS
Scored across 4 tools
Each tool maps to a distinct operation: delegate, poll a job, cancel a job, and a local readiness check. The only potential confusion is between perch_job_status (job result by job_id) and perch_status (free local CLI/sign-in plus job list), but the descriptions explicitly separate these and note the 'no model call' distinction.
All names are snake_case and prefixed around 'perch', which helps grouping, but the structural patterns vary: delegate_to_perch (verb_prep_noun), perch_job_status (noun_noun), perch_job_cancel (noun_verb), perch_status (noun_noun). The verb position shifting between prefix, suffix, and infix makes the set less predictable than a uniform verb_noun scheme.
Four tools is a tight, well-scoped surface for an async delegation server: dispatch, check, cancel, and readiness. Nothing appears extraneous, and the job-list functionality is folded into perch_status rather than adding a fifth tool.
The async lifecycle (delegate → poll → cancel) plus a pre-flight readiness check is fully covered. Minor gaps remain: the delegate response returns a thread id but there is no tool to resume/follow up on an existing thread, and no way to stream or fetch intermediate logs for a long-running job.