client-compatibility

Detects Copilot platform and adapts agent spawning for CLI, VS Code, and fallback surfaces.

2|Updated Jul 24, 2026
One-click install
npx skills add https://github.com/elbruno/ElBruno.MagenticUI --skill client-compatibility-elbruno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: client-compatibility
Source: https://github.com/elbruno/ElBruno.MagenticUI/tree/main/.squad/templates/skills/client-compatibility
Command: npx skills add https://github.com/elbruno/ElBruno.MagenticUI --skill client-compatibility-elbruno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Multi-agent orchestration behaves differently across Copilot surfaces (CLI, VS Code, JetBrains, GitHub.com) because each platform exposes different tools. Without platform detection, spawning logic, model selection, and SQL-based state tracking silently fail on non-CLI surfaces. ## Core Features & Use Cases - Platform Detection: Identifies the runtime surface by checking for the task tool (CLI), runSubagent/agent tool (VS Code), or neither (inline fallback mode). - Adaptive Spawning: Adjusts agent spawning per platform — drops agent_type, mode, model, and description parameters on VS Code, batches the Scribe agent last in parallel groups, and skips read_agent polling where results return automatically. - Feature Degradation Guidance: Provides a degradation table covering parallel fan-out, model selection, launch tables, and the CLI-only sql tool, directing cross-platform state to filesystem-based .squad/ files. - Use Case: A coordinator agent needs to fan out three subagents in parallel. On CLI it uses task with background mode and read_agent; on VS Code it issues three runSubagent calls in one turn and receives results inline. ## Quick Start Detect the current Copilot platform and spawn the worker agents using the correct tool and parameters for this surface.

Frequently Asked Questions about client-compatibility

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

FAQPage Schema
How do I detect which Copilot platform my agent is running on?▼

Check which tools are available before spawning. The task tool indicates CLI mode, runSubagent or agent indicates VS Code mode, and neither means fallback mode where you work inline without spawning.

How to spawn parallel subagents in VS Code Copilot?▼

Issue multiple runSubagent calls in a single turn with only the prompt parameter. They run concurrently automatically, results return inline, and you should drop agent_type, mode, model, and description parameters.

Does the sql tool work in VS Code or JetBrains Copilot?▼

No, the sql tool is CLI-only and does not exist on VS Code, JetBrains, or GitHub.com. Cross-platform workflows must use filesystem-based state in .squad/ files instead of SQL-dependent logic.

Can I select a specific model per subagent in VS Code?▼

No, per-spawn model selection only works on CLI. On VS Code, all subagents use the session model chosen in the model picker, so accept it and log the original intent instead of attempting fallback chains.

Why does fire-and-forget Scribe fail on VS Code?▼

VS Code subagents return results synchronously, so background fire-and-forget is impossible. Batch the Scribe agent as the last subagent in any parallel group, since its file-operation workload is light enough to tolerate blocking.