bridle

Bridle is a unified configuration manager for AI coding assistants. It lets you install, manage, and switch between profiles across multiple harnesses (Claude Code, OpenCode, Goose, Amp, Copilot CLI, and Crush) by translating and aligning MCPs, skills, and commands for each target harness. The tool provides a TUI interface and a suite of commands to inspect current configurations, create and switch profiles, and install new skills or MCPs from GitHub repositories. Using Bridle, you can centrally orchestrate your AI development environment, ensuring that the same intent (e.g., a particular MCP or skill) works consistently across different coding assistants.

To get started, launch the Bridle CLI to view the TUI, check which harnesses are configured, and observe the status across all profiles. You can create a new profile from your current setup, switch between profiles for different harnesses, and install new components from GitHub repositories. Bridle handles the translation of paths, schemas, and configurations for each harness so you don’t have to manually map them yourself. This makes it easier to reuse skills or MCPs across environments and maintain consistent behavior when working with Claude Code, OpenCode, Goose, Amp, Copilot CLI, or Crush.

Key capabilities include: status visibility across all harnesses, interactive profile creation and switching, a core installation workflow to pull skills/agents/commands/MCPs from GitHub, and automatic adaptation of these components to each target harness. The tooling abstracts away the differences in how each harness stores and expects MCPs and skills, so you can focus on building and reusing AI-assisted workflows rather than managing boilerplate configuration per harness.

Prerequisites:

• A supported runtime: Rust toolchain for Cargo-based installations or Node.js for the npx-based quick start. Ensure you have the appropriate tools installed on your system.
• Optional: Homebrew if you want to install via Brew on macOS.

Install methods:

1. Quick start (no install) with npx (recommended for trying Bridle):

• Prereqs: Node.js and npm installed
• Command:

npx bridle-ai

2. Global Node.js installation for repeated use:

• Prereqs: Node.js and npm installed
• Command:

npm install -g bridle-ai

3. Quick try with Bun or PNPM variants (builds are supported):

bunx bridle-ai
pnpm dlx bridle-ai

4. Install Bridle globally via alternative package managers and methods:

• Homebrew (macOS):

brew install neiii/bridle/bridle

• Cargo (Rust):

cargo install bridle

• From source (build from GitHub):

git clone https://github.com/neiii/bridle && cd bridle && cargo install --path .

Notes:

• The npx/pnpm/bunx quick-start path is ideal for trying Bridle without a full install. For long-term usage, consider the Cargo-based or Homebrew installations depending on your environment and preferred tooling.
• After installation, you can access Bridle via the bridle CLI to manage harnesses, profiles, and MCPs across supported environments.

Tips and considerations:

• Bridle translates and normalizes MCPs, skills, and commands across multiple harnesses, so a component originally written for Claude Code can be used with other harnesses by Bridle without manual reconfiguration.
• Common environments and MCP storage locations differ across harnesses (e.g., Claude Code uses ~/.claude/skills, OpenCode uses ~/.config/opencode, etc.). Bridle handles these mappings for you.
• When installing from GitHub, Bridle scans the repository for available skills, agents, commands, and MCPs and prompts you to select components to install for the desired harnesses and profiles.
• All commands support output formatting options (-o, --output) including json for machine-readable results.
• If you encounter issues, ensure your PATH includes the Bridle executable and that you have the required runtimes for your chosen install method (Node.js for npx, Rust toolchain for Cargo, etc.).
• Environment variables are not strictly required by Bridle by default, but you may configure editor preferences or default harness via bridle config set commands.