client-compatibility

Copilot orchestration across different surfaces requires detecting the current platform and applying adaptive spawning strategies. The client-compatibility approach automatically identifies your environment—whether CLI, VS Code, JetBrains, or GitHub.com—and selects the appropriate spawning logic for safe cross-surface execution.

Copilot platform detection identifies your active development environment to trigger adaptive spawning behavior. It works by selecting a surface-specific execution strategy, such as using VS Code runSubagent or falling back to inline execution when specific tools are unavailable.

Copilot spawning differs across surfaces to maximize native capabilities. VS Code receives specific adaptations including parallel subagents, session-model usage, and grouped scribe handling, while other surfaces like JetBrains and CLI use different conditional spawning logic tailored to their environments.

Safe Copilot orchestration when tools are unavailable is ensured through fallback inline execution. The adaptive spawning strategy detects missing platform-specific tools and automatically degrades to inline execution, preventing orchestration failures across CLI, VS Code, and GitHub.com.

Managing multi-surface Copilot tasks with varying timing scenarios is best handled through conditional spawning logic. This approach adapts the orchestration behavior based on the detected platform, ensuring synchronized execution across CLI, VS Code, and JetBrains environments.

Copilot orchestration failures when switching surfaces often occur because the spawning strategy is not adapted to the target platform. Implementing platform detection ensures the correct execution model—like VS Code runSubagent or inline execution—is applied for each specific environment.