> ## Documentation Index
> Fetch the complete documentation index at: https://docs.barndoor.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Barndoor Bridge release notes

> What changed in each stable Barndoor Bridge release: new features, changes admins need to act on, and known limits.

> [!NOTE]
>
> 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-notes`

These notes cover **stable** releases, the channel customer fleets follow. Edge builds between them are not listed. See [Release channels](https://docs.barndoor.ai/how-tos/barndoor-bridge/install-with-mdm#4-how-updates-work).

## v0.1.218

**Stable from November 2, 2026.** Replaces v0.1.210. Coming from v0.1.96? Read the [v0.1.210 notes](#v0-1-210) too; their changes apply as well.

> [!WARNING]
>
> **Bridge v0.1.218 needs macOS 15 Sequoia or later.** `Barndoor.app` does not open on macOS 14 Sonoma or earlier. Check your fleet before it updates: the MDM updater installs the new version on every Mac it targets. The `barndoor` CLI on its own still runs on macOS 13 Ventura or later.

To check a Mac:

```bash theme={null}
sw_vers -productVersion
# 15.0 or later
pkgutil --pkg-info ai.barndoor.app | grep version
# version: 0.1.218
```

### Before you roll it out

* **Move Macs to macOS 15 or later first.** See the warning above.
* **Expect the Codex policy on every managed Mac.** The updater script now installs it whether or not provider lockdown is on. That adds **Launch Codex Desktop**, and makes `codex` in a terminal, and Codex in the ChatGPT app opened directly, work only through Barndoor. If your fleet ships its own `/etc/codex/requirements.toml`, opt out first, because the updater replaces it. See [The Codex policy is installed on every managed Mac](#the-codex-policy-is-installed-on-every-managed-mac).
* **Replace your copy of the updater script.** MDM consoles run the script text you pasted. The new Codex policy behaviour is in the script, so it applies only once you paste the current [`install-latest.sh`](https://downloads.barndoor.ai/barndoor-gui/mdm/install-latest.sh).

### What's new

* **Servers tab.** The Bridge window has a **Servers** tab again, listing each MCP server with its status and, when something is wrong, what to do next. Blocked servers come first, and the Status tab links to it when a server needs attention. `barndoor list --json` gives the same information in a terminal.

  ![The Barndoor window with Status, Servers, and Logs tabs; the Status tab shows Connected, Environment prod, Authenticated yes, Servers 36, and Last sync: Synced 36 servers (16 remote, 18 embedded)](https://mintcdn.com/barndoor/0bFGCBNQXYdMP58U/images/barndoor-bridge/bridge-window-servers-tab.png?fit=max\&auto=format\&n=0bFGCBNQXYdMP58U\&q=85\&s=d5156fb9c3d51c26faa39af1f7239df6)

* **Local MCP servers show why they failed.** When a local MCP server your organization published exits during startup, Bridge now shows the last lines of the server's own error output instead of only "managed server failed to start". The full output is saved to `~/Library/Logs/Barndoor/local-mcp/<slug>.log`, with credentials redacted.

* **`barndoor local-mcp package`** turns an MCP server published on npm or PyPI into one self-contained binary per Mac architecture, tests each over stdio, and prints the command to sign it. See [Publish your own local MCP server](https://docs.barndoor.ai/how-tos/barndoor-bridge/publish-local-mcp).

* **`barndoor local-mcp install`** installs a published local MCP server for your organization from a terminal or CI pipeline, without the admin UI. It can be run on every release. `--availability required` or `opt_in` needs platform v2.53 or later. Setting the server's policy is still done in the admin UI.

* **`barndoor local-mcp exec`** runs a local MCP server's one-time setup command, such as Auth0's `init` sign-in, through the same signed binary Bridge launches:

  ```bash theme={null}
  barndoor local-mcp exec auth0 init --read-only --no-interaction
  ```

  It runs only setup commands the publisher listed when signing the server, and each run is recorded in your audit log. Publishing a server that lists setup commands needs Barndoor platform v2.54.0 or later.

* **Import Claude Sessions is gone from the Bridge window and menu bar.** Bring Claude Desktop chats, Cowork tasks, Code sessions, and claude.ai history over with **Settings → Import** in the Claude Desktop that Bridge launches. Claude Code history from `~/.claude` comes over with `barndoor sessions import` in a terminal.

* **A crashed Bridge session no longer breaks Claude Desktop.** If Bridge was stopped without cleaning up, for example at logout, Claude Desktop opened directly used to keep trying Barndoor's old profile. Bridge now removes it the next time it starts, on every `barndoor run`, and from `barndoor doctor`.

### Changes for admins

#### macOS 15 or later

`Barndoor.app` now needs macOS 15 Sequoia or later and does not open on older releases. Update those Macs, or keep them out of the updater script's targets until they are updated. The bundled CLI still runs on macOS 13 Ventura or later.

#### The Codex policy is installed on every managed Mac

In v0.1.210 the updater script installed the Codex policy, `/etc/codex/requirements.toml`, only where provider lockdown was on, so most fleets never saw **Launch Codex Desktop**. Now the script installs it on every Mac it runs on, and keeps it current. The Claude policy still follows provider lockdown.

What that means on each Mac:

* **Launch Codex Desktop** appears in Bridge when Codex Desktop is installed at `/Applications/ChatGPT.app`.
* `codex` in a terminal, and Codex in the ChatGPT app opened directly, refuse to run outside Barndoor. `barndoor run codex` and **Launch Codex Desktop** work. Tell people before you roll it out.
* **A fleet's own requirements file is replaced** on every run. If you ship your own Codex requirements, opt out.

To opt a fleet out, run the updater with `--no-codex-desktop-policy`, or set `BARNDOOR_MDM_CODEX_DESKTOP_POLICY=0` in its environment. That removes only a file Barndoor wrote, and **Launch Codex Desktop** is no longer offered.

When the file is missing, Bridge and `barndoor codex-desktop-policy verify` now point at your device management instead of asking the user to install it:

```text theme={null}
Error: the Codex requirements file /etc/codex/requirements.toml is missing; your organization's device management installs it (the Barndoor MDM kit installs it on every managed device), and an administrator can install it by hand with `barndoor codex-desktop-policy install` with sudo
```

If one policy fails to install, the updater still installs the others, then exits non-zero.

#### Use plain `barndoor` in a terminal

The package links the bundled CLI at `/usr/local/bin/barndoor`, so `barndoor` works in a terminal without the full path. An older standalone `barndoor` that comes earlier on your `PATH`, for example one in `~/.local/bin`, takes precedence and cannot read the configuration Bridge writes. Check with `which -a barndoor`, and remove the older one.

### Known limits

The [v0.1.210 known limits](#known-limits-in-v0-1-210) still apply. No Windows build ships in this stable release.

## v0.1.210

**Stable from November 1, 2026.** Replaces v0.1.96. Managed Macs pick it up on the next run of the MDM updater script; nothing needs re-uploading.

![The Barndoor window's Status tab after the upgrade: Connected, Environment prod, Authenticated yes, 36 cached servers, Last sync: Synced 36 servers (16 remote, 18 embedded), Version v0.1.210](https://mintcdn.com/barndoor/0bFGCBNQXYdMP58U/images/barndoor-bridge/bridge-window-v0.1.210.png?fit=max\&auto=format\&n=0bFGCBNQXYdMP58U\&q=85\&s=99cffc14b994d90c1fc287b5f0b20360)

To check a Mac:

```bash theme={null}
pkgutil --pkg-info ai.barndoor.app | grep version
# version: 0.1.210
/Applications/Barndoor.app/Contents/Helpers/barndoor version
# v0.1.210 (cli release v0.1.280)
```

### Before you roll out v0.1.210

* **Update Claude Desktop to 2.2553.0 or later.** Older versions are refused at launch. See [Minimum Claude Desktop](#minimum-claude-desktop-version).
* **Review your client settings.** They are now the only thing that restricts a governed session. See [Client settings are the only restriction](#client-settings-are-the-only-restriction).
* **Decide whether you want Launch Codex Desktop.** It appears only on Macs with the Codex policy, which the updater installs only when provider lockdown is on. See [Launch Codex Desktop needs the Codex policy](#launch-codex-desktop-needs-the-codex-policy). Changed in v0.1.218.

### What's new

* **Kilo Code.** Bridge launches Kilo through Barndoor: **Kilo Code** (Kilo Desktop) and **Kilo Code (VS Code)** appear on the Status tab when they are installed, and `barndoor run kilo` starts the Kilo CLI. Kilo can use a ChatGPT subscription route once your organization is on Barndoor platform v2.53.

* **Codex Desktop.** **Launch Codex Desktop** opens Codex with no welcome screens, a model picker that lists only your allowed models, and history kept between launches. If ChatGPT rejects your sign-in, Bridge offers to sign in again. Codex Desktop needs the Codex policy; see [below](#launch-codex-desktop-needs-the-codex-policy).

* **Launches show their models.** Every governed launch prints the model Barndoor picked for each slot, for example:

  ```text theme={null}
  barndoor: models - Default: claude-opus-5-5 (1M) | Opus: claude-opus-5-5 (1M) | Sonnet: claude-sonnet-5-5 (1M) | Haiku: claude-haiku-4-5-20251001 | …
  ```

* **Claude Desktop shows real model names.** Its model picker lists the Claude models your organization allows, by name, including 1M-context versions.

* **Everyday command-line tools work through Barndoor's shell.** `gh`, `git`, `bash`, `curl`, `jq`, `python`, and the rest now run through Barndoor's shell tool, subject to your policies. Earlier releases refused a built-in list of these everywhere, which left Cowork in Claude Desktop with no usable command line.

* **Codex terminal sessions** get a normal shell with network access.

* **Your own local MCP servers.** Your organization can publish, sign, and pin its own local MCP servers, and Bridge runs them. See [Publish your own local MCP server](https://docs.barndoor.ai/how-tos/barndoor-bridge/publish-local-mcp).

* **Questions and notices appear in the Bridge window** instead of separate system dialogs.

* **Clearer errors.** Bridge shows the gateway's error message instead of raw JSON, says what to fix when a launch cannot start, and reports an expired Claude or ChatGPT sign-in as a sign-in problem rather than an outage. The sign-in page shown after you authenticate in the browser now matches what actually happened.

* **Smaller download.** The installer is about half the size of v0.1.96.

### Changes for admins

#### Client settings are the only restriction

Postures are gone. What a governed session may do now comes only from your organization's [client settings](https://docs.barndoor.ai/how-tos/barndoor-bridge/client-settings) and your [policies](https://docs.barndoor.ai/how-tos/manage-policies.md). Bridge adds no restriction of its own.

* The `--posture` flag is removed. `barndoor run claude --posture gateway` now fails with `Error: unknown flag: --posture`.
* The `BARNDOOR_POSTURE` environment variable is ignored.
* No MDM setting ever carried a posture, so your profiles need no change.

Every launch prints the settings in force, for example:

```text theme={null}
Barndoor Agent Runtime: settings=v1 (preset client_default); env=barndoor/prod; filesystem=read_write; shell=native; network=native; skills=true; subagents=true; workspace=…
```

After upgrading, relaunch Claude Desktop from Bridge. A Claude Desktop session started by an older Bridge may pick up stricter instructions than your settings intend if its Barndoor process restarts.

#### Barndoor's shell refuses only the commands you block

Every command now reaches Barndoor's shell tool, where your policies check it and the call is audited as `shell/shell_exec`. Nothing is refused unless you block it.

To block commands, add them to **Deny command patterns** in the Shell panel of client settings. Since this release those patterns apply to Barndoor's shell tool as well as the client's own shell, and wrapping a command in `&&`, a pipe, `$(…)`, `sudo`, `env`, or `bash -c` does not get around them. If your policies require approval for shell commands, people see a confirmation such as:

```text theme={null}
Approval needed: Will execute shell command: gh --version (in $HOME)
```

#### Local MCP servers are opt-in for each person

With Barndoor platform v2.53 and later, installing a local MCP server for your organization makes it **available**. Each person turns it on with **Connect** in **My MCP Servers**. Choose who gets it with **Who gets it** when you install it; the server's card shows which applies.

New installations are opt-in by default. Installations that existed before stay required, so nothing changes for people already using them.

#### Minimum Claude Desktop version

Bridge now needs Claude Desktop 2.2553.0 or later. It is the first Claude Desktop release that can keep plugins' MCP servers behind Barndoor. Bridge refuses to launch an older one:

```text theme={null}
Claude Desktop <version> predates the governed adapter minimum 2.2553.0
```

Push a current Claude Desktop from your software catalog before or with this release.

#### Launch Codex Desktop needs the Codex policy

> [!NOTE]
>
> Changed in v0.1.218: the updater installs the Codex policy on every managed Mac. See [The Codex policy is installed on every managed Mac](#the-codex-policy-is-installed-on-every-managed-mac).

**Launch Codex Desktop** appears only on a Mac that has the Codex policy, `/etc/codex/requirements.toml`, and Codex Desktop at `/Applications/ChatGPT.app`. Without the policy, Bridge shows no button and no explanation.

The MDM updater script installs the Codex policy only where [provider lockdown](https://docs.barndoor.ai/how-tos/barndoor-bridge/install-with-mdm#provider-lockdown-optional) is on. So a fleet without lockdown never gets the button, unless you force the policy with the updater's `--codex-desktop-policy` option. The policy also makes `codex` in a terminal, and Codex in the ChatGPT app opened directly, refuse to run outside Barndoor. Tell people before you turn it on.

#### Hold Codex Desktop updates (optional)

Codex Desktop updates itself and can get ahead of the versions Barndoor supports. Launches on a Mac with an unsupported version fail with "newer than this Barndoor supports" until a later Bridge adds it. A new, optional MDM profile stops Codex Desktop's automatic updates so you release each version yourself. See [Hold Codex Desktop updates](https://docs.barndoor.ai/how-tos/barndoor-bridge/install-with-mdm#hold-codex-desktop-updates-optional).

To check whether a Mac's Codex Desktop is supported without launching it, run `barndoor codex-desktop-policy builds`.

#### Tamper-proof Claude Desktop profile (optional)

A new, optional MDM profile makes Claude Desktop's Barndoor configuration impossible for the user to change or delete. With it, Claude Desktop opened directly cannot be switched to a personal claude.ai account. See [Claude Desktop managed profile](https://docs.barndoor.ai/how-tos/barndoor-bridge/install-with-mdm#claude-desktop-managed-profile-optional). It has not yet been tested across a full range of real devices.

#### Provider lockdown stays off unless you turn it on

`barndoor doctor` now reports whether direct access to LLM provider APIs is blocked on the Mac. On a Mac without lockdown it reads:

```text theme={null}
Result:      not blocked: no DNS control is configured on this Mac and provider hosts are reachable
```

### Known limits in v0.1.210

| Limit | What people see |
| - | - |
| Plugins' MCP servers, remote or local, never connect in Claude Desktop launched by Bridge. This is deliberate: they would bypass Barndoor's policy, audit, and data protection. | **Nothing.** The plugin installs and its other parts work, but its MCP server silently never connects, with no error. Every MCP server your organization connects in Barndoor still works. |
| MCP servers added in Claude Desktop's own settings (local developer MCP servers) are turned off in Claude Desktop launched by Bridge. | The servers don't load. |
| Claude's web search works only on routes to Anthropic or Vertex AI. | Web search is unavailable on Bedrock routes and other routes Barndoor translates. |
| Windows installers are not signed yet. | No Windows build ships in this stable release. |
| Kilo on a ChatGPT subscription route needs Barndoor platform v2.53. | Use an API-key route until then. |
| `barndoor mcp smoke` skips remote servers. | It labels each one "local/embedded provider — not tool-router-backed" and checks nothing for them. |

### Good to know

* **Use the CLI inside Bridge.** Bridge links it at `/usr/local/bin/barndoor`. An older standalone `barndoor` earlier on your `PATH`, for example in `~/.local/bin`, cannot read the configuration Bridge writes and fails with `parse config cache: not sealed protobuf and not legacy JSON`. Remove it.
* **Governed launches own some client options.** Passing them after `--` fails before the client starts, for example `--model is controlled by barndoor run and cannot be overridden` and `claude option "-c" is unavailable in governed mode`. Use `barndoor run … --continue` or `--resume <id>` instead.
* **`barndoor tools call` runs as the agent "Barndoor CLI",** so your policies may treat it differently from Claude Code or Codex.
* **Approvals come after the preview.** Telling the agent "I approve" in advance does not count; it shows the preview and asks.
* **Kilo launches fail with a clear message when Kilo isn't installed,** such as `Kilo Desktop is not installed at /Applications/Kilo.app`. The empty session this leaves can be removed with `barndoor sessions prune`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.