Open Dots is an open-source, self-hosted personal AI agent workspace for chat, tool use, approvals, connectors, and computer tasks. It brings model conversations, a governed action gateway, approval prompts, and an optional browser runtime into one local-first app. It can be evaluated by people searching for open-source alternatives to OpenAI Dots, Meta Muse, Grok Bot, Instinct, Manus Cue, Claude Cowork, or ChatGPT agent; it is an early prototype, not a feature-equivalent replacement for those products.
Open Dots is independently built and is not affiliated with or endorsed by OpenAI, xAI, or any model provider. It offers a self-hostable, inspectable alternative for people looking for an open-source OpenAI Dots alternative, with local data and explicit approval for higher-risk actions.
Status: Prototype / active development. Intended for local experimentation; multi-user hosting and hostile-web isolation are not production ready.
What it does
- Create assistant personas with separate instructions, model IDs, and visual identities.
- Stream chat responses, persist conversations locally, render Markdown, attach images, and dictate messages where the browser supports speech input.
- Connect to models through the included inference adapter and choose from its configured model catalog.
- Request confined workspace reads and writes or computer actions through a deny-by-default gateway. Higher-risk actions pause for approval and produce audit events.
- Connect apps through Composio, with explicit OAuth and narrow GitHub issue lookup/create actions.
- Search the web from chat with
/search <query>. It runs through the governed action gateway like the other tools, works with the keyless You.com free profile, and produces audit events. - Run an optional bot-scoped Docker/Playwright computer runtime or connect a compatible remote computer service.
- Keep application state in SQLite and encrypt provider credentials at rest.
Why Open Dots
Open Dots gives developers and individuals a self-hosted AI workspace they can inspect and adapt. It is an open-source alternative for people who want local-first conversation storage, configurable model access, visible approval steps, and an optional computer runtime under their control. It is a separate project with its own implementation and limitations; see the provider and runtime notes below before deploying it.
Quick start
Requirements
- Node.js and npm
- Python 3.10+ and pip
- An inference API key and base URL for live model responses
Clone and start the API:
git clone https://github.com/Anil-matcha/open-dots.git
cd open-dots/server
python -m venv .venv
source .venv/bin/activate
python -m pip install -r requirements.txt
export MODEL_API_KEY="your_api_key"
export MODEL_API_BASE_URL="https://your-inference-host.example/api/v1"
python run.py
The API is available at http://127.0.0.1:8000; interactive docs are at /docs.
In a second terminal, start the web client:
cd open-dots/client
npm install
npm run dev
Open http://127.0.0.1:3000 and sign in with the Open Dots owner token. On first start, the server creates .auth-token under DATA_DIR (default ~/.open-dots). Read that file locally and paste its value into the sign-in form, or use the value of APP_AUTH_TOKEN if you configured one. This is a separate credential from your model provider API key, which you enter in App Settings after signing in. Never commit, share, or put the owner token in a public frontend environment variable.
Browser sessions use distinct HttpOnly cookies with server-enforced expiry. Sign out revokes the current session, and restarting the API invalidates all browser sessions. Direct API clients can continue to send the owner token as a Bearer credential. Loopback requests, including container gateway and reverse-proxy traffic, must authenticate too.
No comments yet.