Doubao Desktop
Related Servers
Alternatives to Doubao Desktop
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables Doubao Work to submit, monitor, resume, and independently verify coding tasks that a local Codex app-server executes in persistent project sessions, with SQLite-backed task state and artifacts retained on the user's machine.1MIT
- AlicenseNot gradedqualityBmaintenanceLets Codex delegate tasks to a running DeepSeek Harness Desktop instance on Windows over authenticated named pipes, with asynchronous dispatch, event waiting, cancellation, and explicit resume. Also supports blocking structured questions tied to a task, plan checkpoints before writes, independent stage review with rework in the same session, and output fingerprinting that invalidates stale approvals when files change.426 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables Codex to delegate tasks to a visible DeepSeek Harness desktop session by opening it, sending or resuming tasks, and returning results while exposing connection and busy status.MIT
- AlicenseNot gradedqualityBmaintenanceEnables other agents to list, read, start, and steer Codex chats in the macOS ChatGPT desktop app, including sending follow-ups, choosing model/reasoning/speed, interrupting work, and answering approvals. It can run locally or behind bearer-token-protected tunnels for remote monitoring and control.50 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables Codex to bind aliases to specific Kimi Code and ZCode desktop chat sessions, send tasks to them, and collect acknowledgements and results through a local SQLite mailbox. It also supports background wake delivery and optional background computer control via Cua Driver, keeping messages pinned to a session and binding revision.MIT
- AlicenseAqualityCmaintenanceEnables Codex to control a local Brave or Chrome browser via CDP, observing pages and performing actions such as clicking, typing, selecting, scrolling, or waiting through validated action IDs without requiring a model API key.7MIT
TDQS
Scored across 6 tools
Each tool targets a distinct action: create_task vs continue_task are clearly separated (new vs follow-up), read vs sessions separate message reading from conversation listing, and wait vs status separate run-waiting from endpoint checking. Descriptions explicitly call out these boundaries, so an agent can reliably pick the right tool.
All tools share the consistent doubao_desktop_ prefix and mostly use a verb_noun or action pattern (create_task, continue_task). Minor deviation: read, status, and sessions are bare nouns rather than verb_noun forms, but the set is still predictable and readable.
Six tools is well-scoped for a desktop-conversation automation server, with each tool (submit, follow up, wait, read, list, health-check) earning its place. No bloat or obvious redundancy.
Core lifecycle (submit -> wait -> read) plus session listing and status is covered, but there is no way to cancel/stop an in-flight run, close or delete a conversation, or perform the 'independent artifact review' the descriptions repeatedly reference. These gaps are notable though agents can partially work around them.