Is dots broken for others too or a small percentage have issue using it?
Users are reporting issues with Dots' cloud computer, specifically encountering 403 Forbidden errors when trying to access various websites. This limitation prevents tasks like logging into Cloudflare to set up email routes. There's a concern that Dots' context memory has become fragmented, leading to a perceived decline in its proactive capabilities, reminiscent of bugs observed during its dev day announcement.
时间与来源
时间显示为 UTC
显示时区：UTC
本地时区尚不可用，暂时显示 UTC。
发布当时偏移：UTC+02026年10月10日 09:46 UTC
收录当时偏移：UTC+02026年10月10日 11:00 UTC
- 发布
- 2026年10月10日 09:46
- 收录
- 2026年10月10日 11:00
- 来源类型
- 开发者社区
- 档位
- 社区
- 信源状态
- 正常
档位是按信源手工设定的编辑判断，不是逐条打分。
I’m genuinely asking: browser use isn’t working well on Dots’ cloud computer. Every website I’m interested in using returns a 403 (Forbidden) error when accessed from Dots’ cloud. For example, I couldn’t log in to Cloudflare to set up an email route to my home computer, where I could host a mail server and essentially replicate Grokbot’s email feature, which just shows how limitted the cloud computer is (to be fair everything was blocked on Grokbot's cloud computer when I last used it, but there I could ask it to setup a vpn to my own pc).
When using my connected Windows PC, it feels handicapped when trying to do anything. Browser access crashes, as apparently reported here. Many actions on my PC also require my input for example, every script seems to require elevated access, which shouldn’t be necessary for something as simple as dir.
So, basically, what is the reason for using Dots? I could open a separate agent task that isn’t as buggy and has better access. Or are my expectations for what it can handle simply too high?
Above all, the initial hype around it doing things was genuine. Its context was highly limited to the single workflow we had started prompting it with, and everyone kept emphasizing how “proactive” it was. Now, after a couple of weeks, its context memory has inevitably become fragmented, and it just feels lazy. (Thinking twice it is the same bug they had on dev day announcement. and it is very likely they forgot to restart its context and later on their separate recording when it succeeded it was a fresh dots)