other / agent

OpenDots

An open-source template for persistent AI agents called Dots, with text chat, calls, Slack, saved pages and an optional computer for each agent.

At a glance

Purpose
An open-source template for persistent AI agents called Dots, with text chat, calls, Slack, saved pages and an optional computer for each agent.
Runs in
Web service
Operating systems
Not stated
Needs
Runtime: Node.js 24 and npm; Needs internet: Yes; Needs accounts or API keys beyond your agent: Yes
Files and data
Reads files: Yes; Writes files: Yes; Sends data to other services: Yes
Tool type
Agent
Delivery
From GitHub
Version
Latest on the main branch
Access
Code on GitHub
Compatibility
According to the README: Node.js 24 with npm, opened in a web browser. The README header says it is available on web and mobile, but its setup steps describe the web app. The README describes an OpenAI-compatible model provider through TanStack AI, CopilotKit Intelligence for conversation threads, MCP servers, Slack through Channels SDK, a speech provider for calls, and OpenBot services for Dot computers. Docker is named for the local Intelligence evaluation and for separate application and browser containers. The README names no operating systems.
External costs
According to the README, conversations require CopilotKit Intelligence, which you can use as a hosted service, as a local Docker evaluation or as a licensed self-hosted deployment. The README gives no prices for CopilotKit Intelligence. You also add an OpenAI API key and model name, and calls need a speech provider. Public-web research uses Parallel by default. The README says the anonymous service is free for light use with provider-managed limits and that PARALLEL_API_KEY is for production or higher limits. The providers you connect may charge for usage.
Permissions
The README shows npm dependency installation and CopilotKit project selection that writes an Intelligence key to .env, followed by the user's model API key and model name. The README says research, memory, browser, file and shell permissions are configured per Dot. The README describes optional OpenBot computers with persistent browser profiles and workspace files. The README says read-only MCP tools run directly and other MCP tools require an Approve & run card. The README describes requested draft approval before page creation. The README says scheduled server-side turns run in their original conversation and Slack uses managed connections with workspace and user allowlists. The README says public-web research uses Parallel by default; WEB_SEARCH_PROVIDER=browser selects the URL-only reader and WEB_SEARCH_PROVIDER=disabled disables those tools. The README says service credentials stay on the server.
Usage terms
MIT License, as stated in the repository. See its LICENSE file for the exact terms.
Interface
web

Code on GitHub

CopilotKit/OpenDots

MIT

TypeScript5,072 stars714 forksLast pushed 12 Oct 2026 UTC

Your always-on AI coworkers that move between text, calls, and Slack.

Public GitHub data fetched · 0 days old

View on GitHub ↗

What it does

The README describes OpenDots as an open-source template for persistent AI agents called Dots that users host and customize. The README labels it alpha and a starting point built with CopilotKit and AG-UI.

The README describes Spaces, editable pages and Dots configured with roles, instructions and permitted tools. The README says calls need a speech provider and Slack uses a managed Channels SDK connection. The README describes optional per-Dot computers using OpenBot services for browser, file and terminal access.

The README describes draft approval before page creation and per-Dot MCP tools with approval for non-read-only actions. The README lists scheduled work, memory, themes and Automatic Learning, and says shared editing, invitations, file uploads and interactive page embeds are not included.

Who it is for

Developers who want a template to adapt into their own workspace of persistent AI agents.

Example tasks

Create a Space and write a page in the visual editor before connecting any service.
Define a specialist Dot with a name, role, instructions and permitted tools.
Ask a Dot to show a draft, then approve or decline saving it as a page.
Give a Dot tools from an MCP server and approve non-read-only actions in chat.
Mention a Dot in Slack after you connect a managed Slack connection.

Getting started

The README uses Node.js 24 and npm. Clone the repository, then run npm ci, cp .env.example .env and npm run dev, and open the local address the README gives. You can write pages and configure Dots at this point. To chat, connect an Intelligence project and a model. For hosted Intelligence the README runs npx copilotkit@latest login and npx copilotkit@latest project select, which writes a project key to .env. Then add OPENAI_API_KEY and OPENAI_MODEL to .env and restart npm run dev. The README says not to run copilotkit onboard in this folder. It also covers a local Docker Intelligence evaluation, Slack, calls and the browser service in its Setup guide. The README has the exact commands.

Limitations

The README requires Node.js 24 and npm, and says conversation services need CopilotKit Intelligence and a model. The README describes hosted Intelligence, local Docker evaluation and licensed self-hosting; installing or renewing local Intelligence still needs CopilotKit sign-in and internet access. The README says calls need a speech provider and Dot computers need configured OpenBot services. The README labels the template alpha and a single-owner starting point. The README says Slack, spoken compute delegation and parts of Automatic Learning still need connected-service verification. The README says Automatic Learning skills require review and publication in Intelligence and older conversations without a container are not enrolled retroactively. The README warns that interrupted schedules require explicit retry and completed effects may already exist. The README says shared editing, invitations, file uploads, interactive embeds, multi-Dot group conversations and automatic delegation are not included, and schedules are recurring instructions rather than a goal or event-trigger system. The repository can change at any time; check its README before you install.

Data practices

The README says configured CopilotKit Intelligence stores conversation messages, tool calls and run events, with hosted setup sending them to CopilotKit's cloud and local evaluation using Intelligence on the user's machine. The README says SQLite separately stores pages, workspace metadata and thread bindings. The README says the model receives conversation context, authorized page content and tool results, and speech and messaging providers receive data when used. The README says default Parallel research sends queries, requested URLs, a stable session identifier and a research objective that may include conversation context. The README gives WEB_SEARCH_PROVIDER=browser for the URL-only browser reader and WEB_SEARCH_PROVIDER=disabled to disable research tools. The README says SDK telemetry collects usage metadata and OpenDots records bounded browser setup stages and first successful assistant activation with a random installation ID. The README says CPK_TELEMETRY_ID associates SDK usage with the Intelligence account. The README gives COPILOTKIT_TELEMETRY_DISABLED=true or DO_NOT_TRACK=1 to opt out, also disabling setup tracking and purging pending setup events.

Community experience

Not rated yet

Sign in to share your experience.

Comments 0

No comments yet.

Sign in to comment

Report a listing concern