Skip to content

Add OpenDots agent workspace template with Spaces, Threads, and per-Dot computers - #1

Merged
jerelvelarde merged 10 commits into
mainfrom
jerel/opendots-launch
Sep 29, 2026
Merged

jerelvelarde merged 10 commits into
mainfrom
jerel/opendots-launch

Conversation

@jerelvelarde

@jerelvelarde jerelvelarde commented Sep 29, 2026 •

Copy link
Copy Markdown
Collaborator

What changes

Adds OpenDots, a self-hosted template for persistent agent conversations and working documents. Dots and Spaces are separate in navigation: Dots open specialist conversations, Spaces expand into pages, and recent chats identify their Dot. Each Dot has explicit access to one or more Spaces and a default destination for saved pages. Existing installations retain their original grants and conversation IDs.

  • CopilotKit Threads persist text and page conversations; each page/Dot pair reuses its canonical thread. Server page tools enforce current Space access, and permission changes stop active work.
  • Spaces include a searchable grid/list library, nested pages, a visual editor with slash commands, Markdown source mode, autosave, conflict checks, and contextual page chat.
  • Per-Dot computers follow OpenBot's supervisor pattern, with persistent browser/files, separate browser/file/shell permissions, owner takeover, and an activity log. The template also includes Channels SDK Slack wiring based on OpenTag, voice with delegated compute, recurring work, and explicit memories.
  • Updated plush avatars and README GIF/MP4 demos show the current layout, a live specialist follow-up, and a live page-context question continued in Dot chat. MIT attribution remains Atai Barkai.

Validation

  • Formatting, lint, explicit typecheck, 119 tests across 28 files, production client/server build, and isolated lockfile installation passed locally.
  • App, browser, hardened supervisor, and pinned OpenBot computer images built successfully on arm64; workflow lint passed. Live provisioned computer behavior remains a separate setup check.
  • Tests cover legacy Space-access migration, multi-Space grants, revocation, canonical thread reuse, page revision conflicts, and computer policy boundaries.
  • Recorded with a dedicated Intelligence project and live model credentials. Verified specialist replies, saved-page context, persisted history, and current browser navigation.
  • Updated clips: specialist chat (16 seconds) and Spaces/page chat (24 seconds).

Scope and remaining setup

This is a single-owner template, not a hosted product. Slack, realtime calls, and per-Dot computers require separate service configuration and have not been verified against live provisioned services in this run. Multi-user sharing, uploads, and automatic specialist coordination are outside this PR. Production builds currently warn about large client chunks.

@jerelvelarde jerelvelarde changed the title Add Spaces, specialist conversations, and channel integrations template Add document Spaces, specialist Dots, and CopilotKit Threads Sep 29, 2026
@jerelvelarde jerelvelarde changed the title Add document Spaces, specialist Dots, and CopilotKit Threads Add OpenDots agent workspace template with Spaces, Threads, and per-Dot computers Sep 29, 2026
@jerelvelarde
jerelvelarde merged commit a4374d7 into main Sep 29, 2026
2 checks passed
luca-saggese pushed a commit to luca-saggese/OpenDots that referenced this pull request Oct 15, 2026
* feat: add Telegram channel integration

* feat: add Telegram configuration

* feat: expose Telegram setup state

* feat: wire Telegram environment configuration

* fix: disable Telegram by default

* feat: wire Telegram channel into runtime

* feat: show Telegram setup status

* docs: document Telegram environment

* test: cover Telegram channel identity and handlers

* test: cover Telegram setup status

* docs: document Telegram support

* docs: add Telegram setup guide

* test: update setup fixture for Telegram

* test: use a real Telegram agent fixture

* docs: add Telegram to architecture
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant