OpenAI dots Reddit reactions: price, access and clones
Early dots complaints focus on price, Europe and desktop setup. Open Dots and OpenDots have similar names, but their runtimes and missing features differ.
OpenAI dots Reddit complaints start with getting access, before judging the agent. One thread is titled “Barrier to entry with dots is kinda absurd”.
That thread compares the personal ChatGPT Pro entry price with cheaper competing agents. Other users focus on Europe and the need to start setup on a desktop.
Dots launched on September 29, 2026. As of September 30, its first 48 hours are still unfolding, and two public clone repositories are already available to inspect. These early conversations tell you what people are questioning; they can't settle long-term reliability.
The OpenAI dots Reddit price argument starts at $100
In the pricing thread, InspectorSebSimp compares dots' personal entry price with Muse's free access and Grok Bot's cheaper starting subscription. That's a fair entry-cost comparison, even though the subscriptions include more than their agents.
The discussion also muddles which Pro tier qualifies. OpenAI lists Pro 100, Pro 200 and Pro 500 at $100, $200 and $500 per month. The cheapest personal route is $100, not $200.
If you already have an eligible subscription, your incremental cost differs from someone subscribing solely to try dots. Keep that distinction in view when comparing the plans' entry prices.
In the r/codex DevDay announcements thread, MedicalTear0 dismisses dots as underwhelming. Other participants want attention paid to coding plans and access. A persistent personal agent isn't necessarily what a coding-focused forum came to DevDay for.
Neither thread is a representative survey. They give you objections and misunderstandings to examine, without establishing that most users dislike dots or that the product has failed.
The Europe complaint needs a plan name attached
European users complain in the same announcements thread, with replies distinguishing personal and business access. OpenAI's eligibility rules support that distinction.
Personal Pro access excludes the European Economic Area, Switzerland and the UK. Business Premium is rolling out worldwide, and Enterprise access is worldwide with administrator enablement. You can qualify through an enabled workspace while a personal Pro subscriber in the same country can't.
The personal exclusion is real, but “Nobody in Europe can use dots” gets the rules wrong. The announcement doesn't give a definitive legal reason for the exclusion either. Regulation theories in a comment thread remain speculation.
Availability changes what you can judge. Locked-out readers are assessing a promise and a price; people with access can inspect the agent's behavior. Both perspectives are useful, but they answer different questions.
Creating a dot still needs a desktop
Simon Willison tried to create a dot on his phone and was asked to switch to a desktop, according to his DevDay live blog. He was disappointed by the interruption.
The help page confirms the restriction: setup needs a desktop app or browser, while mobile creation and mobile web are unsupported. Mobile app use needs a supporting update. Willison had run into a documented product limit.
He also recorded slow behavior during the live voice demonstration. One stage event can't measure normal response time or completion rates. The useful follow-up is a repeatable task on an ordinary connection.
Launch marketing leaves you to close that gap. An always-available agent can still come with an inconvenient first setup, account restrictions and tasks that need your intervention. Those details decide whether it fits your routine.
Open Dots and OpenDots are different projects
Two repositories use nearly identical names: Anil-matcha/open-dots and diggerhq/opendots. Check the owner and README before treating them as the same project or a drop-in replacement for dots.
| Detail | Open Dots | OpenDots |
|---|---|---|
| Repository owner | Anil-matcha | diggerhq |
| License | MIT | MIT |
| Main shape | Self-hosted web workspace with approval controls | Always-on agent preview using OpenComputer |
| Execution setup | Optional Docker browser or remote computer | Agents run on OpenComputer |
| Model configuration | Prediction-style adapter, not generic Chat Completions | OpenComputer model routes in agent definitions |
| Important limit | README lists no durable memory service or scheduled routine engine | Local app hosting still requires the managed agent platform |
The names suggest the same product category. The runtimes show different starting points, and neither README establishes parity with dots.
Open Dots lacks a durable memory service
Anil-matcha's project combines a web workspace, Python backend, local SQLite storage and an approval gateway. Its README describes encrypted provider credentials and narrowly scoped GitHub actions through Composio.
The default development setup uses a fake computer. You can choose an optional Docker browser or remote computer instead.
The README warns that its Docker setup isn't a hardened sandbox for hostile web content. “Runs in Docker” doesn't establish safe unattended browsing.
The missing-feature list includes mobile and desktop clients, a durable memory service and a scheduled routine engine. The project's own description rules out calling it a complete always-on replacement.
Read the model adapter carefully. It sends prediction-style requests on a model-specific path, with a separate image-upload route. The README explicitly says it isn't a generic OpenAI-compatible Chat Completions adapter.
A field named base URL doesn't mean you can insert any compatible provider. The README's specifics let you judge whether the workspace and approval controls suit a prototype, without assuming the whole agent system is there.
OpenDots runs its agents on OpenComputer
diggerhq describes OpenDots as an early preview built on OpenComputer Serverless Agents. It uses a coordinator and topic workers, with editable persistent notes. Topic workers can obtain a cloud computer when a task needs one.
You can deploy the web app locally or through several hosting options. The agents still run on OpenComputer, so self-hosting the app doesn't make the entire system local. Setup requires an OpenComputer account, and local development needs an HTTPS tunnel for the relevant callbacks.
The README shows model choices including an Anthropic route, connected Codex account models and OpenRouter routes. Selection involves changing the agent definition and deploying it. That's model choice, but it doesn't establish a generic custom OpenAI-compatible base URL setting.
If you want to inspect or adapt the orchestration, OpenDots is worth a look. Factor in the managed platform dependency, account requirements and applicable service terms. The repository doesn't justify a universal running-cost estimate.
The name travels faster than the evidence
The resemblance to earlier personal agents was visible immediately. Willison described dots as “very Muse-like,” and the clone names borrow OpenAI's new vocabulary directly.
That makes discovery easier and confusion more likely. Search for “open dots” and you can find a repository with different runtime assumptions, missing schedules or an adapter that doesn't match your API. Use the name as a search clue, then read the specification.
The useful questions in the early response are direct:
- What does access cost?
- Can I create one from my phone?
- Which environment holds my credentials?
- What keeps running after I close the app?
Those questions will still matter after launch-day excitement fades.
For dots, look next for repeatable user workflows and documented fixes to early problems. For the clones, look for implementations that match their stated boundaries. A public repository gives you code to inspect; trusting an unattended assistant with every account takes more evidence.
FAQ
What are people saying about dots on Reddit?
The linked threads focus on personal entry cost, regional access and coding users' priorities. They show examples of discussion, rather than a representative survey.
Are Open Dots and OpenDots the same GitHub project?
No. Anil-matcha/open-dots is a self-hosted workspace with documented missing features. diggerhq/opendots is an early agent preview that runs on OpenComputer.
Can I use any OpenAI-compatible key with these clones?
Neither README establishes that. Open Dots explicitly uses a different adapter; OpenDots documents platform model routes rather than a generic custom compatible base URL.
Why do dots ask me to switch to a desktop?
Setup needs a desktop app or desktop browser. OpenAI says mobile creation and mobile web are unsupported, while mobile app access needs a supporting update.