4 ms·
For me the most pragmatic way to solve this is in the agent harness layer simply prohibiting commands like git force and others in the settings configuration of
by msejas 2mo ago
For me the most pragmatic way to solve this is in the agent harness layer simply prohibiting commands like git force and others in the settings configuration of your harness of choice with pre tool hooks, its quite easy to setup, obvious ones are prohibiting pushes to main, among others.
Unless someone is building their harness from scratch like you this is a 30sec configuration and you could just save your list of blocked commands with wildcards in a file, and copy paste from one harness to the other.
- knighthacker 2mo agoAgreed. I had to solve this at the harness layer myself. It just makes more sense to me this way. We basically created hooks around these operations and you can configure what happens at these calls. Disclosure: I'm building AQ (aq.dev) a multiplayer coding harness.
- msejas 2mo agoChecked it out, it doesn't particular talk to me but for sure other people, looks like a cool project! Wish you best of luck and success!