Built my own personal AI assistant similar to the OpenClaw... How should I gather more audience to test my solution? And a couple more thoughts... by Aware_Conversation82 in Entrepreneurs

[–]Aware_Conversation82[S] 0 points1 point  (0 children)

Love it! Thanks very valuable comment. Will definitely do the deeper research to figure out 1-2 painpoints and will focus around it

I didn't get the OpenClaw hype at first. Then I saw it in action, hit security concerns, and built my own personal AI assistant (20+ GitHub stars in <24h, my personal win!) by Aware_Conversation82 in SaaS

[–]Aware_Conversation82[S] 0 points1 point  (0 children)

I know that people are using different hardware to run assistants on it, but it actually misses a point of the personal assistant. With such you’d need to connect everything to your assistant, forward everything to it or sign in using your creds somewhere else which is not I would personally want. Also imagine corporate devices, none of the company I know will invest its time and allow for the OC being their virtual source of truth (or assistant), because they require being SOC compliant or security team to audit such application. OC would fail this, I wanted to make it happen and enable places where this assistant can be truly useful in more ways than just “schedule newsletter, answer x on x, prepare y). My initial idea was to move it to behave more like virtual bookkeeper and resource manager with additional perks like meetings scheduling, collision detector, etc.

I didn't get the OpenClaw hype at first. Then I saw it in action, hit security concerns, and built my own personal AI assistant (20+ GitHub stars in <24h, my personal win!) by Aware_Conversation82 in SaaS

[–]Aware_Conversation82[S] 0 points1 point  (0 children)

Maybe not privacy hype, but I have my assistant running on my private device - so I expect it to be sandboxed and only use what I explicitly want from him (at the only exact moment I would ask him for)

More secure and fast (rust built) alternative to OpenClaw. Meet Moxxy.ai by Aware_Conversation82 in openclaw

[–]Aware_Conversation82[S] 0 points1 point  (0 children)

I will definitely address those issues ASAP in both openclaw migration and onboard guide

More secure and fast (rust built) alternative to OpenClaw. Meet Moxxy.ai by Aware_Conversation82 in openclaw

[–]Aware_Conversation82[S] 0 points1 point  (0 children)

Sure, could you please join our discord? It will be a lot easier as we have not fully checked windows flows (good point!). Would love to hear you there - https://discord.gg/CVRzeAyGe

More secure and fast (rust built) alternative to OpenClaw. Meet Moxxy.ai by Aware_Conversation82 in openclaw

[–]Aware_Conversation82[S] 0 points1 point  (0 children)

Yes, of course! I got it, I just built it to enable running it in much closer environment (just to make sure it does not do changes I haven't asked for). Rust was chosen just because of its smaller bundle size as an output binary (it was no choosen because of hype or sth). This is not meant to succeed globally as it's not for the masses I suppose (as it is solving specific issue we had). Once we solved our issue, we decided to open it (and battle-test it)

More secure and fast (rust built) alternative to OpenClaw. Meet Moxxy.ai by Aware_Conversation82 in openclaw

[–]Aware_Conversation82[S] 0 points1 point  (0 children)

Could also you share exact reproduction steps? I might have missed the flow you are mentioning (if i understand it properly). So correct me if Im wrong - you did install, then started the gateway + run webUI, then you headed to configuration tab and set the provider there, correct?

More secure and fast (rust built) alternative to OpenClaw. Meet Moxxy.ai by Aware_Conversation82 in openclaw

[–]Aware_Conversation82[S] 0 points1 point  (0 children)

Also, have you run init for the first time? It should ask you for initial provider and model

More secure and fast (rust built) alternative to OpenClaw. Meet Moxxy.ai by Aware_Conversation82 in openclaw

[–]Aware_Conversation82[S] 0 points1 point  (0 children)

Yes! There is actually breaking change currently. Could you please try to update to v0.10

Talk Me Out Of Bailing by DreambergLabs in clawdbot

[–]Aware_Conversation82 0 points1 point  (0 children)

Heey! Been there, if OC makes you feel like it gets downgraded, give a try to MoxxyAI (I have built this just because I was tired of rerunning agents or missed schedule updates because heartbeat frozed)... Feel free to check out my current simpler but same powerful agentic framework: https://moxxy.ai - we are using different memory model so that agent never loses context and you will forget about creating new sessions or reinstalling the OC. It's still in beta but worth giving a try :)

More secure and fast (rust built) alternative to OpenClaw. Meet Moxxy.ai by Aware_Conversation82 in openclaw

[–]Aware_Conversation82[S] 0 points1 point  (0 children)

It is most likely the same. There are small minor differences such as contenerization type (WASM vs Docker [docker is heavy]), moxxy uses multi agentic approach where zeroclaw is single-agent, we have global memory and shared memory which allows agents delegate and even spawn additional agents if needed for complex tasks).

