CLI Reference
The braid CLI installs and manages rules, skills, hooks, workflows, and sub-agents across your local AI coding tools.
For marketplace installs, the CLI uses the same local-file pipeline. Buy or claim a pack in Braid, then run braid marketplace install <slug>.
Usage
braid <command> [options]Commands
| Command | Description |
|---|---|
install | Install prompts to your coding tools |
auth | Authenticate with braid |
manage | Open the local prompt manager |
scope | Configure which profiles and projects to install from |
scaffold | Scaffold a manifest-backed pack repo |
list | List installed prompts |
update | Update installed prompts to latest versions |
remove | Remove installed prompts |
rules | Create, update, and manage rules |
skills | Browse skills available to install from braid |
profiles | Manage profiles |
projects | Manage projects |
sub-agents | Manage sub-agent configurations |
references | Manage rule reference files |
marketplace | Browse and install marketplace packs |
demo | Manage local demo session context |
rollback | Roll a marketplace install back in braid.lock |
retract | Unpin a locked marketplace version locally |
Command coverage by entity
- Sub-agents are managed through
braid sub-agents. - Skills have a discovery command group at
braid skills, withbraid skills listas the current subcommand. - Workflows do not currently have a dedicated
braid workflowscommand group. They are installed throughbraid installand authored locally withbraid scaffold. - Hooks do not currently have a dedicated
braid hookscommand group. They are authored withbraid scaffold --type hookand managed locally throughbraid manage.
Global options
| Option | Description |
|---|---|
--version | Show CLI version |
--help | Show help for any command |
-s, --server <url> | Custom server URL (review apps, local dev) |
Configuration
The CLI reads from two config files:
braid.json— project-level config, committed to version controlbraid.user.json— user-level overrides, gitignored
Both are created by braid scope.