Windows Native Dialog for Openclaw

Enables Openclaw agents running in WSL2 to interact with native Windows file picker dialogs through PowerShell execution.

owlock
v1.0.2
Mar 23, 2026
0
903
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install windows-native-dialog

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install windows-native-dialog using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Windows Native Dialog?

The windows-native-dialog skill is a specialized utility designed for developers using Openclaw Skills within a WSL2 environment. It solves the common 'invisible element' problem where browser automation tools cannot see or interact with native Windows OS dialogs, such as file upload windows.

By leveraging the interoperability between WSL2 and Windows, this skill allows the agent to trigger PowerShell commands that control the host operating system. This ensures a seamless workflow for complex tasks like uploading media to social platforms or interacting with enterprise software that relies on native system prompts.

Windows Native Dialog Use Cases

  • Automating file uploads on platforms like Meta Business Suite when running Openclaw in WSL2.
  • Interacting with native Windows 'Open' or 'Save As' dialogs that are outside the browser DOM.
  • Bridging automation gaps where standard CDP-based browser-automation fails to detect system-level windows.
  • Integrating legacy Windows scripts or Python-based automation into a Linux-based AI agent workflow.

How Windows Native Dialog Works

  1. The agent initiates a browser-automation action, such as clicking an 'Upload' button that triggers a system dialog.
  2. The skill utilizes the exec tool to call the Windows PowerShell executable located on the host C: drive.
  3. PowerShell executes a specific script (e.g., a Python helper or SendKeys command) to input the file path and confirm the dialog.
  4. Once the native window closes, the agent resumes browser-automation to complete the final steps like clicking 'Publish' or 'Submit'.

Windows Native Dialog Setup

To use this skill, ensure your Openclaw configuration allows for the necessary tool groups:

openclaw config set tools.allow '[\"browser\",\"group:runtime\",\"group:fs\",\"group:web\"]'

Ensure that your file paths are mapped correctly between /mnt/c/ (WSL2) and C:\ (Windows) so the PowerShell script can locate the target files.

Windows Native Dialog Data Schema & Taxonomy

The skill relies on specific execution paths and external scripts to manage native windows. Below is a comparison of how it fits into the broader ecosystem of Openclaw Skills for desktop control:

Feature Specification
Bridge Type exec + PowerShell Interop
Environment Windows 10/11 + WSL2
Target Path /mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe
Primary Tool browser-automation + runtime exec

Windows Native Dialog Advanced Features

  • Multi-stage workflow support combining browser interaction with OS-level execution.
  • Compatibility with custom Python scripts running on the Windows host for complex UI manipulation.
  • Lightweight alternative to full desktop-control skills when only dialog interaction is required.
  • Support for internal Openclaw issue tracking and PR-linked optimizations for WSL2 users.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*