client-compatibility

Detect Copilot platform and adapt agent spawning across CLI, VS Code, and other surfaces.

2|1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/PlagueHO/plagueho.learn --skill client-compatibility-plagueho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: client-compatibility
Source: https://github.com/PlagueHO/plagueho.learn/tree/main/.copilot/skills/client-compatibility
Command: npx skills add https://github.com/PlagueHO/plagueho.learn --skill client-compatibility-plagueho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects platform and adapts agent spawning across Copilot surfaces (CLI, VS Code, JetBrains, GitHub.com) to ensure reliable coordination and optimal tool usage.

Core Features & Use Cases

  • Platform detection through surface-specific tooling (CLI: task; VS Code: runSubagent/agent) to decide spawning strategy.
  • Adaptive spawning with parallelism and appropriate tool surfaces, ensuring consistent results across environments.
  • Use Case: Deploying a cross-surface assistant that coordinates multiple subagents in a single interaction, whether in CLI or VS Code.

Quick Start

Invoke the platform-aware coordinator to spawn a multi-surface agent setup appropriate for the current environment.

Frequently Asked Questions about client-compatibility

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect the Copilot platform and spawn agents across CLI and VS Code surfaces?

Platform detection identifies the current Copilot surface using CLI tools like task or VS Code tooling like runSubagent/agent. It then applies conditional logic to adapt agent spawning, model usage, and timing for deterministic cross-surface orchestration.

What is cross-surface agent spawning and when do I need it for orchestration?

Cross-surface agent spawning coordinates multiple subagents across different Copilot environments like CLI, VS Code, JetBrains, and GitHub.com. You need it when deploying an assistant that requires consistent subagent parallelism and tool usage regardless of the user's current platform.

Does agent spawning work with both VS Code runSubagent and CLI task tools?

Yes, cross-surface spawning supports both VS Code tooling via runSubagent/agent and CLI tools via task. Platform detection evaluates the available surface-specific tooling to decide the appropriate spawning strategy automatically.

What's the best way to coordinate subagents in a cross-surface Copilot environment?

The best approach is using a platform-aware coordinator that detects the active surface and applies conditional logic for spawning, model usage, and timing. This ensures adaptive parallelism and consistent orchestration results across CLI, VS Code, and other Copilot surfaces.

Why does my agent spawning fail when switching between Copilot CLI and VS Code?

Spawning failures often occur because platform-specific tooling like task or runSubagent is not universally available. Implementing platform detection with a fallback inline path ensures deterministic behavior and prevents failures across different Copilot surfaces.