[FEATURE] Sync Claude.ai Teams Project Knowledge with Claude Code

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

Summary

Allow instructions and context defined in Claude.ai Teams Project Knowledge to be automatically available to Claude Code sessions running locally on developers' machines — without requiring manual maintenance of .claude/ files per developer.

---

Current Behavior

Today, Claude Code loads its context exclusively from local filesystem sources:

• CLAUDE.md at the project root (or subdirectories)
• .claude/commands/ for custom slash commands
• .claude/settings.json for permissions and configuration

Instructions shared via Project Knowledge on Claude.ai Teams are only available in the web/desktop chat interface. Claude Code sessions have no awareness of them.

---

Desired Behavior

Teams should be able to define shared instructions once in the Claude.ai Teams interface (Project Knowledge) and have Claude Code sessions pick them up automatically when a developer is authenticated under that Team plan.

This would enable teams to centrally manage:

• Commit and branching standards
• Pre-commit validation rules
• Pull request description templates
• Code review checklists
• Project-specific context (e.g. legacy stack constraints, architecture decisions)
• Custom slash command definitions

### Environment

• Claude Code (latest)
• Claude.ai Team plan
• Affected workflows: commit automation, PR creation, pre-commit validation, code review

Proposed Solution

When a developer authenticates Claude Code using a Team or Enterprise plan account, Claude Code could:

1. Fetch shared instructions from the Team's Project Knowledge via the Anthropic API
2. Merge them with local CLAUDE.md and .claude/ config (local always takes precedence)
3. Refresh periodically or on session start

This would mirror how other developer tools handle team-level configuration (e.g. ESLint shared configs, EditorConfig, Prettier shared configs).

Alternative Solutions

Versioning everything in .claude/ inside the git repository. This works for open or internal repos but doesn't cover:

• Sensitive instructions that shouldn't be in source control
• Cross-repo standards that apply to all projects in the organization
• Real-time propagation of updated guidelines without a git push

Priority

High - Significant impact on productivity

Feature Category

Developer tools/SDK

Use Case Example

Our team uses Claude Code across multiple developers. We maintain a .claude/commands/commit.md and a CLAUDE.md versioned in git to share context — which works, but has friction:

• Developers on new machines must clone the repo before Claude Code has any shared context
• Sensitive guidelines (e.g. security policies, internal API conventions) shouldn't always live in a public or shared git repo
• There's no way to push updated instructions to all developers' Claude Code sessions without a git commit
• Onboarding a new developer means relying on them to pull the latest repo state before Claude Code behaves consistently

A sync mechanism between Claude.ai Teams Project Knowledge and Claude Code would make team-wide AI behavior consistent, centrally governed, and independent of git state.

Additional Context

This gap becomes more noticeable as teams adopt Claude Code more broadly. The Claude.ai Teams interface already supports centralized knowledge management — extending that to Claude Code would make it a much stronger offering for engineering teams standardizing AI-assisted development workflows.