System requirements and limitations in AI Desktop Actions

  • Release version: Zurich
  • Updated November 18, 2025
  • 3 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of System requirements and limitations in AI Desktop Actions

    The AI Desktop Actions application enables defined desktop automations created and executed within the Windows environment. To ensure smooth operation and reliable automation execution, it is important for ServiceNow customers to understand the specific system requirements and limitations that apply to AI Desktop Actions, particularly for versions up to and including the Zurich release.

    Show full answer Show less

    System Requirements

    AI Desktop Actions has defined hardware and software prerequisites to guarantee optimal performance:

    • Hardware: A minimum Intel Core i5 CPU with 4 GB RAM and 20 GB free disk space is required; 8 GB RAM and a Core i7 CPU with 50 GB free disk space are recommended for better performance.
    • Operating System and Software: Windows 11 must be installed along with .NET 9.0 runtime and Desktop Runtime version 9.0.10.
    • Display and Remote Access: No extended monitors are supported. Users interacting with the Execution workspace must be added to the Remote Desktop Users group and have Remote Desktop permissions on target machines. For organizations using Group Policy, appropriate Active Directory group entitlements must be assigned to ensure persistent access.
    • Theme and Display Settings: The theme and screen resolution/scaling must be consistent between recording and execution systems, especially for desktop actions created before version 1.0.1.
    • Network and Security: Firewalls must allow bidirectional traffic on standard HTTP (port 80) and HTTPS (port 443) ports between AI Desktop Actions and the ServiceNow instance. Custom ports require IT confirmation.
    • Permissions: Full permissions are needed to create and use system I/O communication pipes. Also, confirm if the snada:// custom URI protocol is registered to launch AI Desktop Actions from a browser.

    Limitations

    Understanding current limitations helps avoid automation failures or conflicts:

    • Concurrent Execution: Running AI Desktop Actions Execution workspace and RPA Attended Desktop mode simultaneously is not supported to prevent conflicts.
    • Manual Inputs: Any automation requiring human input (like OTP or CAPTCHA) must explicitly instruct the AI Agent to pause and wait for input; otherwise, the process will halt.
    • Single Execution: Only one automation can run at a time within the Execution workspace.
    • Screen Element Accuracy: The reliability of auto-assigned anchors during recording depends on the accessibility and stability of the target application's UI. Complex or dynamic interfaces may necessitate manual tuning.
    • Table Data Capture: The Get Table step requires data to already be in table format; it cannot convert plain text into tables.
    • Browser Usage: Chrome or Edge browsers cannot be used simultaneously in both the main user session and desktop session. The browser session must be closed in the main session before running automations involving these browsers in the Execution workspace.
    • Sensitive Data Handling: Sensitive information is not masked during recording, so users must take care not to record any confidential data.

    Be aware of system requirements and a few limitations when you’re using the AI Desktop Actions application for defined desktop actions.

    Note:
    These system requirements and limitations apply to only defined desktop actions that are created in the AI Desktop Actions Windows application.

    Hardware requirements

    Table 1. Hardware requirements for AI Desktop Actions
    Resource Minimum Recommended
    CPU Intel Processor (Core i5) Intel Processor (Core i7)
    RAM 4-GB RAM 8-GB RAM
    Disk space Minimum 20-GB free disk space after installing the OS, patches, and base software Minimum 50-GB free disk space after installing the OS, patches, and base software

    Software requirements

    • Windows 11 operating system is used.
    • A .NET 9.0 runtime v9.0.10 and .NET 9 Desktop Runtime v9.0.10 is installed.
    • No extended monitors are connected.
    • Add the end users who interact with the Execution workspace of AI Desktop Actions to the Remote Desktop Users group on the target machine and provide Remote Desktop access permissions for seamless automation execution.

      If your organization uses Group Policy, add the end users to a Microsoft Active Directory group that is permitted to use Remote Desktop through Group Policy on each target machine where desktop actions run.

      • Local changes to the Remote Desktop Users group are temporary unless they align with Microsoft Active Directory entitlements.
      • If the user is not entitled, Group Policy refresh automatically removes them from the group.
    • Theme must match between the systems used for recording and execution.
    • Confirm that your firewall allows bidirectional traffic between the AI Desktop Actions application and your ServiceNow instance on the port 80 for HTTP and port 443 for HTTPs.

      If your organization uses non-standard ports for HTTP or HTTPS, confirm the correct ports with your IT administrator before proceeding.

      You must have full permissions to create and use system I/O communication pipes.

    • If applicable, confirm that the snada:// custom URI protocol is registered to launch the AI Desktop Actions application in the browser.
    Note:
    Screen resolution and scaling must be the same between the systems used for recording and execution of desktop actions that are created before AI Desktop Actions v1.0.1.

    Limitations

    Table 2. Limitations with AI Desktop Actions
    Limit Description
    RPA Attended robot and AI Desktop Actions parallel execution

    To avoid conflicts, don't run the AI Desktop Actions Execution workspace and RPA Attended Desktop mode at the same time.
    Pause for human input If your automation requires manual inputs, such as entering an OTP or CAPTCHA, you must provide instructions to the AI Agent to wait for user input during execution. Otherwise, the automation can't proceed.
    Single execution The system supports one automation execution at a time within the Execution workspace.
    Screen elements During recording, auto-assignment accuracy of screen elements depends heavily on the target application’s technology and interface characteristics. Applications with strong accessibility support, such as well-defined UI elements and controls, stable rendering performance, and simple, consistent layouts enable anchors to be detected more reliably. In contrast, UI complexity, such as dynamic elements, frequent layout shifts, animations, or poor accessibility metadata can reduce accuracy and may require manual anchor configuration or additional tuning.
    Getting table information The Get Table step doesn’t convert ordinary text to table data. For the step to capture table data successfully, the data must already be in the table form.
    Browsers parallel execution The Chrome or Edge browser must not be used in parallel in the main session and the desktop session on your system. You must close the session in the main session to execute automations that use the Chrome or Edge browser in the Execution workspace.
    Sensitive information The sensitive information isn’t masked during recording. Confirm that you don’t record any sensitive information.