Agent workbench: goals, tasks, and parallel work
Open the Agent tool from the project rail. Its tabs are available according to project route, role, checkpoint, and service readiness; a hidden tab is not an error when its prerequisite is absent.
Context and command palette
Context summarizes the project memory and current design context. Use the refresh control after a meaningful project change. The command palette searches supported Agent actions; choose an action only after reviewing what it will do in the current project.
Goals and task board
Owners or members with the required authority can create a longer-running goal. Describe the desired outcome and write observable success criteria, then select the offered autonomy level. Review the goal state as it runs; use pause, resume, or cancel only when the displayed lifecycle permits it. The task board groups work by lifecycle, shows prerequisites and build/test evidence, and can include follow-up suggestions. Review a follow-up plan before starting or cancelling it.
Parallel work
The Parallel tab shows readiness, task coordination, and the state of parallel Agent tasks. A task can wait for approval, prerequisites, or capacity before it starts. Inspect each task's state and validation evidence; parallel execution does not mean the final combined result has already passed review.
Artifacts and libraries
Artifacts lists deliverable sets that are relevant to the current project. Create a new artifact request by choosing its offered kind/profile, writing the intended result, and reviewing the handoff before submitting. If the panel reports an upgrade requirement, inspect the compatibility and impact summary before accepting it. The Library tab is shown for Web design projects and can offer organization design systems or templates; applying one hands the requested design-system work to the Agent.
Native mobile delivery
The Mobile tab appears only for Native projects. It reports native delivery readiness and device-build context. It is not a mobile-app conversion feature for a Web project. Use the Native build and distribution workflow for actual packages; external signing and store authorization remain separate requirements.