Sign up at claros.sh with Google, Microsoft or an email code. A new account creates your workspace and walks you through setup.

​
Your first 5 minutes

From sign-in to your first stop, with a policy you already have in writing. No install needed to see it work.
1

Sign in and name your workspace

Go to /signin and continue with your work email (a code), Google or Microsoft. Name your team’s workspace; Home opens on three steps.
2

Paste a policy

Paste a policy on Home: any written rules, a few lines are enough (deploy rules, code conventions, a refund policy). Press Draft the rules. Claros drafts each rule with the sentence it came from; nothing is enforced yet.
3

Approve the rules

Read each rule against its sentence, fix or remove what’s wrong, then Approve and enforce now. (Plain Approve map starts the rules in watch: counted, never stopping anything, so the test action below wouldn’t be stopped.)
4

Connect an agent

Run npx getclaros in the agent’s project and approve the sign-in it opens. It sets up MCP agents, Playwright and browser-use (Quickstart for agents). No terminal at hand: Make a key shows an agent key once.
5

Send a test action

Send a test action on Home checks a made-up action that breaks one of your rules and shows the answer right there: stopped, ask first or a nudge, with the rule and its sentence. In a terminal, npx getclaros test does the same. Nothing runs; the check shows up in Checks.
Measured on our test run (fake sign-in, real LLM drafting a three-rule policy): about 8 seconds of waiting in total, 4.5 of them drafting. The rest is your reading and clicking.

​
Add a rule

No policy in writing? Type one sentence in Add a rule on Home, the way you’d tell a teammate. Pick what happens when it’s broken (stop, ask or nudge, nudge by default), optionally the app it applies to (blank: wherever it’s relevant), and Just for me to keep it to your own checks and your agents’. An editor’s rule, or anyone’s Just for me rule, is live at once: the next check from any agent, browser hook or Claros for Mac can stop on it. A member’s team rule is proposed: it runs in watch, marked Suggested, until an editor confirms it (Roles). Try it below runs a sample message through the real check and shows the verdict; nothing is logged. See Rules & scope.

​
Record rules by voice

Some rules are easier to show than to write. An editor can share one window, do a real task and talk; Claros asks why at the pauses, reads the rules back and publishes them when confirmed. See By voice.

​
Connect your tools

Slack, GitHub, Google Drive, Notion and Linear (or their exports) become suggested rules, each with an owner to confirm. See Connectors.

​
Check people too

Claros for Mac checks a person’s Send, Submit and Approve moments against the same rules, in any app. See Claros for Mac.

​
Then guard your agents

The same rules check your agents. See Quickstart for agents.