Claude Code for teams: one set of rules for every developer’s agents
When a team runs Claude Code, Codex or Copilot CLI, every developer keeps their own permission settings, and nobody knows what the others have allowed. Crest for teams gives the whole team one never-allow and always-allow list, written once on the account page and checked on each Mac. Each developer answers the prompts that are left from the MacBook notch, and the team lead gets a log that keeps outcomes only. Here is how that compares with the other ways teams run their agents, and where the rules stop.
macOS 14 or later. Sign in inside Crest to start your 7 days, no card.
Last updated: October 2026
Written by the developer of Crest, 25 October 2026. Crest is ours, so its row comes first, and every Crest fact on this page is what Crest for teams does today, including where it stops.
Crest for teams next to the other ways
Three ways a team ends up running its coding agents, side by side:
| One rule list for Claude Code, Codex and Copilot CLI | Never-allow rules in the modes that skip prompts | Changed once for the whole team | Prompts answered from the notch | A log the lead can read | |
|---|---|---|---|---|---|
| Crest for teams | Yes, one list for all three | Yes, in bypassPermissions, acceptEdits, a Codex run that never asks and Copilot CLI with --yolo, while Crest is running. If Crest is closed, the agent’s own mode applies. | Yes, on the account page, and each Mac picks it up within 15 minutes | ✓Yes | Yes, outcomes only, kept 90 days |
| Each developer’s own settings files | No: settings.json for Claude Code, .rules files for Codex and flags for Copilot CLI, on every Mac | Up to each agent and to what each person wrote | No, someone edits every Mac | ✗No | No shared log |
| A skip-all switch with no rules | No | No: the agent runs what the model decides | Nothing to change | ✗No | No |
or all three apps, $19.99 once · macOS 14 or later
The other two rows describe each agent’s own settings. How to write those for one developer is on how to make the agents ask less.
One rule list, written once
The owner or a manager of the team writes the rules on the account page, and each teammate’s Crest picks them up within 15 minutes. A rule is matched on the Mac itself, against the command, the file path or the web address, so the command never reaches us.
- Never allow, such as
git push --force*orrm -rf*. A never rule is checked in every agent mode and inside a chain of commands, and the agent is told which rule stopped it, while Crest is running. If Crest is closed, the agent’s own mode applies. - Always allow, such as running
npm test*or editingdocs/*. An always rule answers the prompts your team sees all day, so nobody is interrupted by a test run. It never covers a chained command.
Why a team needs rules in the skip-all modes
When an agent asks twenty times an hour, people stop reading the prompts, or they switch them off with --dangerously-skip-permissions, acceptEdits, a Codex run that never asks or Copilot CLI with --yolo. That is exactly when a shared never-allow list matters, and Crest for teams keeps it in force in those modes, while Crest is running. If Crest is closed, the agent’s own mode applies.
What the skip-all switches cost on a Mac, and the allow lists one developer can use instead, are on how to make the agents ask less.
The prompts that are left, answered from the notch
Each developer answers Claude Code’s questions and permission prompts, and Codex and Copilot CLI requests, on the MacBook notch: the request comes up with the whole command and the folder, and they press Allow or Deny without going back to the terminal. How that part works for one person: Claude Code in the notch.
Every seat is the whole of Crest Pro, plus Take for screen recordings and Minutes for meeting notes, on the person’s own email and two Macs.
A log that keeps outcomes only
The approval log shows who, when, which agent, and whether it was allowed or denied. It never holds the command, the file path or the web address. It is kept 90 days, and the manager can turn it off.
Where the rules stop
Crest’s hooks run in each person’s own account, so these are the honest edges of what they can hold.
- Crest has to be running. If someone quits Crest, or Crest does not answer a check within about a second, the agent carries on as it would without Crest, so a closed Crest never freezes a run.
- Codex asks each person once. Crest’s hook reaches Codex after the person reviews and trusts it in
/hooks. - Commands, edits and fetches are what the rules check. Tools outside those, such as an MCP server’s tools in Claude Code, do not pass through Crest’s hook.
- It is not a lock. Someone who removes Crest’s hooks steps outside the rules. For rules nobody on the Mac can change, Claude Code’s managed settings and Codex’s managed hooks are deployed by your IT, and Crest works beside them.
What a team pays
Team seats are for 3 to 50 people, from $11 a person, paid once through Paddle, with a Paddle tax invoice (PDF) with your company details. Updates come through Crest 7, and you can take a seat back and give it to someone else any time.
See team seats and the price for your team
FAQ
Can a team share Claude Code permission rules?
Yes, with Crest for teams. The owner or a manager writes never-allow and always-allow rules on the account page, and each teammate's Crest applies them to Claude Code, Codex and Copilot CLI on that Mac within 15 minutes, while Crest is running. If Crest is closed, the agent's own mode applies.
Do the rules hold with --dangerously-skip-permissions?
Yes, while Crest is running: a never-allow rule is checked in bypassPermissions, acceptEdits, a Codex run that never asks and Copilot CLI with --yolo. If Crest is closed, the agent's own mode applies, and if Crest does not answer a check within about a second, the agent carries on as it would without Crest.
Does Crest see our developers' commands?
No. Rules are matched on each Mac, and the approval log keeps who, when, which agent and the outcome only, never the command, the file path or the web address.
Does this replace managed settings?
No. Someone who removes Crest's hooks steps outside the rules. For rules nobody on the Mac can change, Claude Code's managed settings and Codex's managed hooks are deployed by your IT, and Crest works beside them.
What does a team seat include?
Crest Pro, Take and Minutes for one person, on their own email and two Macs, with updates through Crest 7, paid once. The price for your team size is on the teams page.
What happens when someone leaves the team?
Take the seat back on the account page and give it to the next person, any time.
Try Crest free
Download it free and sign in with a free account for a 7-day trial, no card. Crest alone is then $14.99 once. All three apps (Crest, Take and Minutes) are $19.99 once, on 2 Macs.
Download Crest for macOS Get all three apps, $19.99macOS 14 Sonoma or later · signed and notarized by Apple · 7-day refund
Keep reading: Crest for teams · Make the agents ask less · Claude Code in the notch · Codex approvals in the notch · Copilot CLI approvals in the notch · Facts and prices · Crest overview