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.5 npm1AGPL 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.13 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.13 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.883 npmMIT
- 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 8 tools
Most tools target distinct objects: handoff_send creates a request for the user's agent, handoff_list/handoff_read inspect desk items, handoff_wait polls one item, and handoff_inbox/handoff_inbox_reply handle the reverse direction. The only soft overlap is handoff_send vs handoff_status (both write to the desk), but the descriptions clearly separate errands/questions from one-line status lines.
All names share the handoff_ prefix and snake_case, which is helpful, but the verb convention is mixed: send/list/read/wait are verbs while status, capabilities, inbox are nouns and inbox_reply is noun+verb. It remains readable, but there is no predictable verb_noun pattern to infer new tools from.
Eight tools is well within a comfortable range and each covers a distinct step of the handoff loop: create, poll, inspect, enumerate, plus policy lookup and inbox exchange. Nothing appears redundant or padded.
The round trip is covered end to end: send a request, wait for the reply, read the content, and answer notes the other agent left, with a capabilities lookup for policy. The gap is lifecycle mutation — there is no tool to cancel, withdraw, or close a desk item or to dismiss an inbox note, so an abandoned request can only be left waiting.