Agents4DevOps combines an agent runtime, control plane, reusable workflow packs, and industry-specific engineering logic. It installs under the Boards tab in Azure DevOps, so teams automate routine work without giving every agent unrestricted access — or treating every task as an open-ended prompt.
Each run is composed from the same layered system — from what starts it to the engineering standards it enforces.
| Layer | Purpose |
|---|---|
| Agent runtime | Starts and executes runs from requests, Azure DevOps events, schedules, APIs, or other workflows — with tool calls, dependencies, retries, cancellations, and outputs. |
| Control plane | Defines scope, models, instructions, tools, permissions, approvals, verification, and run-history behavior for every workflow. |
| Workflow packs | Provide reusable implementations for backlog, code, pipelines, tests, releases, operations, and evidence — available from a prebuilt Agent Library of templates. |
| Industry packs | Apply classifications, standards, traceability, lifecycle gates, and evidence expectations to the work agents prepare. |
Configure the workflow once, then run it manually, from an Azure DevOps event, on a schedule, or through an API. Each run operates within its assigned scope and control policy.
A request, ADO event, schedule, or API call starts the run.
It loads the permitted work items, code, runs, results, and policies.
It applies versioned rules or plans a sequence within scope.
It analyzes, drafts, updates data, or invokes an approved operation.
Actions with side effects pause for the right reviewer.
Post-action checks confirm the expected result exists.
The run record captures inputs, actions, approvals, and outcome.
Use deterministic execution agents for controls you can specify, and planner agents where the work requires investigation or drafting — both run on one execution model.
Configure at the level the workflow requires, then decide where humans stay in the loop.
The same governed building blocks — runtime, triggers, skills, orchestration, approvals, and verification — apply to every agent you configure.
Starts and executes runs with tool calls, dependencies, retries, cancellations, and outputs. A prebuilt Agent Library of templates gets teams to a working workflow fast.
Run agents manually, when Azure DevOps artifacts change, on a recurring cadence, or from another workflow — moving from one-off assistance to repeatable execution.
Compose agents from a reusable Skills library and permissioned Azure DevOps tools. MCP connectivity for external data and actions is on the roadmap, coming in v2.
Coordinate several agents, handoffs, and gates for lifecycle-spanning work. Agents also run from Copilot4DevOps chat in single-agent or multi-agent orchestrator mode.
Define read-only, draft, update, and operational levels, set approval requirements per action, and enforce existing Azure DevOps permissions and project scope on every run.
Post-action checks confirm the expected state, link, or result exists. Every execution creates a Job in a Jobs dashboard with full logs and audit history.
BYOD semantically indexes your work items to find similar items — giving planner agents relevant context from your own backlog. Browse workflow packs →
The most useful evaluation is not a catalog tour. Select one workflow and inspect how it is configured, triggered, executed, approved, verified, and recorded.