client-compatibility

Detect host surfaces and adapt agent spawning across CLI, VS Code, and inline fallbacks.

7|Updated Oct 24, 2020

Search Tags:#cli #subagents #coordinator #parallelism #vs-code #platform-detection #agent-spawning

Ready to run

npx skills add https://github.com/snow-jallen/HomeSpeaker --skill client-compatibility-snow-jallen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: client-compatibility
Source: https://github.com/snow-jallen/HomeSpeaker/tree/main/.copilot/skills/client-compatibility
Command: npx skills add https://github.com/snow-jallen/HomeSpeaker --skill client-compatibility-snow-jallen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Platform-agnostic coordinators must detect the host surface and adapt spawning behavior to use the correct tools (CLI task, VS Code runSubagent, or inline fallback) without manual reconfiguration.

Core Features & Use Cases

Platform Detection: determine CLI vs VS Code vs other surfaces and choose appropriate spawning strategy.
VS Code Spawn Adaptations: use runSubagent for parallel subagents, drop per-spawn model selection, batch Scribe as last, and inherit tools from parent.
Fallback behavior: operate inline when neither CLI nor VS Code tools are available.

Quick Start

Detect the current surface and spawn the appropriate agents automatically.

Frequently Asked Questions about client-compatibility

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

FAQPage Schema

How do I run parallel subagents across different Copilot surfaces like CLI and VS Code?▼

Platform detection identifies the host surface and adapts agent spawning to use the correct tools, choosing CLI task, VS Code runSubagent, or inline fallback automatically. It solves the problem of manually reconfiguring coordinators when switching between different Copilot environments.

How do I adapt agent spawning when switching between CLI and VS Code?▼

Adapt agent spawning by detecting the current surface and applying VS Code spawn adaptations like using runSubagent, dropping per-spawn model selection, batching Scribe as last, and inheriting tools from parent. Use CLI task when available, preferring it if both tools exist.

Does agent spawning work when neither CLI task nor VS Code runSubagent tools are available?▼

Yes, agent spawning operates via inline fallback when neither CLI task nor VS Code runSubagent tools are available. This safe fallback behavior allows the coordinator to continue functioning directly within the current surface without dedicated spawning tools.

What is the best way to handle platform detection for parallel agent execution?▼

The best way is using a platform-agnostic coordinator that detects the host surface and conditionally spawns agents, supporting parallelism and batching. It dynamically selects the correct available tools to execute parallel subagents across differing Copilot surfaces.

Why does my subagent coordinator fail to spawn agents correctly in VS Code?▼

Your subagent coordinator fails in VS Code if it lacks platform detection and attempts CLI-specific spawning. VS Code requires using runSubagent, dropping per-spawn model selection, batching Scribe as the last agent, and inheriting tools from the parent.