OpenAI 開發者大會發布全天候代理 Dots,ChatGPT 週活用戶逾 12 億OpenAI unveils always-on Dots agents at DevDay as ChatGPT weekly users pass 1.2 billion
- 事件
- OpenAI 於 9 月 29 日開發者大會發布全天候代理 Dots,每隻配備雲端電腦,可經 ChatGPT、Slack 與 Teams 操作;同場公布 ChatGPT 週活用戶逾 12 億、企業客戶約 250 萬家。At its DevDay event on 29 September, OpenAI introduced Dots, always-on agents that each run their own cloud computer and can be reached through ChatGPT, Slack and Teams. It also said ChatGPT now has more than 1.2 billion weekly users and about 2.5 million business customers.
- 背後
- 代理由「問答」轉向「常駐執行」。OpenAI 把 Codex 與 ChatGPT Work 接上代理,並以 GPT-6.1 Sol 承接較低成本的日常工序,是把訂閱制延伸成工作平台的收入結構。Agents are shifting from answering questions to holding standing responsibilities. OpenAI wired Codex and ChatGPT Work into Dots and positioned GPT-6.1 Sol for lower-cost day-to-day work, extending a subscription business into a work platform.
我們認為 Dots 的真正變數不是能力,而是誰批准它做什麼。當代理由背景跨應用長期行動,權限設計與覆核責任會先於模型分數決定成敗,提示詞約束並不足夠。We think the decisive variable for Dots is not capability but who authorises what it may do. Once an agent runs in the background across applications, permission design and review ownership decide success before benchmark scores do, and prompt-level constraints are no longer sufficient.
- 對日常工作的影響
- 資訊科技主管須為常駐代理設獨立身分與可一鍵撤銷的憑證;營運與前線主管要重新界定哪些步驟需人手批准,而非只審核最後結果。IT leads must give always-on agents their own identity and credentials that can be revoked in one step. Operations and frontline managers need to redefine which steps require human sign-off rather than reviewing only the final output.
- 如何改善
- 本週挑一條最常出錯的跨系統流程,寫下代理可自行做的三件事與必須先問人的三件事,交出一份書面清單。This week, pick your most error-prone cross-system workflow and write down the three things the agent may do alone and the three it must ask about, as a one-page written list.
