orchestrator-monitor

To monitor orchestrator chunks from creation to completion, you can invoke orchestrator-monitor on your target chunks to automatically poll statuses and handle lifecycle transitions until completion.

Automated polling detects chunk status transitions such as RUNNING, NEEDS_ATTENTION, DONE, and FAILED, applying guardrails and managing the loop lifecycle to ensure automated progression.

To set up automated workflow monitoring for multiple chunks, you need a configured environment with ve orchestr commands and project root access to enforce guardrails and run recurring polling.

Yes, you can optionally post changelog updates automatically while monitoring chunk status, providing visibility and shepherding orchestrator-injected chunks throughout their lifecycle.

The best way to track workflow stalls during automated chunk processing is by using recurring polling to detect progress and stalls, which triggers automated handling of status transitions.

Orchestrator monitoring requires project root access to execute ve orchestr commands, enforce guardrails, and manage the automated loop lifecycle across multiple chunks within the configured environment.