Skills, connectors, and access boundaries
Teams need specialized Agent capabilities, but those capabilities must remain attached to the workspace and access they were configured for. Our extension model separates the way work is done from the external resources it may use.
Three complementary parts
Business suites package specialized work modes and skills. Skills describe how the Agent carries out a task and produces outputs. Connectors link a workspace to external resources when the work requires them. Each workspace can enable the parts it needs.
Authorization follows the work scope
The platform determines an AgentRun's tenant and workspace scope before it uses an external capability. Connector access is checked against the current workspace installation and connection, rather than chosen freely by the Agent. This keeps extensions within the authorized context of the task.
What developers can build on
A new capability can contribute a skill, an external connection, or a focused work-item view. The platform still uses the same work scope, run, and deliverable model. This lets specialized experiences grow without changing the core collaboration model for every new use case.