Qclaw Restart

What This Skill Does

The QClaw Restart skill is a specialized automation utility designed specifically for Windows-based OpenClaw users. Its primary function is to programmatically cycle the QClaw application state, effectively shutting down existing instances and relaunching them using a safe, process-aware PowerShell script. By leveraging the CloseMainWindow() method, it attempts to close the application gracefully, ensuring that configurations are reloaded and potential memory leaks or state issues are cleared without causing unnecessary data loss. The skill is context-aware, identifying the current installation path dynamically from running processes, which makes it compatible with various installation directories without requiring manual configuration.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/chenguangwu/qclaw-restart Once installed, ensure the workspace has permissions to execute PowerShell scripts, as the skill generates a restart-qclaw.ps1 file within your OpenClaw directory to manage the restart lifecycle.

Use Cases

This skill is ideal for environments where QClaw requires frequent updates to configuration files or performance refreshes. It is particularly useful when users modify settings that only take effect upon application restart. Additionally, it serves as a recovery mechanism when the application becomes unresponsive, providing a standardized way to force-stop hung processes and restart the service cleanly.

Example Prompts

1. "Restart the QClaw application to apply my new configuration settings."
2. "QClaw seems a bit slow, could you restart it for me?"
3. "Hey, please restart yourself so that the changes I made take effect."

Tips & Limitations

• Safety First: Always verify the user's intent. The skill enforces a mandatory confirmation step before execution to prevent accidental disruption of ongoing tasks.
• System Requirement: This skill is strictly for Windows environments. It checks for Windows_NT and will exit if executed on non-Windows systems.
• Performance: The script includes a 5-second wait period to ensure the process shuts down completely before attempting to launch it via explorer.exe to avoid conflicts.
• Session Interruption: Note that restarting the application will disconnect the current interaction session. Ensure no critical background tasks are pending before confirming the restart.