Bridle CLI
Bridle keeps configuration profiles for Claude Code, OpenCode, Goose, Amp and Copilot CLI and installs skills and MCP from GitHub.
- 442 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Rewrites assistant configurations when profiles switch.
- Installs skills and MCP servers from any GitHub repository, whose content needs review.
Install
- Works in
Manual install
npx bridle-aiThe first README command: run without installing. For repeated use the README also lists `npm install -g bridle-ai`, Homebrew and Cargo.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Rewrites assistant configurations when profiles switch.
- Installs skills and MCP servers from any GitHub repository, whose content needs review.
This is third-party code. Review the repository files before installing.
What it does
Bridle is a configuration manager for terminal AI assistants with a TUI. It creates profiles per tool, such as `work` and `personal`, and switches them with `bridle profile switch`. A profile can be captured from current settings with `--from-current` and compared with another through `profile diff`. The `bridle install owner/repo` command scans a repository for skills, agents, commands and MCP servers, lets you pick components and target tools, then translates paths and config schemas itself. So a skill for `~/.claude/skills/` also lands in the OpenCode, Goose, Copilot CLI or Crush directory. Every command can print JSON.
Who it is for. Developers who keep several AI assistants with work and personal setups and are tired of copying skills and MCP servers between their directories by hand.
Good fit when
- A work and a personal Claude Code profile must switch with one command.
- A skill from a GitHub repository is needed in both Claude Code and OpenCode.
- You want to see the difference between two profiles before editing settings.
- A script must read assistant state as JSON through `-o json`.
Not a fit when
- You use one assistant with one setup.
- You need Claude Code marketplace plugins with auto-update.
- The source repository has not passed your security review.
Example request
Create a claude work profile from current settings, install the skill from this GitHub repository into it and show the diff with the personal profile.Limitations
The `bridle uninstall` command is marked experimental in the README. The path table shows not every tool supports agents and commands: Goose and Crush have none. Bridle copies the profile into the assistant directory on switch, so edits made outside the profile are easy to overwrite. The author states no content checks for third-party repositories: read skills and MCP configs before installing. A profile is copied into the assistant directory as a whole, so capture the current state with `--from-current` before the first switch.
How to disable. Uninstall the `bridle-ai` package or run `brew uninstall`, and clear `~/.config/bridle/` by hand. Assistant configuration stays in the last active profile.
FAQ
Which assistants are supported?
Claude Code, OpenCode, Goose, Amp, Copilot CLI and Crush.
How do I install a skill from GitHub?
`bridle install owner/repo` scans the repository, offers components and target profiles and translates paths for each assistant. `--force` overwrites existing installs.
How do I make a profile from current settings?
Run `bridle profile create claude work --from-current`. Switch with `bridle profile switch claude personal`.
Where is configuration stored?
In `~/.config/bridle/config.toml`. Keys: `profile_marker`, `editor`, `tui.view`, `default_harness`.
Is there output for scripts?
Yes. The `-o json` flag prints machine-readable results, and `auto` picks text for a terminal and JSON for a pipe.
Discussion
No questions or reviews yet.
Related
CLI toolsA Go CLI that switches Claude Code profiles with one command, swapping settings, CLAUDE.md and MCP servers together with a backup.
The author's personal Claude Code toolbox: meta-prompt and todo commands, skills to create skills, hooks and MCP servers, auditors and a Ralph loop
Claude Bootstrap and Maggy: config pack and routing server
Claude Bootstrap + Maggy
A pack of skills, hooks and rules for Claude Code with enforced tests and cross-session memory, plus a local server that routes work across models
A CLI that deploys managed Claude Code instructions to a project, previews file changes and can undo the installation.
A meta-skill for Claude Code that turns a domain description into an agent team and the skills it uses, using six team-architecture patterns
CCS
CCS - Claude Codex Switch
A CLI that switches Claude Code between accounts, providers and local models without editing configs
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Bridle (this card) | no | 442 | |
| Skills Manager | no | 1,056 | a desktop app for skills across several agents; Bridle works in the terminal and adds settings profiles and MCP schema translation |
| CC Switch | no | 151,986 | switches providers and manages MCP and skills in a desktop app; Bridle keeps profiles in the terminal and installs components from GitHub repositories |
README in short
Bridle acts as a package manager for assistants: it scans a source, translates paths and config schemas and writes components into the chosen tool's profile.