Answers
How do you give teammates who don't work in the repository the same Claude rules?
According to the Claude Code documentation, a project's CLAUDE.md reaches the team through source control, so it reaches the people who clone the repository. A personal ~/.claude/CLAUDE.md is read only by you, and a CLAUDE.local.md holds private preferences that stay out of version control. Someone in operations, legal, marketing or product who never opens the repository has none of these: their Claude starts without the rules the developers' Claude follows, and nothing tells them. To give them the same rules you need a place they and their assistants can read without Git. Arroway is that place: each rule recorded once, with who approved it and when it ends, read before acting by whatever tool the person already uses — Claude, ChatGPT, Codex, Cursor or anything over MCP. The install page is the first step.
Last updated October 8, 2026
What reaches someone who never opens the repository
The Claude Code documentation I read lists where instructions live: a managed file for an organization's machines, ~/.claude/CLAUDE.md for you alone, the project's CLAUDE.md shared through source control, and CLAUDE.local.md for private preferences. All of them are files on a computer. So the pricing rule the sales lead agreed, the confidentiality line the partner insists on or the tone marketing wants reaches a developer's Claude only if someone writes it into a repository, and it never reaches the colleague who works in a chat window. I read only the Claude Code documentation, so how other Claude apps carry instructions is not described here.
Where it stops
Copying the text into each person's own settings gives you many copies, and the copies drift: a change reaches whoever is told. Asking non-developers to open the repository turns a rule problem into a Git problem, and a line added there still does not say who decided it. Nothing in a file tells a reader outside the repository that the rule changed. And it repeats for every tool a person uses, because each one reads its own place.
When to use Arroway
Use Arroway when the people who must follow a rule are not the people who work in the repository. Each rule is recorded once, by whoever answers for it, with who approved it and the condition that ends it, and every connected assistant reads the current version at the start of a session. A person in operations connects the AI they already use to the project, with no Git and no repository, and gets the rules of the project they work on. When a rule changes, the replacement names the one it retires, and everyone's next session opens with the new one. The first step is the install page.
What it looks like in practice
A twelve-person services company has a repository for its internal tools, and four developers work in it with Claude Code. The operations lead uses ChatGPT and the account manager uses Claude in the browser. In October the managing partner decides that any client quote above 10,000 needs a second approval before it goes out. A developer writes the line into CLAUDE.md, and the four developers' Claude knows it. The next morning the operations lead's ChatGPT drafts a quote without it, and so does the account manager's Claude. In Arroway the rule is recorded once, with the managing partner's name. The tools the non-developers already use open their next session with it, nobody needs the repository, and the history shows when it was set. The company in this example is illustrative.
Questions people ask about this
- Can non-developers use a CLAUDE.md?
- Only by working in a repository, because the project file reaches people through source control, and the documentation I read describes no other route for it. Arroway reaches them in the tool they already use.
- Does the developer team have to change how it works?
- No. The developers' tools connect to the same project and read the same current rules. What changes is that each rule is recorded once, with its approver, and not left to whoever remembers to copy it.
- How do I try Arroway?
- Install it in the tool you already use — the install page has one route for Claude, ChatGPT, Codex, Cursor or any MCP tool — and sign in when the tool asks. From then on, sessions open by reading the project and close by recording what was decided.
Where this is verifiable
Claude Code memory documentation (code.claude.com/docs/en/memory), read on 8 October 2026 — Claude Code is described only as that documentation describes it on that date, and it can change in any release. Product documentation on this site (How it works, Install), the answers on sharing a Claude Project with a team and on shared context across AI tools, and the sanction, supersession and expiry-condition rules in the sanctioned product spec. Everything described here about Arroway is behaviour the tools apply today, not roadmap. The company in the example is illustrative.
https://www.arroway.app/en/answers/claude-md-for-teammates-who-dont-work-in-the-repo