Workflows

Map the work.
Expose the decisions.

Design multi-step agent operations as understandable flows of skills, tools, approvals, policy gates, data transformations, and completion evidence.

Product direction · In active development

A graph with semantics

Planned workflow nodes can represent triggers, agents, skills, tools, branches, waits, subflows, exception handling, and audit events.

A data flow, required dependency, approval gate, and tool invocation should read as different relationships.

Policy and approval gates belong within the operational path where people can see what is requested and why.

Completion evidence and outcome states are designed to be explicit rather than implied by a chat transcript.

The workflow experience is being designed for understandable small flows as well as more advanced orchestration.

Workflow editing and runtime behavior remain in active development.