OkayTeacher
EN English 한국어 日本語 中文 हिन्दी বাংলা اردو Español Português Français Deutsch Русский العربية Bahasa Indonesia Tiếng Việt ไทย Türkçe

How to enable notifications

Notifications are unavailable in this browser or on this address. Try a supported browser on the secure SONUB site.

If notifications are blocked, allow them in your browser settings.

  1. Open the site controls beside the address bar, or your browser’s site settings. Set Notifications for this site to Allow.
  2. In your device settings, allow notifications for your browser and check Do Not Disturb or Focus.
  3. Return to SONUB, reload the page, and use the bell to enable notifications.

On iPhone or iPad, add SONUB to your Home Screen, open it there, then allow notifications.
Glossary · Learn more

Project trust

Approving a folder before loads its settings. See what it is, how it works, how it is used and what to watch for, with pictures and examples.

Back to the glossary Claude Code
A closed folder waiting at a front door until a key of light unlocks it, showing a folder approved before its settings load.

What it is

Project trust is the check does the first time you start it in a folder in an interactive session. A can bring its own .claude/settings.json, and some entries there give extra power, such as permissions.allow rules and additionalDirectories. The trust dialog lists those entries so you can read them first, and Claude Code doesn't use them until you accept. deny and ask rules work anyway, because they only restrict. In a repository the answer is saved for the repository root, but in your home folder it lasts only for the current session.

How it works

  1. Start claude in a new folder
  2. Read what the dialog lists
  3. Accept only if you trust it
  4. Answer is saved for that repository

How to use it

  1. ~/.claude.json

    keeps per-project state, including your trust answers. The key is hasTrustDialogAccepted.

  2. claude -p

    never shows the dialog. Project allow rules are not used and a this workspace has not been trusted warning goes to stderr, but hooks and .mcp.json still run.

  3. --setting-sources user

    before running claude -p in a repository you didn't write, this makes Claude Code skip the project's settings files and .mcp.json.

  4. .claude/settings.local.json

    your own untracked file. Its allow rules apply without the trust step, unless git tracks the file.

Watch out

Trust does not hold back everything. Hooks and the env block in a repository's settings are used even when you trusted only a parent folder or ran claude -p. Start Claude Code from a project folder, not your home folder, because home-folder trust is never saved and the dialog comes back on every launch.

Original and official docs

This page explains the term in plain words. The original is the authority: if they differ, follow the original.