setup-windows

Automate BastionClaw setup on Windows with WSL2 and Docker/Podman.

30|3|Updated Feb 21, 2026

Search Tags:#automation #docker #setup #windows #podman #wsl2 #bastionclaw

Ready to run

npx skills add https://github.com/harperaa/bastionclaw --skill setup-windows

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: setup-windows
Source: https://github.com/harperaa/bastionclaw/tree/main/.claude/skills/setup-windows
Command: npx skills add https://github.com/harperaa/bastionclaw --skill setup-windows

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines installing BastionClaw on Windows by guiding users through WSL2 setup, Docker/Podman configuration, and persistence setup, so the agent runs securely in a Windows environment.

Core Features & Use Cases

Supports WSL2 validation and environment prep, Docker Desktop or Podman rootless mode, repository setup on the WSL2 filesystem, container conversion readiness, and systemd user service persistence for BastionClaw.
Use cases include Windows-based development, cybersecurity workflows requiring isolated containers, and quick deployment across Windows hosts.

Quick Start

On Windows, run the setup-windows skill to prepare WSL2, install Docker Desktop or Podman, and configure BastionClaw to start automatically.

Frequently Asked Questions about setup-windows

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I install BastionClaw on Windows using WSL2?▼

To install BastionClaw on Windows using WSL2, you need to automate environment validation, configure Docker or Podman, place the repository on the WSL2 filesystem, and enable systemd-based persistence for the container service.

Can I use Podman rootless mode instead of Docker Desktop to run BastionClaw on Windows?▼

Yes, you can use Podman rootless mode as an alternative to Docker Desktop to run BastionClaw on Windows. The setup process supports configuring either container runtime within your WSL2 environment for isolated cybersecurity workflows.

What is the best way to ensure my BastionClaw container persists across WSL2 restarts?▼

The best way to ensure BastionClaw container persistence across WSL2 restarts is to configure a systemd user service. This approach automates startup and maintains container readiness securely within the Windows environment.

Do I need to place the BastionClaw repository on the WSL2 filesystem?▼

Yes, placing the BastionClaw repository directly on the WSL2 filesystem is required. This setup ensures proper container conversion readiness and optimal performance when running Docker or Podman within the Windows Subsystem for Linux.

Why does my BastionClaw setup on Windows require environment validation before installing Docker?▼

Environment validation is required before installing Docker or Podman to verify your Windows machine meets WSL2 prerequisites. This step ensures your system supports systemd-based persistence and is ready for secure BastionClaw container deployment.