Attended vs. unattended execution for computer-using agents

Overview

Computer-Using Agents (CUAs) can execute tasks in two primary modes:

  • Unattended execution – Fully autonomous agent operation without human involvement
  • Attended execution – Human-in-the-loop workflows where control can be shared or transferred

Choosing the correct execution model is critical to ensure reliability, security, and user trust. Windows 365 for Agents provides a secure Cloud PC environment that supports both execution patterns, including scenarios where agents interact directly with applications and optionally involve users.

Execution models explained

Unattended execution

Unattended execution allows an agent to:

  • Run tasks independently
  • Execute workflows without user interaction
  • Operate on-demand or in scheduled scenarios

This model aligns with fully autonomous agent workflows, where the agent is responsible for completing the entire task lifecycle.

Attended execution

Attended execution allows an agent to:

  • Collaborate with a human user
  • Hand off control during execution
  • Require approvals, validation, or intervention

Windows 365 for Agents explicitly supports human-in-the-loop workflows, enabling safe and controlled transitions between agent and user control.

When to use unattended execution

Use unattended execution when workflows are:

  • Predictable and repeatable

    • Structured tasks with clear steps
    • Minimal variation between runs

  • Safe to run autonomously

    • Low risk of business impact if errors occur
    • No requirement for real-time human validation

  • High-volume and scalable

    • Background processing
    • Batch automation
    • Event-driven triggers

Example use cases

  • Backend data processing across enterprise systems
  • Automated IT remediation (e.g., patching, compliance updates)
  • Report generation and data synchronization
  • System monitoring and alert-driven remediation

Unattended execution is ideal when the goal is maximum scalability and efficiency without human dependency.

When to use attended execution

Use attended execution when workflows require:

  • Human judgment or validation

    • Decisions that cannot be fully automated
    • Context-sensitive approvals

  • Real-time interaction

    • User-driven workflows
    • Interactive UI navigation

  • Sensitive or high-risk operations

    • Financial transactions
    • Compliance-related actions
    • Data access requiring authorization

Example use cases

  • Customer service scenarios where agents assist human operators
  • Approval workflows (for example, procurement or legal review)
  • Complex workflows requiring interpretation of ambiguous inputs
  • Troubleshooting scenarios where users guide agent actions

Attended execution is best suited for collaborative automation, where agents augment rather than replace human decision-making.

Choosing the wrong execution model: risks and issues

Selecting the incorrect execution model can lead to operational, security, and reliability issues.

Using unattended execution when attended is required

Potential issues:

  • Loss of control Agents may execute actions without required approvals
  • Compliance violations Sensitive workflows may bypass governance checkpoints
  • Incorrect decision-making Agents may act on incomplete or ambiguous data
  • User trust erosion Lack of visibility or control can reduce confidence in automation

Using attended execution when unattended is sufficient

Potential issues:

  • Reduced efficiency Human involvement introduces unnecessary delays
  • Scalability constraints Workflows cannot scale without additional human resources
  • Higher operational cost Increased dependency on human oversight
  • Workflow bottlenecks Tasks may stall waiting for user interaction

Windows 365 for Agents Considerations

Windows 365 for Agents provides a controlled execution environment for both models:

  • Agents operate in secure, isolated Cloud PCs
  • Execution is governed by enterprise policies and identity controls
  • Actions can be observed, audited, and validated

This enables organizations to safely implement:

  • Fully autonomous unattended workflows
  • Human-in-the-loop attended scenarios
  • Hybrid execution models within the same workflow

The ability to combine attended and unattended execution is critical for complex enterprise automation scenarios.

Hybrid execution patterns

Many real-world workflows require both execution models.

Common pattern

  • Unattended execution: Agent performs initial data collection and processing
  • Attended checkpoint: Human reviews or approves the result
  • Unattended continuation: Agent completes the workflow

Example

A compliance workflow might:

  • Automatically gather data from multiple systems (unattended)
  • Route findings to a compliance officer for approval (attended)
  • File reports and update systems after approval (unattended)

This pattern balances efficiency with governance and control.

Decision guidance

Scenario Recommended model
Repetitive, low-risk tasks Unattended
High-volume automation Unattended
Real-time user interaction Attended
Sensitive or regulated workflows Attended
Decision-making required Attended
End-to-end autonomous workflows Unattended
Mixed workflows with approvals Hybrid

Next steps

  • Last updated on