CLI overview
The barndog command runs on each developer's machine and delivers your organization's setup into native harnesses.
barndog is BarnDog's local client. It signs you in, chooses which harnesses to manage, installs and syncs assets, and lets you edit and review Skills from the terminal.
Organization setup, teams, repositories, and permissions are managed in the web workspace, not the CLI.
Commands
| Command | What it does |
|---|---|
barndog login | Sign in through your browser |
barndog logout | Revoke and remove this machine's credential |
barndog auth status | Show who you are signed in as |
barndog init | Choose the harnesses BarnDog manages |
barndog sync | Bring your harnesses in line with your selections |
barndog skills | Find, install, pull, and inspect published Skills |
barndog pull, status, diff, push, resolve | Edit a Skill and suggest the change |
barndog changes | Review and merge Suggested Changes |
Running barndog with no command starts first-time setup. If you're already set up, it shows where your configuration is.
Getting help
Every command has built-in help:
barndog --help
barndog help sync
barndog changes comment --helpOrigins
Many commands take --origin to say which scope owns an asset:
orgteam/<slug>repo/<slug>dev/<handle>mefor your own personal assets
You can also pass a scope's UUID, or the colon form such as team:engineering. See Core concepts.
Files
The CLI keeps everything for your user under ~/.barndog/. See Configuration files.