Ask HN: Why don't LLM harnesses enable/expose custom middleware hooks?

https://pi.dev specifically prides itself on having many extensions hook points. Is that one you've looked at? If so, it might be something they'd be willing to add a hook for if you open an issue.

I've been pondering over the same question, but also on an enterprise scale. For example, how could I scrub the customer data, like name, domain, etc., before sending it to LLM if my Claude code is using some MCP to fetch and debug an issue?

I mean, hooks are nice, but they are messy to manage/operate for many developers at a time.

https://github.com/softcane/cc-blackbox I started investigating the proxy path, which I think would be useful for such scenarios.

I am writing my own harness, and I would love to hear more about what you have in mind.

Can you give an example of your use case?

that's sort of what skills are.

create a skill that transformed the json then "/<skill> <prompt>"

They do. See: Claude Code leak.