Sign inDownload
0:00 / 1:25Try freeBuy $14.99

Crest for teams

Shared rules for your team’s coding agents, and three Mac apps, paid once

Tired of developers switching every Claude Code check off? Crest gives your whole team the same agent rules and answers in the notch, plus Take and Minutes, for one payment.

3 to 50 people, from $11 a person, paid once.

Crest and Take need macOS 14 or later. Minutes needs macOS 26 or later on Apple Silicon.

Crest in the notch: Claude wants to run npm test, with the whole command, Deny and Allow. The same ask for Codex: it wants to run pnpm lint --fix in crest-site, with Deny and Allow. The same ask for Copilot CLI: it wants to run gh pr checks 42 in api, with Deny and Allow.

An always-allow for npm test answers this for the whole team.

One payment for the whole team

The price per person drops as the team grows, a team never costs more than a bigger one, and nothing renews.

$15a person, 3 to 9 people
$13a person, 10 to 24 people
$11a person, 25 to 50 people

For a team

Crest Pro, Take and Minutes for each person, on their own email and 2 Macs, with updates through Crest 7. One payment, and you hand out the seats.

$44.99once

3 people · $15 each

From 10 people, $13 each.

More than 50 people? Contact us

Prices in USD. Prices include tax, except in the US and Canada, where tax is added at checkout.Paid through Paddle, not crypto.No discount codes on a team.7-day refunds.A Paddle tax invoice (PDF) with your company details.

Let developers move fast in Claude Code without risking production

When an agent asks for permission twenty times an hour, people stop reading the prompts, or they switch them off with bypassPermissions, acceptEdits, a Codex run that never asks or Copilot CLI with --yolo. Crest for teams fixes both sides. Each developer answers Claude Code’s questions and permission prompts from the notch, and your team’s never-allow rules are checked even in those modes, while Crest is running. If Crest is closed, the agent’s own mode applies.

