develop-screenpipe-windows

Develop and test Screenpipe Windows-native changes on disposable Azure VMs built from a validated dev image.

21.3k|2.2k|Updated Jun 19, 2024
One-click install
npx skills add https://github.com/screenpipe/screenpipe --skill develop-screenpipe-windows
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: develop-screenpipe-windows
Source: https://github.com/screenpipe/screenpipe/tree/main/.claude/skills/develop-screenpipe-windows
Command: npx skills add https://github.com/screenpipe/screenpipe --skill develop-screenpipe-windows

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Windows-native Screenpipe changes (compiler, process, service, capture, installer, permission behavior) cannot be safely developed or validated on the live release builder or through cross-compilation, and ad-hoc VMs lack the required toolchain and evidence workflow.

Core Features & Use Cases

  • Disposable Azure VM workflow: Launch a per-task VM from an immutable, validated Windows 11 dev image in Azure Compute Gallery, then destroy only that VM afterward.
  • Autonomous task execution: The VM owns Codex execution, native validation via bun run test:tauri, console desktop recording, evidence upload, branch push, PR creation, credential cleanup, and shutdown.
  • Image governance: Defines an image contract (toolchain, warmed caches, Sysprep/OOBE policy, no baked credentials) plus a fresh-VM smoke test before an image version is marked usable.
  • Use Case: You need to fix a Windows service permission bug in Screenpipe's src-tauri code. Dispatch an immutable task blob to a fresh VM from the validated image; it runs the native test, records the desktop, uploads evidence, opens a PR with the tested SHA and video link, then cleans up and shuts down.

Quick Start

Ask the agent to develop and test your Windows-native Screenpipe change on a disposable Azure VM from the validated dev image, providing the exact Git revision and acceptance criteria.

Frequently Asked Questions about develop-screenpipe-windows

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

FAQPage Schema
How do I test Screenpipe Windows-native changes without a local Windows machine?

Dispatch an immutable task blob to a disposable Azure VM created from the validated Screenpipe Windows dev image. The VM runs the native tests, records its console desktop, uploads evidence, pushes the branch, and opens a PR before shutting itself down.

How do I run native tests for Screenpipe's src-tauri code?

Run `bun run test:tauri <one-filter> -- --nocapture` from the repository. Never invoke raw Cargo or Tauri commands directly in `src-tauri`, as only repository-supported commands are permitted for native validation.

Can I use the live release builder or cross-compilation for Windows testing?

No. The workflow forbids developing or testing on the live release builder, cloning it as a fallback, or presenting cross-compilation as Windows evidence. Only a disposable VM from a validated dev image is acceptable.

What happens if no validated Windows dev image exists?

Stop and report that the one-time image build is required. Do not fall back to provisioning a cold VM per task or cloning the release runner; build, smoke-test, and publish an immutable image version first.

How are credentials handled on the disposable Windows VM?

No credentials are baked into the image. The VM's runtime managed identity reads only required Key Vault secrets and private task blobs, and it clears environment credentials and Codex auth state before shutdown.