client-compatibility

Detect the platform and adapt agent spawning across CLI, VS Code, and fallback environments.

Updated Jan 5, 2026
One-click install
npx skills add https://github.com/Golnaz89/golnaz89.github.io --skill client-compatibility-golnaz89
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: client-compatibility
Source: https://github.com/Golnaz89/golnaz89.github.io/tree/main/.copilot/skills/client-compatibility
Command: npx skills add https://github.com/Golnaz89/golnaz89.github.io --skill client-compatibility-golnaz89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Platform detection and adaptive spawning for CLI vs VS Code vs other surfaces to ensure correct coordination across Copilot surfaces.

Core Features & Use Cases

  • Platform Detection: Identify whether the environment is CLI, VS Code, or a fallback surface and route spawning logic accordingly.
  • VS Code Spawn Adaptations: When in VS Code, spawn subagents in parallel and rely on session model behavior, omitting per-spawn options.
  • Fallback Mode: If neither CLI nor VS Code tools are available, execute tasks inline without spawning.
  • Cross-Platform Coordination: Maintain consistent coordination across surfaces like JetBrains and GitHub.com.

Quick Start

Detect the current platform and spawn agents using the appropriate tool for CLI, VS Code, or inline fallback.

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 current platform and adapt agent spawning across different environments?

Agent spawning in VS Code uses parallel subagents and session model behavior, omitting per-spawn options to match the editor's native execution flow. This ensures correct coordination within the VS Code surface.

What happens to agent spawning when neither CLI nor VS Code tools are available?

When neither CLI nor VS Code tools are available, the system enters fallback mode and executes tasks inline without spawning subagents. This maintains coordination when standard platform tools are absent.

Does cross-platform coordination maintain consistent behavior across CLI, JetBrains, and GitHub.com?

Yes, cross-platform coordination maintains consistent behavior across CLI, VS Code, JetBrains, and GitHub.com by applying compatibility adjustments during cross-surface orchestration.

What's the best way to handle cross-surface orchestration for Copilot agents?

The best way to handle cross-surface orchestration is to detect the active platform and apply conditional spawning rules, ensuring agents spawn correctly on CLI, VS Code, or execute inline as a fallback.