Skip to main content
Download FreeNo credit card required
CoreLock Team / Developer add-on Pilot

One AI policy across every engineer's Mac.

See which AI tools, MCP servers and skills each engineer runs, who drifted from what you approved, and which keys to rotate when someone leaves.

PER ENGINEERPrice not published yetReports drift, never blocks
.corelock/policy.jsonexample
{
  "version": 1,
  "unlisted": "review",
  "mcp": {
    "approve": [
      { "package": "@playwright/mcp" }
    ],
    "block": [
      { "package": "postmark-mcp" }
    ]
  },
  "skills": {
    "approve": [{ "name": "commit-helper" }]
  }
}
Engineers matching policy
3of 6
Blocked1Needs review1
  • Dana N.Claude Code · Cursor · 7 MCP serversMatches policy
  • Sam L.postmark-mcp in ~/.cursor/mcp.jsonBlocked item
  • Ravi V.New skill: pr-summaryNeeds review
  • Kai O.Codex · Claude Code · 4 MCP serversMatches policy
  • Ana L.Cursor · 5 MCP serversUnknown since Mon
  • Jon B.Claude Code · 6 MCP serversMatches policy
Illustration · planned team viewExample data · Coming
01 · What it covers

AI tool rules, repo checks and connected accounts.

AI TOOL RULESComing

Approve or block MCP servers and skills once, for everyone.

Write the rules in .corelock/policy.json, or edit them once for the whole team. Each engineer's Mac compares its own AI tools to them, and you see who drifted.

unlisted: review → new items wait for a look
block: postmark-mcp → Sam L., with the fix on his Mac
REPO CHECKSComing

Check what steers an agent, before it reads it.

A repo's AI instructions, MCP settings, Claude hooks and CI workflows are checked on each Mac. Results roll up by repo and by person, and a deep read is shared once.

acme/web · .mcp.json → download-and-run server
acme/web · CLAUDE.md → nothing found
CONNECTED ACCOUNTSComing

Vercel, Supabase and AWS.

Each connection uses its own read-only key that the engineer creates for CoreLock, kept in the Keychain on their Mac. CoreLock's servers never hold it. Shared GitHub org and Vercel team alerts come later.

KEYS PER MACComing

Which Mac holds which work key.

By type and fingerprint, and whether it sits in plain text or in the Keychain. Never the key itself.

WHEN SOMEONE LEAVESComing

The rotate list, in order.

The keys and memberships to change when an engineer leaves. CoreLock never revokes anything for you.

02 · The privacy line

What the lead sees. What never leaves the engineer.

The lead also sees

On seats with the add-on, on top of what Team shows.

  • 01AI tools, MCP servers and skills by name, source, version and hash
  • 02Who matches the team policy, and who drifted
  • 03Work key counts, types and fingerprints on each Mac
  • 04The repo and file behind a policy finding
  • 05Credit spend by kind of job

Never shown to the lead

On any seat, with or without the add-on.

  • 01Source code and file contents
  • 02Prompts and agent sessions
  • 03Key values
  • 04Full local file paths
  • 05What an engineer sent for a walkthrough

See what changed across the team. Never the keys, never the code.

03 · Free on any plan

Free for every engineer, add-on or not.

The add-on sells the team view. The checks on each Mac stay free, for engineers and for everyone else.

  • AI agent snapshot

    The open files and network connections of recognized running AI agents, like Claude Code and Cursor.

    Available
  • AI setup check

    MCP servers, skills and hooks on the Mac: keys in plain text, unpinned packages, download-and-run installs.

    Coming
  • AI Analyst verdicts

    A quick AI read of one skill, MCP server or script for hidden instructions and tricks. Deeper walkthroughs use credits.

    Coming
  • Project folder check

    One repo's AI instructions, MCP settings, Claude hooks and CI workflows, on your own Mac.

    Coming
  • The policy file, on one Mac

    Compare this Mac to a repo's .corelock/policy.json, with no team needed.

    Coming
04 · The pilot

Priced per engineer. Never per repo.

Assign the add-on to any engineers on the team, at least one. Finding developer tools on a Mac never changes the bill by itself.

  • RequiresCoreLock Team
  • Billed forEach assigned engineer
  • CreditsThe team's shared pool
Pilotprice not published yet

Macs only. The policy is advisory: CoreLock reports drift and never blocks a tool.

Questions

The add-on, answered.

Does it block MCP servers or skills?

No. The policy is advisory. A blocked item shows as a status with a fix on that engineer's Mac. CoreLock doesn't stop a tool from running or an install from happening.

Does CoreLock read our source code?

No. It reads the files that steer AI tools, like AGENTS.md, CLAUDE.md, MCP settings, hooks and CI workflows, on each Mac. The lead sees item names, versions and hashes, never file contents, source code or prompts.

Where do connection keys live?

On the engineer's Mac, in the macOS Keychain. Each connection uses its own read-only key that the person creates for CoreLock. CoreLock never changes, revokes or deletes anything in those accounts, and its servers never hold the key.

Does it watch our CI?

No. Repo checks read workflow files for risky settings, like agents that run on comments from forks. CoreLock doesn't watch builds while they run.

What does the add-on cost?

The add-on is in a pilot with CoreLock Team, and its price is not published yet. It will be priced per assigned engineer, never per repo or per company.

I'm a solo developer. Is this for me?

The add-on is for teams. On your own, Pro is the plan: $9.99 a month, the same price for everyone, with Night watch and connected accounts added as they're released.