Why organize Agent work with workspaces and work items?
An Agent request is often part of a larger piece of work. Its conversations, source files, actions, and results need a place to belong. In our platform design, that place is a work scope.
One scope, several kinds of context
A workspace brings people and shared materials together. A work item sits inside a workspace and focuses on a project or ongoing matter. Each scope has its own conversations, files, and Agent working directory. An individual conversation keeps its message history; it does not automatically inherit every other conversation in the scope.
Start broad, focus when needed
People can start directly in a workspace and open separate conversations for different tasks. When a matter needs its own long-running context, they can create a work item and keep the relevant conversations, materials, and outputs together. This keeps everyday use simple while giving sustained work a stable place.
What this changes in platform design
The scope becomes a consistent reference for access, files, Agent execution, and deliverables. A task is created for a specific scope, and its results return to that scope. Skills can work at workspace or work-item level according to their contracts, without introducing a separate platform model for every industry.