Engineer's hands-on with Dot agent: wrong job for web automation, right job as ops assistant
Jhon_ST · reddit · 2026-10-02
- An engineer evaluated Dot (a persistent agent) for growth/social workflows: researching opportunities, monitoring channels, handling distribution busywork.
- The bottleneck was the execution environment, not reasoning: workflows depended on arbitrary sites, signed-in sessions, and platform rules; a cloud-browser 502 on Medium killed the run.
- His existing local stack (Codex + APIs + scripts + scheduler + authenticated browser) was more controllable and debuggable; maintaining Dot's extra connections wasn't worth it, so he dropped that use case.
- Better fit: a persistent personal ops assistant — a morning briefing aggregating email, tickets, PRs, and calendar, running in the cloud independent of his laptop.
- Takeaway for agent evals: decide between cloud agent vs local automation based on execution-environment dependencies first.
More from coding & agent
- Dev Has Claude Build a Custom Jump Animation Editor to Speed Up Game Feel Iteration — andrew_n_carr · 2026-10-02
- Translating an entire book with DeepSeek: pennies and under an hour, decent quality — teortaxesTex · 2026-10-02
- OmniSeek turns Omni-LLMs into agents that actively seek audio-visual evidence — Haibo Wang · 2026-10-02
- Microsoft's ActiveSaddler Uses Automated Curriculum Learning to Boost Agent Harnesses by 7.5 Points — microsoft · 2026-10-02
- Alibaba's PoS Maintains Explicit Belief States to Fix Long-Horizon Agent 'Belief Trapping' — alibabagroup · 2026-10-02
- IntentFlux Benchmarks 'Intent Drift' in LLM Agents: Scores Fall from 0.476 to 0.384 as Users Change Their Minds — Yanjie Zhang · 2026-10-02