Codex Asks Developers What's Holding Them Back
In a high-engagement X post, Tibo Sottiaux asks people who have considered Codex but never tried it to name the blocker. The question generated 428 likes, 18 reposts, 376 replies, and 34,458 views, turning a product pitch into a public adoption pulse.
The interesting issue is not whether Codex can code, but why awareness has not converted into first use. Codex’s breadth is now both its advantage and a potential onboarding liability.
- –Codex spans ChatGPT, editors, terminals, cloud environments, worktrees, skills, and scheduled background tasks, leaving newcomers unsure where to start
- –Pricing is less likely to be the universal blocker now that Codex is included across ChatGPT plans, though usage limits vary
- –Developers already have established IDE, CLI, and incumbent-agent workflows, making switching costs significant
- –The 376 replies give OpenAI valuable customer research; converting those objections into simpler first-run experiences could matter more than another capability announcement
DISCOVERED
6d ago
2026-09-01
PUBLISHED
6d ago
2026-09-01
RELEVANCE
AUTHOR
thsottiaux