How GSD's Multi-Runtime Support Works Across Claude Code, Gemini, Codex, Copilot, and More

Apr 21, 2026

I recently needed to set up GSD (Get Shit Done) across multiple AI coding assistants, and I discovered that one installer handles all 15+ runtimes. Here’s how it works.

The Problem: Multiple AI Assistants, One Workflow

If you’re like me, you switch between different AI coding assistants depending on the project or team requirements. Claude Code for one project, Gemini CLI for another, maybe Copilot or Codex somewhere else. Each has its own conventions and configuration locations.

The question I had: does GSD work with all of them, or am I locked into one runtime?

Single Installer, Multiple Runtimes

One command installs GSD for any runtime:

npx get-shit-done-cc@latest

The installer prompts you to select which runtimes you want. You can pick multiple in a single session.

For non-interactive installs, use runtime-specific flags:

npx get-shit-done-cc --claude --global
npx get-shit-done-cc --gemini --local
npx get-shit-done-cc --codex --global

Or install for all runtimes at once:

npx get-shit-done-cc --all --global

Runtime-Specific Command Syntax

Here’s where things get interesting. Different runtimes use different command invocation patterns:

Runtime	Command Syntax
Claude Code	`/gsd-command`
Gemini	`/gsd-command`
Copilot	`/gsd-command`
Qwen Code	`/gsd-command`
OpenCode	`/gsd-command`
Kilo	`/gsd-command`
Augment	`/gsd-command`
Trae	`/gsd-command`
CodeBuddy	`/gsd-command`
Codex	`$gsd-command`
Cline	`.clinerules` (no slash commands)

The same functionality works across all runtimes—only the invocation differs. For example, to get help:

# Claude Code, Gemini, Copilot, Qwen:
/gsd-help

# Codex:
$gsd-help

# Cline:
cat .clinerules

Same Core Content Across All Runtimes

Regardless of which runtime you choose, you get identical:

Agents: planner, executor, researcher, verifier, and more
Workflows: new-project, plan-phase, execute-phase, etc.
References: checkpoints, gates, model-profiles
Templates: PLAN.md, SUMMARY.md, etc.

The Runtime Abstraction Layer handles the differences in invocation patterns while keeping the core experience consistent.

Installation Locations by Runtime

Each runtime has its own configuration directory:

Runtime	Global Location	Local Location
Claude Code	`~/.claude/`	`.claude/`
Gemini	`~/.gemini/`	`.gemini/`
Codex	`~/.codex/`	`.codex/`
Copilot	`~/.github/`	`.github/`
Cursor	`~/.cursor/`	`.cursor/`
Windsurf	`~/.codeium/windsurf/`	`.windsurf/`
Cline	`~/.cline/`	`.clinerules`

The installer knows where to place files for each runtime automatically.

Skills vs Commands Format

Modern Claude Code (2.1.88+), Codex, and Qwen Code install GSD as skills using .claude/skills/gsd-*/SKILL.md. Older versions use the commands format (commands/gsd/*.md). The installer detects and handles both formats automatically—you don’t need to worry about compatibility.

Supported Runtimes

GSD currently supports 15+ runtimes:

Claude Code
OpenCode
Gemini CLI
Kilo
Codex
Copilot
Cursor
Windsurf
Antigravity
Augment
Trae
Qwen Code
Cline
CodeBuddy

The community has also contributed ports, though now they’re all natively supported via the unified installer.

Internationalization

If you prefer documentation in your native language, README translations are available:

Portuguese (README.pt-BR.md)
Chinese (README.zh-CN.md)
Japanese (README.ja-JP.md)
Korean (README.ko-KR.md)

My Take

The multi-runtime support is well-designed. I appreciate that I can use the same workflow concepts regardless of which AI assistant I’m working with. The command syntax differences are minor—once you know which pattern your runtime uses, it becomes second nature.

The installer’s ability to handle multiple runtimes in a single session is practical for developers who switch between tools. No need to remember different installation procedures for each platform.

Final Words + More Resources

My intention with this article was to help others share my knowledge and experience. If you want to contact me, you can contact by email: Email me

Here are also the most important links from this article along with some further resources that will help you in this scope:

👨‍💻 GSD GitHub Repository

Oh, and if you found these resources useful, don’t forget to support me by starring the repo on GitHub!