Key Takeaways
- OpenAI introduced ChatGPT Spaces at DevDay 2026 as a shared environment for documents, slides, and HTML artifacts where humans and software agents work together.
- Spaces allows users to @mention AI agents directly inside live documents to update project plans, build slide decks, and manage running task lists.
- During testing, Vo found that her autonomous agent, Dots, spun up a dedicated workspace called “your personal scratch pad” to organize joint tasks without manual prompting.
- Vo argues this release targets Google Workspace directly, pointing out that legacy productivity suites treated AI as a sidecar chat window rather than an active collaborator.
The Shift to Agent-Native Workspaces
Most software companies spent the last two years pasting a chatbot sidebar onto thirty-year-old word processors. You wrote text in a box, highlighted a sentence, opened a side panel, and asked an assistant to rewrite it. The document remained passive, and the human remained the sole editor.
OpenAI's announcement of ChatGPT Spaces at DevDay 2026 flips that dynamic. Spaces acts as an interactive canvas for docs, slide decks, and HTML code where AI agents hold the same permissions as your human teammates. As Claire Vo put it: “Space is a place in chat GBT where you can work on documents, artifacts, slides with humans and with agents. And I think this is what companies have been waiting for.”
Vo tested the product alongside OpenAI's new autonomous agent, Dots. During her demo, the agent took initiative on its own. “One of the things I love that my dot did one moment of delight that I didn't touch on in the overview before is it made a space for me called your personal scratch pad and it just created a space where my dot and I could just collaborate via dot on things we have to do,” Vo explained.
Instead of treating a document as an exportable text file, Spaces turns it into an active coordination board. You @mention an agent, the agent edits the canvas directly, and the state stays synchronized across your entire team.
Why Legacy Suites Are Losing the Workflow War
The design choice here is deliberate. Companies do not want another isolated chat history that disappears into a sidebar archive. They want a central place to store structured work with built-in data controls and native agent actions.
“We have been waiting for an AI native document slide HTML collaboration platform with all the right sharing built in with all the right data controls built in with all the like agent native kind of aspects of this built in,” Vo noted. “And again, what's nice about this is it's not just a doc. It is you have the ability to @mention your doc, @mention chat GBT, and get updates to the doc.”
This setup creates immediate friction for traditional workplace suites. Vo called the release “a little bit of shots fired on Google, which again is just watching this AI opportunity go by.” When your primary workspace lets autonomous bots build working HTML prototypes, adjust slide decks, and assign tasks directly inside the file, a static Google Doc feels obsolete.
What to Do With This
Audit your team's weekly document workflows tomorrow morning. Identify every document where a human acts as a copy-paste bridge between a chat window and a shared spreadsheet or slide deck. Move one recurring project plan into an active agent canvas and assign an autonomous agent direct editing permissions to maintain the task backlog.