xpz-daemon

Install and manage persistent XPZ monitors via Windows Task Scheduler.

11|3|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/GxBrasilNOficial/GeneXus-XPZ-Skills --skill xpz-daemon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: xpz-daemon
Source: https://github.com/GxBrasilNOficial/GeneXus-XPZ-Skills/tree/main/xpz-daemon
Command: npx skills add https://github.com/GxBrasilNOficial/GeneXus-XPZ-Skills --skill xpz-daemon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Instala e gerencia um monitor persistente de XPZ que sobrevive a reinicializações do sistema, garantindo que a sincronização ocorra sem intervenção, mesmo após reboot.

Core Features & Use Cases

  • Monitora uma pasta XPZ com um watcher em Windows Task Scheduler para disparar sincronizações automaticamente.
  • Mantém daemon persistente por KB, com controle de iniciar/parar e ver status.
  • Suporta instalação, atualização e remoção segura de daemons, com logs de operação para auditoria.

Quick Start

Install and start the XPZ daemon for the target KB to begin automatic monitoring.

Frequently Asked Questions about xpz-daemon

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

FAQPage Schema
How do I keep a Windows task scheduler daemon running after a system reboot?

To keep a Windows task scheduler daemon running after reboot, you need a persistent monitoring watcher that assigns a unique Task Scheduler name per KB and starts automatically, ensuring synchronization occurs without manual intervention across reboots.

What is a persistent XPZ monitor and how does it handle automatic synchronization?

A persistent XPZ monitor is a daemon that watches a target KB folder and triggers synchronization automatically. It manages its lifecycle through Windows Task Scheduler, surviving reboots to maintain continuous file monitoring without manual intervention.

Do I need administrative privileges to install a persistent daemon on Windows?

Yes, installing and managing a persistent daemon on Windows requires administrative privileges. Elevated access is necessary to configure Task Scheduler entries, assign unique names per KB, and ensure the watcher survives system reboots reliably.

How do I manage and monitor the status of a persistent Windows daemon per KB?

You manage a persistent Windows daemon per KB using control commands to start, stop, and check status. The system supports safe installation, updates, and removal of daemons, while generating operation logs for auditing purposes.

Does the XPZ daemon watcher work with other synchronization and builder workflows?

The XPZ daemon watcher coordinates with xpz-sync and xpz-builder workflows to provide reliable automatic synchronization. This integration ensures triggered file monitoring events properly feed into downstream synchronization and build processes.