Workflows

Workflows turn one-off agent requests into repeatable, inspectable execution paths.

Current Workflow Areas

• Coding and patch proposals
• Read-only project analysis
• Research source collection and synthesis
• Browser QA
• Security QA and scoped pentest workflows
• Provider smoke checks
• Planner tasks, calendar context, and scheduling workflows
• Composable report workflows with source intake, sandbox/preflight gates, section producers, rendering, and delivery drafts
• Worker polling workflows that claim outbound jobs, heartbeat, complete, wait, or fail through signed worker requests
• Automations triggered manually, on schedules, through webhooks, and through workflow primitives for file, git, and provider-health events

Workflow Designer

The workflow designer supports triggers, branches, filters, agent steps, connector tools, parser steps, notifications, retries, approval gates, and structured outputs.

For step-by-step usage, see Build a workflow from scratch and Use the workflow assistant.

For adding or changing reusable workflow families, see Workflow Extension Lifecycle.

Agent Steps

Agent steps can specify:

• provider and model;
• memory mode;
• allowed tools;
• connector accounts and scopes;
• structured output settings;
• approval policy;
• step-specific prompts and objectives.

Verification

Runs should complete because verifiers pass, not because an agent reported success. Verification artifacts remain part of the run history.

For run review, see Inspect a run and its artifacts.

Composable Reports

For report workflows that assemble outputs from multiple standalone workflows, see Build composable report workflows.

Customer-specific report-production and worker-polling notes do not belong in the docs tree. Reusable patterns should be documented with generic Aegis terms and sanitized examples only.

The current primitive and tool-family inventory is in Capability Inventory.