Bridle

Unified configuration manager for AI coding assistants. Manage profiles, install skills/agents/commands, and switch configurations across Claude Code, OpenCode, Goose, Amp, Copilot CLI, and Crush.

Installation

Try it instantly (no install)

Run once without installing:

Install globally

For repeated use, install once:

Node package managers:

Other methods:

# Homebrew
brew install neiii/bridle/bridle

# Cargo
cargo install bridle

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

Quick Start

# Launch the TUI
bridle

# See what's configured across all harnesses
bridle status

# Create a profile from your current config
bridle profile create claude work --from-current

# Switch between profiles
bridle profile switch claude personal

"Package Manager" for your harness

With Bridle, you're able to install skills, agents, commands, and MCPs from any GitHub repository, similar to how Claude Code does it. With Bridle, however, you're not limited to just one harness; we auto-translate all the paths, namings, schemas, and configurations for you.

# Install from GitHub
bridle install owner/repo

# What happens:
# 1. Bridle scans the repo for skills, agents, commands, and MCPs
# 2. You select which components to install
# 3. You choose target harnesses and profiles
# 4. Bridle translates paths and configs for each harness automatically

Why this matters: A skill written for Claude Code uses ~/.claude/skills/. The same skill on OpenCode lives at ~/.config/opencode/skill/. MCPs follow different JSON/YAML schemas. Bridle handles all these differences for you.

Core Concepts

Harnesses are AI coding assistants: claude, opencode, goose, amp, copilot, crush

Profiles are saved configurations. Each harness can have multiple profiles (e.g., work, personal, minimal). Bridle copies the active profile's config into the harness's config directory when you switch.

Commands

Status & TUI

Profiles

Installing & Uninstalling

Configuration

Config keys: profile_marker, editor, tui.view, default_harness

Output Formats

All commands support -o, --output <format>:

• text (default) — Human-readable
• json — Machine-readable
• auto — Text for TTY, JSON for pipes

Configuration

Bridle stores its config at ~/.config/bridle/config.toml:

profile_marker = false  # Create marker files for debugging
editor = "code --wait"  # Editor for `profile edit`
default_harness = "opencode" # Which tab to open on launch

[active]
claude = "work"
opencode = "default"

[tui]
view = "Dashboard"      # Will add more later :P 

Supported Harnesses

Honorable Mentions

• Thank you Melvyn for pointing out my stupidity
• Thank you Theo for giving me a chance to show my work
• Thank you Kai for the help on GitHub Copilot CLI integration
• Thank you rari404 for the help on Crush CLI intergration

License

MIT