You can set up and configure attended bots to run in a virtual desktop using the picture-in-picture (PIP) mode in Automation Co-Pilot. This feature lets attended bots operate in a secure, isolated full-screen workspace, which is perfect for using desktop apps like Microsoft Office.

You can set up a virtual desktop using PiP mode through bot settings or change it while it's running. This gives you more flexibility, control, and security when the bot is working. The bot runs in a new full-screen desktop session, which offers better isolation and improved access to Microsoft Office applications.

Prerequisites

Before you can run automations in PiP mode using Virtual desktop, make sure you have the following:
  • A Co-Pilot license is needed to access PiP mode.
  • Automation 360 Bot Agent must be installed and active.
  • Latest version of Automation Co-Pilot Desktop Assistant should be in use.

Procedure

  1. Set PiP Mode in Advanced Settings: To enforce this option for all attended bot runs:
    1. Open the Advanced Settings of your bot.
    2. Scroll to Run in PiP mode section.
    3. Check Run in PiP mode.
    4. Select Virtual desktop. This launches the bot in a separate full-screen workspace (rather than a floating resizable window).
    5. Save your settings.
      Note:

      This applies to all bot executions unless overridden manually during run-time.

  2. Override PiP Mode at Run-Time (Optional): To change the PiP mode dynamically:
    1. In Co-Pilot Desktop Assistant, click the Run-time options menu.
    2. Toggle Run in PiP mode.
    3. Select between: Virtual desktop or Virtual window. This allows flexible, per-execution control without altering global bot settings.
  3. Execute the Bot
    1. Launch the bot from Co-Pilot Desktop Assistant or Embedded Co-Pilot.
    2. A pop-up will appear with a button like Join Session.
    3. Click Join Session to switch into the new virtual desktop and interact with the bot’s execution environment.
You can run a sample automation to see how it works:

  • Use actions like Open Notepad, Simulate Keystroke, and Recorder > Set Text.

  • Watch what happens on the virtual desktop workspace.

  • Check if the automation works as expected when you are using the virtual desktop.

    Note: Simulated keystrokes and mouse clicks only work if you are actively in the virtual desktop session at run-time.
  • Separate log files are created for: Normal user mode and Admin mode. These logs are kept in the Virtual Desktop Launcher Logs directory. They are helpful for fixing problems related to virtual desktop isolation or user privileges.

Use Case: Secure Interaction with Microsoft Office via Co-Pilot

Use Case Overview: A financial analyst uses Co-Pilot to run a bot that:
  • Opens Microsoft Excel.
  • Gets data from an internal report.
  • Makes a summary chart.
  • Sends it using Microsoft Outlook.
Benefits with Virtual Desktop:
  • Isolation: Microsoft Excel runs in a separate full-screen workspace, so the user’s personal desktop is not disturbed.
  • Security: Microsoft Office credentials and sensitive file paths are better protected in the virtual desktop.
  • Focus: Distractions from other open applications are reduced.

This is especially helpful in regulated industries like banking, insurance, healthcare, and legal operations.

Use Case Summary:
Feature Benefit
Virtual desktop in PiP mode Run bots in a clean, isolated environment
Dynamic run-time overrides Adjust PiP settings on the fly
Secure Office automation Prevent context leakage between user and bot
Separate logs Easier troubleshooting and compliance tracking