handoff-desk
Related Servers
Alternatives to handoff-desk
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents on the same machine to exchange asynchronous messages as plain Markdown files, with optional wake-up notifications per agent.1AGPL 3.0
- AlicenseAqualityCmaintenanceEnables a planning Claude chat and Claude Code to exchange work through local Markdown files, letting the chat create tasks that code agents pick up, complete, and report back on. Project-scoped task and report tools track each item's status from open through reported, eliminating manual copy-paste between the two clients.5MIT
- AlicenseNot gradedqualityAmaintenanceGives AI coding agents persistent cross-session memory by storing atomic markdown knowledge cards with bidirectional wiki-links that agents recall before starting work. Syncs across clients and devices via git without any vector database or embeddings.9 npmISC
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to save insights from completed tasks as atomic markdown knowledge cards with bidirectional links, then recall relevant cards before starting new work so context carries across sessions. Cards live in a shared local directory readable and editable by humans, with optional git-based sync across devices and clients, and no vector database or embeddings required.9 npmISC
- AlicenseNot gradedqualityCmaintenanceEnables local coding agents to track sessions, exchange isolated collaboration messages, and optionally delegate coding work to Codex with Git worktree isolation and task management.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to file and track issues, plan epics with steps, comment as they work, and hand decisions back to the user through a local Markdown- and YAML-backed issue tracker.MIT
TDQS
Scored across 10 tools
Several pairs have blurry boundaries: handoff_pending vs handoff_list (both enumerate desk items, one filtered by 'waiting'), handoff_send vs handoff_status (status is essentially a lightweight send), and handoff_answer vs handoff_inbox_reply (two reply tools that differ only by direction). The descriptions do explicitly note which role calls what ('a sender never calls this'), which rescues the set, but the dual-role sender/answerer split plus inbox-vs-pending directionality requires careful reading before an agent picks correctly.
All ten tools share the handoff_ prefix and consistent snake_case, so the family is immediately recognizable. The only wobble is grammatical form: mostly verbs (send, answer, list, read, wait) mixed with nouns/adjectives (status, pending, capabilities, inbox) and one reversed compound (handoff_inbox_reply).
Ten tools is well within a comfortable range for a two-party handoff protocol, and each maps to a real step (send, list, read, wait, answer, status, capabilities, inbox lifecycle). A couple are thin — handoff_status is nearly a special case of handoff_send, and handoff_pending largely duplicates a filtered handoff_list — but nothing is gratuitous.
The core lifecycle is covered end to end: compose, list, read, poll for reply, answer, plus the auxiliary inbox and capability-rules surfaces. The notable gap is no cancel/withdraw/delete for a sent note and no search across items, so a request sent in error or an obsolete item has no cleanup path.