Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Control Claude permissions using a cloud-based decision table UI

github.com

Post reply on HN
Print view View original

1–10 of 13 posts

Show HN: Control Claude permissions using a cloud-based decision table UI

#1

Post by sidgarimella »

We’ve been building visual rule engines (clear spreadsheet interfaces -> API endpoints that map incoming data to a large number of potential outcomes), and had the fun idea lately to see what happens when we use our decision table UI with Claude’s PreToolUse hook.

The result is a surprisingly useful policy/gating layer– these tables let your team:

- Write conditional, exception-friendly policies beyond globs/prefixes (e.g. allow rm -rf only in */node_modules/*, deny / or $HOME, ask if --force or network call; gate kubectl delete / SQL DROP with a clear reason)

- Roll out policy changes instantly (mid-run, flip a risky operation from allow → ask; the next attempt across devs and agents is gated immediately– no git pull or agent restart required)

- Adopt lightweight governance that is somewhat agent agnostic and survives churn (MCP/skills/etc)- just add columns/rules as new tools and metadata show up

- Gain a central utility to understand which tools are being used, which tools get blocked most often, and why

Show HN: Control Claude permissions using a cloud-based decision table UI
github.com

Re: Show HN: Control Claude permissions using a cloud-based decision table UI

#4

Post by bflesch »

It's hard for me to comprehend how ublock origin blocks a total of 10 different tracking scripts on your website https://rulebricks.com/ and all you can come up with is a small text in the bottom saying "This website may collect cookies to optimize your user experience".

"May collect cookies"? Do you think google makes money by collecting cookies? You are brazenly lying into my face and even using a dark pattern to hide this ridiculously formulated sentence at the bottom of the screen.

Why does your company decide to employ falsehoods and dark patterns at such an obvious place? It erodes any trust.

Re: Show HN: Control Claude permissions using a cloud-based decision table UI

#5

Post by sidgarimella »

bflesch wrote: post #4

It's hard for me to comprehend how ublock origin blocks a total of 10 different tracking scripts on your website https://rulebricks.com/ and all you can come up with is a small text in the bottom saying "This website may collect cookies to optimize your user experience". "May collect cookies"? Do you think google makes money by collecting cookies? You are brazenly lying into my face and even using a dark pattern to h…

The wording has been updated, and we’ll review our instrumentation. Appreciate your feedback.

Re: Show HN: Control Claude permissions using a cloud-based decision table UI

#6

Post by threecheese »

I like the approach, I’ve been looking for something with a UI but not from a corp compliance perspective; as I scale usage of Claude I am finding permission checks to be a huge pain in the neck. In my circle, you can identify someone who uses the heck out of Claude Code by their use of —dangerously-skip-permissions (I did that with fat fingers but without typos, that’s how often I need it).

Re: Show HN: Control Claude permissions using a cloud-based decision table UI

#7

Post by sidgarimella »

threecheese wrote: post #6

I like the approach, I’ve been looking for something with a UI but not from a corp compliance perspective; as I scale usage of Claude I am finding permission checks to be a huge pain in the neck. In my circle, you can identify someone who uses the heck out of Claude Code by their use of —dangerously-skip-permissions (I did that with fat fingers but without typos, that’s how often I need it).

Guilty as charged

Thoughts on /permissions from the CLI?

Re: Show HN: Control Claude permissions using a cloud-based decision table UI

#8

Post by furyofantares »

threecheese wrote: post #6

I like the approach, I’ve been looking for something with a UI but not from a corp compliance perspective; as I scale usage of Claude I am finding permission checks to be a huge pain in the neck. In my circle, you can identify someone who uses the heck out of Claude Code by their use of —dangerously-skip-permissions (I did that with fat fingers but without typos, that’s how often I need it).

> I did that with fat fingers but without typos, that’s how often I need it

You mean you don't just have it aliased to "claude" ?

Post reply on HN