# docs: Document configuration boundaries for external agents \(\#54759\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/d8afa2d0360853922807858e2d74748eed2c8fb3)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: d8afa2d0360853922807858e2d74748eed2c8fb3

Requested commit: d8afa2d0360853922807858e2d74748eed2c8fb3

Commit: d8afa2d0360853922807858e2d74748eed2c8fb3

Tree: 61e56359d2f89fc69052d533ca97c527b4123ffa

Author: morgankrey

Committer: GitHub

## Message

```
docs: Document configuration boundaries for external agents (#54759)

## Summary

- Add a new "Configuration Boundaries" section to the external agents
documentation explaining what settings are shared between Zed and ACP
agents
- Clarify bidirectional configuration story: what Zed forwards to agents
AND what agents inherit from native installations
- Add troubleshooting section for common user confusion points
- Update MCP docs with clearer cross-links

## Context

Users are confused about which Zed settings apply to external ACP agents
like Claude and Codex. Common questions:
- "I configured MCP in Zed but Claude can't see it"
- "My Codex config.toml isn't being used"
- "Do profiles apply to external agents?"

## Key Points

**What Zed forwards to ACP agents:**
- Model/mode selection, env vars, MCP servers (with limitations),
CLAUDE.md

**What's NOT forwarded:**
- Profiles, tool permissions settings, `.rules` files

**What agents DON'T inherit from native installations:**
- `~/.claude/` config, `~/.codex/config.toml`, native MCP servers,
authentication state

## Test plan

- [x] Review for technical accuracy against codebase
- [x] Check brand voice compliance

Release Notes:

- N/A
```

## Parents

- [f2e9c5a02596ecb716c75ff06d11e1dbacd10d0e](https://git.cafe/gitcafe/zed/commit/f2e9c5a02596ecb716c75ff06d11e1dbacd10d0e?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/d8afa2d0360853922807858e2d74748eed2c8fb3?format=markdown)