Manage Claude Code permissions visually.
Bundle permissions, hooks, and environment variables into one named Harness Profile, then export straight to settings.json. No more hand-editing JSON.
Screens
What it does
- 01Harness Profile
- One named bundle of permissions, hooks, and env vars. Switch profiles per project or per agent.
- 02Four built-in presets
- Import readonly, backend-dev, prod-safe, or full-auto in one click, then tune it into your own.
- 03Wildcard permission rules
- Flexible allow/deny rules — allow Bash(*), deny Bash(git push --force*).
- 04Hooks that can block
- Attach shell commands to PreToolUse, PostToolUse, Stop, or Notification. Set blocking: true to hard-stop a dangerous call.
- 05Live JSON preview
- See the exact settings.json that will be written before you export it — no surprises after the fact.
- 06Import / export
- Import an existing settings.json as a new profile, edit it, export it to any .claude/ folder.
How it works
Create a profile
Start from a preset or from scratch. Give it a name and description.
readonly / backend-dev / prod-safe / full-auto
Set permissions, hooks, env
Move between tabs to add allow/deny rules, hooks, and environment variables.
allow Bash(*) · deny Bash(git push --force*)
Export
Pick your project's .claude/ folder — or ~/.claude/ — and write it out.
✓ Exported → .claude/settings.json
Good to know
- Unsigned build — on first launch your OS will say the developer can't be verified. On macOS, right-click the app → Open.