Barndoor Bridge is in Early Access. These pages are not listed in the navigation. Overview:
/how-tos/barndoor-bridge/overview · Using Bridge: /how-tos/barndoor-bridge/using-bridge · Install with MDM: /how-tos/barndoor-bridge/install-with-mdm · Client settings: /how-tos/barndoor-bridge/client-settings · Publish a local MCP: /how-tos/barndoor-bridge/publish-local-mcp · Release notes: /how-tos/barndoor-bridge/release-notesWhat it is
Barndoor Bridge is the endpoint half of the Barndoor platform: software on a developer’s Mac that puts AI coding sessions under the organization’s governance. The platform’s admin UI, LLM Gateway, policy service, data protection, and audit are the cloud half; Bridge is how that control reaches the laptop. It ships as one signed, notarized macOS installer,Barndoor.app, containing two parts:
- The Bridge app. A window and menu-bar item that handles sign-in, keeps configuration synced, and launches a governed Claude Desktop or Codex Desktop with one click. It appears as Barndoor in Applications, the Dock, and the menu bar.
- The
barndoorCLI. The governed launcher and local tool gateway underneath the app. Developers can also use it directly from a terminal to start Claude Code, Codex, or Kilo.
The current stable release is v0.1.218, from November 2, 2026. It needs macOS 15 Sequoia or later. See the release notes for what changed.
What it does
Without Bridge, Claude Desktop and Codex talk to their vendors and to whatever MCP servers the user configured locally. Barndoor never sees the session, cannot apply policy, and cannot route traffic through the organization’s LLM Gateway. With Bridge:1
Sign in
The user signs into Barndoor from the app. Sign-in opens the browser and completes with the organization’s identity provider.
2
Sync
Bridge pulls the organization’s list of connected MCP servers onto the laptop at sign-in, then about every five minutes while signed in. It also caches a signed policy bundle, used only as a fallback for local tool calls if the platform cannot be reached.
3
Launch
One click starts Claude Desktop or Codex Desktop in a Barndoor-managed profile. Model traffic goes through the organization’s LLM Gateway. Calls to the organization’s remote MCP servers go through the Barndoor platform, where policy, data protection, confirmations, and audit apply. Calls to local tools are checked against the platform’s policy service at call time before they run on the laptop.
Model traffic
When a client runs through Bridge, model calls go to a loopback credential broker on the laptop, which forwards only to the organization’s Barndoor LLM Gateway. There:- Model Access decides which Model Routes the session may use. At launch, the client’s default and per-family models are filled with the newest route the user is allowed; see Client settings;
- policy and data protection run on every request and response;
- every call is audited with the user, client, and agent identity attached.
Tool traffic
Bridge runs a local MCP gateway that the client sees as its only tool server. Agents interact through a small set of meta-tools (search tools, describe tools, execute a tool, list servers, confirm an action, help). Behind that surface Bridge exposes:- Remote servers the organization has connected on the platform (Salesforce, Jira, GitHub, Slack, and the rest of the registry). These calls are routed through the Barndoor platform, with the platform’s OAuth, per-agent policy, data protection, and audit applied there.
- Local providers built into Bridge, which run on the laptop once the organization installs them: Kubernetes, ArgoCD, CloudNative-PG, Docker, Terraform, Playwright, GitHub, Git, Shell, Filesystem, PostgreSQL, and Google Cloud.
- Local MCP servers your organization builds, signed by you and pinned through MDM. See Publish your own local MCP server. Installing a local MCP server makes it available; each person turns it on with Connect in My MCP Servers, unless you install it for everyone.
- Bundled skills, exposed as MCP tools and prompts. A curated set is on by default and the rest are opt-in.
shell/shell_exec, with the command text in the record. Bridge refuses only the commands you block with Deny command patterns in client settings; gh, git, curl, and every other command run otherwise. In Claude Desktop’s Cowork, this is the only shell.
What every governed launch enforces
Your organization’s client settings are the only restriction on a governed session. They decide, per client, which of its own native tools stay on: files, shell, network, browser, secrets, skills, and subagents. By default every native tool is on, exactly as the client ships. Bridge has no restriction levels of its own, and developers cannot loosen the settings from the command line. Whatever the settings say:
Launches fail closed. If the installed client does not match what Barndoor has reviewed, if a workspace carries a competing configuration, or if the user is allowed no model that fits the client, Bridge refuses to start rather than launching ungoverned.
At a glance
Other MCP clients such as VS Code and Cursor can add Barndoor as a remote MCP server today. That governs MCP calls only, not the client’s own terminal, and it is not a Bridge launch.
Coming in GA
The EAP is scoped to macOS and developers. The general-availability release is planned to extend Bridge in these directions. Scope and timing can change.Before you install
Bridge does not govern anything on its own. It routes Claude and Codex through your Barndoor organization, so that organization has to be configured before the first Mac gets the package. A laptop with Bridge installed and nothing behind it will sign in, sync an empty server list, and then refuse to launch. Work through these in the admin UI first. The right column is what the developer sees if you skip one.The gateway routes Bridge needs
Developers keep their own Claude subscription. Bridge takes that credential from the laptop and attaches it to each request; your gateway forwards it to Anthropic. In LLM Management this is the Anthropic OAuth provider, added from the Providers tab, where there is no API key to store, and then attached to a Model Route carrying the Claude models you want available. See Anthropic OAuth passthrough.
Models and client settings
There is no profile to create. Two things decide what a governed session gets:- Model Access decides which models each developer may use. At launch, Claude Code’s default, Opus, Sonnet, Haiku, and Fable models are each filled with the newest allowed route of that family, and Claude Desktop lists every allowed Claude route. Check Model Routes: badges such as Claude Code · Opus show which route fills what.
- Client settings, under LLM Management → Client settings, decide which native tools stay on, once for Claude Code and once for Codex.
Values IT will be asked for
These go into the MDM profiles at render time, and re-rendering later reissues the profiles, so collect them now.
Once those are done, continue to Install with MDM.
Download
The current stable release is a signed, notarized macOS installer on Barndoor’s download host:- Package: https://downloads.barndoor.ai/barndoor-gui/latest/Barndoor.pkg
- Checksum: https://downloads.barndoor.ai/barndoor-gui/latest/Barndoor.pkg.sha256
- MDM kit for IT: https://downloads.barndoor.ai/barndoor-gui/latest/barndoor-mdm-kit.tar.gz
Stable and edge
Bridge has two release channels:
The download links above and
barndoor update-gui always follow stable. To put a pilot group on edge, see How updates work.
Requirements
- A Mac on macOS 15 Sequoia or later.
Barndoor.appdoes not open on earlier releases. - Barndoor.app installed by IT, or a one-off
.pkgfor a lab machine. - A Barndoor account in the organization the Mac is pinned to.
- Claude Desktop 2.2553.0 or later for Launch Claude Desktop. Bridge refuses an older one with
Claude Desktop <version> predates the governed adapter minimum 2.2553.0. - The ChatGPT desktop app with Codex, plus the Codex policy that MDM installs, for Launch Codex Desktop. Kilo Desktop or the Kilo Code extension in VS Code for the Kilo buttons. All optional.
- Bridge launches these apps; it does not install them.
- The organization’s LLM Gateway configured with at least one enabled route that the developer’s Model Access allows. See Before you install.