TechPulseTechPulse
Back to News
Advertisement
Advertisement

⚡ Community Insights

Discussion Sentiment

100% Positive

Analyzed from 132 words in the discussion.

Trending Topics

#permissions#deny#read#claude#bash#agents#settings#https#allow#list

Discussion (5 Comments)Read Original on HackerNews

tomaytotomato•about 3 hours ago
Not a criticism, but why would I use this instead of locking down my Claude using the allow/deny permissions list?

    "permissions": {
    "allow": [
      "Bash(npm run lint)",
      "Bash(npm run test *)",
      "Read(~/.zshrc)"
    ],
    "deny": [
      "Bash(curl *)",
      "Read(./.env)",
      "Read(./.env.*)",
      "Read(./secrets/**)"
    ]
  },
softie123•about 1 hour ago
Idea is not to deny permissions to everything but just keep a log on what the agents are doing thats not in line with our permissions and also you have to know what they are bypassing so we can put them in deny list later. Very useful when you spawn many agents working in parallel. This is more of an observability tool.
FishAngular12•about 3 hours ago
Where would one put this? In AGENTS.md?
abirch•about 3 hours ago
Your settings file: User settings are defined in ~/.claude/settings.json

or /permissions

https://code.claude.com/docs/en/permissions

AdmiralAsshat•about 4 hours ago
Probably needs a better metaphor than "police department", what with the most popular cop meme being:

https://www.reddit.com/media?url=https%3A%2F%2Fpreview.redd....