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: Testing OpenAI Dots: It Defaults to Cloudflare Stack Every Time(3 posts)→
More from coding & agent
- Dev shares NL-driven testing UI: 'the best interface is chat' — KlausCodes · 2026-11-19
- Devs flag GPT's defensive programming for hiding bugs; OpenAI asks for /feedback cases — pvncher · 2026-11-19
- Flutter ships A2UI 1.0: agents respond with real interactive widgets, not chat text — rseroter · 2026-11-19
- Skills vs MCP vs RAG vs Memory: the four context mechanisms AI agents actually need — MaryamMiradi · 2026-11-19
- Anthropic details agent memory: 'dreaming' lets Claude organize its experience — daniel_mac8 · 2026-11-19
- The case for externalized memory as the real fix for continual learning — daniel_mac8 · 2026-11-19