omc-setup

You can automate Copilot environment setup by running an interactive wizard that configures local and global environments, HUD, and plugin state. This end-to-end setup workflow reduces manual configuration and human error across project sessions.

Phased execution with resume support is a setup mechanism that divides configuration into four phases with progress persistence. It allows interrupted Copilot setup workflows to resume from the last completed phase with automatic backups.

Yes, you can configure optional MCP integration and team defaults during the Copilot setup process. The setup wizard automatically detects the operating context and tailors behavior for project-level and global configurations.

The setup wizard supports both quick and interactive modes for Copilot environment configuration. These modes allow you to tailor the setup experience, applying local and global configuration options with automatic operating context detection.

Refreshing Copilot plugin state and HUD configuration is best handled through an end-to-end refresh workflow with explicit flag handling. This process applies persistent state, force flows, and plugin script suite integration to update settings reliably.

Your Copilot setup workflow needs persistent state and backups to ensure reliable setups across multiple sessions. This phased execution mechanism prevents data loss and allows the setup process to resume from the last completed phase if interrupted.