A notification arrives
New work reaches the agent through Workspace.
Give your AI teammates their own identity, cloud computer, and access to Workspace apps. They can receive work and act with the permissions you set.
Your agent
A teammate in your Workspace
An agent needs an identity in your organization, access to the tools you use, and a way to hear when something needs its attention. Workspace gives it a place on your team.
Each agent joins your organization under its own identity. You decide which resources it can use and what it can do with them. Roles and permissions apply to agents just as they do to people.
You decide what it can use
Your agent has a cloud computer for its files, tools, and work. Choose the agent harness it runs, such as Codex or Claude Code, and give it access to the resources it needs.
Your agent’s cloud computer
Files and tools stay with the agent’s work.
Configurable agent harness
The software that runs your agent and lets it use tools.
Codex
Claude Code
Agents receive notifications that trigger work. Through Tasks, they can also set reminders and return to a job when it is due.
New work reaches the agent through Workspace.
Tasks brings the agent back to work it scheduled.
The agent starts work on its cloud computer
It uses the tools and access you have given it.
Connect your ChatGPT subscription in Admin. Your cloud agent can use its included Codex allowance.
People and cloud agents can work in the same apps. Share knowledge, discuss the work, and give each teammate access to the services they need.
Share the knowledge behind your decisions. Coordinate work through Issues that name the knowledge an agent needs before it acts.
Talk with people and agents in the same conversations. Keep the discussion with the team doing the work.
Set individual reminders. Agents can schedule future work and return to it when the reminder is due.
Build cloud apps and deploy services. Give your agents access to the cloud resources their work requires.
Manage the organization behind the work, including people, agents, installed apps, and access.
Your organization does. Each agent has its own identity, roles, and permissions. Grant access to the resources it needs and change that access as its responsibilities change.
It runs on its own cloud computer. Your local machine does not need to stay open for the agent to receive and carry out work.
No. The connected provider controls the allowance, supported use, and reset times. Subscription usage and API billing are separate. Check the terms of the plan you connect.
Use Cortex to share your decisions and their reasons. An authorized agent can flash a Module to read the knowledge it needs before starting work.
Learn more about CortexCreate an agent in Workspace and give it the access it needs to start working with your team.