OpenAI 将 Workspace Agents 引入 ChatGPT,团队级 AI 工作流开始从“聊天”走向“执行”
Key takeaways
2026年6月18日
2026年6月18日
目录
- 事实概述
- 背景与原因
- 为什么值得关注
- 对 AI 工具用户的影响
- 对 ENHE 用户的实际启发
- 总结
- 来源
事实概述
OpenAI 于 2026年4月22日发布 ChatGPT Workspace Agents。根据 OpenAI 公告,这类 agent 面向团队工作流,可在组织权限和控制范围内处理复杂任务与长时间运行的流程。
OpenAI 称,Workspace Agents 由 Codex 驱动,可在云端运行,支持文件、代码、工具和记忆,并可在 ChatGPT 与 Slack 等工作场景中使用。该功能目前以 research preview 形式提供给 ChatGPT Business、Enterprise、Edu 和 Teachers 计划。
背景与原因
过去一年,AI 工具正在从“单次问答”转向“持续执行”。OpenAI 在公告中提到,许多组织内部流程依赖共享上下文、跨团队交接和审批,因此需要能理解流程、调用工具并在必要时请求确认的 agent。
公告列举的软件请求审核、产品反馈路由、周报生成、销售线索跟进和第三方风险管理等场景,说明这类工具的目标不是替代所有工作,而是把重复、跨工具、需要上下文整理的流程标准化。
为什么值得关注
这条新闻属于 AI 智能体和 AI 工作流自动化主线。它的关键信息差在于:团队级 agent 的难点并不只是模型能力,还包括权限、工具连接、审批、监控和组织知识复用。
OpenAI 同时提到,管理员可以控制 connected tools 和 actions,查看 agent 配置、更新和运行情况,并在需要时暂停 agent。这说明企业和小团队在使用 agent 前,仍需要明确数据权限、操作边界和人工确认规则。
对 AI 工具用户的影响
对普通 AI 工具用户而言,Workspace Agents 代表一个明确趋势:AI 使用能力将从“会写提示词”扩展为“会拆解流程、配置工具、设置检查点”。未来学习 AI 技能时,只学习对话技巧可能不够,还需要理解任务流程、数据来源、权限范围和结果验收。
对中小团队而言,适合优先尝试的场景通常不是高风险决策,而是低风险、重复性强、容易验收的流程,例如周报整理、资料归档、客服问题分类、线索初筛和内部知识问答。
对 ENHE 用户的实际启发
对恩禾ENHE AI 的受众来说,这条新闻的重点不是追逐新功能,而是判断自己是否已经具备使用 AI agent 的基础条件:是否有清晰流程,是否有可连接的数据源,是否能定义审批节点,是否能回看 agent 的执行记录。
如果团队正在学习 AI 工具、搭建本地 AI 应用或做工作流自动化,可以先从“半自动 agent”开始:让 AI 负责检索、整理、生成草稿和提醒,人负责确认、发布、付款、删除和外部发送等关键动作。这样更容易在效率和安全之间取得平衡。
总结
OpenAI 的 Workspace Agents 显示,AI 智能体正在进入团队协作和业务流程场景。短期内,它更适合作为流程助手和自动化执行层,而不是完全自主的决策者。对 AI 工具用户来说,真正值得投入的能力,是把日常工作拆成可验证、可授权、可复用的 AI 工作流。
Tools you may use
Related tutorials
Related Tools And Tutorials
Use the following ENHE AI sections to continue from the news signal into tool selection, account-service guidance, or practical learning.
Related reading
Anthropic Launches Claude Opus 5 as Complex AI Work Becomes an Everyday Model Choice
Anthropic released Claude Opus 5 on July 24, 2026 and positioned it as the default model for Claude Max and the strongest option on Claude Pro. GitHub added the model to Copilot Pro+, Max, Business, and Enterprise on the same date, with administrator approval required for managed plans. The useful question for ordinary users is not whether one benchmark ranks the model first. It is whether a task is complex and long-running enough to justify a higher-capability model, whether the user has access through the relevant plan, how usage-based charges apply, and whether stricter cyber safeguards may block security-adjacent prompts.
MCP 2026-07-28 Is Final: Recheck GitHub MCP Initialization Assumptions
The Model Context Protocol project released MCP 2026-07-28 on July 28, 2026. The final specification removes the initialize lifecycle, protocol-level sessions, and most capability negotiation. Requests are self-describing, and workflows that need continuity use explicit handles rather than hidden session state. ENHE's original July 24 page had carried forward prerelease information, so this update corrects the record using the final specification and GitHub's current guidance. Teams should identify the version used by each client, server, SDK, and hosted product, test authentication and discovery behavior with non-sensitive data, verify errors and rollback, and keep human approval for high-risk tools before moving real work.
China Proposes a Global AI Agent Trust and Interoperability Initiative
A global cooperation initiative released on July 17, 2026 calls for mutual trust, connectivity, and interoperability among AI agents. Its nine proposals span ecosystem development, security governance, open-source collaboration, standard interfaces, privacy protection, and digital inclusion. The initiative arrives alongside an ITU focus group on agent identity and access management, the Linux Foundation's Agent Name Service proposal, and the A2A protocol project. Together, these efforts show AI agent competition expanding beyond model quality toward trusted identity, service discovery, cross-platform communication, permission control, and auditable execution. For users and small teams, the immediate task is not to assume a universal standard exists, but to demand clear identities, scoped permissions, logs, approval gates, and rollback paths.
IBM Introduces Power Autonomous Operations as AI Agents Move Into On-Prem Infrastructure
IBM announced Power Autonomous Operations and the Power S1112 on July 15, 2026. The operations software is scheduled for general availability on September 23 and is designed to coordinate multiple agents that monitor IBM Power systems, diagnose issues, recommend actions, and act only after authorization. IBM says humans remain in the loop for major changes. The compact Power S1112, scheduled for July 24, adds an on-premises option for local AI inference using on-chip acceleration. The practical lesson is not that infrastructure can run without people. It is that agentic operations require explicit permissions, observable evidence, approval gates, rollback paths, and clear data boundaries before automation can be trusted.
GitHub Copilot App Adds Security Reviews as Coding Agents Move Risk Checks Earlier
GitHub added a /security-review command to the public preview of the GitHub Copilot App on July 14, 2026. The command checks local or uncommitted changes and prioritizes high-confidence findings with severity, confidence, and remediation guidance. It is available across Copilot plans, but it does not replace CodeQL, Dependabot, secret scanning, or human review. A separate enterprise preview can add AI-powered security detections to pull requests and consumes AI credits. Together with agentic autofix and new CodeQL prompt-injection coverage, the update shows coding assistants moving security checks earlier in the development workflow. Ordinary users should treat the output as a review aid, verify each finding, and keep existing testing and approval controls.
GitHub Copilot Adds Enterprise-Managed OTel Export for VS Code and CLI
GitHub announced enterprise-managed OpenTelemetry export for VS Code and CLI on July 8, 2026. The update lets administrators route Copilot telemetry to an approved collector, covering the Copilot Chat extension in VS Code and the agent host process behind Copilot CLI. For ordinary AI users and teams, the important shift is practical governance. AI coding agents are no longer judged only by answer quality or speed. Teams now need to understand sessions, tool calls, token usage, model behavior, errors, approvals, and where logs are stored. This makes observability a core part of AI-agent rollout, local deployment decisions, account governance, and workflow automation training.
Sources
FAQ
What is this ENHE AI article about?
2026年6月18日
Why is this AI update worth watching?
It may affect how AI users choose tools, understand platform changes, and plan practical AI workflows.
What does it mean for everyday AI users?
Everyday users should compare the update with their own tool needs, data boundaries, account access, and learning path before changing workflows.
Where can readers continue learning on ENHE AI?
Readers can continue with ENHE AI software apps, AI skill tutorials, and AI account service guidance to turn the news signal into practical action.


