ES version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
43% Positive
Analyzed from 983 words in the discussion.
Trending Topics
#openclaw#enterprise#team#agents#systems#code#claude#https#com#claw
Discussion (21 Comments)Read Original on HackerNews
The biggest feedback we collected was that any tasks they assigned to the Claw systems would turn into tangled messes often requiring significant time investment to understand, and mostly ending in the team scraping the code changes over quality concerns. The team really struggled to find anything these Claw systems could be tasked with that wouldnt end in poor results, So we ended up scraping the idea entirely. I think it will be quite a few more years until these types of systems are appropriate for the enterprise.
As a learning exercise it was pretty nice. But since then the plugin/connector ecosystem for things like Claude Code/Cowork and ChatGpt/Codex has first come into existence and then matured to the point where they do most of what made OpenClaw interesting before that was the case. But in a way that can be shipped to lots of users. That wasn't true when I started using it. We played with it for a bit but in the end the code base is a mess, random shit breaks every time you update it, and you end up doing very dodgy shit with it that no responsible CIO would want to sign off on.
The current batch of tools from Anthropic and OpenAI is pretty solid but there are still lots of feature gaps, UX issues, security challenges, etc.
I think a lot of these tools will get into the enterprise in exactly the same way that usb sticks, MS Office, smart phones and other consumer tech got into the enterprise: employees will bring them and use them. Some bosses will tell them off and then make an exception for themselves. Because the promise of not having to do monkey work that can now be automated is unbelievably tempting if you need to do lots of that work. Even if this stuff only half delivers on some of the promises. So, my guess is that this could go fairly quickly. I already see a lot of non technical people that are pretty clued in to things like Claude Cowork. There will be some rogue early adoption followed by more enterprise appropriate solutions. That's already happening.
Here in Germany, there are a few German AI companies that work with big conservative German companies and the public sector (e.g. Langdock and Deepset). The type of organization where privacy and data security concerns weigh heavily. These companies can work with OSS models but OpenAI can do proper data residency in Germany as well if you talk to them. Azure, AWS, and others have very acceptable options. And there's a whole ecosystem of companies that are building on top of that.
I created Atom based on current research on agentic systems and am looking for maintainers & testers to help out.
https://github.com/rush86999/atom
https://github.com/rush86999/atom/blob/main/docs/features/at...
That's why we built https://lobu.ai which is a multi-tenant implementation for proactive agents like OpenClaw. It has entity based memory for building the org context layer and every channel/user gets its isolated container.
Protocol aware network proxy coming soon Then you can match a DSL and block particular network requests.
This ensures you no longer fear --dangerously-skip-permissions and stop babysitting agents
What else would you want to see in this project? Please star the repo, if you like the idea :)
With all the openAI token spend they get, where do you think the project will be in a year?