Building the Workbench Suite on the Agent platform
The Workbench Suite is a development case: it lets a team describe the view it needs and have an Agent create a usable workbench page. The suite builds on existing work scopes, AgentRun, Skills, and artifacts instead of adding a new core page type for each scenario.
Start with the platform's existing work model
A page might summarize work items, recent runs, files, and deliverables, or track a team's own records. The workspace already supplies the collaboration scope; AgentRun supplies execution; and an HTML artifact supplies a page that can be previewed and revised. The suite focuses on how that page is made and what it may access.
What makes up the suite
- A suite registration describes its name, capabilities, installation entry, and Skill. Installing it in a workspace makes those capabilities available there.
- A lightweight Web module contributes localized messages and capability definitions. This suite does not introduce a new work item type or replace the main application page.
- The page-building Skill provides the Agent with a page contract, an example, and the supported host data interface. It guides the Agent to create a self-contained HTML page and register it as an artifact.
- The suite backend provides optional storage for user-defined lists and tracking records. Platform work items and artifacts remain owned by the main application.
From a request to a workbench page
A user describes the sections and data the page should show. The Agent follows the installed Skill, builds a self-contained HTML file, and saves it as an HTML artifact in the current work scope. The page opens through the existing artifact preview; a later request can revise it without introducing a new page route or changing the core work item model.
Let the page collaborate with the platform
In an authenticated artifact preview, a limited host bridge gives the page its workspace context, theme, and language. It can read approved workspace data, open a file or artifact in the host preview, and send an explicit user-triggered instruction to the AI panel. If the page needs its own editable records, it uses the suite's backend through the plugin channel. The bridge is unavailable on public share pages, where the page must still render a useful empty state.
Keep the boundary clear
The generated page does not receive credentials or direct access to the platform's internal services. Host data access is limited to approved reads in the current workspace; writes belong to the suite's own storage and permissions. This keeps a custom view flexible while leaving identity, work scope, Agent execution, and artifact handling with the platform.