Unpacking ChatGPT Work: the Agent for a Billion Users
- ID
- 10812
- Status
- summarized
- Published
- 05 Aug 2026, 2:20 AM
- Fetched
- 05 Aug 2026, 2:58 AM
- Provider
- Latent Space
- Category
- developer-ai
- Original URL
- https://www.latent.space/p/unpacking-chatgpt-work
- Source URL
- https://www.latent.space/feed
Summary
- Score
- 8.0
- Created
- 07 Aug 2026, 1:32 PM
- Tags
- Audience
- developersvibe_codersai_ml_learnersai_agent_userssaas_startup_founders
What happened
OpenAI released ChatGPT Work on July 9th, 2026 as an agent for knowledge work that connects to Slack, email, Drive, CRMs, and hundreds of plugins, running on the Codex harness inside a cloud computer. It reportedly crossed 10 million users in three weeks, and Greg Brockman confirmed Work and Chat modes will merge by end of year—making Work a preview of how ChatGPT's ~1B weekly users will soon interact with the product. The article is an external reconstruction of Work's architecture: Memory, Proactivity, Scheduling, Browser Use, Plugins, Skills, and Tools, with the author poking around inside the product to reverse-engineer its design choices and tensions.
Why it matters
If Work and Chat merge by year-end, every ChatGPT user becomes an agent user by default—builders shipping AI agents or SaaS integrations should evaluate whether their product survives as a plugin/skill inside Work or gets disintermediated by it. The detail that Work runs on the Codex harness with sub-agents and browser use means the same agent infrastructure powering coding agents is now the substrate for general knowledge work, so tooling and integration patterns from Codex carry over directly.
Discussion angle
Which of your current SaaS workflows would survive being absorbed into a Work-style agent that already connects to Slack, Drive, and CRMs—and which integrations should you build now to ride that wave instead of being replaced by it?