StackMap
Subscribe

OpenDots vs OpenDuet

CopilotKit template for always-on AI coworkers ('Dots'): each gets a role, tools and its own computer, works in chat, calls and Slack, and saves approved drafts into editable Spaces. — versus — Proactive self-hosted AI assistant template on CopilotKit's OpenBot: morning briefs from mail, calendar and Slack, keeps working on its own computer, asks before sending, paying or deleting.

The curated verdict

Sibling CopilotKit templates on the same OpenBot runtime; Dots are role-based coworkers, OpenDuet is one proactive personal assistant.

OpenDotsOpenDuet
Stars6.7k2.1k
Forks982293
LanguageTypeScriptTypeScript
LicenseMITMIT
Last activityyesterday5 days ago
Topicsagents, orchestrationagents
Curated connections63

OpenDots — the curator's take

Use it as a starting point for a self-hosted agent workspace where specialist agents share a document library with humans — per-Dot permissions, approve-before-run cards for MCP tools, and an optional persistent browser/terminal per Dot. NOT a hosted product or a plain library: alpha, you run the infrastructure, and conversations need CopilotKit Intelligence (hosted, local Docker eval, or a licensed self-host) — a real dependency to weigh. Want only the governed computer per agent? Take OpenBot.

OpenDuet — the curator's take

Fork it for a proactive personal agent that triages your day and acts with explicit approval gates. It's a community-maintained skin over OpenBot and needs a CopilotKit Intelligence project for threads and memory — for a company rollout, go straight to OpenBot, which has sign-in, per-bot permissions and audit trails.