workflows

You can manage long-running shell commands by binding them to a named workflow with an optional port to monitor. This enables you to automate startup, inspect status, and handle lifecycle operations across background services and web servers.

Yes, persistent workflows support automatic restarts after package installations and module changes. This ensures your web servers and background services remain synchronized with the latest dependencies without requiring manual lifecycle intervention.

Configure persistent app workflows by defining a named workflow with its start command and an optional port to monitor. You can then start, stop, inspect status, and manage the lifecycle of processes across web servers, TUIs, and background services.

Yes, workflow orchestration enforces a YAML-frontmatter entry point in SKILL.md defining the name and description. It also supports optional scripts, references, and assets directories to provide runtime APIs for listing and managing lifecycle status.

The best way to coordinate lifecycle operations is to bind your tasks as managed workflows, enabling you to start, stop, restart, and inspect status across background services and TUIs. This centralizes control over persistent processes.