> ## 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.

# What's blocked and why

> Why a tool, command, model, or server isn't available in a Barndoor Bridge session, what you see when it happens, and what to do about it.

This page is for people using Bridge. When something doesn't work in a session you started from Bridge, there are three possible reasons: a choice your organization's admins made, a rule that keeps every session governed, or a known limit. Find what you see below.

Admins looking for the fix on their side: see [Monitor and troubleshoot](https://docs.barndoor.ai/how-tos/barndoor-bridge/monitor-and-troubleshoot.md#common-problems).

## Your organization's choices

Your client's own tools stay on unless your admin restricts them. Barndoor's tools work the other way: each one runs only when your organization's policy grants it to you.

| You see | Why | What to do |
| - | - | - |
| `This tool is blocked by policy.` | Your organization's policy doesn't give you that tool. | Ask your admin for access. |
| The client asks you to approve an action first | Your organization's policy requires approval for that tool. | Read what it's about to do, then approve or decline. |
| A tool's result has text replaced or removed, or the call is refused for data protection | Your organization's data protection policy acted on it. This applies to tools on your computer too. | Ask your admin if you need that data. |
| A shell command is refused, however you write it | Your admin blocked that command. | Ask your admin, or use a different command. |
| The client's own file, shell, or web tool is missing, and it uses Barndoor's tools instead | Your organization routes that kind of work through Barndoor. | Nothing; the work still gets done, through Barndoor. |
| `None of the models you're allowed to use fit Claude Code. Model Access decides this — ask your admin.` | Your organization allows you no model that Claude Code can use. | Ask your admin. |
| `None of the models you're allowed to use can run in Codex. Codex cannot forward a Claude login, so an admin needs to allow a model route that uses a provider credential or a Codex login in Model Access.` | Every model you're allowed bills a Claude subscription, which Codex can't use. | Ask your admin. |
| `None of the models you're allowed to use can run in Kilo Code. Kilo Code cannot forward a Claude login, so an admin needs to allow a model route that uses a provider credential or a Codex login in Model Access.` | The same, for Kilo. | Ask your admin. |
| Fewer models than you expected | Your organization decides which models each person sees. | Ask your admin. |
| A GPT model your organization allows isn't in Claude Desktop | Claude Desktop shows only Claude models. | Use Codex or Kilo for GPT models. |
| Under MCP only, a tool that runs on your computer is refused with a message that it only runs locally through barndoor-cli | Claude used your own Barndoor connector from claude.ai instead of the `barndoor` connector Bridge added. Your own connector can't run tools on your computer. | Turn your own Barndoor connector off for that chat or Code session under **+ → Connectors**, and try again. |
| Kilo won't launch, and the message names your organization's Bridge setting | Your organization has Bridge govern MCP only, and Kilo needs Barndoor's models. | Use another client, or ask your admin. |

To check a single tool yourself, run `barndoor tools test-policy <server> <tool>` in a terminal, for example `barndoor tools test-policy filesystem read_text_file`.

## Rules that keep sessions governed

These apply whenever your organization has Bridge govern models, so that everything a session does goes through Barndoor. If Bridge governs **MCP only** in your organization, you use your own Claude or ChatGPT sign-in and choose your model inside the client, and Claude Desktop is your own copy, where your own MCP servers still load.

* **Your own MCP servers don't load.** MCP servers you add in Claude Desktop's settings, in Claude Code's config (`~/.claude.json`, a project's `.mcp.json`), or in Kilo's settings don't run in a governed session. Ask your admin to connect the server in Barndoor instead.

* **Plugins' MCP servers don't connect** in Claude Desktop. The plugin installs and its skills and commands work, but its MCP server never connects, and Claude shows no error.

* **Some client options belong to Barndoor.** Passing them after `--` stops the launch:

  | You passed | Message | Instead |
  | - | - | - |
  | `--model` | `--model is controlled by barndoor run and cannot be overridden` | Your organization picks the models; they're in the launch summary. |
  | `--allowedTools` | `--allowedTools is controlled by barndoor run and cannot be overridden` | Your organization's policy decides which tools you can use. |
  | `-c` or `--resume` (Claude Code) | `claude option "-c" is unavailable in governed mode` | `barndoor run claude --continue`, or `--resume <id>`, before `--`. |
  | `--skip-git-repo-check` (Codex) | `codex option "--skip-git-repo-check" is unavailable in governed mode` | Leave it out; Barndoor already lets Codex work in the folder you chose. |

