[GH-ISSUE #15924] Allow disabling some extensions to allow compliance with corporate security guidelines #72202

Open
opened 2026-05-05 03:37:35 -05:00 by GiteaMirror · 0 comments
Owner

Originally created by @neopunisher on GitHub (May 1, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/15924

I work at a corporation and they are not a fan of openclaw. It sets of our IDS and people start asking questions. Can we add a setting that can be configured to filter unallowed extensions? I was thinking even something like a configuration environment variable that could be set when its installed so people dont try to accidentally

ollama launch openclaw

that would be enough to make our compliance people happy and I could use local models.
Thank you for your consideration.
I can do the work myself I just want to know if it would be accepted and best way to implement.

Originally created by @neopunisher on GitHub (May 1, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/15924 I work at a corporation and they are not a fan of openclaw. It sets of our IDS and people start asking questions. Can we add a setting that can be configured to filter unallowed extensions? I was thinking even something like a configuration environment variable that could be set when its installed so people dont try to accidentally ```bash ollama launch openclaw ``` that would be enough to make our compliance people happy and I could use local models. Thank you for your consideration. I can do the work myself I just want to know if it would be accepted and best way to implement.
GiteaMirror added the feature request label 2026-05-05 03:37:35 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#72202