Crater Scope analyzes your codebase and generates role-based scopes that control what each team member can modify. Works with Claude Code today.
packages/api/src/payments.ts is not covered by your scopes:Import your repo, let AI generate scopes, assign them to your team.
Connect GitHub and select which repositories to manage. Crater Scope reads your file structure and config files — never your code.
Our AI analyzes your codebase architecture and generates semantic scopes by area — UI, API, database, auth, config — tailored to your actual stack.
Assign scopes to team members. When they use Claude Code, scope restrictions are enforced automatically. No workflow changes required.
--dangerously-skip-permissionsNot just file paths — Crater Scope understands what a change does. A CSS change in a .tsx file is different from a logic change in the same file.
Import a repo and get role-based scopes in seconds. Knows the difference between a Next.js app and a Django project.
Installs as a plugin. No workflow changes. Scopes are enforced through Claude's own instruction system — invisible to your team.
Invite members via email, pre-assign scopes before they even join. Device-code CLI auth like GitHub and gcloud.
Works even when users run Claude Code in full permission-bypass mode. Scope enforcement lives in the instruction layer, not the permission layer.
See when team members attempt out-of-scope changes. Audit trail for compliance. Coming soon: PR review bot integration.
Set up in under 5 minutes. No code changes required.
npx craterscope init