Editor Support

⚠️ DEPRECATED: This documentation is outdated and has been archived. Orchestre no longer uses command files or editor-specific formats. All functionality is now provided through MCP tools that work natively with Claude Code. This file is kept for historical reference only.

Last Updated: Before v4.0.0 Status: Archived Reason: Orchestre moved to a pure MCP tool-based architecture

---

Editor Support (Historical)

Orchestre is designed to work with multiple AI-powered code editors. While Claude Code provides first-class support through the MCP protocol, Orchestre also supports Windsurf and Cursor through format conversion.

Supported Editors

✨ Claude Code - First-Class Support

Claude Code is Orchestre's primary platform with full MCP integration.

Features:

• Native MCP protocol support
• All 25 Orchestre commands work natively
• Real-time tool execution
• Multi-LLM orchestration
• Automatic state management

Installation: Commands are installed in .claude/commands/ directory.

🌊 Windsurf - Full Support

Windsurf support through workflow conversion when you specify the editor.

Features:

• Commands converted to Windsurf workflows
• Markdown-based format with front matter
• Natural language instructions
• Works with Cascade AI

Installation: Commands are installed in .windsurf/workflows/ directory.

↗️ Cursor - Full Support

Cursor support through MDC rule conversion when you specify the editor.

Features:

• Commands converted to Cursor rules
• MDC format with file pattern matching
• Context-aware execution
• Works in Agent mode (Cmd+K)

Installation: Commands are installed in .cursor/rules/ directory.

Editor Selection

Since development teams often use multiple editors in the same project, Orchestre asks you to specify which editor you're using. This ensures commands are installed in the correct format for each team member.

Specifying Your Editor

When using the install_commands or initialize_project tools, you can specify your editor:

// For Claude Code (default)
{ editor: 'claude' }

// For Windsurf
{ editor: 'windsurf' }

// For Cursor
{ editor: 'cursor' }

Format Conversion

Orchestre automatically converts commands to the appropriate format:

Claude Code Format (Original)

# Orchestre | Create New Project

Initialize a new project with template.

## Your Mission
Create a new project using the specified template.

Windsurf Format (Converted)

---
description: Initialize a new project with template
---

# /create

Initialize a new project with template.

## Purpose
Create a new project using the specified template.

## Completion
Inform the user of what was accomplished.

## Error Handling
Provide clear error messages and suggest fixes.

Cursor Format (Converted)

---
description: Initialize a new project with template
globs:
  - "*.ts"
  - "*.js"
  - "*.md"
alwaysApply: false
---

# Orchestre Command: /create

Initialize a new project with template.

## When user types /create

Execute the following...

## Context References
- Use @codebase to understand project structure
- Reference @.orchestre for orchestration state

## Error Handling
If the command cannot be executed...

Best Practices

1. Always specify your editor when installing commands or initializing projects
2. Teams can use different editors - each member installs commands for their preferred editor
3. Commands work the same regardless of editor format
4. Restart your editor after installing commands
5. Share the same codebase - editor-specific directories (.claude/, .windsurf/, .cursor/) can coexist

Limitations by Editor

Claude Code

• None - full feature support

Windsurf

• No direct MCP tool access (uses Cascade AI)
• Single AI model (no multi-LLM orchestration)

Cursor

• Commands only work in Agent mode (Cmd+K)
• Manual context management with @ references
• Single AI model

Roadmap

We're continuously improving editor support:

• Better conversion quality
• Editor-specific optimizations
• More editors coming soon