Workflows and delivery
Connect signals and context to tasks, execution, and review
Studio connects the context that informs work with the environment that executes it. A request can start with a person, a connected system, or a diagnostic signal. A task records the outcome; an agent works toward it; review determines whether the result is ready.
The intended loop is signal → objective → task → execution → review. A signal identifies an issue or opportunity. An objective describes what you want to improve. A task turns that intent into work with a concrete result.
The loop does not run end to end yet. Tasks are mature and in daily use. Signals are partial, with diagnosis on demand rather than continuous monitoring. Objectives are planned. Use the availability state of each feature when designing a workflow.
Availability
| Capability | State | Guide |
|---|---|---|
| Tasks, agent execution, pull requests, and previews | Live | Tasks and the board |
| Repository connections across GitHub, GitLab, and Bitbucket | Live | Tasks and the board |
| Steering execution through task comments | Live | Writing a task |
| Automated review, preview QA, and delivery lanes | Live, partly behind a flag | Reviews and QA |
| Diagnosis from connected data | In build; becoming continuous | Signals and monitoring |
| Goals with a metric and a budget | Planned | Objectives |
Upstream: connect context
Start with Connections. Connect the systems an agent needs to understand and operate: repositories, documents, business tools, and custom MCP servers. Supply the context needed to distinguish a useful task from a plausible guess.
The working surface: tasks and apps
Use Tasks to define work, follow execution, and provide feedback. Writing a task explains how to specify a result an agent and a reviewer can assess.
Extend the interface with MCP Apps when the workflow calls for a richer interaction. The Site Editor is one such application; its usage guides live under Storefront.
Downstream: execute and review
For repository changes, the execution environment supplies the checkout and tools, and can expose a preview. The result enters a review workflow with evidence your team can evaluate. Read Architecture for sandboxes and Reviews and QA for validation and delivery.
These primitives apply to more than storefronts. The connected systems, apps, task instructions, and execution tools define your workflow.