Skip to content

Works with the agents you already use

Configure your company’s AI coding environment once. Ship it to every harness.

BarnDog is a shared workspace where developers build, review, and version Skills, MCP configurations, and Hooks, then sync them into Claude Code, Codex, and Cursor.

~/work/dashboard
barndog skills install code-review --origin team/platform BarnDog sync   Installed  Claude Code ~/.claude/skills/code-review  Installed  Codex       ~/.agents/skills/code-review  Installed  Cursor      ~/.cursor/skills/code-review Sync complete. 3 installedRestart your harness to pick up the changes.
Delivers natively into
  • Claude Code
  • Codex
  • Cursor
  • OpenCodesoon
  • Gemini CLIsoon

What BarnDog does

Your team’s agent setup, managed like the rest of your code.

BarnDog sits above the tools your developers already use. It is not another agent, IDE, or chat window.

One environment, every harness

Pick the recommended setup from your organization, team, and repository, add the extras you like, and BarnDog writes it into each tool’s native format.

  • One machine-wide configuration in ~/.barndog/config.yaml
  • Enable, disable, or exclude assets without touching shared content
  • barndog sync follows every published update

Built together, like code

Skills and Hooks get versions, Suggested Changes, inline review, and protected merges. Work in your editor or in the browser, whichever suits you.

  • Immutable published versions: v1, v2, v3…
  • Line comments and one-click reviewer suggestions
  • Team merge rules, with direct publishing for admins

Skills

Packages of instructions, references, and scripts your agents load on demand. Every Skill keeps its full history.

code-review/
├─ SKILL.md
├─ references/
└─ scripts/

MCP configurations

Connection definitions for organization, team, and personal MCP servers. Definitions hold secret names, never secret values.

name: github
transport: http
env: [GITHUB_TOKEN]

Hooks

When an event happens, run a command. Compatibility is declared per harness, so nothing claims to work where it doesn’t.

event: after_file_edit
run: prettier --write
claude ✓ · codex ✓ · cursor ◐

How collaboration works

From your editor to every teammate’s agent.

No local Git commits required. Each push becomes one Suggested Change that your team reviews like a pull request.

  1. Pull a Skill into a folder

    barndog skills pull code-review --origin team/platform
  2. Edit it in your own editor

    barndog diff
  3. Suggest the change

    barndog push --title "Clarify the checklist"
  4. Review and merge, in the browser or the terminal

    barndog changes merge 42 --revision 2
  5. Everyone gets the new version

    barndog sync

code-review · Suggested Change #42 · revision 2

Clarify the review checklist

SKILL.md

6 ## Checklist
7−- Check the tests.
7+- Run the tests and note any that are skipped.
8+- Flag public API changes in the summary.
Maya

Nice. Could line 8 link to our API guidelines?

1 approval· ready to mergeMerge

Scopes

Assemble your setup from the scopes you work in.

Each organization, team, repository, and developer can share assets and mark them recommended or optional. Nothing is installed until you choose it.

  • orgrecommendedsecure-codinggithub
  • team/frontendrecommendedreact-guidelinesfigmagithub
  • repo/dashboardallformat-after-edit
  • meindividualdebug-react

Your environment

Deduplicated by identity, synced to every selected harness.

  • secure-codingSkill
  • react-guidelinesSkill
  • debug-reactSkill
  • githubMCP
  • figmaMCP
  • format-after-editHook

github comes from two scopes and installs once. Disable a team’s set and anything another scope supplies stays put. Switch teams, and only team selections change.

Principles

Keep your harness

Developers keep using Claude Code, Codex, and Cursor directly. BarnDog configures them; it never replaces them.

Never overwrites your work

Sync only touches what it installed. Collisions and hand edits stop the sync instead of being replaced.

Secrets stay on your machine

Shared definitions name the variables they need. Credentials stay local or in each harness’s own sign-in.

Self-host when you need to

Point the CLI at your own server once. Normal commands never need a server flag again.

Give every developer the same great agent setup.

BarnDog is in early access. Join the waitlist, or read the docs to see how it works.