Ask HN: Why don't LLM harnesses enable/expose custom middleware hooks?
I want to be able to execute a prompt derived from a piece of structured data (JSON) by transforming it into markdown and decorating it at prompt-time, without building my own infrastructure around or alongside the harness...
(
8 comments
| 4 points
| on HN
)
Can you give an example of your use case?
The newer models are nice, but the harness is the secret sauce that can make or break the experience. I wish we had better open tools for using/modifying these types of things.
create a skill that transformed the json then "/<skill> <prompt>"
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.