* **Codex works only in a project folder.** It won't start in your home folder if you have your own Codex settings there, and in Codex Desktop it can change files only in the folder you chose.

* **Computer use and browser use are off in Codex Desktop.** In Claude Desktop, computer use is off when your organization has changed any client setting.

* **Clients opened directly** may refuse to work on computers where IT has made Claude or Codex run only through Barndoor. A Claude Desktop opened directly then shows a profile named **Barndoor (open Claude Desktop from Bridge)**. Launch it from Bridge instead.

## Known limits

* **Web search** in Claude works only when your organization sends Claude traffic to Anthropic or Google Vertex AI.
* **On Windows**, Kilo Desktop and Kilo in VS Code aren't available. The Kilo CLI works.

## Check your servers

The **Servers** tab in the Bridge window shows each MCP server you can use:

| Status | What it means |
| - | - |
| **Connected** | A server in Barndoor's cloud that you've connected. |
| **Available** | A tool built into Bridge. Ready to use. |
| **Ready** | A local server from your organization that passed Bridge's checks. **Downloads the first time it is used** means it isn't on your computer yet. |
| **Blocked** | A local server Bridge won't run. The row says why and what to do, for example **Ask IT to add your organization's publisher key to the Barndoor MDM profile.** |
| **Local approval only** | A server approved only on this computer with `barndoor local-mcp trust`. Bridge ignores those approvals; ask IT to publish the server. |

`barndoor list` in a terminal shows the same thing.

* **A server isn't listed:** you haven't connected it in **My Apps**, or Bridge hasn't synced since. Connect it, run `barndoor sync`, and check again.
* **A server is listed, but its tools are blocked by policy:** your organization hasn't given you those tools yet. Ask your admin.
* **A local server is Ready but fails when used:** the error ends with the last lines the server printed, and the path to its full log (on a Mac, `~/Library/Logs/Barndoor/local-mcp/<server>.log`). It's usually missing credentials: enter them when you **Connect** the server in **My Apps**. Otherwise, send the error and the log to your admin.

## Other messages

| Message | What to do |
| - | - |
| `Claude Desktop <version> predates the governed adapter minimum 3.1623.0` | Update Claude Desktop, then launch it from Bridge again. |
| A prompt titled **Claude Code isn't installed**, with **Install** and **Not now** | Select **Install**. When your organization's Claude models bill your Claude subscription, Claude Desktop needs Claude Code to sign you in. Bridge installs Claude Code from Anthropic, signs you in, and reopens Claude Desktop. |
| `your organization's Claude route uses Claude subscription seats, so Claude Code must be installed and signed in…` | You selected **Not now** on that prompt, or didn't answer it. Launch again and select **Install**, or install Claude Code yourself, run `claude auth login`, and launch again. |
| `claude executable not found in PATH` | Install Claude Code, or open a new terminal. |
| Codex Desktop is "older than Barndoor supports" | Update it (on a Mac, **ChatGPT → Check for Updates**; on Windows, from the Microsoft Store) and launch again. |
| Codex Desktop is "newer than this Barndoor supports" | Wait for the next Bridge update, which IT installs for you. |
| `your home folder cannot be a governed Codex workspace…` | Run Codex from a project folder. |
| `codex project configuration … is unavailable in governed mode…` | The project has its own `.codex/config.toml`. Move or remove it, or run Codex in another folder. |
| `Kilo … configuration … is unavailable in governed mode…` | Your home folder or project has its own Kilo settings, such as `~/.kilo/kilo.json` or `.kilocode/rules`. Move or remove them, as the message says. |
| `kilo executable not found in PATH`, or `Kilo Desktop is not installed at /Applications/Kilo.app` | Install Kilo. |
| `the Kilo Code extension is not installed in VS Code` | Install it with `code --install-extension kilocode.kilo-code`. |
| `Barndoor: this Mac runs Claude only through Barndoor…` | Use `barndoor run claude`, or launch Claude Desktop from Bridge. |
| `parse config cache: not sealed protobuf and not legacy JSON` | An older standalone `barndoor` is answering instead of Bridge's. Run `/usr/local/bin/barndoor doctor`, which says how to remove it. |
| `barndoor update` says updates are managed | Expected. IT keeps Bridge up to date. |

## Getting help

Send your admin, or Barndoor support:

1. Bridge's log: **Logs → Copy** in the Bridge window.
2. The output of `barndoor doctor` in a terminal. It shows your Bridge version, your environment, what IT has set up on your computer, and the last lines of Bridge's log.


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