Project-scoped connector access — cross-repo/cross-context isolation gap

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Connectors (GitHub and others) are authenticated at the account level and enabled per-conversation, with no way to bind a specific connector/credential/repo scope to a specific Project. This breaks the core Projects use case of isolated, scoped contexts for separate clients/repos/initiatives.

Issue: With two Projects each meant to work against a different GitHub repo, there's no way to give Project A live access to Repo A only and Project B live access to Repo B only. The GitHub App installation is shared across the whole account, so any Project with the connector enabled can reach every repo the installation has been granted — regardless of which Project it's meant for. The only real workaround (separate self-hosted MCP servers with separately-scoped PATs) requires infrastructure most users shouldn't need to run for basic repo isolation.

Config Gap: Project knowledge (file-based GitHub sync) is correctly Project-scoped, but it's chat-only — Cowork sessions don't read Project knowledge at all. So there's no option that is simultaneously (a) Project-scoped, (b) live/interactive, and (c) usable in both chat and Cowork.

Related: anthropics/claude-code #25566, #53656 (per-project connector control), #44980 (per-user connector scoping on Teams), #27302 (multiple accounts per connector), #25833 (Cowork/Claude Code reading Project knowledge).

Proposed Solution

Some mechanism to bind a connector instance (or a connector's granted scope) to a specific Project, so access doesn't leak across Projects, plus Cowork read access to Project knowledge so isolation and live-tool parity aren't mutually exclusive.

Alternative Solutions

Hosting our own MCP server connectors running independent PATs. Seams heavy for something as simple as "a project needs access to this repo only".

Priority

Medium - Would be very helpful

Feature Category

MCP server integration

Use Case Example

We have several engineers working on different projects and have isolated the cowork development into separate claude teams. Each project has its own repo. We would like the entire project scope (chats, cowork) to have access to the repo live based on GH user access. We regularly open chats in the projects to brainstorm ideas and there is no easy way for us to migrate these ideas into actual cowork sessions other than manual copy paste or file save / import. We would save these ideas into an MD or HTML file in the repo so they can be worked on in the team Cowork sessions.

This would be a much cleaner workflow for us and allow brainstorming away from the desktop with direct documentation share from chat to Cowork on return to the desktop. All while keeping the repo updated for the whole team.

Additional Context

_No response_