cancel

To cancel an active OMG automation workflow, run the cancel command to detect the running mode from local state and execute an orderly shutdown. It reads `.omg/state/` to identify the active mode and clears state files in dependency order to prevent leftover loops.

Dependency-aware cleanup stops automated process orchestration by canceling workflows in a specific dependency order, such as OMG Autopilot first, then linked parallel execution or QA cycling loops, ensuring no background automation processes are left running.

State cleanup preserves resumable data when aborting autopilot workflows by retaining state files for OMG Autopilot and Self-Improve modes while clearing all other temporary execution state. This allows you to safely abort active loops and resume them later.

Yes, you can force a full state wipe when aborting OMG automation modes by passing the `--all` flag for a nuclear cleanup. The `--force` flag is also available for immediate cancellation, overriding the default smart cancellation behavior.

To stop parallel execution and QA cycling without breaking workflow state, use the default smart cancellation. It detects the active mode from `.omg/state/` and safely clears temporary files while preserving resumable state for supported workflows.

You should use force cancellation over smart cancellation for workflow control when an automation mode is unresponsive and default state cleanup fails to stop the process. The `--force` flag bypasses orderly shutdown, and `--all` completely wipes local state files.