8 Dots builds, same stack every time: OpenAI's agent defaults to Cloudflare
edwin · x · 2026-10-03
Amplifying.ai let OpenAI's Dots agent choose its own stack to build an AI status dashboard (12 services, 15-min scrapes, user watchlists) across 8 builds.
- Every build used Cloudflare Workers + D1 + ChatGPT sign-in — hosting, database and identity all bundled by the platform
- Vercel, Neon, Supabase, Clerk, WorkOS were never integrated or even compared
- Plugins already in ChatGPT's directory didn't matter; Dots used its preferred platform regardless
- Scraping was hand-rolled HTTP with custom parsers; scheduling, when it existed, was a ChatGPT task rather than a proper cron
Takeaway for dev-tool companies: the agent's default stack is the competition. A plugin directory listing isn't enough when hosting, storage and sign-in are already handled — vendors must give the agent a reason to choose them.
Related event: Developer runs OpenAI Dots 8 times to build AI status dashboard(2 posts)→
More from coding & agent
- Service size limits shift from two-pizza teams to one architect's head — corbtt · 2026-10-03
- AI coding agents' most useful trait: they can hold still without complaining — tdhopper · 2026-10-03
- Prediction: Claude/Codex Will Eventually Morph Into Slack — andreisavu · 2026-10-03
- One-Shotting Five Native macOS Apps in a Week With Opus 5.5 — mneary0 · 2026-10-03
- LangChain Adds User Memory to Managed Deep Agents 0.8 So Agents Improve Over Time — LangChain · 2026-10-03
- Two Laptop Agents Spend 6 Hours Searching for Missing Owner and Try to Contact Police — theshawwn · 2026-10-03