Sensitive Paths¶

nah protects sensitive filesystem locations from accidental access. Both directory paths and filename patterns are checked.

Built-in sensitive paths¶

Path	Default policy
`~/.ssh`	block
`~/.gnupg`	block
`~/.git-credentials`	block
`~/.netrc`	block
`~/.aws`	ask
`~/.azure`	ask
`~/.config/gcloud`	ask
`~/.config/gh`	ask
`~/.docker`	ask
`/etc/docker`	ask
`/var/run/docker.sock`	ask
`/run/podman/podman.sock`	ask
`~/.kube`	ask
`/etc/systemd`	ask
`~/.config/systemd/user`	ask
`/lib/systemd`	ask
`~/.config/az`	ask
`~/.config/heroku`	ask
`~/.terraform.d/credentials.tfrc.json`	ask
`~/.terraformrc`	ask
`~/.claude/settings.json`	ask
`~/.claude/settings.local.json`	ask
`~/.bashrc`	ask
`~/.bash_profile`	ask
`~/.bash_aliases`	ask
`~/.bash_login`	ask
`~/.bash_logout`	ask
`~/.profile`	ask
`~/.zshrc`	ask
`~/.zshenv`	ask
`~/.zprofile`	ask
`~/.zlogin`	ask
`~/.zlogout`	ask
`~/.bashrc.d`	ask
`~/.zshrc.d`	ask
`/etc/shadow`	block

These are checked for guarded file-oriented tools: Bash, Read, Write, Edit, MultiEdit, NotebookEdit, Glob, and Grep.

Built-in sensitive basenames¶

Basename	Default policy
`.env`	ask
`.env.local`	ask
`.env.production`	ask
`.npmrc`	ask
`.pypirc`	ask
`.pgpass`	ask
`.boto`	ask
`terraform.tfvars`	ask

Basename matching triggers regardless of directory -- a file named .env anywhere will be flagged.

Hook self-protection¶

~/.claude/hooks/ is always protected. Write, Edit, MultiEdit, and NotebookEdit to this directory are blocked (not just asked). This is immutable -- no config can change it.

Config options¶

sensitive_paths¶

Override policies for existing paths or add new ones:

# ~/.config/nah/config.yaml
sensitive_paths:
  ~/Secrets: ask            # add new sensitive directory
  ~/Documents/taxes: block  # add new blocked directory
  ~/.aws: ask               # already default, but explicit

Valid policies: ask, block. Project config can only tighten by default (e.g., escalate ask to block), unless global config explicitly sets trust_project_config: true.

sensitive_paths_default¶

Set the default policy for all sensitive paths:

sensitive_paths_default: block   # default is "ask"

allow_paths¶

Exempt specific paths from sensitive path checks for a given project:

# ~/.config/nah/config.yaml (global only)
allow_paths:
  ~/.aws/config:
    - /Users/me/infra-project

This allows ~/.aws/config access only from /Users/me/infra-project. The exemption is scoped to the project root.

CLI: nah allow-path ~/.aws/config

trusted_paths¶

Directories outside the project root where Write/Edit/MultiEdit/NotebookEdit are allowed without asking:

# ~/.config/nah/config.yaml (global only)
trusted_paths:
  - ~/builds
  - /tmp/staging

Without this, Write/Edit/MultiEdit/NotebookEdit to paths outside the git project root triggers an ask decision (project boundary check).

CLI: nah trust ~/builds

Global config only

Both allow_paths and trusted_paths are only accepted in global config. Project .nah.yaml cannot modify them.

profile: none¶

Setting profile: none clears all built-in sensitive directories and basenames. The hook self-protection (~/.claude/hooks/) remains active regardless.