PiP mode for developers
- Updated: 2025/09/23
Picture-in-Picture (PiP) mode allows developers to run and test automations in a separate window, enhancing productivity by enabling real-time monitoring without disrupting their main desktop activities.
What is PiP mode for developers?
PiP mode is a feature that allows developers (Citizen Developers and Professional Developers) to run and test bots inside a separate, isolated window session on the same machine, without interrupting their personal desktop activities.
PiP mode options
- Virtual desktop
- This is the default PiP mode that Bot Creators can use to deploy automations. A virtual desktop session maintains its own security context, similar to the primary desktop. This ensures controlled access to applications, files, and other system resources. It is particularly useful when automations interact with Office applications or other environments that handle sensitive data. By using virtual desktop mode, developers can achieve safer execution, minimize the risk of interfering with their main desktop, and test or validate automations in a controlled, production-like environment.
- Virtual window
- A virtual window (PiP) is a user interface feature that allows you to keep a small window (like a video player, log monitor, or task runner) floating on top of your screen while you are working with other applications. The small, resizable window remains accessible without taking up much screen space, so you can continue working in your primary window or Bot editor. Using a virtual window for developers is an effective way to streamline workflow and boost productivity. It allows developers to keep an eye on essential tasks such as running automations, logs, or real-time outputs while still being able to work in the Bot editor. It enhances productivity by improving the adoption of the Citizen Developer Program.
Benefits
- Reduced context switching
- With virtual window, developers can keep relevant information easily accessible without constantly switching between tools.
- Improved productivity
- By reducing the need to toggle between tabs or windows, developers can maintain their flow and focus on the task at hand while keeping an eye on critical information, leading to enhanced multi-tasking.
- Enhanced security
- Runs in its own security context, reducing the risk of exposing sensitive data from the developer’s main desktop.
- Error isolation
- If the automation crashes or encounters issues, only the virtual desktop session is affected, not the main desktop.
- Multi-application support
- Suitable for end-to-end workflows that require switching between multiple applications. For example, Excel + Outlook + File explorer.
Virtual desktop vs Virtual window
Using PiP mode in development is an excellent way to stay productive while monitoring processes like automation tasks, test results, or server logs in real-time. Whether you are working with your automations or debugging your code, a virtual desktop or virtual window ensures you never need to leave your primary development environment to track the status of important tasks. This feature is especially valuable for both Citizen Developers and Professional Developers who need to maintain focus while running background processes.
The below table describes the key difference in PiP mode options:
| Feature | Virtual desktop (PiP) | Virtual window (PiP) |
|---|---|---|
| Scope | Full isolated desktop | Single application UI |
| Developer view | Entire desktop visible | Only application window visible |
| Automation interaction | Across multiple applications or windows | Limited to that application |
| Resource usage | Higher (full desktop environment) | Lower (lighter) |
| Use case | End-to-end or multiple application workflow testing | Application specific automation testing |
| Supported OS | Windows 8, Windows 10, Windows 11, Windows Server 2012, Windows Server 2016, Windows Server 2019, and Supported versions of Windows client | Windows 8, Windows 10, Windows 11, Windows Server 2012, Windows Server 2016, Windows Server 2019 |