Never allow

  • Never run git push --force*
  • Never run rm -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

  • Always allow running npm test*
  • Always allow editing docs/*

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.

  • Written once for everyone. The owner or the manager writes the rules on the account page, and each teammate’s Crest picks them up within 15 minutes.
  • Matched on the Mac. The rule is checked against the command, the file path or the web address on the Mac itself, so the command never reaches us.
  • Private by design. The approval log keeps outcomes only. It never holds a developer’s command, file path or web address.

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

That is 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.

Need 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. How the rules work across a team, agent by agent: Claude Code for teams. For one developer who just wants fewer prompts, the allow lists are on how to make the agents ask less.

A log that keeps outcomes only

The log shows who, when, which agent, and whether it was allowed or denied. It never holds the command, the path or the web address.

Three Mac apps in every seat, with no monthly fee

Every seat unlocks Crest Pro, Take and Minutes for one person, on their own email and two Macs, with updates through Crest 7.

Crest Pro

Answer Claude Code, Codex and Copilot CLI from the notch, fill passwords with Touch ID and two-factor codes from the notch, and keep the file shelf, the clipboard and 22 widgets one swipe away. Passwords and codes work in Safari, Chrome, Arc, Brave and Edge.

macOS 14 or later.

How the agents part works

Take

Take records the screen, the camera and the voice for a bug report or a pull request, and the recording comes out already edited, with zooms and captions, no watermark and nothing uploaded.

macOS 14 or later.

About Take

Minutes

Minutes records Zoom, Teams or Meet from both sides with no bot joining the call, and writes the notes on the Mac.

macOS 26 or later on Apple Silicon.

About Minutes

For IT and finance: one payment, a Paddle tax invoice (PDF) with your company details, and seats you can see and take back. There is nothing to host.

Invite with a link, reassign seats any time, and download your invoice

There is no spreadsheet of licence keys to keep. From your account page you type one email per seat, paste a whole list, or turn on an invite link for your company’s email domain and share it in Slack or your onboarding doc. When a contractor finishes or someone changes roles, take the seat back and give it to the next person, any time.

Each person signs in inside the apps with the email on their seat, and everything unlocks. Paddle, our merchant of record, issues a tax invoice (PDF) with the company name, address and tax number you enter at checkout, and every invoice can be downloaded again from your account page.

What leaves the Mac

Here is the exact list, for your security review.

Sent to us

Signing in and the licence
The account, the Mac’s hardware identifier and its name.
Update checks
With an anonymous install count anyone can turn off, and for Crest, whether a sale is on.
Team rules and the approval log
Rules, notices, servers, and outcomes only.
Seat usage
When a seat’s Macs last checked in, and how many there are.

Stays on the Mac

Recordings, calls and notes
Take’s movies, and Minutes’ audio, transcripts and summaries.
Agent prompts and commands
Answered between the agent’s hook and Crest, never sent to us.
Crest’s widgets
Every widget runs on the Mac.

The full list, with every service a widget reaches: the privacy policy.

More than 50 people?

Or ask a question first. The developer who makes these apps answers it himself.

Bigger teams, an invoice before you pay, or a call with your IT team: contact@crestnotch.app

The details, if you want them

Questions9
When do the agent rules apply, and when do they not?

They apply while Crest is running on the teammate’s Mac. If Crest is closed, or does not answer a check within about a second, the agent’s own mode applies: its own prompt in the terminal, or no prompt at all in an autonomous mode. While Crest runs, a never-allow rule is checked in every agent mode, including Claude Code’s bypass, accept-edits and plan modes, Codex sessions that never ask and Copilot CLI started with --yolo, and the agent is told which team rule stopped it. While a team has a never-allow rule, Crest keeps its hooks for the three agents installed, even if that person has switched off answering prompts on the notch. An always-allow only answers a prompt that reaches the notch. Codex runs Crest’s hook only after each person trusts it once in /hooks. The rules check commands, file edits and web fetches, and Claude Code’s MCP tools do not pass through Crest’s hook. Crest is not a lock: for rules nobody on the Mac can change, Claude Code has managed settings and Codex has managed hooks in requirements.toml, both deployed by your IT, and Crest works beside them.

Do team rules still work if a developer runs Claude Code with --dangerously-skip-permissions?

Yes, while Crest is running on that Mac. That flag puts Claude Code in bypassPermissions mode, and there Crest’s hook still checks your team’s never-allow rules first, so a blocked command is stopped and the agent is told which rule stopped it. The same holds in acceptEdits and plan mode, for a Codex run that never asks and for Copilot CLI with --yolo. If Crest is closed, or does not answer within about a second, the agent’s own mode applies.

What does the approval log keep?

Outcomes only: who, when, which agent, the project folder’s name, the kind of action (run, edit, fetch or other), allowed or denied, and whether the person, a team rule or session trust decided. Never the command, the file path or the web address: the app has no field that could carry them, and our server refuses a batch that tries. The owner and the manager read it on the account page, it is kept for 90 days, and the manager can switch it off. Not in the log: prompts answered in the terminal while Crest was closed, and commands an agent ran without asking in an autonomous mode, unless a never-allow rule stopped one.

What do team servers share with teammates?

A name, the address, and a user and a port if you add them. The servers appear in every teammate’s Hosts in Crest, read-only, so nobody has to ask for the staging box’s address again. There is no field for a password or a key.

Is it a subscription?

No. You pay once for the number of people you pick, from 3 to 50, and the seats are yours, with updates through Crest 7. Every seat includes a first month of Passwords and 2FA, and after that month Crest Passwords is $2.99 a month or $24.99 a year for anyone who wants to keep them filling in and syncing. Teams that bought before October 6, 2026 keep every update for life. Nothing renews for the seats. Adding seats later is one more payment for the difference.

What happens when someone leaves?

Take their seat back from your account page and give it to someone new, any time, without buying another seat. The person who left loses Crest Pro, Take and Minutes, their Macs are signed out, and the seat is empty for the next person.

Do the apps send our recordings, notes or commands anywhere?

No. Take’s recordings and Minutes’ audio, transcripts and summaries stay on the Mac, and the apps do no tracking. They go online to sign in, check the licence every few days and look for updates. Coding agent approvals are answered on the Mac and never reach us.

Can we get an invoice with our company name and tax number?

Yes. Paddle, our reseller and merchant of record, issues a tax invoice (PDF) for every purchase. Use Add tax number in the checkout to enter your company name, address and VAT or tax number, and they are printed on it. Every invoice can be downloaded again from your account page.

What if we are more than 50 people?

Email contact@crestnotch.app with how many people and we set the team up with you. The same address takes security questionnaires and questions before you buy.

Agent rules, in full
Where the rules live
The owner or the manager writes the rules once, on the account page. Each teammate’s Crest fetches them within 15 minutes and applies them on that Mac, before a permission prompt reaches the person. The rule is matched against the command, the file path or the web address on the Mac itself, so the command is never sent to us. Offline, the last rules Crest fetched keep applying.
Never allow: block what nobody should run
A pattern such as git push --force* or rm -rf* for commands, a path for edits, or a web address for fetches. While Crest is running, a never-allow rule is checked in every agent mode: Claude Code in bypass, accept-edits or plan mode, Codex sessions that never ask, and Copilot CLI started with --yolo. If Crest is closed, the agent’s own mode applies. It catches the command inside a chain too, so cd app && git push is stopped by git push*, and the agent is told which team rule stopped it.
Always allow: wave through the boring ones
For what the team runs all day: npm test, a lint, edits under docs/. An always-allow answers a prompt that reaches the notch, so the agent asked, Crest is running and the person answers prompts there. It never covers a chained command, so npm test* cannot wave through npm test && curl … | sh: the person is asked instead. A teammate can switch an always-allow off for themselves and be asked again. Nobody can switch off a never-allow.
An approval log with outcomes only
Who, when, which agent, the project folder’s name, the kind of action (run, edit, fetch or other), allowed or denied, and whether the person, a team rule or session trust decided. Never the command, the file path or the web address: the app has no field that could carry them, and our server refuses a batch that tries. The owner and the manager read it on the account page. It is kept for 90 days, and the manager can switch it off.
Team servers and notices
List the team’s servers once and they appear in every teammate’s Hosts in Crest, read-only: a name, the address, and a user and a port if you add them. There is no field for a password or a key. A notice of up to 140 characters, with an end date if you want one, shows once on each teammate’s notch.
Crest has to be running
If a teammate quits Crest, or Crest does not answer a check within about a second, the agents carry on as they would without it: their own prompt in the terminal, or no prompt at all in an autonomous mode. That is on purpose, so a closed Crest never freezes a run.
Codex asks each person once
Codex runs a hook only after the person has reviewed and trusted it in /hooks, so Crest’s rules reach Codex from then on.
Commands, edits and web fetches
That is 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
Crest works in each person’s own account, so someone who removes its hooks steps outside the rules. For rules nobody on the Mac can change, Claude Code has managed settings and Codex has managed hooks in requirements.toml, both deployed by your IT. Crest works beside them.
Every team size, priced

The price per person drops as the team grows. Every total ends in .99, and a team never costs more than a bigger one. Prices include tax, except in the US and Canada, where tax is added at checkout.

PeopleTotal, onceWhy
3$44.99$15 a person, from 3 to 9 people
6$89.99$15 a person
9$129.99The same as 10, so one more person is free
10$129.99$13 a person, from 10 to 24 people
17$220.99$13 a person
22 to 24$274.99The same as 25, so make it 25
25$274.99$11 a person, from 25 to 50 people
50$549.99The most you can buy here. More? Talk to us

In short: $15 a person for 3 to 9 people, $13 for 10 to 24 and $11 for 25 to 50, so 3 people are $44.99, 10 are $129.99, 25 are $274.99 and 50 are $549.99. Paid through Paddle, and crypto is not offered for teams. No discount codes apply to a team.

Seats, in full
Buy for the team
Pick 3 to 50 people and pay once. The email you pay with becomes the team’s owner, and seat 1 is yours.
Give out the seats
From your account page: type one email per seat, paste a whole list at once, or turn on an invite link for your company’s email domain and share it. Only addresses at that domain can use the link, and free email domains such as Gmail or Outlook can never be a team domain.
Each person signs in
Inside Crest, Take and Minutes, with the email on their seat, and everything unlocks, on up to two Macs each. A seat is one person, on their own email. There are no licence keys to send around.
One manager besides you
They give and take back seats and run the invite link from their own account. Only you, the owner, add seats or choose the manager.
See which seats are used
Each seat shows when it was last used and on how many Macs, and seats nobody has used in 30 days are marked, so you can take them back.
Take a seat back any time
The person loses Crest Pro, Take and Minutes, their Macs are signed out, and the seat is empty for the next person. Every move is logged.
Add seats later, up to 50
You pay the difference between the two team prices: going from 8 to 12 people is $36.00, the price of 12 minus the price of 8.
Refunds
Refunds work like every purchase: 7 days, and a refunded team takes back every seat.
Invoices

Paddle is our reseller and merchant of record, so Paddle is the seller on the invoice and charges the tax your country requires. Each purchase comes with a Paddle tax invoice (PDF). In the checkout, use Add tax number to enter your company name, address and VAT or tax number, and they are printed on it. Every invoice, for the team and for seats added later, can be downloaded again from your account page whenever you need it. Need a purchase order number on it, or a detail changed? Email contact@crestnotch.app.

What leaves the Mac, in full

The apps run on the Mac and do no tracking, apart from an anonymous install count sent with update checks that anyone can turn off. This is everything they send to us, and what never leaves. The full list, including the services a widget reaches straight from the Mac, is in the privacy policy.

Sent to us: signing in and the licence
When a person signs in inside an app, it sends their account sign-in, the Mac’s hardware identifier and the Mac’s name, so the licence is bound to that Mac and the Mac appears on their account page. Every few days the app sends its signed licence back to be renewed. The identifier is how the two-Mac limit and seat usage work; it also keeps one free week per Mac and counts active Macs. It is never sold or used for ads.
Sent to us: updates and offers
Each app checks our update feed for a new version. Crest also asks our server twice a day whether a sale is on. Neither sends anything about what a person does in the app.
Stays on the Mac: recordings, calls and notes
Take’s recordings are ordinary movie files in the person’s Movies folder. Minutes records, transcribes and summarizes on the Mac with Apple’s on-device models, and the audio, transcripts and summaries never leave it. Crest’s widgets run locally.
Stays on the Mac: coding agent prompts
Claude Code, Codex and Copilot CLI permission prompts are answered on the Mac: the command, the file and the answer go between the agent’s hook and Crest, and never to us. Crest’s Claude widget talks to Claude through the person’s own Claude Code, or the AI service and key they set.
Sent to us: team rules, notices and the approval log
The manager sets always-allow and never-allow rules for coding agents, posts short notices and lists the team’s servers, and each teammate’s Crest reads them from us every 15 minutes. Never-allow rules apply in every agent mode while Crest is running, and a teammate can only be stricter. If Crest is closed, the agent’s own mode applies. The approval log records outcomes only: who, when, which agent, the project folder’s name, the kind of action (run, edit, fetch or other), allowed or denied, and whether a person, a team rule or session trust decided. Never the command, the file path or the URL. The manager can turn the log off, and it is kept for 90 days.
Sent to us: your account page
Seat usage on the account page comes from the licence check-ins above: when a seat’s Macs last checked in and how many there are. Nothing else about a person’s day is recorded.
Rollout

Signed and notarized by Apple, so macOS opens them with no warnings. Each app updates itself, and updates through Crest 7 are included.

Download links that stay put
crestnotch.app/download is always the newest Crest, crestnotch.app/take/download is Take and crestnotch.app/minutes/download is Minutes, each a signed disk image you can hand to your deployment tool.
Homebrew
Crest is in Homebrew: brew install --cask crest. Take and Minutes install from their download links.
Sign in with the seat email
Each person opens the app and signs in with the email on their seat. That is what unlocks it: there is no key to paste. Crest and Take need macOS 14 or later, and Minutes needs macOS 26 or later on Apple Silicon.

Download Crest