Hey HN, I've had a side-project that I've slowly ticked away at over the last year called Tilde. Tilde is a harness SDK platform - I've tried to take the best things of OpenClaw, H…

Over a year later into building this side project, point 1 is still true. On the other hand other frameworks, libraries and harnesses have come a long way but I still find myself reaching daily to Tilde to build agents to automate things for me. Having worked through the common pitfall most software engineers make, namely that "there's always one more feature before it's ready" - I can finally convince myself that it's ready. I've taken out the meat of what makes a good harness, and composed it into components you can pick and choose to give to your agent: Everything in Tilde is cloud based & centrally managed & permissioned. I've currently built a client-side library to work with Vercel's AI SDK but expect other frameworks and languages to be supported in future. One of the first agent's I built with Tilde was a code-review agent. I'm a software engineer and we tend to have a habit of automating ourselves out of work so what the heck. TLDR; here's the final example you can deploy yourself: https://github.com/trytilde/examples/tree/main/code-review-bot With Tilde, I could essentially just focus on point 7 in the above diagram and the Tilde's SDK took care of everything else. For bonus points: You'll notice a tilde-state.yaml file in the example github repo above. You can spin up a Tilde account, head to your settings and import it there to setup the required Tilde infrastructure and integrations. From there it'll ask you to configure your Github & Modal sandbox settings. This is how I've designed the system to be as portable as possible. I've spent a lot of time and energy into building the platform but less so on the docs - expect them to get a refresh in the coming days.