ridruejo

You are overthinking it :) You are one of the most interesting people on HN. I am sure others think along those lines too and would love to learn more about what you are building and where the industry is going. Others can just tune it out.

Despite the title (the original in the Reddit thread) it is an interesting and timely update from the OpenClaw foundation

Local models are one of the main drivers for our installer / Desktop app for OpenClaw https://holaclaw.ai (disclaimer I am one of the founders). The smaller models are really only suitable for the most basic tasks, but if you have 32gb-64gb you can get real work done (ie complex web workflows) without third party hosted models

Hola! Co-founder here. We made HolaClaw, a free desktop app for OpenClaw on Mac. It features a 1-click install (just a regular .app that you drag into the Applications folder), secure default settings (curated set of skills, agent running inside a VM) and can optionally run local models. Looking forward to your feedback!

Forgot to mention there is also a companion cli tool (also open source) that just reads directly from your agent data directories and skips the uploading part. You can also use it to anonymize a session and share it using GitHub Gists.

npx @endorhq/capsule --help

Hi, one of the cofounders here! We work with a ton of different agents in our other open source project, Rover (https://endor.dev/rover). Sometimes we need to debug how the agents are behaving and we built this tool to make our life easier. It is a web interface in which you can upload sessions logs that you have exported from Claude, Codex or any other coding agent. You can easily navigate them, check the reasoning, tool calls, etc. as well as explore what subagents were doing. Everything happens local to the browser, so no data is sent to any server.

It can also be used to safely share agent session logs with others, either projects you are contributing to or to troubleshoot something. It has an optional, built-in anonymizer so no private information leaks accidentally.

Endor cofounder here, happy to answer any questions you may have!

We applied a lot of the technical hacks described in this article and the original one to provide a full Linux environment (including networking and mounting directories) running inside the browser. https://endor.dev/s/lamp

Pretty cool

The secondary provided that relief. Continuing to work on the company makes perfect sense if you enjoy it, which he clearly does (with the inescapable ups and downs of every start up of course).

Correct. The secondary provides the safety net to confidently swing for the fences.

This is a really well-written article. The whole thing is so absurd and this makes it so clear.

Hi! Co-founder here, happy to answer any questions you may have

We do Rover, which is different from the Microsoft product but the goal is similar. I was just responding to the above comment. I agree with you, it is a pretty good project and will be taking a look. We are so early there are tons of things to learn and try.

The main use case why we developed Rover internally (and still is) was the ability to run agents in parallel. It allows us to go much faster but requires tooling around it.

Secondarily it makes it easier for everyone to share those best practices and tooling among us, but is less of an issue because we are a small team

You may not be the target user for this project then and that’s fine! They are releasing this as a research project so a business model was not probably one of the key decision points.

Not sure if you are being serious or not. That was indeed the point of the very first Linux distros and why most people use them nowadays vs the alternative.

I started using Linux before there were distros (circa 1993) and it was not a pleasant experience compared to when Slackware came out

Our “product” is a tool we developed internally and found it so useful that decided to open source it.

With full potential I refer to getting the best possible results. For example, being able to work on tasks in parallel without Claude instances interfering with each other vs , well, no doing so.

Exactly. I don’t understand the cynicism in the comments and they literally are just trying to make the technology more accessible

I see a Linux distro as a collection of libraries that someone puts together following best practices and conventions (ie all config files go into /etc). The similarity with this project is that Microsoft has taken a collection of tools and best practices and put them together in an easy to install package

How can it be gatekeeping when they are literally making it easier to use? The analogy is probably closer to a Linux distro. You can put everything together yourself but if someone gives you a pre integrated environment with best practices it makes it easier to get started

Agreed, it is in my bio but I updated the post in any case

We have built Rover, an OSS tool that allows you to run multiple instances of Claude (and Codex, Gemini...) while keeping them from stepping on each other toes using containerized environments and Git worktrees https://github.com/endorhq/rover/

You can use Rover (disclaimer, I am one of the cofounders) which is an open source tool that you can use to parallelize the work of coding agents that in addition to Claude also works with Gemini, Codex and Qwen https://github.com/endorhq/rover/

This matches our experience developing with agents. In particular, as we wanted to use multiple agents in the background to do tasks, we had to really invest in different areas so they would not go in wild directions or have to ask continually for feedback, defeating the purpose of working in the background. First, we needed to provide relevant context on how to do the task (some of it is "generic" like Svelte documentation, some of it is specific to how to write tests for our particular project), be extremely detailed and specific in the prompt about what we want and how to go about it (divide it in different well defined steps) and finally provide with specific tools via MCP (like MySQL access and installing system packages). Once we consistently do all this work upfront, it really pays off because you can launch a large number of agents in parallel that don't interfere with each other (git worktrees, containerized environments) and don't require babysitting for the most part. We just open sourced the tooling we used internally for this: https://github.com/endorhq/rover

A2C?

Previous submission here with some comments already: https://news.ycombinator.com/item?id=45481585

This is a great article and not sure why it got so few upvotes. It captures the way we have been working for a while and why we developed and open sourced Rover (https://endor.dev/blog/introducing-rover), our internal tool for managing coding agents. It automates a lot of what Simon describes like setting up git worktrees, giving each agent its own containerized environment and allowing mixing and matching agents from different vendors (ie Claude and Codex) for different tasks

Thanks! Looking forward to your feedback

Hi! Co-founder of Endor/Rover here, happy to answer questions you may have