t3_openbot
Related Servers
Alternatives to t3_openbot
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables Claude Code to delegate software-engineering tasks to OpenCode agents working in the same workspace.727 npm1MIT
- AlicenseAqualityCmaintenanceEnables Codex/ChatGPT to coordinate OpenCode agents, managing tasks, sessions, parallel execution, and project context through 25 local tools.254 npm1MIT
- AlicenseAqualityDmaintenanceLets Claude Code delegate coding tasks to external models running on a local opencode serve, preserving main agent tokens for planning and review.81MIT
- AlicenseBqualityBmaintenanceLets a coding agent delegate planning, coding, review, and research tasks to other headless coding agents on the machine, returning concise summaries and keeping code changes isolated until approved.15MIT
- AlicenseAqualityBmaintenanceEnables Claude Code to delegate tasks to OpenCode subagents asynchronously, with tools for starting tasks, polling status, and fetching results.7288 npm6MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to explore, search, and reference code implementation details across different project repositories. It also supports a task delegation protocol for agents to request and track work between separate codebases.MIT
TDQS
Scored across 6 tools
Most tools have clearly distinct purposes: status vs. listing agents vs. sending messages vs. handling pending questions. The only mild overlap is send_message and run_routine, both of which initiate work, but their descriptions distinguish agent-directed work from existing routines.
Five tools follow a clear verb_noun pattern (list_agents, send_message, run_routine, list_pending, answer_prompt). openbot_status is a minor deviation using a noun-prefixed status form, but it remains readable and predictable.
Six tools is well-scoped for a focused OpenBot connector. Each tool maps to a distinct operation with no obvious redundancy.
The set covers the core lifecycle: check status, list agents, dispatch work, run routines, inspect pending requests, and answer questions. Approvals and browser takeovers are intentionally handled outside the connector, and there is no cancel/stop operation, but these are minor gaps for the stated purpose.