Skip to content
Claros, home

Your agents know the tools. They don’t know how you work.

Claros learns the rules your best people never wrote down and checks every agent and person at the moment of action.

Get started

For people: the Mac appFor agents: one command

$ npx getclaros

Guards Claude Code, Cursor and Codex (hooks + MCP). Signs you in through the browser. Browser agents

fig. 1/3 — AP agentan AP agent books an invoice

Agents break the rules they’re given. Most of yours were never written down.

Learned from the people who hold the rules.

  1. Connect tools and docsSlack, GitHub, Drive, Notion, Linear, policies. Or add a rule in one sentence.
  2. The owner confirmsEach rule has a name on it. Mined and drafted rules watch first, then act when the owner says.
  3. Checked at the actionAgents before the action runs. People at Send.
  4. Answers become precedents, then rulesThe same action is never asked twice.

Taste and compliance are the same problem.

  • Design systems lead, Design: “If it’s not a token, it’s a bug. No hand-picked hex values.” Coding agent writing CSS: nudged with a fix, fix: use var(--primary).
  • AP manager, Finance: “New bank details for a vendor? Call a number we already have. Never trust the email.” Agent updating a vendor: stopped.
  • Brand lead, Marketing: “We say ‘customers’, not ‘users’. No exclamation marks in headlines.” Agent writing site copy: nudged with a fix, fix: say customers, drop the !.
  • Eng manager, Engineering: “Nothing goes to prod during the freeze. Not even a typo fix.” Agent triggering a deploy: stopped.
  • Account executive, Sales: “First email: three sentences, one question. No feature dump.” Agent drafting outbound: nudged with a fix, fix: 3 sentences, 1 question.
  • Commercial counsel, Legal: “We never accept uncapped liability. Flag any edit that touches the cap.” Agent redlining a contract: stopped.
  • Support lead, Support: “Apologise once, then fix it. No ‘we deeply regret any inconvenience.’” Agent drafting a reply: nudged with a fix, fix: one sorry, then the fix.
  • Controller, Finance: “Anything over $10k gets my sign-off, approved vendor or not.” Agent approving an invoice: asks the owner.
  • Analytics lead, Data: “Revenue means net of refunds. If you mean gross, say gross.” Agent writing SQL: nudged with a fix, fix: rename to net_revenue.
  • People partner, People: “Pay numbers never go in a channel, even a private one.” Agent posting in chat: stopped.
  • Head of product, Product: “Empty states show the next step. No ‘Oops, nothing here.’” Agent writing in-app copy: nudged with a fix, fix: show the next step.
  • Sales director, Sales: “Past 15% off goes to deal desk. Don’t float it in the email first.” Agent drafting a quote: asks the owner.
  • Staff engineer, Engineering: “Controllers don’t talk to the database. Go through the service.” Coding agent’s pull request: nudged with a fix, fix: call OrderService instead.
  • Security engineer, Security: “No keys in code, logs, or tickets. If you pasted one, it gets rotated.” Agent committing code: stopped.
  • Product designer, Design: “One primary button per screen. Two means nobody decided.” Agent generating a screen: nudged with a fix, fix: second button: secondary.
  • Data protection officer, Data: “Raw emails and phone numbers don’t leave the warehouse.” Agent exporting data: stopped.
  • Operations manager, Ops: “Reschedule a customer once. The second time, a person calls.” Agent in the scheduling tool: asks the owner.
  • Accessibility lead, Design: “Body text clears 4.5:1 contrast. Brand grey doesn’t get an exception.” Component pull request: stopped.

stopasknudge

Try one of yours.

0/400 · empty tries the example · nothing is saved

Your rule’s card lands here, with two actions checked against it.

Hard rules stop. Unclear ones ask. Taste nudges.

Every agent and person, every check logged. Coding agents too: Claude Code, Codex and Cursor, through hooks and MCP. And apps with no API, via Pomerado.

Tool use, over MCP

An agent calling your apps

“Money goes back the way it came in. Never onto a gift card.”

Claros for Mac, in the notch

A person, at the moment they hit Send

“Refunds past 30 days or over $200 go to a person.”

Playwright, browser-use

An agent clicking through a website

“Apologise once, then fix it. No ‘we deeply regret any inconvenience.’”

Benchmark · 2026-10-23

Agents keep to the rules more often with Claros.

+16 ptsaccuracy over the team’s docs in the agent’s context on both sets, +24–29 over RAG. GLM-5.3 Flash, 282 agent actions, one set held out.

See the benchmark Whitepaper (PDF)
Accuracy · GLM-5.3 Flash

Standard · 122 actions

Claros93%

Repo docs77%

RAG69%

Held out · 160 actions

Claros91%

Repo docs75%

RAG63%

Agents break written policy: PhantomPolicy, HANDBOOK.md.

What works now.

Next: the record agent work is insured and audited on.

  1. PreviewCompanyRules from your tools, each with an owner.
  2. PreviewPersonClaros for Mac, in the notch. Quiet until it matters.Get the Mac app
  3. LiveAgentsEvery person’s agents, checked before each action.npx getclaros
    Claude Code · Cursor · Codex
  4. LiveEvidenceA signed record anyone can verify.hash chain · Ed25519
    SIEM · AIUC-1 pack

Show us one workflow your agents must not get wrong.

You talk to the founder.

For people: the Mac appFor agents: one command

$ npx getclaros

Guards Claude Code, Cursor and Codex (hooks + MCP). Signs you in through the browser. Browser agents