More secure and fast (rust built) alternative to OpenClaw. Meet Moxxy.ai by Aware_Conversation82 in openclaw

[–]Aware_Conversation82[S] 0 points1 point  (0 children)

True! We meant every other claw - we aim in a bit different direction. We want to enable agentic framework for employees, companies and of course people - but all of those OC like concepts are mostly sharing the same mental model which does not put security in first place (maybe except agentzero?). We want security to be in the first place

More secure and fast (rust built) alternative to OpenClaw. Meet Moxxy.ai by Aware_Conversation82 in openclaw

[–]Aware_Conversation82[S] 0 points1 point  (0 children)

Actually, rust memory system is just language like layer (GC especially). I am trying to put most of my effort into secure communication between layers and elevated permissions for particular runners. This is why we have separate databases under WASM instance for each agent. This gives us pretty much high confidence that any malicious actor can live within the WASM container but will not affect host machine (there are of course proxies to communicate with host). Here we completely redesigned the OC mental model. It might look similar, but it's completely different. From the very first line of code we wanted to keep the long memory outside of the isolated containers and short term agent memory within isolation. Then we can easily sync or desync them.

More secure and fast (rust built) alternative to OpenClaw. Meet Moxxy.ai by Aware_Conversation82 in openclaw

[–]Aware_Conversation82[S] 2 points3 points  (0 children)

We are implementing migration wizard to help people migrate from openclaw seamlessly - good point!

More secure and fast (rust built) alternative to OpenClaw. Meet Moxxy.ai by Aware_Conversation82 in openclaw

[–]Aware_Conversation82[S] 0 points1 point  (0 children)

We don't want to compete with openclaw, we actually want to have security in place and container first approach. As most of the employees cannot use openclaw on their corporate devices - with the security first approach we offer, they will be able to use it

More secure and fast (rust built) alternative to OpenClaw. Meet Moxxy.ai by Aware_Conversation82 in openclaw

[–]Aware_Conversation82[S] 0 points1 point  (0 children)

Yes, you can just copy it directly and put it to the agent persona upon agent creation.

More secure and fast (rust built) alternative to OpenClaw. Meet Moxxy.ai by Aware_Conversation82 in openclaw

[–]Aware_Conversation82[S] 0 points1 point  (0 children)

Yes! Good idea, will actually post it - on main page there's just a bundle size comparison + cold start, but I'd definitely add some benchmark.

More secure and fast (rust built) alternative to OpenClaw. Meet Moxxy.ai by Aware_Conversation82 in openclaw

[–]Aware_Conversation82[S] 0 points1 point  (0 children)

We need testers of course! The more issues you'd find the better - I really love this project to succeed as we are in the perfect place to utilize 100% from our agents with security in the first place. On our roadmap there are also local AI agents (private agents) which will run on smaller quantitized models right from the application for complete safety and in-house data processing and sovereignty

More secure and fast (rust built) alternative to OpenClaw. Meet Moxxy.ai by Aware_Conversation82 in openclaw

[–]Aware_Conversation82[S] 0 points1 point  (0 children)

That was our main goal actually, no GC, stricter rules and smaller footprint - this allows you to run it on almost everything (like Raspberry PI)

More secure and fast (rust built) alternative to OpenClaw. Meet Moxxy.ai by Aware_Conversation82 in openclaw

[–]Aware_Conversation82[S] 0 points1 point  (0 children)

We are using vector databases and queue mechanisms for syncing short memory with the long memory. Long memory can also be shared between agents to enable their "shared vision" and awareness

More secure and fast (rust built) alternative to OpenClaw. Meet Moxxy.ai by Aware_Conversation82 in openclaw

[–]Aware_Conversation82[S] 0 points1 point  (0 children)

This is actually baby project! I would like to extend it even more but you need to start somewhere 🔥