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.
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: - 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: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
Getting help
Send your admin, or Barndoor support:- Bridge’s log: Logs → Copy in the Bridge window.
- The output of
barndoor doctorin 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.