hi thank you for reporting this, definitely will check it out

Yo @divakaran5005 — the issue is likely that OpenClaude doesn't support shell script hooks like file-access-enforcer.sh the way the CLI does.
The CLI is shell-native, so it can execute your .sh file directly. OpenClaude (depending on the specific client/wrapper you're using) usually looks for config-based permissions in settings.json instead of external scripts.
You'll likely need to translate that bash logic into OpenClaude's specific permission format or check if it has a "Middleware" feature that handles file I/O restrictions. That .sh file won't work automatically unless OpenClaude explicitly supports external command execution.

Hi @P-r-e-m-i-u-m @kevincodex1

I am new to the developer community and still learning. I found a CLI tool called Pi.
I have tried many CLIs: Codex, Ader, Qwen, Kimi, Claude Code, Opencode, Rocode, Cline, OpenClaude, and Pi. After testing them, I feel Pi is the most powerful. The problem is that with Pi we need to build everything from the beginning. The good thing is that there is already a community creating extensions.

Claude code is good, but I cannot use another model.

I am join as Vibe coder, but I am still struggling.

If we can combine Open Claude with Pi and its extensions, it could become one of the most powerful CLIs in the world. I really believe this. I don’t know how many people have used Pi, but I suggest you try it. If possible, ### "integrate OpenClaude with Pi".

I checked the Claude code source code with the help of AI. Right now, Open Claude still depends on Claude’s original source code modules. Because of that, some functions do not work — including Hooks.