PathruleEsta página solo está disponible en inglés.
How to Share Claude Code Memory Across a Team
Claude Code supports project instructions, scoped rules and local auto memory.
Team sharing means deciding which knowledge belongs in Git and which belongs in a shared workspace.
Respuesta breve
Only one of the three layers is shareable. Project memory in CLAUDE.md is checked in and travels; user memory in your home directory and the auto memory the assistant writes for itself stay on your machine. Sharing one CLAUDE.md works at small scale and breaks like every team file as it grows, with the rules for the current work competing against everything else in it.
Qué cubre este artículo
- Auto memory is local to the agent’s environment, so it is separate from team-approved project guidance.
- Pathrule shares workspace knowledge across supported agents, while working preferences and machine setup have their own boundaries.
Signs your team has outgrown a single CLAUDE.md
- New teammates ask the same context questions in chat that the file already covers.
- The file has grown past the point where anybody reads it end to end.
- Folder-specific notes keep getting added at the root because there is no better place.
- The same exception appears in multiple sections written in slightly different words.
- Reviewers cannot tell whether a generated change was made under the right rule.
- A rule needed for one folder breaks behavior in another folder where it was loaded by accident.
Separate local memory from project guidance
Claude Code’s memory documentation describes project instructions, scoped rules and auto memory. They serve different purposes. A note learned by an agent in one local environment is not automatically a convention approved by the team.
Put shared build commands, architecture decisions and project constraints in the repository or a shared knowledge workspace. Keep private working preferences separate.
Files are a useful team interface
CLAUDE.md can carry project guidance, and .claude/rules can scope it to paths. Commit those files, review changes and keep the package-specific parts near their scope. Teams do not need to force everything into one root file.
The maintenance cost appears when the same fact is copied into the formats several agents read. A changed decision needs an owner and a way to update every copy.
Share one authored source across agents
Pathrule stores workspace memories, rules and skills by path. The CLI and VS Code extension attach each contributor’s repository and deliver knowledge through the channels their agent supports. Teammates can use different agents without creating separate knowledge stores.
Cloud knowledge is shared according to workspace access. Local folder bindings and hook configuration stay specific to the machine. Working preferences remain distinct from project rules.
Keep authority and review visible
Record why a decision exists, which path it applies to and who changed it. A finding an agent inferred from code is advice to verify, not a rule. Required project checks remain requirements even when someone prefers less verification.
Use native files while they are enough. Add a shared layer when repeated corrections and conflicting copies are consuming review time.